MDS and Medicaid Reimbursement: What SNF Teams Must Verify Before Assuming PDPM Drives the Rate

For skilled nursing facilities, MDS accuracy can affect compliance, resident assessment, care planning, quality reporting, Medicare payment, and, depending on the state, Medicaid reimbursement.

The important qualification is “depending on the state.”

Medicare replaced RUG-IV with the Patient-Driven Payment Model, or PDPM, in October 2019. Medicaid nursing-facility reimbursement, however, remains state-specific. Some states use PDPM-based approaches. Some use the PDPM nursing component only. Some use MDS information in a different case-mix methodology. Others rely more heavily on cost-based, price-based, acuity-adjusted, or blended payment systems.

For MDS coordinators, directors of nursing, administrators, business office directors, and CFOs, the operational question is not simply:

Are we good at PDPM?

It is:

Which assessment data and payment rules actually determine our state Medicaid rate, and do our MDS, clinical, and billing workflows support them?

Key Takeaway: Medicare PDPM knowledge does not automatically protect Medicaid reimbursement. SNFs must confirm the specific Medicaid payment methodology, MDS inputs, assessment schedule, and case-mix components used in the states where they operate.

Medicare PDPM and Medicaid payment are different

PDPM is Medicare’s case-mix classification methodology for covered SNF Part A stays. It replaced RUG-IV for Medicare on October 1, 2019.

Under PDPM, Medicare payment is calculated through five case-mix-adjusted components:

• Physical therapy
• Occupational therapy
• Speech-language pathology
• Nursing
• Non-therapy ancillary, or NTA

The PT, OT, SLP, nursing, and NTA components are calculated using different MDS items and clinical information. The resulting classifications help determine payment for Medicare Part A SNF stays.

CMS provides the current MDS 3.0 Resident Assessment Instrument Manual and related assessment materials through its MDS 3.0 RAI Manual resource center.

Medicaid payment is different.

Each state determines its Medicaid nursing-facility payment methodology, within federal Medicaid requirements. A state may use:

• PDPM-based case-mix classification
• The PDPM nursing component only
• MDS data within a state-developed case-mix process
• Resource Utilization Group, or RUG, information collected through a state-specific approach
• Cost-based or price-based methodology
• Peer-group, geographic, staffing, or quality adjustments
• A blended payment method using more than one factor
• Managed-care contract rates that differ from state fee-for-service payment

That is why “PDPM Medicaid reimbursement” is not a universal national model.

A facility should never assume that the MDS items with the greatest impact on Medicare PDPM necessarily have the same impact on Medicaid payment.

Why states are changing their approaches

CMS phased out routine support for RUG-III and RUG-IV classification through federally required MDS assessments.

CMS previously explained that states relying on RUG-III or RUG-IV for Medicaid case-mix payment would need a new approach after the necessary legacy assessment data and federal support were removed. CMS created an Optional State Assessment, or OSA, to help states manage the transition, but the OSA was a temporary bridge—not a permanent national Medicaid reimbursement solution. Read CMS’s Nursing Facility Case-Mix Payment Changes guidance.

CMS later ended support for RUG-III and RUG-IV groupers through the OSA after September 30, 2025. States that previously depended on RUG-based Medicaid classification had to adopt another process for gathering and using payment-relevant data.

That does not mean every state chose full PDPM.

A state can use PDPM, use part of PDPM, create a state-specific acuity method, retain a different payment approach, or combine MDS assessment information with cost, quality, peer-group, or other rate factors.

For multi-state SNF operators, the practical implication is clear:

Build a state-by-state Medicaid payment map. Do not manage Medicaid case mix from a Medicare PDPM assumption.

A current example: Connecticut’s PDPM nursing-only model

Connecticut provides a useful example of how state Medicaid adoption can differ from Medicare PDPM.

Effective July 1, 2026, Connecticut’s Medicaid nursing-facility acuity-based reimbursement methodology uses the PDPM nursing-only component to calculate nursing-home case-mix index scores. Those scores are used for quarterly case-mix adjustments to the direct-care component of the Medicaid per diem rate. Read Connecticut’s Medicaid nursing-facility reimbursement notice.

