10.5 Denials Management and Appeals

Denials as Feedback, Not Just Rework

Domain 4 includes denials management. A denial means a payer refused or delayed payment for a stated reason, usually communicated on the remittance advice via CARC (Claim Adjustment Reason Codes) and RARC (Remittance Advice Remark Codes). The RHIA task is not to chase every account blindly — it is to determine whether the denial reflects a documentation gap, coding error, charge problem, authorization issue, medical-necessity issue, payer-policy dispute, timely-filing problem, or payer processing error.

Classify Before You Work

Two classification axes drive strategy:

• Hard vs. soft denial. A hard denial results in lost revenue unless overturned on appeal (e.g., medical necessity, no authorization). A soft denial is temporary and correctable without a formal appeal (e.g., missing information, a resubmittable claim error).
• Front-end vs. back-end. Front-end denials originate before/at service (registration, eligibility, prior authorization); back-end denials arise from coding, documentation, or medical necessity. Front-end fixes are usually cheaper and more preventable.

Evidence-Based Appeals and the Medicare Ladder

An appeal package should explain why the claim is supported — relevant documentation, code rationale, medical-necessity support, and payer-rule references — in a targeted response to the specific denial reason. A generic form letter is weaker. For Medicare fee-for-service, the five-level appeals process runs: 1) Redetermination by the MAC (within 120 days of the initial determination), 2) Reconsideration by a Qualified Independent Contractor (QIC), 3) ALJ (Administrative Law Judge) hearing (with a minimum amount-in-controversy), 4) Medicare Appeals Council review, and 5) Judicial review in federal court.

Each level has firm filing deadlines; timely filing failures forfeit otherwise valid revenue.

Knowing When NOT to Appeal

The RHIA must also recognize when a denial is valid. If documentation does not support the code, the account requires correction, rebill, write-off review, or compliance escalation per policy — appealing an unsupported claim wastes resources and increases risk. Conversely, accepting an incorrect payer denial without review loses legitimate revenue and distorts metrics.

A Denial Management Cycle

1. Capture the denial reason (CARC/RARC) and payer data accurately.
2. Triage by type, dollar value, deadline, and likelihood of overturn.
3. Review documentation, codes, charges, authorization, and payer rule.
4. Correct, appeal, or accept per evidence and policy.
5. Trend denials by payer, service line, provider, code, department, and root cause.
6. Feed trends into education, edits, CDM review, CDI, and leadership reporting.

Denials are expensive: they create rework, delay cash, age A/R, and expose compliance gaps. RHIA leadership treats denials as a mirror for the health of documentation, coding, charging, and claim processes.

A Worked Triage Example

A denial workqueue holds three accounts the same morning. Account A is a soft denial: the payer returned it as "missing the operative report" (a documentation-request type) — the fix is to attach the report and resubmit, no formal appeal needed. Account B is a hard medical-necessity denial citing a local coverage determination (LCD); review shows the ordering diagnosis was not linked to the service, so this needs an evidence-based appeal if the record supports necessity, or a write-off if it does not.

Account C is an authorization denial — a front-end failure where registration never obtained prior authorization; the account may be unrecoverable, and the real fix is upstream in scheduling/registration so it stops recurring. Working all three with the same generic appeal letter wastes effort and misses two preventable root causes. Triage by type, dollar value, deadline, and overturn likelihood is what makes the queue productive.

Timely Filing and Deadline Discipline

Deadlines are unforgiving and heavily tested. Timely filing limits (commercial payers often 90–180 days from service; Medicare generally one year) bar otherwise valid claims if missed. Appeal deadlines stack on top: in Medicare fee-for-service, Redetermination must be filed within 120 days of the initial determination, and each subsequent level (QIC reconsideration, ALJ, Council, judicial review) has its own clock.

An RHIA managing denials builds a deadline-driven worklist so high-value, near-deadline accounts are worked first — letting a winnable appeal lapse on a filing deadline is a self-inflicted revenue loss that no audit can recover.

From Account Resolution to Operational Intelligence

The management payoff of denials work is not just recovered cash; it is the trend data. Classifying every denial by CARC/RARC reason, payer, service line, provider, code, and department turns the workqueue into a prevention engine. A cluster of medical-necessity denials on one procedure feeds provider education and a prebill edit; a cluster of charge/CDM denials feeds chargemaster maintenance; a cluster of authorization denials feeds front-end workflow redesign. This is how denials management connects back to every earlier Domain 4 topic — coding validation, CDI, CDM, and revenue integrity governance.

The strongest exam answer asks why the denial happened and whether the organization can prevent it next time.