Healthcare Revenue Cycle Intelligence Series Post 4 of 5 April 04, 2026 |Bob Klein

Payers Have Industrialized Denial. Here's How Providers Fight Back -- Systematically.

Diagram showing seven intervention points across the revenue cycle where AI prevents claim denials

Key takeaway: As many as 60% of denials are never appealed. The only response that changes the economics is intelligence applied at all seven stages of the revenue cycle -- before the denial happens when possible, and with the specific CMS documentation to fight it when it happens anyway.

McKinsey estimates healthcare revenue cycle costs the industry more than $140 billion annually. Sitting inside that number is a specific, structural loss that is almost entirely preventable: revenue that gets denied, never appealed, and written off -- not because the denial was valid, but because no one had the time or the data to fight it. As many as 60 percent of denials are never appealed. At a community hospital with $200 million in net patient revenue and a 20 percent denial rate, that could represent $14 million or more in uncontested write-offs every year.

$140B+

Annual industry RCM cost

60%

Denials never appealed

$14M+

Potential annual write-offs at $200M NPR

Payers have invested heavily in making sure that doesn't happen. Their adjudication systems are sophisticated, automated, and designed around a simple economic insight: a denial that is never appealed is free revenue. They just need to make the appeal process slow, expensive, and uncertain enough that most providers conclude the effort isn't worth it. For smaller and rural hospitals operating on thin margins, that calculus often comes out in the payer's favor. The hospital writes off the claim and moves on.

That dynamic is not going to fix itself. The only response that changes the economics is a systematic one -- intelligence applied at every stage of the revenue cycle, before the denial happens when possible, and with the specific CMS documentation needed to fight it when it happens anyway.

Seven places to intervene -- and why all seven matter

There is no single intervention point that solves the problem. Organizations that focus only on denial management improve their overturn rate but don't reduce their denial volume. Organizations that focus only on clean claim submission improve their first-pass rate but miss the upstream documentation and prior authorization issues that keep denial rates elevated. The HFMA revenue cycle framework maps seven distinct stages where intelligence makes a material difference, and all seven are connected.

Front end — pre-service
1
Registration & eligibility Surface payer constraints before care

Data sources

EHR demographics + payer/plan ID

Eligibility transaction (270/271)

Scheduled service codes

Intelligence output

Authorization required flag + deadline

Coverage limitation + network risk alert

CMS coverage check against plan rules

2
Prior authorization Submit correctly, on time, with justification

Data sources

Payer auth matrix for this plan

Clinical indication documentation

Submission deadline + ordering provider

Intelligence output

Auth criteria + clinical requirements list

Historical denial rate — missing auth

CMS: plan requires auth CMS doesn't — appeal rights surfaced

Middle — point of service
3
Clinical documentation & coding Prevent documentation-related denials at the source

Data sources

Diagnosis + procedure codes

Plan-level medical necessity criteria

Historical denial rate: payer + service

Intelligence output

Payer-specific denial risk flag with %

Specific code to add for medical necessity

Undercoding alert — comorbidity review

4
Utilization review Justify admission status and continued stay

Data sources

Admission status + projected LOS

Payer clinical necessity criteria

Concurrent review deadlines

Intelligence output

Inpatient status risk — specific criteria gap

LOS outlier vs payer DRG average

CMS: plan applying stricter standard — document for appeal

5
Discharge planning Align post-acute disposition with payer criteria

Data sources

Discharge disposition + functional status

Payer post-acute coverage rules

Prior auth status for post-acute service

Intelligence output

Post-acute denial risk — criteria gap

Clinical assessment required before referral

CMS qualifying criteria met — documentation path for appeal

Back end — post-service
6
Pre-bill review & claim submission Final risk assessment before the claim goes out

Data sources

Fully coded encounter

Auth record — status, dates, approvals

Prior denial history: this payer

Intelligence output

Claim risk score — confidence-rated

Predicted denial reason — top 1–3

CMS conflict check — appeal argument identified pre-submission

7
Denial management, appeals & learning Fight winnable appeals — every outcome feeds the model

Data sources

Clearinghouse remittance (835 ERA)

Denial reason codes (CARC/RARC)

Appeal submissions and outcomes

Intelligence output

Denial classification + appeal winnability

