RAI-MDS 3.0 Completion Rules and Their Compliance Implications

RAI-MDS 3.0 completion rules govern how every nursing home tracks resident status, timelines, and payment classification, and compliance failures in skilled nursing facilities are often rooted in misunderstandings of these rules rather than isolated clerical mistakes. A standardized tool required for use by certified nursing homes is used to record a resident's functional, medical, and psychosocial condition. It feeds care planning, quality measurement, and payment, all at once. A coding error or a missed deadline rarely stays contained to one problem.

Most facilities run two assessment tracks side by side and, in practice, treat them as one job. That's the first mistake. OBRA assessments apply to every resident, regardless of who pays, and follow a rolling schedule tied to each resident's own admission date. PPS assessments apply only to residents under Medicare Part A and are tied to the first day of the covered stay, feeding directly into PDPM payment classification. Each track carries its own Assessment Reference Date window, its own submission clock, and its own penalty if a deadline slips. Conflate the two, and the resulting errors don't show up on a spreadsheet. A surveyor sees the errors when pulling the resident's ARD history and counting days.

The current RAI Manual, version 1.20.1, took effect October 1, 2025. Version 1.20.11 follows on October 1, 2026. Both versions carry coding changes that reach into the same items CMS now audits under its data validation program, discussed further below. That overlap is the throughline of this piece: completion rules, covering assessment type, ARD timing, coding accuracy, and submission deadlines, form the structural point of origin for nearly every compliance problem tied to this assessment tool that a facility will face. Getting this right is risk management. It's risk management.

OBRA assessment types and the rolling deadlines that govern every resident

Four OBRA assessment types make up the backbone of the resident-level schedule, and each has a distinct ARD rule under RAI Manual v1.20.1, Chapter 2.

The Admission assessment requires an ARD on or before Day 14, counting Day 1 as the admission date itself. The care plan is due within 7 days of the ARD, and the record must reach iQIES within 14 days of the care plan completion date. That last point trips up more coordinators than it should: the submission clock starts at care plan completion, not at the ARD.

Quarterly reviews are where drift happens quietly. The rule is that the ARD must fall within 92 days of the prior assessment's ARD, full stop. Not 92 days from the end of a calendar quarter. Not 92 days from when the last assessment was submitted. From the prior ARD. A facility that tracks quarterlies by calendar month instead of by each resident's individual prior ARD will drift out of compliance in a way that stays invisible until a surveyor does the math and finds the gap.

Annual assessments require an ARD within 366 days of the last comprehensive assessment's ARD, and they reset the OBRA cycle entirely since they're comprehensive in scope. Significant Change in Status Assessments work differently: an event triggers them, not a date. Once the interdisciplinary team determines a significant change has occurred, the ARD must be set within 14 days, and that assessment resets the quarterly cycle going forward.

Item Z0500B, the MDS completion date, has to land no later than Day 14 and can't come after the CAA completion date recorded in V0200B2. Sequencing matters here just as much as the window itself; a completion date that's technically within 14 days but falls after the CAAs were finished is still a defect.

Corrections carry their own clock. If an error surfaces in an accepted iQIES record, the facility has 14 days from discovery to file a modification request, alongside the required Section X items. And the item set that determines which fields even appear on a given MDS record comes from Type of Provider (A0200) and the reason-for-assessment items (A0310A, A0310B, A0310F, A0310H). Software handles this determination automatically in most systems, but staff still need to understand the underlying logic. Software makes mistakes too, and someone has to be able to catch them.

PPS assessments under PDPM and a widespread calendar error still circulating in 2026

A calendar error from the pre-PDPM era is still circulating among facility staff well into 2026: the 14-day, 30-day, 60-day, and 90-day PPS assessment schedule no longer exists. That structure was eliminated when PDPM launched in October 2019. Under PDPM, a Medicare Part A stay requires exactly one scheduled PPS assessment, the 5-day.

The legacy A0310B item codes numbered 02 through 05 no longer apply under federal Medicare payment rules for standard Part A stays. Some state Medicaid programs still require versions of them for state-specific payment purposes, so facilities working across payer types should confirm requirements with their State RAI Coordinator rather than assume federal Medicare rules cover every case.

The 5-day PPS assessment generates a HIPPS code, a five-character string. The first four characters represent the PDPM classification across physical therapy, occupational therapy, speech-language pathology, and nursing; the fifth identifies the assessment type. That code sets Medicare payment for the entire covered stay, unless the facility completes an Interim Payment Assessment, which generates a fresh HIPPS code covering the remainder of the stay. The IPA has no fixed schedule; it's triggered clinically, when a resident's status changes enough to justify reclassifying the payment group.

