LTC

The SNF Triple Check Process: Who Verifies What, When to Run It, and What the Written Record Must Contain

SNF Triple Check process claims compliance

Triple Check the pre-billing audit that cross-references clinical documentation, MDS assessments, and billing data before a Medicare Part A claim leaves a skilled nursing facility is one of the most described and least understood compliance functions in SNF revenue cycle management.

Every guide on this topic explains who should attend the meeting. Few explain what each person is accountable for verifying. Almost none describe what the written record must contain for it to function as a compliance control rather than a meeting that happened.

This guide covers all three: role-specific verification accountability, the iQIES timing rule that determines when Triple Check should run, and the seven required elements of a written record that holds up when an auditor asks for it.

Quick Summary

Triple Check is a mandatory pre-billing review of every Medicare Part A claim before submission. Three parties must sign off: the MDS coordinator confirms HIPPS code and assessment accuracy; the billing coordinator confirms the UB-04 claim data; the clinical or therapy director confirms that therapy evaluations and nursing notes support the billed classifications.

The meeting must produce a written record with date, attendees, HIPPS codes confirmed, discrepancies resolved, and three-party sign-off. A verbal Triple Check with no written documentation is not a compliance control. It is a story you tell during an audit.

Table of Contents

What Triple Check Actually Is and What It Is Not

Triple Check is an internal pre-billing audit conducted before Medicare Part A claims are submitted for a billing period. Its purpose is to confirm that clinical documentation, MDS assessments, and UB-04 billing data are consistent with each other before the claim enters the Medicare system.

It is not a clinical meeting, a care conference, or a documentation catch-up session. Under PDPM the Patient Driven Payment Model, Medicare’s SNF reimbursement framework since October 2019 the 5-day MDS assessment sets the HIPPS code that determines the payment rate for the entire Medicare stay. Triple Check is the last opportunity to catch a HIPPS code error before that rate is locked by submission.

Triple Check is also distinct from Utilization Review. UR Utilization Review is the process by which clinical staff determine whether a resident continues to meet Medicare’s skilled care criteria during a stay. UR happens during the stay. Triple Check happens before the claim goes out. They serve different purposes, run at different points in the revenue cycle, and require different attendees.

Triple Check is not a clinical meeting. It is a billing compliance event. The three-way sign-off is the last documented control before a claim enters the Medicare system. Running it without a written record leaves the facility with no audit defence when a MAC questions the claim after payment is made.

For a deeper look at how the HIPPS code is built and what each PDPM component classification means for reimbursement, see the PDPM reimbursement and billing guide.

Who Needs to Be in the Room and Why Each Role Is Non-Negotiable

Think of Triple Check as a three-legged stool. Remove one leg and the structure collapses not because the remaining two do poor work, but because no single role carries the visibility the review requires.

The MDS coordinator owns the 5-day PPS assessment. The HIPPS code on the UB-04 claim is the direct output of that work. If a coding error was made during the assessment window, Triple Check is the last moment to catch it before an inaccurate HIPPS code drives the payment rate for the entire Medicare stay.

The billing coordinator or business office manager owns the UB-04 the standardized claim form submitted to Medicare. This role confirms that revenue codes, dates of service, patient demographic data, and payer information align with the clinical record and the MDS output. Billing has full visibility into the claim form. Billing has no independent visibility into whether the clinical documentation actually supports the classifications on that form.

The clinical or therapy director or the DON acting as designee confirms that nursing notes and therapy evaluations support the billed level of care. Under PDPM, the therapy director’s verification obligation is a classification check, not a minutes check. The question is whether the therapy evaluation documents the functional score and clinical category embedded in the HIPPS code grouper not simply that therapy was provided.

A social worker should be included when Medicare Secondary Payer coordination is in question. A physician liaison or designee should be available when certification status is unresolved at the time of the meeting.

A Note on Who Should Not Run Triple Check

The billing coordinator should not run Triple Check independently. Billing can confirm the claim data is internally consistent. Billing cannot confirm that the clinical documentation supports the HIPPS code classifications. The three-party structure is not a procedural formality it is the control design. When Triple Check collapses into a solo billing review, the control fails regardless of how accurately billing does its job.

What Each Party Verifies: The Role-Specific Accountability Framework

Most Triple Check guides describe who attends. This section describes what each role is accountable for confirming and what a gap in their verification lane specifically produces.

MDS Coordinator Verification Responsibilities

