The Inpatient Rehabilitation Facility Patient Assessment Instrument, known as the IRF-PAI, sits at the center of both IRF payment and IRF audit exposure. Every IRF claim is grouped into a case mix group based on data collected through the IRF-PAI — the patient’s impairment group code, functional status scores, age, and comorbidities — meaning that any error in how this instrument is completed and coded translates directly into a payment classification error, not merely a documentation footnote. Because IRF-PAI data drives payment so directly, it has become a natural focus for Targeted Probe and Educate (TPE) reviews conducted by Medicare Administrative Contractors and for Recovery Audit Contractor (RAC) review of case mix group accuracy.
This article explains how the IRF-PAI feeds into case mix group assignment and payment, the specific coding accuracy issues that most frequently draw TPE and RAC attention, the documentation elements that support defensible IRF-PAI coding, and how IRFs should structure their response when this coding is challenged. It closes with how HealthBridge US supports IRFs defending IRF-PAI coding accuracy under Medicare audit.
How the IRF-PAI Drives Payment
The IRF-PAI is completed for every Medicare Part A IRF patient, with data collected during the initial days of the admission capturing the patient’s impairment group, functional status using standardized assessment items, age, and relevant comorbidities. This data feeds directly into the IRF PPS Grouper, which uses it to assign the patient to a case mix group, or CMG — a classification designed to group together patients expected to require similar intensity of rehabilitation resources. The CMG assignment, along with any applicable comorbidity tier adjustment, determines the specific payment rate the IRF receives for that patient’s stay.
Because payment flows directly and mechanically from the coded IRF-PAI data, coding accuracy in this instrument is not a peripheral administrative task — it is functionally equivalent to DRG coding accuracy in the acute care hospital setting, carrying the same direct connection between documentation, coding, and payment. This also means that IRF-PAI coding errors, whether they result in overpayment or underpayment, are precisely the kind of systematic, data-verifiable issue that TPE and RAC reviews are specifically designed to identify.
Common Coding Accuracy Issues That Draw Audit Attention
Impairment group code selection is one of the most frequently scrutinized elements of IRF-PAI accuracy, since the impairment group code selected must accurately reflect the primary condition necessitating the intensive rehabilitation stay, and this single code has a substantial effect on CMG assignment. A pattern of impairment group coding that consistently selects a higher-weighted code than the clinical documentation clearly supports, or that does not align with the same diagnosis information reported on the corresponding UB-04 claim, is a common trigger for both TPE probe selection and RAC review.
Functional status scoring is a second area of sustained attention. The functional assessment items completed on the IRF-PAI are intended to reflect the patient’s actual level of independence or need for assistance at the specific assessment timepoints defined by CMS, and reviewers examine whether the scores recorded are consistent with the narrative clinical documentation describing the patient’s functional status — nursing and therapy notes, in particular — during the same period. A pattern of functional status scores that consistently reflect greater impairment than the corresponding clinical notes describe can suggest a scoring practice designed to influence CMG assignment rather than to accurately reflect the patient’s actual status.
Comorbidity coding, which can move a patient into a higher-paying comorbidity tier when a qualifying secondary condition is present, requires the same clinical substantiation applied to comorbidity or complication coding in the acute care DRG context: the comorbidity must be clinically evident and actively managed during the stay, not simply present in the patient’s history without evidence of active treatment or monitoring during the IRF admission itself. Reviewers specifically test whether comorbidities coded for tier adjustment purposes are genuinely supported by the medical record’s evidence of active management.
The Dual Coding Burden: IRF-PAI and UB-04 Consistency
IRF coding staff face a distinctive challenge not present in most other post-acute settings: the same clinical encounter must be coded twice, once for the IRF-PAI assessment instrument that drives CMG assignment, and once for the UB-04 institutional claim that reflects standard ICD-10-CM diagnosis coding. These two coding processes draw on the same underlying medical record but serve different classification systems, and inconsistency between the two — for example, an impairment group code on the IRF-PAI that does not align with the principal diagnosis reported on the UB-04 — is a specific pattern that reviewers examine closely, since it can indicate either a coding error in one of the two systems or documentation that does not clearly and consistently support a single, coherent clinical picture.
IRFs should build a coding quality assurance process that specifically reconciles IRF-PAI and UB-04 coding for the same encounter before both are finalized, rather than treating the two coding processes as entirely separate workflows handled by different staff with no cross-verification step.
Documentation Elements That Support Defensible IRF-PAI Coding
Defensible impairment group coding requires clinical documentation that clearly establishes the primary condition necessitating the IRF admission, consistent with both the preadmission screening and the physician’s ongoing assessment throughout the stay. Defensible functional status scoring requires that therapy and nursing documentation, recorded at or near the same assessment timepoints defined for IRF-PAI purposes, provide a clear, objective basis for the specific scores recorded — the assessment should not stand alone as an isolated data point disconnected from the narrative clinical record describing the patient’s actual functional performance during therapy sessions and daily activities.
Defensible comorbidity tier coding requires documentation of active management for any comorbidity relied upon for tier adjustment — medication changes, monitoring, or treatment specifically directed at that comorbidity during the IRF stay, rather than a comorbidity that appears only in the patient’s past medical history without evidence of active clinical attention during the admission being billed.
Building an Effective TPE or RAC Response
When a MAC issues a TPE probe notice or a RAC issues a request for documentation supporting IRF-PAI coding, the response should assemble the complete IRF-PAI assessment alongside the underlying clinical documentation supporting each coded element at issue — the preadmission screening and physician documentation supporting the impairment group code, the therapy and nursing notes supporting the functional status scores recorded, and the specific clinical documentation of active management for any comorbidity coded for tier adjustment. The response narrative should address each coding element individually, connecting the specific IRF-PAI data point to the corresponding clinical documentation, rather than submitting the assessment and medical record without an organizing explanation connecting the two.
For TPE reviews specifically, IRFs should use the individualized education provided after each review round to correct systemic coding patterns — for example, a consistent pattern of functional status under-scoring by a specific assessing clinician — before the review proceeds to additional rounds or escalates to broader contractor involvement. Response timelines for RAC-issued requests generally follow the standard 30- to 45-day Medicare ADR framework.
Coordinating a Response When TPE and RAC Reviews Overlap
Because a MAC’s TPE program and a nationwide RAC review can both examine IRF-PAI coding accuracy at the same facility, sometimes for different reasons and on different timelines, IRFs benefit from tracking both types of inquiry together rather than treating them as unrelated correspondence. A documentation gap identified during a TPE round — for example, a pattern of functional status scores inconsistent with therapy documentation for a specific assessing clinician — is often the same underlying issue a RAC would identify independently if it selected a broader sample of the same facility’s claims. Addressing that pattern once, through consistent clinician education and a strengthened quality assurance review, is more effective than responding to each contractor’s request as an isolated event that leaves the same systemic issue unaddressed for the next reviewer to find.
Building Proactive IRF-PAI Coding Accuracy
IRFs that experience fewer IRF-PAI coding denials generally implement a structured internal quality assurance review comparing a sample of completed IRF-PAI assessments against the underlying clinical documentation on a regular basis, specifically testing impairment group selection, functional status scoring consistency, and comorbidity tier substantiation. Reconciliation between IRF-PAI and UB-04 coding for the same encounter, performed before both are finalized, catches inconsistencies while they can still be corrected rather than after a claim has been billed. Ongoing training for the clinicians completing functional status assessments — emphasizing that scores must reflect genuine, objectively observed performance rather than a general clinical impression — addresses one of the more subjective and therefore vulnerable elements of IRF-PAI accuracy.
The Role of the CMG Coordinator
Many IRFs designate a specific individual — often referred to as the Case Mix Group Coordinator — responsible for ensuring the accuracy and completeness of IRF-PAI data before submission. This role carries significant weight given how directly IRF-PAI data drives payment, and IRFs benefit from treating it as a genuine quality assurance function rather than a purely clerical data-entry responsibility. An effective CMG Coordinator reviews completed assessments against the underlying clinical documentation before submission, flags inconsistencies between the assessing clinicians’ scores and the narrative clinical record for follow-up before the assessment is finalized, and maintains a working relationship with therapy, nursing, and physician staff that allows for timely clarification when documentation and assessment data do not clearly align. IRFs that treat this role as a full quality assurance function — with the authority and time allocated to actually query clinicians and request clarifying documentation before finalizing an assessment — tend to have meaningfully fewer downstream coding accuracy findings than facilities that treat IRF-PAI completion as a final administrative step with no substantive review built in.
How HealthBridge US Supports Your Inpatient Rehabilitation Facility
IRF-PAI coding accuracy connects directly to case mix group assignment and payment, making it functionally equivalent to DRG coding accuracy in the acute care setting and an increasingly common focus of TPE and RAC review. HealthBridge US supports Inpatient Rehabilitation Facilities with IRF-PAI coding accuracy audits, IRF-PAI and UB-04 reconciliation review, functional status scoring and comorbidity tier documentation support, and TPE and RAC response preparation. If your IRF is facing a TPE review or RAC audit of IRF-PAI coding, or wants to strengthen coding accuracy and CMG Coordinator quality assurance processes proactively, HealthBridge US is here to help — contact our team to discuss your IRF-PAI coding accuracy and audit defense needs across every reviewing contractor your facility may face.
References
• Centers for Medicare & Medicaid Services. “IRF-PAI.” https://www.cms.gov/medicare/payment/prospective-payment-systems/inpatient-rehabilitation/pai
• Centers for Medicare & Medicaid Services. “IRF Grouper - Case Mix Group (CMG).” https://www.cms.gov/medicare/payment/prospective-payment-systems/inpatient-rehabilitation/grouper-case-mix-group
• Centers for Medicare & Medicaid Services. “Inpatient Rehabilitation Facility (IRF).” https://www.cms.gov/files/document/inpatientrehabilitationfacilityrefbooklet2pdf.pdf
• Centers for Medicare & Medicaid Services. “TPE QAs.” https://www.cms.gov/files/document/tpe-qas-12-27-2017pdf
• Centers for Medicare & Medicaid Services. “Medicare Fee for Service Recovery Audit Program.” https://www.cms.gov/data-research/monitoring-programs/medicare-fee-service-compliance-programs/medicare-fee-service-recovery-audit-program
• Centers for Medicare & Medicaid Services. Medicare Claims Processing Manual, Chapter 29 (Appeals). https://www.cms.gov/regulations-and-guidance/guidance/manuals/downloads/clm104c29.pdf
HealthBridge US is here to help. Our audit specialists support Inpatient Rehabilitation Facilities with IRF-PAI coding accuracy review and TPE/RAC audit defense — contact us to protect your facility’s reimbursement.
