Texas Medicaid PDPM LTC: Validate the Rate Group and Effective-Date Bridge

A Texas nursing facility needs to connect three different facts: the accepted assessment-based classification, the rate applicable to that classification, and the service dates on the payment. A label saying “PDPM” is not enough to establish that the correct state calculation was used.

HHSC’s methodology page identifies the September 1, 2025 transition. The approved State Plan Amendment 25-0028 was approved July 28, 2026 with that earlier effective date. Store approval date and payment effective date separately.

Understand the state structure

Texas combines six nursing categories, three non-therapy ancillary categories and two cognitive classifications: 6 × 3 × 2 = 36 combinations. The approved text separately describes default groups when assessment information is unavailable or invalid.

The total rate has seven components: nursing, NTA, cognitive, dietary, operations, administration and fixed capital assets. Nursing and NTA use case-mix adjustment. This structure does not import the full Medicare therapy-component or stay-day payment calculation.

The operational task is to verify the state result, not recreate clinical classification from a few diagnoses. Retain the accepted assessment identifier, effective interval, state group result and rate-table version. If a group is in default status, open an assessment-data exception rather than assuming it is the resident’s final supported classification.

Build a three-resident rate bridge

The following October example uses invented group labels and per diems. It intentionally avoids a clinical coding table. Assume all listed days are otherwise payable and that state records establish the classifications and effective dates shown.

The current supported total is $17,870. Suppose B was paid 31 days at $190, or $5,890. Its supported split totals $6,400, leaving a $510 difference. The correct variance is 17 × ($220 − $190); changing the entire month to $220 would overstate the amount by $420.

C’s team expects a possible supported rate of $200 after the state record is corrected. That produces a $1,240 sensitivity for 31 days, but it remains a separate unresolved scenario. It is not added to the $17,870 supported expectation or treated as an approved receivable merely because the facility believes the default will change.

Resolve the cause before requesting an adjustment

For B, compare the accepted effective date with the claim and remittance intervals. If the state record is correct but the claim used the old group, route the claim correction through the applicable payer process. If the assessment change is only in a local work queue, resolve acceptance first. If the payer used a different published rate version, preserve both versions and the service dates in the inquiry.

For C, record the reason for default, missing or invalid data, responsible assessment owner and next state response. A finance employee should not manufacture a classification or change clinical documentation to reach the modeled $200.

Reconcile special add-ons separately where applicable. The base group comparison cannot prove eligibility for an additional payment, and a rate effective on one date should not automatically be extended backward.

Use the bridge as a purchasing test

Ask a prospective platform team to reproduce A’s stable month, B’s mid-month split and C’s unresolved default. The reviewer should see the evidence supporting each interval and a separate sensitivity for an unapproved correction. Then replace the rate table with a later revision and identify only the affected rows.

A successful demonstration produces a traceable rate-and-date reconciliation with an actionable owner for each exception. It does not turn a potential assessment correction into promised revenue or claim that all Texas payment arrangements use identical submission routes.