The MDS coordinator arrives at Triple Check with one foundational question already answered: are all MDS assessments for the billing period accepted in iQIES not submitted, but accepted?

Specific items to confirm at Triple Check:

  • All required assessments for the billing period are completed, submitted, and accepted in iQIES the Internet Quality Improvement and Evaluation System, CMS’s MDS submission and validation platform.
  • The HIPPS code on each assessment matches the PDPM grouper output for all five components: PT, OT, SLP, Nursing, and NTA (Non-Therapy Ancillary the PDPM component that captures comorbidity-driven costs for high-acuity residents).
  • The ARD Assessment Reference Date, the anchor date that defines the 5-day MDS window for PPS purposes is documented correctly and falls within Days 1 through 8 of the Medicare stay.
  • An IPA Interim Payment Assessment, the optional mid-stay assessment that resets all five PDPM component classifications following a significant clinical change has been filed if a qualifying change occurred.
  • The primary diagnosis in Section I0020B is not one of the 33 ICD-10 codes reclassified to Return to Provider status in the FY 2026 SNF PPS Final Rule.

The iQIES Acceptance Requirement

The MDS coordinator’s Triple Check obligation begins before the meeting convenes. Submitted and accepted are not the same status in iQIES a submitted assessment can still be rejected or returned for correction during processing. Running Triple Check against an assessment in submitted-not-accepted status means verifying a HIPPS code against data that can still change before the claim is built. The correct sequence is iQIES acceptance confirmed, then Triple Check, then claims released.

Billing Coordinator Verification Responsibilities

The billing coordinator’s lane covers the UB-04 claim form and its alignment with source records:

  • Revenue codes on the UB-04 match the HIPPS code generated by the MDS a mismatch between the two produces a CO-B7 denial, the specific denial code triggered when claim revenue code structure is inconsistent with the associated MDS classification.
  • Dates of service align with the Medicare Part A admission date, benefit period, and any IPA effective dates.
  • Patient name, MBI (Medicare Beneficiary Identifier the unique identifier that replaced the Social Security Number-based HICN in 2018), and date of birth match the Medicare eligibility record exactly.
  • The MSP Medicare Secondary Payer questionnaire is on file, current, and accurately reflects whether another payer is primary before Medicare.
  • Physician certification of skilled care need is signed and dated prior to or at the time of admission, with any recertification for extended stays executed within the required window.
  • No claims in the billing period are approaching the one-year Medicare Part A timely filing limit from the date of service.

Clinical and Therapy Director Verification Responsibilities

The clinical or therapy director confirms the documentation foundation beneath the classifications the other two roles are verifying:

  • Therapy evaluation notes are on file and support the PT, OT, and SLP PDPM classifications on the 5-day MDS. This is not a minute’s check it is a classification check. Does the evaluation document the functional baseline and clinical category that drove the grouper output?
  • Nursing notes in the medical record support the nursing PDPM classification specifically, the conditions placing a resident in Special Care High, Special Care Low, Clinically Complex, or Behavioural Symptoms categories must appear in the nursing record, not only in MDS coding.
  • NTA conditions documented on the MDS are supported by physician diagnosis or nursing documentation in the medical record. A coded comorbidity with no supporting clinical record is an audit flag at every level of CMS review.

The PDPM Shift in Therapy’s Triple Check Role

Under RUG-IV, the therapy director’s Triple Check obligation was a minutes verification confirm that documented therapy minutes matched what was billed. Under PDPM, the obligation is a classification verification confirm that the therapy evaluation supports the functional score and clinical category embedded in the HIPPS code. A therapy director who approaches PDPM Triple Check with a RUG-IV mindset is verifying the right number at the wrong stage of the payment model. The billing consequence is not a minutes discrepancy. It is a HIPPS code that cannot be defended if the underlying evaluation does not support the classification.

When to Run Triple Check: The iQIES Timing Rule

Most Triple Check guidance recommends holding the meeting around the 8th day of the month following the billing period close. That is a convention, not a compliance standard, and applying it mechanically produces a specific failure mode.

The correct trigger for Triple Check is iQIES acceptance of all MDS assessments for the billing period. Not the calendar date. Not submission status. Acceptance status confirmed before the meeting is scheduled.

An assessment submitted to iQIES but not yet accepted is still in processing. iQIES can reject it, flag it for correction, or return an error. Triple Check run before acceptance means verifying HIPPS codes against assessments that may still change and the claim built on that verification is built on unstable data.

