From 5-hour meetings to 45-minute exception reviews — before the claim leaves the building
How a leading Illinois Skilled Nursing Facility replaced its manual Medicare Part A Triple Check process with automated CMS rule validation — and caught over $300,000 in billing errors in the first month.
“"The Change Log rule alone paid for the entire system. That one catch would have been a denial and a resubmission cycle costing us weeks."”
— Director of Billing, Pilot Facility (Illinois SNF, 100 beds)“"We had a patient whose payer changed mid-month — something that used to be easy to miss in the spreadsheet. TripleCheck flagged it immediately. That one catch would have been a denial and a resubmission cycle costing us weeks. Before this, we had no way to catch that without someone physically checking every patient's record against their billing before submission."”
A 100-bed Illinois SNF — running Medicare Part A Triple Check entirely on paper
Medicare Part A billing at a Skilled Nursing Facility is not a simple process. Every claim submitted to CMS must satisfy a set of compliance rules that cross-reference three distinct document types: the UB-04 claim form, Minimum Data Set (MDS) assessments, and physician certification and recertification forms. Miss a single field mismatch — a wrong bill type code, a therapy minutes figure that doesn't align with the MDS, a missing recertification date — and the claim is denied, potentially triggering a RAC audit or a post-payment recoupment demand months later.
This leading 100-bed SNF in Illinois — with significant leadership within their state's care association network — had been running their Triple Check entirely on paper and spreadsheets. Every billing cycle, a small team of clinical and billing staff would convene for three to five hours to manually cross-check each active Medicare Part A patient's claim against 22 compliance elements drawn from the CMS QRM reference guide.
The process worked — until growing census counts, PDPM-era billing complexity, and staff turnover stretched the manual approach past its limits. One missed meeting or distracted coordinator, and a six-figure billing error could leave undetected.
The core problem: With 22 elements to check per patient and 20+ active Part A patients each cycle, manual Triple Check meetings produced fatigue-driven gaps. Events happening mid-cycle — payer changes, level-of-care shifts, unexpected discharges — were chronically missed. No system existed to create an audit trail of what changed between admission and submission.
22 compliance elements. 20+ patients. Every billing cycle. By hand.
The QRM Medicare Part A Triple Check framework — the industry standard the facility was following — requires checking 22 compliance elements per patient across three document sources. At 20+ active Medicare Part A patients per cycle, that is 440+ individual data-point verifications every month, all performed in a single meeting by a team that had patient care responsibilities for the rest of the day.
The PDPM billing model introduced further complexity. Under PDPM, therapy minutes thresholds, MDS assessment timing (ARD dates), IPA assessment indicators, and HIPPS code accuracy all determine the payment rate. A single wrong therapy minutes figure in the UB-04 that doesn't match the MDS is not just a compliance flag — it is a payment accuracy problem on every future claim for that patient until corrected.
The biggest gap was mid-cycle events. Between a patient's admission and the end-of-month billing submission, things change: payers change, levels of care are adjusted, unexpected discharges occur. In a manual process, these events are only as visible as the person who happened to note them in a spreadsheet. In a busy SNF, they frequently weren't — and the billing team had no systematic way to know what they didn't know.
The key gap: No existing billing software caught these errors before claim submission. The EHR (MatrixCare) generated the UB-04, but it did not validate it against the MDS. The Triple Check meeting existed specifically to catch that gap — but doing it manually for 20+ patients every month was neither reliable nor scalable.
Five steps from document upload to a claim-ready confirmation
TripleCheck Pro does not replace the billing team's judgment — it replaces the manual verification work that consumes their time, surfacing only the exceptions that genuinely need human attention.
Upload three document types
The billing coordinator uploads the batch UB-04 PDF export from MatrixCare (all patients in one file), individual MDS assessment PDFs, and any physician certification or recertification forms. All uploads are encrypted at rest (AES-256) and in transit. PHI stays within the HIPAA-compliant AWS environment.
Intelligent document parsing
The UB-04 batch PDF is split by page and each patient's record extracted. MDS fields are parsed per patient per assessment period — multiple assessments per month (admission and discharge) are handled automatically. A dual-mode parser handles standard EHR exports via high-precision rules; an LLM-assisted mode handles non-standard layouts, toggled per facility by the administrator.
Monthly Change Log uploaded
Throughout the cycle, the billing coordinator maintains a structured Change Log capturing mid-month events: unexpected discharges, payer changes, level-of-care transitions. This log is uploaded at validation time and powers TC-023 — the platform's proprietary rule that no manual checklist can reliably replicate.
23 rules run simultaneously
All 23 CMS compliance checks run in parallel across every active Medicare Part A patient. Each check maps to a specific field or cross-document comparison — bill type code, therapy minutes alignment, MDS ARD date, physician cert timing, HIPPS code match, and more. Results surface in seconds. Every check passes or flags with the source field identified.
Exception review — 45 minutes
The billing team reviews a dashboard showing green / amber / red status per patient per rule. Each exception links directly to the source field. Routine verifications that passed need no attention. The team's time is spent entirely on real issues — the kind that actually require clinical or billing judgment to resolve.
Change Log entry dated 04/17 records payer change for J. Morris — Medicare Part A → Managed Care (Aetna Better Health). UB-04 still shows Medicare Part A as primary payer. Claim as submitted would be sent to the wrong payer and denied. Statement covers period must also be split at the transition date.
Split into two claims: (1) 04/01–04/16 to Medicare Part A with bill type 211, (2) 04/17–04/30 to Aetna Better Health as primary. Confirm level-of-care documentation supports managed care authorization for second claim period. Update payer sequence on second UB-04.
Two applications. 23 rules. Dual-mode parsing. One HIPAA-compliant platform.
TripleCheck Pro is a purpose-built SaaS system — not a repurposed billing tool. Every component was designed specifically for the Medicare Part A Triple Check workflow and the document formats SNF billing teams actually work with.
Main facility application — app.triplecheck.metricoidtech.com
Facility portalThe primary application used by billing teams at each SNF. Handles document uploads (UB-04 batch, MDS PDFs, physician certs), Change Log entry, validation runs, and exception review. Role-based access assigns Billing Coordinator, Clinical Lead, and Facility Administrator roles — each seeing only the data their function requires. Built in React + TypeScript + Tailwind CSS.
Superadmin portal — admin.triplecheck.metricoidtech.com
Platform adminA separate application for Metricoid administrators managing the full platform. Controls per-facility LLM mode toggle — enabling AI-assisted parsing for facilities with non-standard EHR export layouts while keeping manual parsing for standard MatrixCare and PointClickCare formats. Manages per-facility parser configuration, onboarding, and user provisioning across all facilities on the platform.
Dual-mode PDF parsing architecture
Core parsingStandard EHR exports (MatrixCare batch UB-04, individual MDS PDFs) are handled by a high-precision manual parser using pdfplumber — no AI cost, no latency, configured per facility's specific export format. Facilities with non-standard layouts can enable LLM-assisted parsing via a per-facility toggle in the superadmin portal. Parser routing logic: if facility.llm_mode → LLM parser; else → manual parser with facility-specific field mapping. The UB-04 batch PDF is split by page; MDS files are grouped by patient and session date to handle multiple assessments per patient per month.
Monthly Change Log engine (TC-023)
Proprietary ruleThe platform's most impactful proprietary capability. The billing coordinator maintains a structured Change Log throughout each billing cycle — recording mid-month events with patient, date, event type, and details. At validation time, TC-023 automatically cross-references every active patient's claim against the Change Log, flagging any claim where a recorded mid-cycle event (payer change, discharge, level-of-care transition) is not reflected in the UB-04. This is the rule that catches the errors most likely to reach a payer undetected — and most likely to generate a RAC audit inquiry.
Physician certification date logic
Cert validationPhysician certification and recertification date validation uses a three-tier priority system: (1) standalone certification PDF with discrete signature date — most reliable; (2) MDS fields Z0100A (initial certification) or Z0100B (recertification) — standard embedded source; (3) exception flagged — no date found, claim cannot pass TC-002/TC-003. The platform accepts standalone physician certification PDFs directly, with date extraction from the signature block. For facilities where dates are embedded in the MDS, the MDS fields are used automatically with no additional upload required.
HIPAA-compliant cloud infrastructure
InfrastructureBuilt on AWS with a signed Business Associate Agreement. All PHI encrypted at rest (AES-256) and in transit (TLS). JWT-based authentication with bcrypt password hashing and full RBAC. AWS S3 for document storage, PostgreSQL on AWS RDS for structured data, APScheduler for scheduled validation jobs, AWS SES for billing cycle notifications, and AWS CloudWatch for monitoring and audit logging. Google Workspace BAA also signed for any staff-facing communications.
All 23 CMS rules — automated. Documentation Review and Claims Review.
TripleCheck Pro covers the complete QRM Medicare Part A Triple Check compliance framework — both the Documentation Review (items 1–10, verifying clinical record accuracy) and Claims Review (items 11–22, validating the UB-04 against MDS and payer data) — plus one proprietary rule built for the realities of mid-cycle billing events.
The 22 standard QRM elements map directly to CMS Triple Check guidance. TC-023 is Metricoid's addition: a structured Change Log cross-reference that has no equivalent in any manual checklist because no manual checklist can track mid-cycle events in real time.
From signed agreement to first upload in under two weeks
No EHR integration project. No IT department involvement. No change to the billing team's existing document exports. TripleCheck Pro works from the PDFs already produced every billing cycle.
Onboarding & Configuration
Facility administrator account created, user roles assigned (Billing Coordinator, Clinical Lead, Administrator), and facility-specific parser configuration confirmed against a sample UB-04 export from MatrixCare. Superadmin portal used to configure field mapping for this facility's exact export format and confirm manual parser mode is appropriate (LLM mode not required for standard MatrixCare exports). HIPAA BAA with AWS confirmed.
Parallel Run
First billing cycle run in parallel — the facility completed their manual Triple Check meeting as normal, and TripleCheck Pro ran simultaneously on the same documents. Every flag the platform raised was verified against the manual checklist. Results compared. Platform flags that the manual process missed were documented — establishing the value case for the team and building confidence in the automated results.
Live — Exception Review Only
From the third cycle, the Triple Check meeting shifted to exception review only. Upload, validate, review flags, submit. No spreadsheet cross-checking. No manual item-by-item verification of clean records. The process that once consumed most of a morning became a focused 45-minute team check-in on the specific issues TripleCheck Pro flagged.
Results
First full month of live operation. Billing errors identified before submission totalling over $300,000 — including the payer change catch from the TC-023 Change Log rule that the Director of Billing identified as the single most impactful outcome. The combination of TC-023 and the automated therapy minutes cross-check (TC-004) accounted for the majority of identified errors.
Change Log & Continuous Compliance
The billing coordinator maintains the structured Change Log throughout each billing cycle, capturing mid-month events as they occur rather than trying to reconstruct them at month end. TC-023 runs automatically against this log on every validation. The team's compliance posture shifts from reactive (discovering problems after denial) to proactive (eliminating problems before submission).
$300K in billing errors caught. Before a single claim went out.
The most important outcome was not the time saved — it was the type of errors found. The $300,000+ in billing errors identified in month one were not errors the team was making carelessly. They were errors that a manual process could not reliably catch: mid-cycle payer changes logged in one system but not reflected in another, therapy minutes discrepancies between MDS fields that different staff members referenced for the same value, physician recertification dates that sat in the wrong document type and were checked against the wrong field.
These are the errors that generate RAC audits. Not because they indicate fraud — but because they indicate a compliance process that cannot keep pace with the complexity of modern Part A billing. TripleCheck Pro makes that process systematic rather than person-dependent.
The 85% reduction in review time has a compounding benefit. Clinical staff who previously sat through three-hour meetings to verify records that turned out to be clean are now available for patient care during those hours. The meeting time that remains is genuinely productive — focused entirely on cases where clinical judgment is needed.
All metrics measured across the first full billing cycle post go-live. Billing error value calculated from identified claim issues that would have resulted in denials or incorrect payments if submitted as-is. Review time reduction measured against the facility's pre-TripleCheck Pro meeting duration. 0 known compliance gaps refers to exceptions reviewed and resolved before submission — not a guarantee against all possible CMS findings.
Errors caught before submission — claims corrected before they reached the payer. Revenue protected rather than pursued through denial management.
Exception review only. No manual verification of records the system confirmed as clean. Clinical staff attendance only needed for flagged cases.
All 22 standard QRM Triple Check elements plus TC-023 (Change Log cross-reference) — the proprietary rule that catches mid-cycle events no manual checklist can reliably surface.
Every exception flagged by the system is reviewed and resolved before submission. The facility's compliance posture is now proactive rather than reactive.
What EHRs, billing software, and generic tools cannot do — and why
TripleCheck Pro fills a compliance gap that exists specifically because no existing tool was built to fill it. Here is what each incumbent does — and does not do:
Generates the UB-04 from its own data. Does not validate the UB-04 against the MDS — these are separate data entry processes. Does not cross-reference mid-cycle events against the claim.
Cross-references UB-04 fields against MDS source fields for every rule that requires cross-document validation. Catches the discrepancies EHR auto-population misses because the source data was wrong when entered.
Validates claim format and payer-specific edits at submission time. By that point the claim is already built — a format-valid claim with wrong therapy minutes or a missed payer change passes clearinghouse checks and reaches the payer.
Runs before the claim is submitted — at the document review stage, not at the transmission stage. Errors are caught when they can be corrected in minutes, not after a denial that requires 30–60 days to resolve.
Cannot systematically track mid-cycle events across 20+ patients. Fatigue causes later checklist items to receive less scrutiny. Knowledge walks out the door with staff turnover. No audit trail of what was checked.
Every check runs to the same standard for every patient every cycle. TC-023 creates a formal record of mid-cycle events. Audit logs document every validation run. Staff turnover does not affect compliance quality.
Pre-submission billing validation is a market gap — not a solved problem
Every SNF in the US that bills Medicare Part A is required to perform a Triple Check before submitting claims. CMS guidance has required it since 1994. The market has produced sophisticated EHRs, billing platforms, and RCM tools — but none of them are built to do what the Triple Check meeting was doing manually:
TripleCheck Pro's competitive advantage is not technology sophistication — it is vertical focus. The platform does one thing for one workflow, and does it completely. That focus is why SNFs adopt it without an integration project: it works with the documents they already produce, for the process they are already required to perform.
Built for HIPAA compliance and enterprise SNF requirements — by design
HIPAA BAA Executed
AWS Business Associate Agreement
AES-256 Encryption
PHI at rest — AWS S3
TLS in Transit
All API and document transfers
Role-Based Access Control
Billing, Clinical, Administrator roles
JWT Authentication
bcrypt password hashing
Audit Logging
Every validation run logged — AWS CloudWatch
Google Workspace BAA
Staff communications covered
Multi-Facility Architecture
Per-facility data isolation
No EHR Integration Required
PDF upload — no API access to EHR
HIPAA Workforce Agreement
Required for all staff with PHI access
Explore related Metricoid capabilities
Healthcare RCM Automation
Custom automation for billing workflows across payer types — from pre-authorization through denial management and remittance reconciliation.
Custom AI & NLP Solutions
Bespoke AI systems trained on your organization's data — for healthcare organizations that need models that understand their specific workflows, payers, and documentation patterns.
Skilled Nursing Facilities
See how Metricoid serves SNF operators — from individual facilities to multi-location networks — across billing compliance, care coordination, and operational automation.
See your compliance results before your next billing cycle.
Request a 30-minute demo. Upload a real UB-04 and MDS sample — we will run all 23 rules live and show you exactly what TripleCheck Pro would flag in your facility's claims.