Facilities also need to keep QRP submission deadlines separate from per-resident iQIES deadlines, because these are two different obligations that get folded together constantly. The 2026 SNF QRP quarterly submission dates, February 17, May 18, August 17, and November 16, govern aggregate quality measure data tied to the Annual Payment Update determination. They have nothing to do with any single resident's assessment deadline.

There's also a revenue dimension to ARD timing that gets overlooked. The 5-day window gives facilities some flexibility in exactly when they set the ARD, and an ARD set early in the stay tends to capture therapy minutes and NTA diagnoses at the point when acuity is often highest. Facilities that default to the same ARD placement on every admission, out of habit or convenience, may be leaving clinical accuracy, and the payment that follows from it, on the table.

What a late or missing submission costs, by track

The consequences differ sharply depending on which track slips, and treating them as one generic "compliance risk" obscures which failure produces which outcome.

On the PPS side, a late or missing assessment doesn't generate a fine. It blocks the Medicare Part A claim from processing. Revenue simply waits until the assessment clears iQIES, with no grace period. Facilities running lean on cash flow feel this immediately and directly, since the money doesn't move until the paperwork does.

On the OBRA side, a missed quarterly or annual ARD window creates survey citation exposure under F640, Encoding and Transmitting Resident Assessment, and F641, Accuracy of Assessments. Surveyors routinely request MDS schedules during standard surveys and calculate gaps against each resident's ARD history. Critically, the citation doesn't require proof that harm occurred. A missed window is the violation on its own.

Then there's the SNF QRP Annual Payment Update consequence, which runs on a different mechanism. To avoid a 2% cut to the APU, facilities need to hit a 90% compliance rate on submitted 5-day PPS assessments and Medicare Part A PPS Discharge assessments, and those submitted assessments have to carry 100% of the required data elements. Partial data doesn't count toward compliance even if the assessment technically made it into the system on time.

F641 coding accuracy and the escalating enforcement posture CMS adopted in April 2025

F641 requires that an MDS accurately reflect a resident's actual condition during the observation period, coded by professionals qualified to assess medical, functional, and psychosocial status. It's consistently one of the most frequently cited F-Tags during surveys, and CMS just made it carry more weight.

On March 10, 2025, CMS issued a revision to LTC Surveyor Guidance, effective April 28, 2025, that folds the former F642, Coordination and Certification of Assessment, into F641. That's a consolidation, but it's also an expansion of what surveyors are checking under a single tag.

The sharper change is in the enforcement pathway itself. Surveyors are now instructed to refer inaccurate coding directly to a federal oversight office, not to a CMS regional office, whenever they find a pattern involving at least three residents with the same inaccurate coding, combined with indications that staff knew the coding was wrong. That's a meaningfully different exposure than a standard survey deficiency. CMS has said that a pattern of clinical documentation or MDS coding practices that results in inflated PDPM scores, untriggered Care Area Assessments, or unflagged Quality Measures, where the underlying information doesn't reflect the resident's actual status, "may be indicative of payment fraud or attempts to avoid reporting negative quality measures.""

Beyond survey citations, inaccurate coding carries its own financial tail through CMS audit processes, which can claw back payments tied to incorrect coding, whether that coding inflated Medicare PPS reimbursement or Medicaid reimbursement calculated from CMI. The scale of what this can look like in practice showed up in a November 2025 OIG audit of Pinnacle Multicare Nursing and Rehabilitation Center, where 99 out of 100 sampled claims for skilled nursing services failed to meet Medicare payment requirements, a systemic breakdown in coding accuracy across nearly an entire sample. That's a systemic breakdown in coding accuracy across nearly an entire sample.

The 2026 CMS MDS data validation program's added compliance obligation for every facility

CMS started randomly selecting SNF providers for a new MDS data validation program in 2026, with selection notices uploaded to each facility's iQIES Provider Preview Reports folder beginning mid-January. Nobody gets a phone call or an email about this. Facilities need to be checking iQIES directly, on a schedule, or they'll miss the notice.

Once selected, a facility has 45 calendar days to submit medical records for 10 sampled MDS assessments, uploaded as PDFs per CMS guidelines. The requirement to pass is about submitting all ten records within the window. It's about submitting all ten records within the window. Missing the deadline creates compliance exposure under the SNF QRP program, where penalties can reach up to 2 percentage points off the Annual Payment Update.