Connecticut’s transition is phased in over three years, from state fiscal year 2027 through state fiscal year 2029, with stop-gain and stop-loss provisions intended to limit abrupt facility rate changes.

The Connecticut example demonstrates three important points:

• A state may use PDPM for Medicaid.
• A state may use only one PDPM component rather than the full Medicare five-component model.
• The financial impact may be phased in and applied only to a specific rate component.

A facility that focuses only on Medicare therapy and NTA classification may miss the Medicaid payment inputs that matter most in a nursing-only state model.

Start with a state Medicaid payment map

Before changing MDS review workflows, create a current map of the payment methodology in each state where your SNF operates.

This map should be updated when the state issues a new rate letter, provider bulletin, state plan amendment, budget change, MCO payment notice, or case-mix methodology update.

Which MDS information matters under PDPM

For Medicare Part A PDPM classification, different components rely on different categories of clinical and assessment data.

The exact item logic, coding instructions, and classification process are contained in the current CMS MDS 3.0 RAI Manual. Facilities should use the current manual and applicable CMS technical resources rather than relying on informal summaries.

At a high level:

Section GG functional information can matter across multiple PDPM components. But its relevance to Medicaid depends entirely on whether and how the state uses PDPM or MDS-derived functional data in its own payment method.

Similarly, diagnosis and clinical-condition documentation must be accurate and supported. A diagnosis should not be included merely because it appeared on a prior record; it must meet applicable coding and assessment requirements.

The right goal: defensible accuracy

The goal is not to increase a resident’s payment classification.

The goal is to ensure that:

• MDS data accurately reflect the resident’s assessed condition
• Clinical documentation supports the assessment
• Physician, nursing, therapy, and care-plan documentation are internally consistent
• Payment-relevant information is not omitted
• Unsupported or outdated information is not carried forward
• The facility can explain the relationship between the assessment, the resident’s condition, and the payment method used

That protects the facility from both underpayment and compliance risk.

Build an MDS-to-reimbursement workflow

MDS accuracy cannot sit entirely with the MDS coordinator.

For facilities where MDS information affects Medicaid payment, the process should connect clinical documentation, assessment completion, billing, finance, and payment reconciliation.

1. Review new admissions early

For each new Medicaid or Medicaid-pending admission, establish:

• Payer source and anticipated Medicaid pathway
• State Medicaid payment methodology
• Required MDS or state assessment timeline
• Relevant rate-effective dates
• Supporting documentation sources
• Current diagnoses and clinical conditions
• Functional status documentation
• Care plan and nursing documentation
• Any required authorization, LOC, PASRR, or waiver documentation
• Owner for billing setup and rate reconciliation

The purpose is not to perform payment-driven assessment. It is to make sure that the records needed for an accurate, supportable assessment are available before the assessment reference date.

2. Reconcile assessment and clinical records

Before finalizing a payment-relevant assessment, check consistency across:

• Nursing assessments and progress notes
• ADL and functional documentation
• Therapy evaluations and treatment records
• Physician orders and diagnoses
• Medication and treatment records
• Restorative nursing documentation
• Cognitive, behavioral, and mood documentation
• Care plan
• Hospital transfer or discharge information
• Prior assessment history, where clinically relevant

This is particularly important when a state uses the nursing component or functional status in its Medicaid case-mix process.

3. Track state-specific assessment timing

A facility must distinguish among:

• Federally required OBRA assessments
• Medicare Part A PPS assessments
• State Medicaid assessments
• State-required Optional State Assessments or replacement processes, if applicable
• Change-in-condition assessments
• Quarterly, annual, or other recurring assessments
• State-specific picture dates and rate-setting cycles

One assessment schedule should not be assumed to replace another.

4. Reconcile expected and paid rates

After a rate is applied, finance and billing should compare expected and paid amounts.

