5 Signs Your Coding Team Isn’t IRF-Ready
By: Tonya Bachmeier, RHIA, CDIP, CCS
Rehab/IRF Coding Consultant
IRF coding gaps rarely show up as an obvious error. More often, they show up as a slow, hard-to-pin-down pattern — reimbursement that feels lower than it should, denials that don’t quite make sense, or a 60% Rule number that no one’s fully confident in. Here are five practical signs worth paying attention to, and why each one matters.
1. Coders Are Applying MCC/CC Logic to IRF Charts
If your coders are evaluating comorbidities using the same major/standard complication hierarchy they’d use for acute-care DRG coding, they’re working from the wrong framework. IRF tier coding uses its own list of qualifying conditions — MCC and CC status, as defined in acute care, isn’t part of that system. This is often the single most common gap, because it’s invisible on the surface: the claim still processes, it just doesn’t reflect the tier the documentation could have supported.
2. Nobody Can Say When the Tier-Comorbidity List Was Last Reviewed
CMS updates the tier-comorbidity list and CMG relative weights periodically, alongside broader IRF-PAI Manual revisions (the current version, 4.4, took effect for FY 2026). If your team can’t point to when they last reviewed the current list, there’s a real chance they’re coding against an outdated one — quietly missing tier opportunities that would otherwise be available.
3. IRF-PAI and UB-04 Data Don’t Always Match
Since IRF coders are responsible for both documents, inconsistency between them is a direct signal of a workflow gap — whether that’s a training issue, a communication issue between whoever completes each document, or simply unfamiliarity with how the two are supposed to align under CMS’s dual regulatory framework for IRF PPS payment and the IRF QRP.
4. Physician Queries Related to Tier-Qualifying Conditions Are Rare or Nonexistent
Tier coding often depends on documentation that isn’t automatically clear-cut. A coding team that’s genuinely engaged with tier opportunities will generate physician queries when documentation is ambiguous but a qualifying condition seems plausible. A near-total absence of these queries can mean either documentation is unusually clean, or coders aren’t looking closely enough to know what to ask about — and in practice, the second explanation is far more common than the first.
5. No One Owns 60% Rule Monitoring as an Ongoing Process
If 60% Rule compliance is checked reactively — mainly when a Medicare Administrative Contractor review is already underway — rather than monitored as a routine part of coding and compliance workflows, that’s a structural gap, not just a coding one. Given that MAC determinations happen annually and apply for a full cost reporting period, reactive monitoring means a facility can be out of compliance for months before anyone notices.
What to Do Next
None of these signs on their own proves a problem. Together, they’re worth an honest look — starting with a sample chart review to see how current coding practices actually compare to IRF-specific standards. CBS offers exactly that kind of initial assessment, along with the coding, auditing, and training services to close whatever gaps it finds.
Frequently Asked Questions
What’s the fastest way to check if these signs apply to our facility?
A sample chart audit comparing a handful of recent IRF-PAI and UB-04 pairs against current tier-comorbidity guidance is usually the quickest, most concrete way to see whether these patterns are present.
Does a low physician query rate always indicate a problem?
Not always — some facilities genuinely have very clean, complete documentation. But combined with the other signs on this list, a near-zero query rate is worth investigating rather than assuming it reflects clean charts by default.
How quickly can these gaps be corrected once identified?
Coding-level gaps can often be addressed relatively quickly through targeted training, while facility-level issues like 60% Rule drift may take a full cost-reporting cycle to fully resolve, since MAC compliance determinations are annual.
To laern mora about IRF coding, call us today at: 610-442-2346 or e-mail us at: info@codingbillingsolutions.com