The practical window falls within the first seven to ten business days of the following month for most facilities. The trigger remains iQIES acceptance, regardless of the date. High-census facilities or those with complex payer mixes benefit from a mid-period soft review for newly admitted residents whose 5-day assessment window has closed but whose billing period has not.

“Hold Triple Check on the 8th of the month” is a scheduling convention. If MDS assessments for the billing period have not all been accepted in iQIES by the 8th, running the meeting on schedule means verifying against data that can still change. The correct sequence is: iQIES acceptance confirmed, Triple Check meeting conducted, claims released. Calendar dates do not override that order.

For a full breakdown of iQIES submission and acceptance mechanics, see the MDS 3.0 submission deadlines and compliance guide.

What the Written Record Must Contain

Here is the gap no competitor on this SERP has filled: what the written Triple Check record must actually contain to function as an audit defense document.

The SNF improper payment rate reached 17.9% in the 2024 reporting period, with 75.5% of those errors driven by insufficient documentation (Source: CMS 2024 Medicare Fee-for-Service Supplemental Improper Payment Data). That is not a claims submission problem. It is a documentation problem that precedes submission by days or weeks. Triple Check is the control designed to close it but only if the written record is specific enough to demonstrate that a meaningful review actually occurred.

A compliant Triple Check written record contains seven elements:

  1. Date and time of the meeting. Not “monthly Triple Check” the specific date and time the review was conducted.
  2. Names and roles of all attendees. Each person named individually MDS coordinator, billing coordinator, clinical or therapy designee with their role noted.
  3. Billing period covered. The statement from-date and through-date for the claims under review.
  4. Each resident reviewed with HIPPS code confirmed. Every Medicare Part A resident in the billing period should appear with the HIPPS code confirmed at the time of review. A generic “all claims reviewed” note does not constitute specific verification.
  5. Discrepancies identified during review. Each error, inconsistency, or missing document identified by which role flagged it, what the issue was, and how it was resolved before the claim was released.
  6. Claims held pending correction. Any claim not released due to an unresolved discrepancy, with the specific issue documented and a target resolution date assigned.
  7. Three-party sign-off. A dated signature or written attestation from each of the three mandatory roles confirming their portion of the review is complete.

The Written Record Is an Audit Defense Document, Not a Meeting Summary

When a MAC (Medicare Administrative Contractor the regional Medicare claims processor that handles ADRs and billing reviews) or UPIC (Unified Program Integrity Contractor the CMS entity that investigates suspected Medicare fraud and abuse) requests evidence that pre-submission billing controls were in place, the Triple Check written record is the primary document. A record that lists attendees but shows no HIPPS codes confirmed and no discrepancies documented provides almost no protection. The record must show what was reviewed not simply that a meeting occurred.

Managing Triple Check documentation in a shared drive folder, a paper checklist, or an email thread works until an ADR arrives and the record either cannot be located or does not contain what the auditor needs. LTC Apps Medical Code Analysis supports the ICD-10 accuracy that feeds upstream into the HIPPS code your MDS coordinator confirms at Triple Check so the coding your billing team is verifying was built on a structured, documented foundation. See how the Medical Code Analysis module works.

What Happens When Triple Check Is Skipped or Incomplete

Triple Check failures produce predictable claim consequences. These are not worst-case scenarios. They are the mechanics of what CMS audits specifically flag.

A HIPPS code mismatch between the MDS and the UB-04 revenue code structure produces a CO-B7 denial. CO-B7 denials are correctable through resubmission, but each one represents administrative recovery time the Triple Check process exists to eliminate.

A claim submitted with missing physician certification, an unsupported therapy classification, or an unresolved MSP issue is a high-probability ADR trigger. The response window is 45 days under 42 CFR Section 405.930. Non-response within that window results in automatic claim denial.

If an audit finds inaccurate HIPPS codes or unsupported clinical classifications, CMS recoupment authority applies not only to the reviewed claim but potentially across similar claims in the audit period through statistical extrapolation. For facilities without a documented Triple Check process, the absence of a pre-submission control record makes demonstrating intent to submit accurate claims significantly harder in any DOJ or OIG review.

For the full ADR response framework and documentation standards for audit defense, see the SNF compliance documentation guide.

Triple Check Is Not a Billing Function

