SNF QRP Completeness: Reconcile the Provider Threshold Report Before the Deadline

Start with the report year, not the upload count

A QAPI director receives two reassuring numbers: all files transmitted successfully, and the local dashboard shows few missing fields. Neither establishes SNF QRP completeness. The CMS quick reference guide defines the assessment threshold using complete qualifying assessments divided by successfully submitted qualifying assessments. One required missing element can keep an assessment out of the numerator.

For FY 2026 onward, 42 CFR 413.360(f) requires at least 90 percent of submitted assessments to contain 100 percent of the required MDS data. This guide addresses that assessment calculation. The regulation also establishes distinct NHSN and selected-chart requirements; a favorable assessment result cannot offset a failure in another applicable requirement.

Save the Provider Threshold Report with its requested fiscal year, generation time and reporting periods. Pair it with the matching annual-payment-update data-element table from the CMS technical information page. The fiscal year of the payment update and the calendar year of collection differ. A table downloaded today may govern a future collection period.

Reconcile assessment units before calculating a percentage

CMS's April 2026 quick reference guide says the current denominator includes accepted Medicare 5-Day and PPS Discharge assessments before the submission deadline. A combined 5-Day/PPS Discharge assessment counts as two assessment units. Counting files or distinct residents can therefore give a different answer from counting the units CMS uses.

The following fictional reconciliation assumes the MDS lead has already confirmed the applicable assessment population and completeness status. It does not assign item responses.

The initial result is 88 ÷ 100 = 88 percent. It is not 88 ÷ 92. The four unaccepted units still require investigation even though they are outside this accepted-data denominator.

Suppose qualified review supports corrections to three counted units and those corrections are accepted before the applicable deadline. The result becomes 91 ÷ 100 = 91 percent. If all four outstanding units are then properly completed and accepted, the result becomes 95 ÷ 104, approximately 91.35 percent. A changing denominator explains why the final rerun matters.

Investigate the failed element, not just the warning count

Create an exception record for each affected assessment unit: assessment identity, reporting period, required element, validation message, supporting-document location, qualified review decision and accepted replacement identity. Distinguish a missing source from an unavailable source and from a response that is correct under the instructions. Those situations require different action.

CMS identifies validation messages 3897 and 3908 as examples related to missing required QRP data. A warning is an investigation cue; staff should not populate a field merely to clear it. Preserve the original submission and the rationale for a supported correction. Route an unresolved coding question to the appropriate qualified assessment resource.

Use the deadline for this collection period

The FY 2028 deadline table lists November 16, 2026 for April–June 2026 assessment data. A November 14 preview-review deadline concerns a different process. Beginning with calendar-year 2027 collection for FY 2029, the finalized assessment submission schedule becomes the 15th day of the second month after the quarter, subject to the published adjustment rules. Use the current CMS deadline table, rather than carrying an old calendar forward.

The final review packet should retain the report before correction, assessment-unit reconciliation, accepted correction evidence and a refreshed threshold result. Identify any unresolved required submissions even when the displayed percentage exceeds 90 percent.

For a platform buyer, the essential capability to evaluate is a traceable join between the assessment population, governing element set, validation messages and accepted record history. A green transmission badge cannot perform that job. Test the combined-assessment case and a correction that changes the denominator before accepting a completeness dashboard.