Chapter 29 — Key Takeaways

Denial versus rejection, restated for the work

A denial queue fed only by remittances has a blind side the size of your rejection report.

The fix is one line in a job description: the person who works denials also works rejections, and both counts appear on the same report.

The seven categories

Four of the seven are not the coder's, and those four are usually the majority by volume.

Two independent axes

                      PREVENTABLE          NOT PREVENTABLE
      SOFT       │ missing modifier    │ unpredictable payer edit
   (recoverable) │ wrong POS           │ retroactive eligibility
      HARD       │ TIMELY FILING       │ genuinely non-covered
   (dead)        │ no authorization    │ never eligible
                 │ ►► THE EXPENSIVE QUADRANT

Hard/soft = can the money still be obtained. Preventable = could you have stopped it. A soft denial left unworked becomes a hard one — time is the only difference.

"Preventable" does NOT mean "somebody erred." Account 10-4471 was correct at every step and still preventable. Misreading this is the single largest cause of under-reported prevention data, and a category nobody will admit to is a category nobody can fix.

Root cause, and the integrated triage

The REMEDY is what you did about this claim. The ROOT CAUSE is what produced it.

One missing modifier → five root causes: training · template · edit · payer policy · chargemaster maintenance (Ch. 26 §26.5). Different fix every time. A log recording the remedy cannot tell you which.

   1  WHICH OF THE FOUR?  (Ch. 20 §20.10)
        bundled · not a benefit · not recognized ·
        NOT NECESSARY AS DOCUMENTED ◄── the only arguable one

   2  IF AN EDIT, WHICH BRANCH?  (Ch. 21 §21.11)
        indicator 0 ............... DO NOT APPEAL
        indicator 1, docs support . APPEAL
        indicator 1, docs do not .. DO NOT APPEAL — correct
        MAI 2 ..................... DO NOT APPEAL
        MAI 1 or 3 ................ workable
        proprietary ............... GET THE POLICY FIRST

   3  IF NECESSITY:  coded wrong · never going to be covered

Ninety seconds, and the highest-return ninety seconds in the revenue cycle — not because it wins appeals, but because it stops you writing the ones that cannot be won.

The category list: registration · authorization · credentialing (NOT fixable by billing) · coding-selection · coding-modifier · coding-units · edit-NCCI/MUE · edit-proprietary · documentation · chargemaster · claim data · timely filing · coverage · duplicate · payer error.

No catch-all "other" — it collects the interesting third. And "payer error" must exist, or §28.8's findings have nowhere to go.

Working the queue

   SORT:  1 DEADLINE   2 CATEGORY   3 dollar

   WORK:  read the codes → run the triage → CLASSIFY →
          decide → act and record BOTH → report the pattern

Deadline first because time, not difficulty, creates the hard-and-preventable quadrant. Category second because twelve denials of one kind are one investigation. Classify before acting, or you will record the remedy.

Close what has no appeal rights immediately — RARC MA130 says so — or the queue lies about how much recoverable work exists.

A queue is not a control. A person who works the queue is a control.

Four questions: how many items · what is the oldest and why · how many closed as "no action" · and what is in here that nobody in this department can fix.

Corrected claims

Both wrong answers produce a DUPLICATE — and the original problem is still unfixed.

You need the original claim number (it returns on the remittance). And correcting is not appealing — at some payers a corrected claim forfeits the appeal rights attached to the original determination.

The log and its numbers

Row: DOS · denial date · payer · provider · code and modifiers · charge and allowed · group code · CARC · RARC · ROOT CAUSE · PREVENTABLE? · action · OUTCOME · date resolved.

The two most-omitted fields are root cause and outcome, and they are the two that matter.

And "denial rate" is not one number: lines or claims · zero-pay only or any non-contractual adjustment · adjudicated or submitted. (Account 10-4471: 25% by line, 100% by claim.) Pick one definition, write it down, never change it silently. Report lines. Treat benchmarks as comparisons of definitions.

   NORTHGATE, ONE MONTH
     4,180 adjudicated · 267 denied ............... 6.4%
     registration 71 + authorization 44 ........... 43% of denials
     PREVENTABLE 185 .............................. 69.3%
     appeals 84 decided, 57 upheld ................ 68% OVERTURN

Prevention

   THE FRONT END  before the visit  ► 43% of Northgate's denials
   THE TEMPLATE   during the visit  ► improves the RECORD, not the claim
   THE EDIT       before submission ► only what is ON the claim

Prevent where the information exists. An edit that stops a claim must tell somebody what to do. And prevention is a fixed cost against a recurring loss: a denial costs you every time; an edit costs you once.

An edit may STOP a claim and ask a question. It may not ANSWER the question.

Same for templates. "Was a separately identifiable service performed?" is prevention. "A separately identifiable service was performed" is an assertion nobody made — Ch. 21's Account 31-2245 (\$25,720.80) and this chapter's Case Study 2.

Making the case

Dollar figure for a period · name the process, never the person · the smallest possible fix · a comparison, not a benchmark · ask for a measurement, not a commitment.

When the answer is no: ask what would change it · keep measuring · do the part you control · write down what you found and when. Do not escalate early — it converts a disagreement about priorities into a conflict about authority.

Key terms

denial · rejection · hard/soft · preventable · denial taxonomy · root cause vs. remedy · integrated triage · denial work queue · queue ordering by deadline · corrected claim · replacement · void · denial log · denial rate · initial denial rate · first-pass resolution rate · overturn rate · denials resolved · rejection rate · scrubber edit · documentation template · prevention as a fixed cost

Monday morning

• Run the triage before working anything.
• Sort your queue by deadline.
• Classify root cause before you act.
• Close the unwinnable and count it.
• Put a rejection rate next to your denial rate.
• Never let an edit or a template answer.

The Encounter — day 20.

   CO 45  56.60 · CO 97 128.40 · RARC N19  on 99214-25

   TRIAGE  branch 1: BUNDLED — would ordinarily end here
           branch 2: indicator 1, modifier 25 present,
                     DOCUMENTATION SUPPORTS ►► APPEAL

   ROOT CAUSE ..... EDIT — PAYER (E/M with minor procedure)
   HARD/SOFT ...... SOFT       PREVENTABLE .... YES
   OUTCOME ........ UPHELD 05/12 · resolved 05/19

   TOUCH 1  read, classify, pull the note ........ 14
   TOUCH 2  assemble, write, submit .............. 31
   TOUCH 3  track, follow up day 45, post ........ 13
                                                   ────
                                                    58 minutes

The four elements supporting modifier 25 — three chronic conditions separately assessed · prescription drug management · two labs ordered with stated reasons · a new problem with its own history, exam, and decision. Elements 1 through 3 have nothing to do with the knee.

The claim was correct AND the denial was preventable.

This payer denies this pairing predictably. A scrubber rule or a documentation template would have changed the outcome without changing the claim's correctness. "Preventable" means a process could have stopped it — not that anyone was wrong.

Q4 remains open.