Live demos: no login required HIPAA-aligned · BAA on every account Austin, TX · Built for skilled nursing operators
(405) 383-5214

PDPM Case-Mix Review: A Monthly Routine for Administrators

How administrators can run a monthly PDPM review that connects MDS coding, documentation and billing without turning it into a compliance scramble.

3 min readBy CarePulse Analytics Team

Since PDPM replaced the prior payment model, skilled nursing reimbursement has depended heavily on how accurately a resident's clinical picture is captured on the MDS 3.0. That makes the MDS a financial document as well as a clinical one. Administrators who treat case-mix as a monthly operational review, rather than a once-a-quarter worry, tend to catch problems while they are still small.

The aim of this routine is accuracy. Reimbursement should reflect the care residents actually need and receive, documented fully and correctly, no more and no less.

What a monthly review is for

A good PDPM review answers four questions:

  1. Are assessments being completed on time?
  2. Does the coding reflect what the clinical record supports?
  3. Is the building's case-mix pattern changing, and if so, does the admission mix explain it?
  4. Are there process gaps, such as late diagnoses capture or missed items, that show up repeatedly?

None of these require a consultant. They require a consistent view of data you already have in your EHR and billing system.

The monthly agenda

1. Assessment timeliness

Start with a list of assessments due, completed, and overdue. Late or missed assessments can affect payment and compliance, so the overdue list deserves attention before any other metric. Assign each overdue item an owner and a date.

2. Admission-to-first-assessment flow

Look at how many days pass between admission and the first assessment, and whether admission information, such as hospital diagnoses and procedures, reached the MDS coordinator in time. Delays here often trace back to missing records from the referring hospital rather than anything in the building.

3. Case-mix trend by payer type

Track average case-mix indexes over several months for your Medicare Part A population. Do not react to a single month. Ask whether a change lines up with a change in admissions, such as a new referral relationship or a shift toward a different kind of patient. A lower or higher index is neither good nor bad on its own; it is a prompt to understand why.

4. Component-level view

PDPM breaks payment into components, including physical therapy, occupational therapy, speech-language pathology, nursing, and non-therapy ancillary. Reviewing each component separately shows where changes occur. For example, if the nursing component moves while therapy stays flat, the conversation is about clinical complexity capture, not therapy delivery.

5. Documentation support

For any area where coding changed notably, a clinical leader should confirm that the record supports it. This is the quality control step. It protects residents' care plans, supports accurate payment, and reduces audit exposure.

Questions to ask each month

  • Which diagnoses are most common among new admissions, and are they being captured consistently on the first assessment?
  • Are there residents whose condition has changed and whose assessment has not yet reflected it?
  • Are therapy and nursing teams reading the same data when they talk about a resident's needs?
  • Where do we see variation between MDS staff or between buildings that cannot be explained by residents?

Avoid common pitfalls

  • Chasing the number. Case-mix is an outcome of care and documentation, not a target. Managing to a number invites errors and risk.
  • Reviewing only when something goes wrong. A steady cadence reveals drift; a crisis review only reveals the crisis.
  • Keeping MDS data in a silo. Billing, clinical, and administration should see the same view.
  • Ignoring front-end data. Referral information quality affects first-assessment accuracy.

Making it visible

A dashboard that places assessment status, case-mix trend by component, and billing outcomes side by side lets one meeting replace three. For multi-facility groups, the same view across buildings highlights where a practice from one location might help another. The conversation shifts from "why is this different?" to "what does the strongest building do?"

Keep language careful when sharing it. Variation between buildings is a question, not a verdict, because resident populations differ.

Bringing it together

Monthly PDPM review is about steady attention to accuracy, timeliness, and shared understanding. When the data is visible and current, administrators can focus on supporting the clinical team and spend less time reconstructing what happened.

CarePulse Analytics can build this kind of view from your EHR and billing data, and a demo is a straightforward way to see your own assessment and case-mix numbers in one place.