Clinical documentation improvement
Keep
- Queries work when the specialist knows the attending
- Outsource the regroup analytics that say where to look
Guide · Hospital revenue cycle outsourcing
Hospital RCM: what to outsource first, and what to keep
Short answer: argue the deal as a sequence, not a scope. Move the function whose output you can count, whose handoff fits in a file layout, and whose failure you would see within 30 days. Keep everything that touches a physician or a patient at the bedside.
1. Aged insurance follow-up2. Denials and appeals3. Eligibility and authorizationKeep: CDI, charge capture, UR, access
Edition
Oct 2026
Focus
Hospital RCM outsourcing
Audience
CFO · VP revenue cycle
Archetype
Under 300 beds
Metric
48.2% name denials the top threat
Length
6 min read
48.2%greatest threat
Executives naming commercial denial volume the greatest threat to the revenue cycle [2]
37.6%top barrier
Naming difficulty prioritizing which denials to work as the biggest recovery barrier [2]
61.0%hardest to staff
Expecting appeal writing to be the hardest denials role to staff over three years [2]
83.0%slower appeals
Saying commercial payers take longer to process appeals than three years ago [2]
Greatest threat to the revenue cycle, share of respondents
A community hospital rarely needs a full outsourcing contract on day one; it needs one handoff that measurably pays for itself inside a quarter.
HFMA survey of 172 hospital and health system executives, fielded late 2024
Those are workflow problems before they are staffing problems [2].
Volume of denials from commercial insurers
48.2%greatest threat
Declining reimbursement rates
21.6%
Prior authorization issues
14.4%
Insufficient analytics
4.3%
Labor shortages
3.6%
0%10%20%30%40%50%
DenialsOther threats
Takeaway
Outsource the function whose output you can count, whose handoff you can define in a file layout, and whose failure you would see within 30 days. That rules the order below.
Hospital RCM outsourcing, in the order the handoffs can be proven
For hospitals under 300 beds. Each step needs a daily file from the host system, a shared work queue with named ownership, and a weekly reconciliation of the vendor's numbers to the hospital's own.
Aged insurance follow-up
First, 30 to 60 days
- Insurance AR over 90 days by payer
- The file is a claim list, the output is cash and closed accounts, the baseline is yesterday's aging
Eligibility, benefits and authorization
Third, 30 days
- Runs on transactions: 270/271, authorization portals
- Countable result: verified before service, authorized before service
Coding overflow and DNFB relief
Fourth, 90 days
- Outpatient first, then inpatient with a documented accuracy sample
- Moves only when MS-DRG accuracy can be measured
Payment posting and underpayment review
Fifth, 30 to 60 days
- Electronic remittance posting plus contract-variance review
- Measurable against the 835 and the contract
Everything that touches the physician
Stays in-house
- CDI, charge capture, utilization review, patient access
- Vendor supplies analytics, not staff
The people who talk to physicians and patients, and why
Charge capture at the point of care
Keep
- A departmental discipline; a vendor can audit it, nursing and ancillary leaders fix it
Utilization review and status
Keep
- Inpatient versus observation is a clinical judgment with regulatory weight; it belongs to the physician advisor
Patient access and the front desk
Keep
- Registration quality drives everything downstream; let the vendor supply the eligibility results
Payer contracting
Keep
- The hospital signs; the vendor models the contracts and finds the underpayments
Compliance and privacy
Keep
- Policy, audit response and the business associate framework stay inside
The metrics that prove the handoff worked
54.7% of executives can see payer trends but cannot identify root causes, and 23.9% cannot see the trends [2]; a vendor who cannot show root cause has not earned the next function. Our rural hospital case study shows a 15 percent gross collection rate pitched against a 9.5 percent ceiling in the actual payer mix: set the metric from the data.
| Function | Primary metric | Secondary metrics | Proof window |
|---|---|---|---|
| Aged insurance follow-up | Cash collected on the transferred inventory | Accounts closed, untouched AR over 60 days, touches per claim, median claim-to-remit days | 30 to 60 days |
| Denials and appeals | Overturn rate and dollars recovered by payer and denial category | Appeal cycle time, first-pass denial rate trend, write-offs by root cause | 60 to 90 days |
| Eligibility and authorization | Share of scheduled visits verified and authorized before service | Eligibility denials, authorization denials, registration rework | 30 days |
| Coding overflow | Coding accuracy on a blind sample (MS-DRG, severity, principal diagnosis) | Coding turnaround, DNFB days, coding-related denials | 90 days |
| Payment posting and underpayments | Unposted cash aging and variance dollars recovered | Posting lag, contract variance by payer | 30 to 60 days |
Two clocksMeasure the same receivable by date of service and by first-bill date; a bucket old by service date may have been re-billed last week
Every touch countsA submitted record with a documented outcome, so "worked" means something
Incremental cashSeparate what the vendor collected on transferred accounts from what the hospital would have collected anyway
Six terms that protect the sequence
A written service level per functionMetric, baseline and measurement source named in the contract.
A shared work queue the hospital can seeNamed ownership for every account and an audit trail of every action.
Monthly reconciliation signed by both sidesVendor-reported cash to the hospital's posted cash.
A 90-day proof window per functionBefore the next function moves.
Data return and knowledge transferIf the hospital brings a function back in-house.
BAA and access controls reviewed firstBy the hospital's compliance officer, before the first file.
Takeaway
The agreement should make the next step conditional on the last one's proof. Short terms, published numbers, and the right to take a function back without penalty keep both sides honest.
Three moves before any vendor call
Pull insurance AR over 90 days by payerYesterday's aging is the baseline for the first handoff.
Name the daily file and the queue ownerHost-system extract, shared work queue, weekly reconciliation; our revenue cycle command center puts every response, denial and follow-up action in a named queue, and Work Genie records each touch with a quality-control sample behind it.
Read before you outsource codingWhat autonomous inpatient coding covers; also this month's Hospital Cash Cycle, the MRF self-audit and the denial reduction engagement pattern.
Frequently asked questions
What should a hospital outsource first in revenue cycle?
Aged insurance follow-up, usually insurance AR over 90 days by payer. It has the clearest file, the clearest output (cash and closed accounts) and the fastest proof window, which makes it the right place to test a vendor before moving denials, front-end verification or coding.
What should stay in-house?
Functions that touch physicians and patients directly: clinical documentation improvement, charge capture at the point of care, utilization review and patient status, patient access, payer contracting and compliance. A vendor can supply analytics and audits for these; the hospital keeps the people.
How do we know an outsourced function is working?
Agree the baseline and the metric before the first file, measure weekly, and reconcile the vendor's report to the hospital's own system monthly. For follow-up that is cash on the transferred inventory; for denials it is overturn rate and dollars by payer; for coding it is accuracy on a blind sample.
How long should the proof window be before moving the next function?
Thirty to ninety days depending on the function, written into the contract. Follow-up and front-end work can show results in 30 days; denials and coding need 60 to 90 because appeals and audits take time to resolve.
- HFMA: Revenue Cycle Claims, Denials and Appeals Research Report (survey of 172 hospital and health system executives, published July 2, 2025)
- HFMA: Revenue Cycle Claims, Denials, and Appeals Survey Summary Report (fielded November 13 to December 9, 2024)
Those are workflow problems before they are staffing problems [2].
Want the first handoff priced on your own aging?
Send us your insurance AR over 90 days by payer and we return the baseline, the proof metrics and a written service level for the first function, with no commitment to the second.