SNF Discharge Function Score: Validate Observed and Expected Results

Find the exact measure and model

A report labeled “function” might show a raw assessment item, an admission-to-discharge change, a local therapy outcome or the official Discharge Function Score. Begin with the CMS measure identity, reporting period, eligible-stay definition and model version.

The SNF QRP Measure Calculations and Reporting User's Manual v8.0, effective October 1, 2026, describes the measure in Section 7.6 and Table 8-8. The accompanying risk-adjustment and imputation files supply the relevant coefficients and logic. Preserve the applicable files with the analysis; a newer download does not automatically apply to an older report period.

Review three layers before the percentage

First confirm which stays belong in the target population and which meet the specified exclusions. Use a stay-level reconciliation, because a resident can have more than one included stay. Record excluded stays with the governing reason instead of quietly dropping them.

Next verify the observed discharge score. CMS combines specified function items and applies its imputation procedure to specified not-attempted, dashed, skipped or missing responses. Scores range from 10 to 60. An exported item sum that replaces those responses with zero can differ materially from the official value. Imputation is part of measure calculation; it is not permission to write a modeled value back into the resident's assessment as an observation.

Then verify the expected score using the applicable model intercept, coefficients and resident-level inputs. The manual caps an expected score above 60 at 60. It specifies coefficient precision and reporting rounding. Keep full calculation precision until the required step; rounding a near-boundary value prematurely can reverse whether a stay meets expectation.

A five-stay reconciliation

These fictional scores are assumed to have been generated correctly under the applicable model. They illustrate the final comparison, not clinical assessment coding or an independent model implementation.

Three of four eligible stays meet or exceed expectation: 3 ÷ 4 × 100 = 75 percent. Counting the excluded stay produces 60 percent and answers the wrong question. Averaging the four observed scores also answers a different question, even if it is useful for another local analysis.

Suppose the dashboard shows 50 percent. The reviewer discovers that it classified Stay C as a failure because its comparison used “greater than” instead of “greater than or equal to.” Correcting that comparison restores 75 percent in the synthetic test. A real discrepancy still needs verification against the full source data and applicable CMS report.

Investigate unexpected movement without changing clinical facts

A changed result can come from a different cohort, a corrected assessment, a new model version, an imputed value or a genuine difference in observed function. Keep those explanations separate. Staff should never alter a supported assessment response to achieve the model's expected score.

The expected value is a reporting estimate derived from the specified population model. It does not establish what a particular resident must achieve, which treatment to provide or whether a discharge is appropriate. Qualified clinicians and the resident determine care goals using the clinical assessment and preferences.

A useful software acceptance case includes an equality boundary, an excluded stay, an imputed item and an expected score subject to the cap. Retain both source and calculated values with their provenance. The completed review should explain the percentage and its limitations before anyone turns it into a quality initiative or a performance claim.