In-House vs. Outsourced IRF Coding: What Facilities Should Weigh

By: Tonya Bachmeier, RHIA, CDIP, CCS

Rehab/IRF Coding Consultant

Once a facility recognizes an IRF coding gap, the next question is usually practical: build the expertise in-house, or bring in outside support? There’s no universal right answer, but there is a useful way to think through it.

The Case for Building In-House Expertise

Facilities with a stable, long-tenured coding team sometimes prefer to invest in training rather than adding an outside vendor to the mix. This keeps institutional knowledge concentrated internally and can work well when there’s enough IRF volume to keep coders’ tier-coding skills genuinely sharp — skills that erode if they’re only used occasionally.

The tradeoff is time and ongoing maintenance. Training isn’t a one-time event; CMS updates the tier-comorbidity list, CMG weights, and the IRF-PAI Manual itself on a recurring basis (the current manual, Version 4.4, took effect for FY 2026). Someone needs to own staying current on those changes, and that responsibility doesn’t disappear once initial training is complete.

The Case for Outsourced Coding

Outsourcing to coders who specialize specifically in IRF work — rather than acute-care coders covering IRF as a secondary responsibility — addresses the specialization problem directly. It also removes the burden of tracking CMS’s periodic tier and CMG updates from internal staff. The tradeoff is less direct day-to-day control and the need to vet a vendor’s actual IRF-specific expertise rather than general coding credentials; not every coding vendor that lists “hospital coding” as a service has genuine depth in IRF-PAI and tier logic specifically.

The Middle Ground: Auditing and Training Without Full Outsourcing

Facilities don’t have to choose between the two extremes. A periodic outside audit — even without ongoing outsourced coding — can validate whether in-house coding is capturing tier opportunities correctly and staying aligned with the 60% Rule’s requirements under 42 CFR 412.29(b)(2). Paired with targeted training for existing staff, this approach builds internal capability while still bringing in specialized IRF expertise where it matters most: catching what an internal team, close to its own work, might not see on its own.

A Framework for the Decision

Rather than treating this as a binary choice, it helps to separate the underlying needs: ongoing coding capacity, periodic quality assurance, and staff development are three distinct functions that don’t have to be sourced the same way. A facility might fully outsource coding capacity while keeping quality assurance internal, or vice versa — the right combination depends on volume, staffing stability, and how confident leadership already is in current coding accuracy.

Questions Worth Asking Before Deciding

• How much IRF-specific volume does the facility actually handle, and is it enough to keep in-house skills sharp?
• Who currently owns tracking CMS’s tier, CMG, and IRF-PAI Manual updates, and how reliably does that happen?
• When was coding accuracy last independently audited against IRF-specific standards, rather than general coding QA?
• Would training existing staff, an outside audit, or full outsourcing address the actual gap identified?

CBS offers all three paths — coding, auditing, and training — so facilities can start with an assessment and choose the model that fits, rather than committing to full outsourcing as the only option.

Frequently Asked Questions

Is outsourcing always more accurate than in-house IRF coding?

Not automatically — it depends on the vendor’s actual depth of IRF-specific expertise. A vendor with genuine CMG and tier-coding specialization will generally outperform a stretched or under-trained in-house team, but a well-trained, high-volume in-house team can perform just as well.

Can a facility outsource just auditing without outsourcing coding itself?

Yes. Periodic outside auditing paired with internal coding and training is a common middle-ground approach that many facilities use before committing to full outsourcing.

How much IRF volume justifies keeping coding fully in-house?

There’s no fixed threshold, but the underlying question is whether volume is high enough and consistent enough to keep coders’ tier-coding skills genuinely current — low, sporadic volume makes it harder to maintain sharp in-house expertise regardless of team size.