Appeal draft with CMS citation

Model update — pattern propagates to stages 1–6

The learning loop: every claim outcome — paid, denied, overturned — flows from the clearinghouse back into the intelligence layer, updating denial predictions across all seven stages for every future similar claim.

HFMA Revenue Cycle Standards · Digital Scientists · digitalscientists.com/healthcare/domains/revenue-cycle-ai/

Stages 1–2: front end — where the denial is often set in motion

Most denials don't originate in billing. They originate in registration and prior authorization. An eligibility check that doesn't surface a benefit limit at registration becomes a denial six weeks later that is genuinely hard to fight. A prior authorization submitted without the specific clinical criteria the plan requires — or submitted too late — produces a denial that may be impossible to overturn regardless of medical necessity.

The most important output of the intelligence layer at stage 2 isn't just "auth required." It's the specific clinical documentation the plan needs to approve the auth — drawn from that plan's actual criteria. And when a Medicare Advantage plan is requiring authorization for a service that CMS does not require, that's a specific, actionable fact that belongs in the auth submission and potentially in an appeal.

Stages 3–5: middle — where the money is made or lost at the point of care

The middle of the revenue cycle is where clinical decisions and financial consequences intersect most directly — and where most organizations have the least payer-aware intelligence. A physician documenting a diagnosis doesn't know that this specific payer denies that service at a 34 percent rate when paired with that diagnosis code. A case manager planning a discharge doesn't know that this payer requires a physical therapy assessment before it will approve the SNF stay — and that the CMS qualifying criteria for an appeal are already met if the documentation is right.

When an MA plan applies more restrictive criteria than the CMS standard — and they frequently do — the concurrent review record needs to document against the CMS standard so the appeal argument is built before the denial arrives. It's a matter of surfacing the right prompt at the right moment in the clinical documentation process.

Stages 6–7: back end — where AI gives providers the same data payers have

Pre-bill review is the last upstream opportunity before a claim enters the payer's adjudication system. A claim risk score — based on this payer's actual behavior with this claim configuration, not industry averages — lets the revenue integrity team make a data-driven decision about whether to hold the claim and fix something, or submit and prepare the appeal documentation.

And at stage 7, the learning loop closes. Every remittance file that comes back from the clearinghouse — every denial code, every payment amount, every appeal outcome — is signal data. The organization that has been running this system for twelve months knows its payers' denial behavior better than it did at the start. It files more appeals, wins more of them, and prevents more denials at the front end because the model has learned what actually gets paid.

The CMS thread that runs through all of it

The CMS rules most organizations aren't systematically using

CMS publishes National and Local Coverage Determinations that define exactly what is covered, for which diagnoses, under which conditions. Medicare Advantage plans are legally required to cover all services that traditional Medicare covers — they cannot apply internal criteria more restrictive than CMS standards as grounds for denial.

In practice, they do it constantly. They count on the fact that most hospitals won't identify the specific CMS rule the denial violates, won't cite it in the appeal, and won't have documentation structured to support the CMS standard. An intelligence layer that tracks NCD and LCD updates and surfaces the specific citation when an MA plan's denial contradicts a CMS standard changes that calculation entirely. The No Surprises Act creates additional appeal rights. The three-day qualifying stay rule protects SNF coverage. These aren't obscure regulations — they're public law. Using them systematically is an operational capability, not a legal strategy.

What this means for the CFO and COO

At $200 million net patient revenue, a 1.5 point improvement in cost to collect is $3 million annually. The investment is defensible because of sequencing -- you don't have to solve all seven stages simultaneously. Start with a Revenue Integrity Audit, find the two or three intervention points where the ROI is highest and the data is ready, generate the return inside a budget cycle, and use that proof point to fund the next phase.

The CFO question is always "how fast do we get paid back, and how do we know?" The answer has to be specific: a denial prediction model targeting your highest-volume payer, generating measurable improvement in first-pass rate within 90 days. Not a platform deployment. A targeted intervention with a measurable outcome.

Start here

Want to know where your revenue is leaking before we build anything?

We start every engagement with a Revenue Integrity Audit -- 2 to 4 weeks, 12 to 18 months of claims data, and a prioritized list of denial drivers ranked by dollars, not count.

Revenue Cycle Intelligence Series