Track:

The IPA: important for Medicare, not a default Medicaid lever

The Interim Payment Assessment, or IPA, is a Medicare SNF PPS assessment used under PDPM.

An IPA may be completed when a Medicare Part A resident experiences a clinical change that would change the resident’s PDPM classification and payment. CMS designed the IPA as an optional assessment; it is not a required assessment for every change in condition. Read CMS archived MDS assessment materials.

The crucial distinction is this:

An IPA does not automatically change a state Medicaid rate.

Whether a Medicaid program recognizes an IPA, uses the related MDS data, requires another state assessment, or recalculates its payment based on a change in condition depends on the state’s Medicaid methodology.

For Medicare Part A, a facility may consider an IPA when a resident’s clinical status changes in a way that affects PDPM classification. Examples can include significant changes in clinical status, functional needs, nursing characteristics, or NTA-related conditions, subject to current CMS assessment rules.

For Medicaid, the facility should verify:

• Whether the state uses PDPM or a PDPM component
• Whether the state recognizes IPA-related information
• Whether the state requires an OBRA assessment, state-specific assessment, or other process
• Whether the change affects current or future case-mix classification
• Whether the rate update occurs immediately, quarterly, at a picture date, or under another schedule
• Whether an MCO contract uses the state methodology or a separate rate structure

Build a change-of-condition review

A practical workflow is to flag significant clinical changes for both care-planning and payment-review purposes.

For each material change in condition, the team should ask:

• Does this require an updated care plan?
• Does this trigger a required MDS or state assessment?
• Does it affect Medicare PDPM classification?
• Does it affect the state Medicaid case-mix methodology?
• Does it require an authorization, Level of Care, or payer notification?
• Does it affect the resident’s billing category, service level, or rate?
• Who is responsible for confirming the payment impact?

This avoids two opposite errors:

• Missing a valid Medicare or Medicaid reassessment opportunity
• Completing or treating an assessment as payment-changing when the relevant payer methodology does not support that assumption

Three common MDS and Medicaid payment mistakes

The examples below are illustrative and not client case studies, coding advice, or legal advice.

A facility applied Medicare PDPM logic to Medicaid

An SNF had strong Medicare PDPM processes and assumed the same documentation priorities determined Medicaid payment.

The state’s Medicaid method used a narrower case-mix approach focused on different assessment inputs. Staff spent significant time reviewing Medicare-relevant components that did not affect the Medicaid rate while missing state-specific rate indicators.

What failed: The facility did not confirm its state Medicaid methodology.

Better control: Maintain a current state payment map and identify exactly which assessments, components, and data elements affect Medicaid reimbursement.

An MDS change did not produce the expected Medicaid rate update

A resident’s condition changed and the MDS coordinator completed the appropriate assessment process. The business office expected the Medicaid rate to change immediately.

The state’s methodology updated case mix only on a quarterly cycle, and a phase-in provision limited the immediate payment impact.

What failed: The team assumed that an assessment change automatically resulted in an immediate full-rate change.

Better control: Track the state’s rate-effective dates, picture dates, transition rules, and payment cycle alongside the clinical assessment schedule.

An underpayment was not identified

A facility had accurate resident assessment data, but no one reconciled the expected Medicaid rate against the remittance advice after a state rate update.

The issue was found months later during a broader AR review.

What failed: The organization treated MDS completion as the end of the reimbursement process.

Better control: Add expected-versus-paid rate reconciliation to the monthly billing and finance workflow.

How LTCPro supports MDS and Medicaid rate accuracy

LTCPro supports U.S. skilled nursing facilities with revenue-cycle, billing, accounts-receivable, prior-authorization, and financial workflow services.

For SNFs where MDS and state assessment data may affect Medicaid reimbursement, LTCPro can help organize the operational controls that connect clinical records, payer requirements, billing, and payment reconciliation.

Depending on the facility’s state, payer mix, systems, contracts, and available records, support may include:

• Organizing state-specific Medicaid rate and assessment information
• Tracking payment-effective dates, rate notices, and payer updates
• Building worklists for assessment-related billing controls
• Supporting authorization, eligibility, and claims readiness
• Reconciling expected payments against remittance activity
• Identifying underpayment, adjustment, denial, and payment-variance patterns
• Improving coordination between MDS, nursing, admissions, billing, AR, and finance teams
• Creating finance-ready reports that show payment changes, AR risk, and unresolved variances
• Accounting for newer care delivery models, like virtual nursing programs, where documentation and billing patterns may still be evolving

LTCPro does not complete MDS assessments, determine clinical coding, make resident classification decisions, establish state Medicaid payment policy, provide legal advice, or guarantee reimbursement outcomes.

Final assessment, coding, clinical, payer, and regulatory decisions should remain with qualified clinical leaders, MDS professionals, state Medicaid agencies, MCOs, reimbursement advisors, and legal counsel.

LTCPro’s role is to help facilities establish the documentation, billing, reconciliation, and workflow controls needed to ensure that valid payment information is visible, actionable, and followed through to collection.

FAQ

Does PDPM apply to Medicaid nursing-facility reimbursement?

PDPM applies nationally to Medicare SNF Part A payment. Medicaid nursing-facility reimbursement is determined by each state. Some states use PDPM-based methods, some use only the PDPM nursing component, and some use different methodologies. Confirm the payment method in your specific state.

Does MDS accuracy affect Medicaid reimbursement?

It can. If a state uses MDS information, case-mix classification, functional information, or PDPM-derived elements in its Medicaid payment method, MDS accuracy can affect reimbursement. The exact impact depends on the state methodology and payer arrangement.

Do all states use the full five-component PDPM model for Medicaid?

No. States may use a different methodology or only selected PDPM components. Connecticut, for example, uses the PDPM nursing-only component for its Medicaid nursing-facility case-mix index beginning July 1, 2026. Read Connecticut’s reimbursement notice.

Which MDS items matter most for PDPM?

The answer depends on the PDPM component. Functional status, clinical category, cognitive status, nursing characteristics, selected comorbidities, and extensive services can all be relevant. Refer to the current CMS MDS 3.0 RAI Manual for specific item instructions and classification requirements.

Does Section GG affect Medicaid reimbursement?

Possibly, but not universally. Section GG can affect Medicare PDPM classification and may be relevant in state Medicaid methodologies that use PDPM or MDS-derived functional data. Confirm how your state uses Section GG before treating it as a Medicaid rate driver.

What is an Interim Payment Assessment?

An IPA is an optional Medicare SNF PPS assessment used under PDPM when a clinical change affects Medicare payment classification. It does not automatically change Medicaid reimbursement. Whether it affects Medicaid depends on the state’s payment methodology. See CMS MDS assessment resources.

How should an SNF verify Medicaid rate accuracy?

Confirm the state payment methodology, rate-effective date, applicable assessment or picture date, case-mix factor where relevant, phase-in rules, payer assignment, MCO contract terms, and remittance payment. Then compare expected reimbursement with actual payment at the resident and service-date level.

Key takeaways

• PDPM is Medicare’s SNF Part A payment model. Medicaid nursing-facility reimbursement remains state-specific.
• CMS ended routine support for RUG-III and RUG-IV classification through federal MDS processes, requiring states that used RUG-based Medicaid methods to adopt another approach. Read CMS guidance.
• Do not assume every state uses the full Medicare PDPM model. Some states use selected components, such as the nursing-only model adopted by Connecticut effective July 1, 2026. Read Connecticut’s Medicaid reimbursement notice.
• MDS accuracy should be clinically supportable and aligned with the state methodology—not optimized around generic payment assumptions.
• An IPA is a Medicare PDPM tool. It may matter for Medicare Part A but does not automatically affect Medicaid rates.
• Strong Medicaid reimbursement controls connect clinical documentation, MDS processes, state payment rules, billing, remittance reconciliation, underpayment recovery, and finance reporting.