IRF-PAI vs. UB-04: Understanding Dual Coding Responsibility
By: Tonya Bachmeier, RHIA, CDIP, CCS
Rehab/IRF Coding Consultant
Most hospital coding roles center on a single claim form. IRF coding is different: coders are responsible for two distinct documents that serve two distinct purposes and answer to two different parts of CMS’s regulatory structure — the IRF-PAI & UB-04.
The IRF-PAI: The Assessment That Drives Payment
The IRF-PAI (Patient Assessment Instrument) is a functional and clinical assessment required for every Medicare Part A fee-for-service and Medicare Part C patient discharged from an IRF. It captures the impairment group, functional and motor scores, comorbidities, and other data points that CMS uses to assign the Case-Mix Group and comorbidity tier — the core determinants of how much the stay is reimbursed. CMS governs the IRF-PAI through a dedicated manual (currently Version 4.4, effective for FY 2026) that provides item-by-item coding instructions and examples specifically to standardize how facilities complete it.
Getting the IRF-PAI coded accurately isn’t a secondary task; it’s the document that establishes payment before the claim itself is even submitted, and it also feeds the IRF Quality Reporting Program (QRP), which ties into separate CMS quality measure and reporting obligations beyond payment alone.
The UB-04: The Claim Form
The UB-04 is the institutional claim form submitted to Medicare for payment — familiar territory for any hospital coder, since it’s used across acute care as well. But in an IRF context, the UB-04 has to align with what was captured on the IRF-PAI. A mismatch between the two — a diagnosis reflected on one but not the other, for example — creates exactly the kind of inconsistency that draws payer scrutiny, and can complicate both individual claim adjudication and facility-level 60% Rule compliance calculations, which draw on the same underlying diagnosis data.
Why This Combination Is an Unusual Skill Set
Coders typically specialize in one workflow or the other: functional/clinical assessment coding, or claims coding. IRF coding asks for both, plus the ability to keep them consistent with each other across two different CMS regulatory frameworks — the IRF PPS payment rules governing the UB-04, and the IRF QRP governing the IRF-PAI. This is part of why treating IRF coding as “regular coding, just for a different setting” underestimates what the role actually requires — it’s less like assigning one more coder to a familiar task, and more like combining two coding specialties into a single, tightly coordinated workflow.
What This Means for Staffing
Facilities evaluating their coding team’s IRF-readiness should ask specifically whether coders are comfortable and accurate on both documents, not just one. A coder who’s confident on the UB-04 but unfamiliar with IRF-PAI-specific data capture is only half-equipped for the role — and the half that’s missing is the half that determines payment in the first place.
CBS’s IRF coding services cover both the IRF-PAI and UB-04, with training available for facilities that want their existing staff to build competence across both.
Frequently Asked Questions
Is the IRF-PAI required for every IRF patient?
It’s required for every Medicare Part A fee-for-service and Medicare Part C patient discharged from an IRF, per CMS’s IRF Quality Reporting Program requirements.
What happens if the IRF-PAI and UB-04 don’t match?
Inconsistencies between the two documents can trigger payer scrutiny, complicate claim adjudication, and potentially distort facility-level compliance calculations, such as the 60% Rule, that rely on consistent diagnosis data.
Does the IRF-PAI affect anything besides payment?
Yes. Beyond driving CMG and tier assignment, the IRF-PAI also feeds CMS’s IRF Quality Reporting Program (QRP), which governs separate quality measure reporting obligations.
Call us today at: 610-442-2346 or e-mail us at: info@codingbillingsolutions.com