IRF Auditing Services: What a Thorough Audit Actually Catches
By: Tonya Bachmeier, RHIA, CDIP, CCS
Manager, Inpatient Rehab Coding
Tonya brings 8+ years of specialized IRF coding experience across multiple health systems and EHR platforms, with hands-on expertise in rehab chart coding, coder training, and IRF-PAI compliance.
In eight years of auditing, coding, and training coders across IRF settings — different health systems, different EHR platforms, different documentation cultures — I’ve learned that the gaps I find almost never look like mistakes. They look like clean, technically defensible coding that’s quietly leaving money and compliance protection on the table.
That’s the case for treating IRF auditing as a distinct discipline, not a variation on general coding audits. Here’s what I actually look for, and why.
Why an IRF Audit Isn’t a Standard Coding Audit
A general inpatient coding audit checks whether diagnosis and procedure codes are supported by documentation. An IRF audit has to do that too, but it’s checking something else at the same time: whether the case’s Case-Mix Group and comorbidity tier reflect the full clinical picture, and whether the IRF-PAI and UB-04 are telling the same story. Those two documents answer to different parts of CMS’s regulatory structure — the IRF PPS payment rules and the IRF Quality Reporting Program — and I’ve seen plenty of charts where both are individually clean but inconsistent with each other.
What I Actually Review
- Tier assignment — checked against the current tier-comorbidity list, not an acute-care coder’s MCC/CC instinct
- Documentation support — is the documentation specific enough to defend a tier-qualifying diagnosis, or is it there but too vague to code confidently?
- IRF-PAI/UB-04 alignment — do the diagnosis codes on the IRF-PAI match what’s on the UB-04, and if not, why not?
- Facility-level compliance — in aggregate, does the facility’s diagnosis coding pattern support its 60% Rule position, or is that number softer than anyone realizes?
- Query patterns — is the volume and pattern of physician queries what I’d expect given the documentation I’m seeing, or is the coding team under-asking?
The Pattern I See Most Often
Across different facilities, the single most common finding isn’t a wrong code — it’s a right code that was never assigned, because the documentation supporting it existed but wasn’t queried or wasn’t recognized as tier-relevant. This happens most with coders who come from acute-care backgrounds and are applying MCC/CC instincts to a system that doesn’t use them. It’s not a competence problem. It’s a training gap, and it’s a completely fixable one once it’s identified.
What a Facility Actually Gets From an Audit
An audit report is only useful if it tells you what to do next, not just what went wrong. When I complete an IRF audit, I prioritize findings into two categories: issues affecting individual claim reimbursement, and issues with facility-level compliance implications — particularly anything touching 60% Rule risk, since that’s a different order of urgency than a single undercoded claim. From there, the recommendation is usually one of three things: targeted coder training, a documentation workflow adjustment with the PPS Coordinator and clinical team, or, less often, a deeper look at how queries are being handled.
Why This Matters Beyond the Audit Itself
An audit is a snapshot, not a fix. The facilities that see lasting improvement are the ones that pair an audit with follow-through — training the coding team on what the audit found, and building a habit of periodically checking tier accuracy and 60% Rule alignment rather than waiting for the next external review to surface a problem. That ongoing partnership is what I’m building out at CBS: not a one-time audit and a report that sits in a drawer, but a standing relationship that keeps IRF coding accurate as CMS’s tier list, CMG weights, and IRF-PAI requirements continue to evolve.
If you’re not sure where your facility’s IRF coding actually stands, I’d welcome the conversation — no pressure, just an honest second look.
— Tonya
Frequently Asked Questions
What does a CBS IRF audit actually review?
A CBS IRF audit reviews IRF-PAI and UB-04 coding accuracy, tier assignment against current comorbidity guidance, documentation support for coded conditions, and aggregate diagnosis coding patterns against the 60% Rule’s qualifying categories.
How long does an IRF audit typically take?
Timeline depends on chart volume and scope, but CBS typically starts with an initial sample review to identify patterns before scaling to a fuller audit — so facilities get early signal without committing to a lengthy process upfront.
Does an audit include recommendations, or just findings?
Both. A CBS audit report identifies specific gaps and also prioritizes them — distinguishing between issues affecting individual claim reimbursement and ones with facility-level compliance implications, like 60% Rule risk.
Can an audit happen without switching our coding vendor?
Yes. An IRF audit is an independent review and doesn’t require outsourcing coding itself — many facilities use it as a standalone check on their current team’s accuracy, whether that team is internal or already outsourced elsewhere.