Every Triple Check guide on this SERP frames the process as a billing accuracy function something the billing coordinator runs to confirm the claim is correct before it goes out. That framing assigns Triple Check to a single role. It is the wrong mental model, and it produces the most common Triple Check failure in practice.

The billing coordinator reviews the claim independently, marks the review complete, and the cross-functional meeting never happens. The claim may be accurate. The compliance control is not in place.

No single role carries the visibility this review requires. Billing cannot verify that MDS coding is clinically supported. The MDS coordinator cannot verify that UB-04 revenue codes align with the HIPPS code. The clinical director cannot verify that claim dates match the benefit period. The three-party structure is the control design. When it collapses into a solo review, the control fails regardless of how accurately any one party does their job.

For smaller facilities where staff time is limited: Triple Check can run in 20 minutes. The written record does not require a formal template. It requires specificity HIPPS codes confirmed, discrepancies documented, three-party sign-off dated. Format is secondary. Content is not.

Who This Is For

LTC Apps is the right fit if you
You operate a skilled nursing facility running Medicare Part A billing in-house
Your Triple Check process is informal, undocumented, or primarily run by the billing coordinator without consistent clinical sign-off
You want to reduce Medicare claim denials and build a pre-submission compliance record that holds up in an ADR
This is not the right fit if:
You have fully outsourced your revenue cycle to a third-party billing company that manages Triple Check on your behalf
You are looking for a full physician-facing clinical EHR with automated claims submission

Frequently Asked Questions

Triple Check is an internal pre-billing audit conducted before Medicare Part A claims are submitted for a billing period. It cross-references MDS assessments, clinical documentation, and UB-04 claim data to confirm all three are consistent before the claim enters the Medicare system. Three parties must complete the review: the MDS coordinator, the billing coordinator, and the clinical or therapy director.

Three roles are mandatory: the MDS coordinator (confirms HIPPS code and assessment accuracy), the billing coordinator or business office manager (confirms the UB-04 claim form), and the clinical or therapy director or DON designee (confirms that nursing notes and therapy evaluations support the billed classifications). A social worker should attend when MSP coordination is in question.

The correct trigger is iQIES acceptance of all MDS assessments for the billing period not a fixed calendar date. Schedule the meeting only after every assessment for the period shows accepted status in iQIES. For most facilities, that falls within the first seven to ten business days of the following month, but iQIES acceptance status determines the trigger, not the date.

A HIPPS-to-revenue-code mismatch produces a CO-B7 denial. A claim with missing physician certification or unsupported clinical classifications triggers an ADR with a 45-day response window non-response results in automatic denial under 42 CFR Section 405.930. If an audit finds inaccurate HIPPS codes, CMS recoupment can extend across similar claims in the audit period through statistical extrapolation.

Utilization Review is conducted during a Medicare stay to determine whether the resident continues to meet skilled care criteria. Triple Check is conducted before claims submission to verify that clinical documentation, MDS assessments, and billing data are internally consistent. Different purpose, different timing, different required attendees.

A verbal Triple Check provides no audit protection. The written record must include the meeting date and time, names and roles of all attendees, billing period covered, each resident's HIPPS code confirmed, discrepancies identified and resolved, claims held pending correction, and three-party sign-off. A record listing only attendees with no HIPPS codes confirmed and no discrepancies documented does not function as a compliance control.

What Happens After You Request a Demo

Here is exactly what happens when you reach out:

  1. A member of the LTC Apps team responds within one business day to schedule a call.
  2. We run a 30-minute live walkthrough of the modules most relevant to your billing and documentation workflow.
  3. You receive pricing specific to your facility size and module selection.

Most facilities have a clear picture of fit and pricing within one week of the first conversation.

 

Common questions before booking: No long implementation timelines most facilities are live on their first module within 2 to 4 weeks. No minimum facility size. If you are mid-contract with another vendor, a parallel evaluation now means you are ready to switch at contract end without rushing a decision under time pressure.

Ready to Strengthen Your Triple Check Process?

 

If you operate a skilled nursing facility and want to reduce Medicare claim denials, improve HIPPS code accuracy before submission, and build a Triple Check documentation record that holds up when an auditor asks for it LTC Apps was built for exactly this.

About Our Company
Ronan D'silva

Meet Ronan D'silva, Marketing Manager at LTC Apps and healthcare technology writer focused on helping skilled nursing facilities streamline operations, reduce eligibility denials, and simplify compliance through purpose-built software solutions.

Follow Us On
Scroll to Top