Under the Patient Driven Payment Model, the MDS is not just a clinical assessment. It is the document that determines how a stay is classified and paid. That makes the quality and timing of MDS data an operational and financial concern, not only a compliance task.
The good news is that many of the common problems are visible in data you already have, if you look at them regularly. This post covers a practical set of checks that help a building protect accurate reimbursement without adding burden to the clinical team.
Why data quality is a financial issue
PDPM classifies stays using components such as nursing, therapy, non-therapy ancillary and a non-case-mix component, with clinical characteristics captured on the MDS driving much of the classification. When an item is missing, late, inconsistent or not supported by the record, the effect can be an inaccurate classification, a payment that does not reflect the resident's documented needs, or rework after the fact.
None of that requires bad intent. It usually comes from busy teams, hand-offs between departments and the sheer number of items on an assessment. That is exactly where analytics helps: making the pattern visible so the process can be improved.
Checks that pay off
Assessment timing
Track whether assessments are completed and submitted within expected windows. A simple weekly view of upcoming assessment reference dates, assessments in progress and assessments awaiting submission gives the MDS coordinator a clear queue. Late or missed assessments should surface as exceptions rather than discoveries.
Completion and consistency
Look for items left blank or inconsistent with related items. A resident coded in one area in a way that conflicts with another section is a prompt to look more closely at the documentation. A short list of such flags, reviewed weekly, can prevent bigger problems later.
Diagnosis and documentation alignment
Classification depends in part on diagnoses captured in the record. Comparing what appears on the MDS with what is documented in the electronic health record is a collaborative task between the MDS team, nursing and the clinicians who document. The role of analytics is to flag where the sources do not line up, so the team can review them. Clinical judgment stays with clinicians.
Interrupted stays and transitions
Admissions, discharges and return-to-facility events add complexity. Visibility into stays that cross assessment boundaries helps the team avoid missed or duplicated assessments.
A weekly rhythm for the MDS team
Consider a short weekly meeting, perhaps fifteen to twenty minutes, with the MDS coordinator, the DON and someone from business office or finance. A simple agenda:
- Upcoming assessments: What is due this week and who has what?
- Exceptions: Which assessments are late, incomplete or flagged for inconsistency?
- Hand-off issues: Where did information fail to reach the MDS team in time?
- Payment view: How does the case-mix picture for current residents compare with what the building expected?
Over time the exceptions list tells you where the process breaks down. If the same hand-off causes the same problem each month, fix the hand-off.
Reading the case-mix picture
Looking at the distribution of classifications across residents, and how it shifts over time, can be informative. A hypothetical building might notice that its mix has moved noticeably after a change in admission sources, or that a unit's pattern differs from what its resident population would lead you to expect. These are questions to investigate, not conclusions. The investigation itself is often the value, because it prompts a review of documentation and processes.
Mistakes to avoid
- Treating MDS as only the MDS coordinator's job. Accurate assessments depend on input from nursing, therapy, dietary, social services and others.
- Optimizing for payment rather than accuracy. The aim is to reflect residents' documented needs correctly. Accuracy protects both residents and the organization.
- Waiting for audits to find problems. Internal review on a regular schedule is far less stressful than external review.
- Relying on memory. A tracked queue beats a mental list every time.
Making it visible
CarePulse can pull assessment timing and related data from PointClickCare and other systems into a single view, with exceptions flagged for the weekly review. If you would like to see how your own assessment queue and case-mix trend might look, a demo with your data is a good place to start.