How PDPM margin is modeled for SNF admissions.
A plain-language explainer on what the Patient-Driven Payment Model is, how margin is modeled from case-mix classification and cost of care, and what drives it. AdmitScore™ keeps this as an administrator-only planning estimate inside referral review; it does not guarantee a financial result.
What PDPM is.
The Patient-Driven Payment Model (PDPM) is how Medicare classifies a covered Part A skilled nursing stay for payment; Medicare Advantage plans may reference PDPM-informed rates, but terms vary by contract. Instead of paying primarily on therapy volume, PDPM builds a per-diem rate from a resident's clinical characteristics, grouped into separate case-mix components plus a non-case-mix portion. The formal classification is set by the MDS assessment after admission — referral documentation only previews it, so a pre-admission estimate is a starting point to verify, not a determination.
Case-mix components
PDPM scores physical therapy, occupational therapy, speech-language pathology, nursing, and non-therapy ancillary needs as distinct components, each tied to different clinical and diagnostic details.
Documentation drives classification
Diagnoses, comorbidities, functional status, and clinical notes determine how each component classifies. Missing or unclear source support can change where a stay lands.
The rate can shift over a stay
Some components are designed to change across the length of stay rather than stay flat, so timing and expected duration are part of any honest model.
It is a payment model, not a result
PDPM describes how a stay is classified for payment. It does not, by itself, tell you what a specific stay will cost to deliver or what it will net.
- Model the revenue side from the case-mix classification the documentation supports.
- Model the cost side: staffing, therapy, medications, supplies, and expected length of stay.
- Treat the difference as an estimated margin, clearly labeled as a planning aid.
- Verify the documentation behind both sides before relying on the estimate.
Margin is modeled revenue minus modeled cost, and both sides are estimates.
A margin model does not observe a result. It compares two projections. The revenue projection follows the per-diem a stay is modeled to classify into under PDPM. The cost projection reflects what delivering that care is expected to require. Because each side depends on documentation and assumptions, the model is only as trustworthy as its inputs, which is why every figure should be reviewed against source records.
- Signals page: PDPM admissions signals
- Core page: SNF admissions software
- Functional context: MDS Section GG guide
What drives PDPM margin.
Margin moves when either the modeled revenue or the modeled cost of a stay moves. On the revenue side, that traces back to how well the documentation supports case-mix classification. On the cost side, it traces back to what the stay actually requires to deliver. None of this is a guaranteed outcome; it is context a team can review before a decision. To model a single admission with your own per-diem, stay length, and costs, use the in-browser PDPM margin calculator.
Clinical complexity and comorbidities
Conditions that inform the non-therapy ancillary and nursing components can change how a stay classifies when they are documented and supported.
Therapy and functional need
Therapy support and functional status, including Section GG context, feed the therapy components and shape both the model and the plan of care.
High-cost medications and supplies
Expensive medications, wound care, isolation, and equipment sit on the cost side of the model and are worth surfacing during packet review.
Length and timing of the stay
Because parts of the per-diem are designed to change over a stay, expected duration and timing affect the modeled revenue as well as accumulated cost.
Margin stays an administrator-only planning estimate inside admissions review.
AdmitScore does not turn PDPM into a standalone reimbursement product. It keeps modeled margin as one administrator-only planning signal alongside financial-free Referral Fit, so clinical users stay focused on care fit while administrators see planning context. Staff verify the documentation behind every estimate and make the final admission decision. Revenue, PDPM, and margin outputs are estimates and do not guarantee payer reimbursement.
What is PDPM margin?
A planning concept: the difference between the per-diem reimbursement a facility is modeled to receive under PDPM for a stay and the modeled cost of delivering care for that stay. It is an estimate for review, not a guaranteed financial result.
How is PDPM margin modeled?
By estimating the per-diem revenue built from a resident's case-mix classification across PDPM's components, then comparing it against the modeled cost of care, including staffing, therapy, medications, and supplies, over the expected length of stay. Both sides depend on documentation that must be verified.
What drives PDPM margin?
The clinical complexity and documentation that support case-mix classification, such as nursing acuity, comorbidities that inform the non-therapy ancillary component, therapy needs, and functional status, alongside cost drivers like high-cost medications, supplies, and the length of the stay.
Does AdmitScore guarantee a margin result?
No. AdmitScore surfaces margin as an administrator-only planning estimate for review. Facility staff verify the underlying documentation and make the final admission decision, and no output guarantees payer reimbursement.