That distinction matters enormously and gets lost easily: the validation report itself is informational. The 45-day response window is the operative compliance deadline for selected facilities, and failing to submit records within it creates APU penalty exposure. CMS reviews specific quality measure areas as part of this validation process, comparing coded MDS data against the underlying medical records submitted.

Maureen McCarthy, President and CEO of Celtic Consulting, described the program as "an audit verifying MDS coding and the supportive documentation used to code the item," and added that it looks like "a precursory way for CMS to account for incentive payments, and whether they were appropriate," calling it "the tip of the iceberg" with potential to reduce incentive multipliers under a related payment program going forward. CMS itself has said that if it finds systematic coding errors, mismatches between documentation and reported data, or elevated error rates concentrated in specific regions or facilities, those findings "may flag these for further scrutiny" and lead to an escalated audit approach.

Under the new rules, MDS accuracy is no longer just a survey-cycle concern but a standing documentation obligation, requiring that the records behind the coded values exist, be organized, and be retrievable inside a 45-day window, at any point, without warning. It's not enough for the coded values on the MDS to be defensible. The records behind them have to exist, be organized, and be retrievable inside a 45-day window, at any point, without warning.

The manual changes in v1.20.1 and v1.20.11 that alter coding accuracy requirements going forward

Version 1.20.1, effective October 1, 2025, rewrote several items that carry direct compliance weight. Section J's fall definitions got much more specific: "fall with major injury" now explicitly covers traumatic bone fractures, joint dislocations or subluxations, internal organ injuries, amputations, spinal cord injuries, head injuries, and crush injuries, while excluding pathologic fractures. That item feeds the falls-with-major-injury quality measure, which is a VBP performance metric and also falls within the scope of the 2026 data validation program. Miscode that item, and the error compounds across multiple CMS programs at once.

Section O saw a consolidation: most therapy items under O0400 folded into a new item, O0390, Therapy Services, and O0420, Distinct Calendar Days of Therapy, was removed. Any facility that hasn't updated its coding workflow to match will produce inaccurate submissions without realizing it.

Section A replaced A0800 (Gender) with A0810 (Sex), and swapped A1250 (Transportation) for A1255 (Transportation), the latter required only on Medicare 5-day PPS assessments where the resident was in the community fewer than 366 days before the ARD. Section R disappeared entirely: Living Situation, Food, Utilities, and Transportation items are gone, and facilities still coding to that section are coding to something that no longer exists. Section GG was restructured around GG0130 (Self-Care) and GG0170 (Mobility) for clearer coding, and those items feed directly into the Discharge Function Score, a quality measure also subject to CMS review,.

Version 1.20.11, effective October 1, 2026, adds further refinement. Chapters 1 through 3 now clarify that state or payer rules can't replace, modify, or expand CMS coding requirements for non-Section S items, closing a loophole some facilities leaned on. Chapter 2 adds guidance on resident transfers during a public health emergency. Section A updates ethnicity and race reassessment guidance and drops the resident interview icon from several items. Sections C and D clarify coding when a resident undergoes multiple interviews, covering a cognitive screening tool and a mood screening tool, within a single look-back period. Section M updates guidance on pressure ulcers present at admission that heal and then reopen, plus new guidance on advanced wound dressings, skin substitutes, and adhesive bandages, all of which bear directly on the pressure ulcer and injury rate measure under validation. Section O refines isolation criteria and skilled respiratory therapy coding.

Comparing both versions together reveals a pattern: the items receiving the most definitional revision are the same items feeding validated quality measures and VBP metrics. That is part of a pattern, not a coincidence. Facilities that skip retraining on these updates are exposed on three fronts simultaneously: distorted quality measures, potential payment claw-backs, and audit failure, all from the same coding gap.

The September 2026 Risk-Based Survey process's implications for facilities with MDS gaps

CMS rolled out the Risk-Based Survey process nationwide starting September 8, 2026, for qualifying nursing homes. The mechanism prioritizes which facilities get surveyed, and how closely, based on risk signals: MDS-derived quality measures, complaint history, and other performance data feed directly into that prioritization.

That means the coding accuracy discussed throughout this piece functions as more than a matter of passing or failing a single audit. It is an input into whether a facility draws heightened survey attention. A facility with clean submission timing but sloppy Section GG or Section M coding isn't just risking an F641 citation down the road; it's feeding the exact data CMS uses to decide how hard to look. The completion rules covered here, assessment type, ARD windows, coding accuracy, and submission deadlines, aren't separate administrative boxes to check. They're the raw material a facility's entire risk profile gets built from, whether the people filling out the MDS realize it or not.