Ohio Medicaid PDPM Phase-In: Reconcile the Direct Care Rate Across Transition Dates

Ohio’s transition creates a practical reconciliation problem: the facility can have a correct case-mix result and an incorrect budget because the wrong fraction, baseline or effective date was used. Finance needs a direct-care rate bridge before it attributes a payment difference to occupancy or coding.

The Ohio Medicaid September 12, 2025 fact sheet describes nursing-only federal fiscal year 2024 weights, a peer-group multiplier and the transition schedule. The current state rate index lists facility rate files for January and July 2026. Match the applicable published revision to the facility and service period.

Keep three inputs independent

The bridge needs the January 1, 2025 direct-care baseline, the current PDPM direct-care result and the applicable phase-in fraction. The peer-group multiplier aligns the RUG and PDPM case-mix scales; it is not the same thing as the transition fraction. Avoid applying either adjustment twice.

Retain the peer-group assignment, underlying case-mix period, weight version, multiplier and rate-file publication date. Medicare’s total PDPM per diem cannot replace Ohio’s direct-care component. The remaining Medicaid rate components need their own reconciliation.

Work the four transition dates

Assume a fictional baseline direct-care rate of $150 and a current PDPM direct-care result of $180. Hold that modeled result and a 1,000-day census constant to isolate the transition effect. These are invented amounts, not Ohio published rates.

The model is baseline + fraction × (current PDPM result − baseline). It is not baseline multiplied by one-third or two-thirds. As of November 10, 2026, the last two rows are future scheduled stages, not completed payment results.

Now change only the current PDPM result to $135. The difference is negative $15. The same schedule produces $145, $140, $140 and $135. The transition can cushion a decrease as well as phase in an increase.

Separate a rate revision from the transition

Suppose the July modeled result is corrected from $180 to $186, while the baseline remains $150. At two-thirds, the corrected direct-care rate is $174. The change from the prior $170 is $4, yielding a $4,000 difference for 1,000 applicable days. Applying the entire $6 modeled correction would overstate that bridge by $2,000.

The working record should identify which days were paid at the old rate and whether the state has instructed a reprocessing or adjustment route. A spreadsheet variance alone does not authorize a new claim. Preserve both rate versions so staff can distinguish a revised rate from a payment-posting error.

If actual days are 950 rather than 1,000, compute the volume effect separately. At the corrected $174, the 50-day difference is $8,700. Combining it with the $4,000 rate correction would make a single unexplained monthly variance harder to resolve.

Complete the rate-control handoff

A useful exception record contains facility, service dates, component, baseline, modeled current rate, fraction, expected amount, paid amount and the exact supporting publication. Assign case-mix questions to the assessment owner and rate-file or payment questions to finance. Do not ask either team to change a source value merely to make the totals agree.

In a platform review, use the positive and negative examples, then introduce the July correction. Require separate outputs for component rate, total payment and affected service days. This tests whether the system can preserve Ohio’s transition logic through revisions, rather than merely display a generic PDPM estimate.