Chapter 1: The Revenue Cycle: How Healthcare Gets Paid, From Patient Check-In to Final Payment

"Nobody in the room where care happens knows what it costs. Nobody in the room where the price is set has met the patient. Your entire job lives in the space between those two rooms." — constructed; the working premise of this book

Overview

The bill arrives eleven days after the stitches come out and it says \$3,842.00.

Nobody in the emergency department mentioned a number. The insurance card was in the wallet the whole time. The visit lasted ninety minutes, most of it waiting. The wound needed four sutures, a tetanus shot, and an X-ray to make sure there was no glass in it. Three thousand eight hundred and forty-two dollars.

Then a second envelope arrives, from a different sender, for \$680.00, and it appears to be for the same visit.

Here is the part that almost nobody outside this industry knows: neither of those numbers is what anyone will pay. They are not what the hospital expects. They are not what the insurer has agreed to. They are not what will end up on the patient's statement. They are opening figures in a settlement process whose terms were fixed by contract two years before this patient cut their hand, and by the time it is finished, the hospital will collect \$1,196.40** of its \$3,842.00, the emergency physician's group will collect \$318.60** of its \$680.00, the patient will owe \$503.00 between them, and \$3,007.00 will be erased in a single keystroke by someone who will never read the chart.

The work of turning \$4,522.00 into those numbers — correctly, legally, quickly, and in a way that can be defended two years later to an auditor who was not there — is what this book is about.

It has a name. It is called the revenue cycle, and it is one of the largest administrative enterprises in the American economy. It employs coders, billers, denial specialists, patient access representatives, auditors, clinical documentation integrity specialists, and managers, and it runs on two code sets, two claim forms, a body of federal law, and about ten thousand payer-specific policies that contradict each other.

This chapter puts the whole thing on one page. Then the other thirty-nine take it apart.

In this chapter, you will learn to:

• Distinguish the four numbers on every account and state how they relate
• Trace an encounter from registration to a zero balance, naming what the money is at each stage
• Explain why one visit can produce two claims, and tell which charges belong to which
• Describe what a coder does all day, what a biller does all day, and where the line falls
• Name the six places revenue is most commonly lost, and the cheapest place to fix each
• Read a statement and an explanation of benefits well enough to account for every dollar

Learning Paths

🎓 Certification — This chapter is context, not content; the exams do not test it directly. But the vocabulary in §1.2 appears in question stems constantly, and candidates who have never worked in a business office lose points to it. Learn the four numbers cold.

💼 New Coder — Read it all. §1.5 and §1.6 answer the two questions every new coder asks in the first week: why are there two claims? and what am I actually supposed to be doing?

💵 Biller / AR — §1.2, §1.3, and §1.8 are your map for the entire book. §1.8 in particular is a preview of Parts V and VI.

🏥 Practice Manager — §1.8 is the chapter. Six leaks, each with an owner and a cost. Everything else here is background for a conversation you will have with your staff.

1.1 The bill that makes no sense

Start with the artifact, because the artifact is why most people end up reading a book like this.

A person cut their left hand on a Sunday evening. They went to a hospital emergency department because their doctor's office was closed and because a laceration that will not stop bleeding is a reasonable thing to take to an emergency room. They were registered, triaged, seen, X-rayed to rule out a retained foreign body, sutured, given a tetanus booster, and discharged with wound care instructions.

Here is what arrived in the mail.

📋 Read the Chart

text FIGURE 1.1 — "The bill that started this book" [constructed teaching example] THE DOCUMENT Hospital itemized statement, Account 22-7788, mailed 11 days after the date of service. A second, separate statement for Account 10-7789 arrived from an emergency physicians' group four days later. THE CONTEXT A Sunday-evening emergency department visit for a laceration of the left hand. Commercial PPO coverage, in network, deductible already satisfied for the year. The patient presented an insurance card at registration and it was scanned. WHAT IT SHOWS Two separate accounts for one visit. Facility charges of $3,842.00 across five departments; professional charges of $680.00 for the emergency physician's own work. Total billed, $4,522.00. WHAT IT DOESN'T It does not show the allowed amounts, so it does not show what anyone will actually pay. It does not show the contractual adjustment, which is the largest single number in the whole transaction. It does not explain why there are two bills. A charge statement is a list of what was done, priced at a number almost nobody pays. THE DECISION Do not pay anything yet. Wait for the explanation of benefits from the plan, then compare it line for line against these statements. THE LESSON A charge is an opening position, not a price. Reading a healthcare bill means finding the four numbers, and a charge statement only contains one of them.

Here is the facility side, itemized the way the hospital's system produced it:

FACILITY CHARGES — Account 22-7788, Ridgeview Regional Medical Center
[constructed teaching example — every figure illustrative]

  REV   DEPARTMENT                       CODE      CHARGE
  ----  -------------------------------  -------   ---------
  0450  Emergency room                   99284      2,485.00
  0270  Medical/surgical supplies        —            318.00
  0250  Pharmacy                         —             96.00
  0300  Laboratory                       —            243.00
  0320  Radiology — diagnostic           73090        700.00
  ----  -------------------------------  -------   ---------
  0001  TOTAL CHARGES                               3,842.00

Four things in that small table will occupy whole chapters later, and it is worth naming them now so you know they are coming.

The four-digit numbers in the left column are revenue codes. They tell an institutional payer which department of the hospital produced the charge. Revenue code 0450 is the emergency room; 0320 is diagnostic radiology. They are not procedure codes and they do not describe what was done — they describe where in the building it happened and out of which budget it came. Chapter 26 is entirely about them.

99284 and 73090 are CPT codes. They describe what was done: a level 4 emergency department visit and a two-view radiologic examination of the forearm. Part III of this book is about where they come from and how they are chosen.

The supplies, the pharmacy, and the laboratory lines have no code at all in this rendering. That is not sloppiness. In the outpatient hospital payment system, many charges are packaged — the payment for the visit is understood to include them, and they will be allowed at \$0.00. The hospital still charges for them, because the chargemaster charges for everything, and because some payers pay a percentage of charges rather than a fee schedule. Chapter 34 explains packaging in detail. For now, notice only this: a line can be legitimately billed and legitimately allowed at zero, and a patient reading a statement has no way to know that.

And the total, \$3,842.00, is a number the hospital does not expect to receive.

Now the professional side, which arrived separately:

PROFESSIONAL CHARGES — Account 10-7789, emergency physicians' group
[constructed teaching example]

  LINE  CODE       MOD   DESCRIPTION (paraphrased)              CHARGE
  ----  ---------  ----  -------------------------------------  --------
   1    99284      25    Emergency department visit, level 4      455.00
   2    12002      —     Simple repair, 2.6–7.5 cm, extremity     225.00
  ----  ---------  ----  -------------------------------------  --------
        TOTAL                                                     680.00

The same code, 99284, appears on both bills. It is not a duplicate and it is not an error. Section 1.5 explains why, and it is the single most common source of confusion for people new to this field and for every patient who has ever received two bills for one visit.

📞 On the Phone

This is the call, more or less verbatim, that a business office gets four hundred times a year.

"I'm looking at a bill for three thousand eight hundred and forty-two dollars for four stitches. Four. I want to know how you people sleep at night."

The wrong answer — the one that guarantees an escalation — is "that's just the charge, ma'am, your insurance will reduce it." It is technically true and it sounds like a brush-off, because it asks the patient to accept that the number on the paper in their hand is not real without explaining why.

The answer that works is specific and takes about forty seconds: "That statement is a list of everything that was done, priced at our standard charge — it isn't the bill. Your plan has a contract with us, and under that contract this visit is worth \$1,196.40, not \$3,842.00. The difference gets written off; you never owe it and neither does your plan. What you'll owe is your \$250 emergency room copay plus twenty percent of the rest, which comes to \$439.28. I can send you the breakdown today, and if you want, I'll walk you through it line by line."

That answer requires knowing the four numbers. Everything in §1.2 is what makes that call possible.

1.2 Charge, allowed amount, adjustment, payment: the four numbers everything is built from

There are exactly four numbers on any healthcare account, and every argument you will ever have about a claim is an argument about one of them. Learn them in this order, because the order is the logic.

The charge

The charge is what the provider bills. It is set by the provider, unilaterally, in advance, and it is recorded in a fee schedule (in a practice) or a chargemaster (in a hospital). It is not negotiated with anyone. It is not a price in the ordinary sense, because almost nobody pays it.

Who does pay it? A very small number of people: some self-pay patients without a discount policy, some out-of-network situations, and certain liability and workers' compensation arrangements. For every patient with in-network commercial insurance, Medicare, or Medicaid, the charge functions as nothing more than the starting figure in a settlement that has already been decided.

This produces the single most counterintuitive fact in American healthcare finance, and it is worth stating plainly because new coders and billers trip over it for months: raising your charges does not increase your revenue on contracted business. Chapter 23 explains why a practice sets charges above what it expects to collect anyway, and why setting them below the contracted allowed amount is a genuine and expensive error.

The allowed amount

The allowed amount is what the contract says the service is worth. It is the number that matters.

It is determined before the patient walks in, by an agreement between the provider organization and the payer, and it is typically expressed as a fee schedule — a list of codes and dollar amounts — or as a percentage of some published schedule ("115% of Medicare"), or as a case rate, or as a per-member capitation payment. Chapter 2 covers the forms these contracts take.

The allowed amount is the total the provider will receive for that service from all sources combined. That is the part people miss. It is not what the insurer pays; it is what the insurer and the patient pay together.

The contractual adjustment

The contractual adjustment is the difference between the charge and the allowed amount, and it is written off. The provider does not collect it, may not bill the patient for it, and in most contracts is expressly forbidden from trying — which is what "balance billing" means and why the practice is prohibited in network. Chapter 32 covers the federal protections that now extend some of those prohibitions to out-of-network situations.

$$\text{Contractual adjustment} = \text{Charge} - \text{Allowed amount}$$

In the emergency department example: \$3,842.00 − \$1,196.40 = \$2,645.60, gone, on the facility side alone.

That number is not a loss in any meaningful accounting sense, because the provider never expected to receive it. But it is the largest number in the transaction, it appears on the patient's explanation of benefits under a name like "plan discount" or "network savings," and it is the reason healthcare billing feels like a negotiation conducted in a language the patient does not speak.

Payment: the plan's share and the patient's share

The allowed amount splits in two.

$$\text{Allowed amount} = \text{Patient responsibility} + \text{Plan payment}$$

Patient responsibility is the portion of the allowed amount the patient owes under their benefit design: the deductible, the copayment, the coinsurance, or all three. Chapter 2 defines each. The critical structural point is that patient responsibility is computed on the allowed amount, not on the charge. A twenty percent coinsurance on this visit is twenty percent of \$1,196.40, not twenty percent of \$3,842.00. The difference is \$529.12, and a patient who does not understand it will believe they have been overbilled by a factor of three.

Plan payment is the remainder.

🧮 Run the Numbers

The whole emergency department visit, both claims, every dollar accounted for. [constructed teaching example — illustrative figures]

Facility claim, Account 22-7788:

Line	Charge	Allowed	Contractual adj.	Patient	Plan
ED visit, 99284	2,485.00	742.00	1,743.00	—	—
Supplies	318.00	0.00	318.00	—	—
Pharmacy	96.00	0.00	96.00	—	—
Laboratory	243.00	62.40	180.60	—	—
Radiology, 73090	700.00	392.00	308.00	—	—
Total	3,842.00	1,196.40	2,645.60	439.28	757.12

Patient responsibility is applied to the claim, not line by line: a \$250.00 emergency department copay, then 20% coinsurance on the remaining allowed amount.

• Allowed after copay: \$1,196.40 − \$250.00 = \$946.40
• Coinsurance: \$946.40 × 0.20 = \$189.28
• Patient: \$250.00 + \$189.28 = \$439.28
• Plan: \$1,196.40 − \$439.28 = \$757.12

Professional claim, Account 10-7789: charges \$680.00, allowed **\$318.60, contractual adjustment \$361.40**. No second copay applies; coinsurance is 20% of \$318.60 = \$63.72. Plan pays \$254.88.

Both claims together:

	Amount
Total charges	\$4,522.00
Total allowed	\$1,515.00
Total contractual adjustment	\$3,007.00
Total patient responsibility	\$503.00
Total plan payment	\$1,012.00

The checks. \$4,522.00 − \$1,515.00 = \$3,007.00 ✓ · \$1,515.00 − \$503.00 = \$1,012.00 ✓ · \$757.12 + \$254.88 = \$1,012.00 ✓ · \$439.28 + \$63.72 = \$503.00 ✓

The interpretation. The patient owes \$503.00 on \$4,522.00 in charges — about eleven cents on the billed dollar. The providers collect \$1,515.00, about a third. Two-thirds of the number that frightened the patient was never real. Every figure here resolves, and every figure in this book will resolve; if a table of numbers is a total, it adds up.

Four numbers. Two subtractions. That is the entire arithmetic skeleton of the revenue cycle, and every complication in the remaining thirty-nine chapters hangs on it.

⚠️ Where Claims Die

The most common conceptual error a new biller makes is computing patient responsibility against the charge instead of the allowed amount. It happens because the charge is the number on the screen when the patient is standing there, and because point-of-service collection often happens before adjudication.

Collecting twenty percent of \$3,842.00 (\$768.40) rather than twenty percent of the post-copay allowed amount (\$189.28) overcollects by **\$579.12** and creates a credit balance the practice is legally obligated to refund. Chapter 31 covers what happens if it does not: an unrefunded credit balance is an overpayment, and a knowingly retained overpayment is not a bookkeeping problem, it is a False Claims Act problem.

The reverse error is quieter and just as expensive. A practice that collects nothing at the desk because "we'll wait for the EOB" converts a payment the patient was standing there ready to make into a receivable that will be chased for ninety days and collected at a discount, if at all.

🔍 Check Your Understanding

1. A practice charges \$220.00 for a service. The contract allows \$146.80. The patient has met their deductible and has 20% coinsurance. What is the contractual adjustment, the patient responsibility, and the plan payment?
2. If the practice raised the charge to \$400.00 tomorrow, which of those three numbers changes?
3. A patient says "my insurance only paid \$757 of a \$3,842 bill." Which of the four numbers are they confusing, and what is the one sentence that corrects it?

(Answers: 1. Adjustment \$73.20; patient \$29.36; plan \$117.44. 2. Only the contractual adjustment — it grows to \$253.20. Patient and plan payment are unchanged, because both are computed on the allowed amount. 3. They are comparing the plan payment to the charge, and skipping the allowed amount entirely. "Your plan didn't pay \$757 of \$3,842 — it paid \$757 of the \$1,196.40 that the contract says this visit is worth; the rest was written off and nobody owes it.")

1.3 The revenue cycle end to end

Now the whole machine, in order.

THE REVENUE CYCLE — six stages, and what the money IS at each one

  ┌───────────┐  ┌───────────┐  ┌──────────┐  ┌────────┐  ┌────────┐  ┌───────────┐
  │  ACCESS   │→ │ ENCOUNTER │→ │  CODING  │→ │ CLAIM  │→ │ REMIT  │→ │ FOLLOW-UP │
  └───────────┘  └───────────┘  └──────────┘  └────────┘  └────────┘  └───────────┘
   schedule       the visit      ICD-10-CM     scrub        835/EOB     denials
   register       the note       CPT/HCPCS     837 out      post        appeals
   verify         charge         modifiers     ack back     adjust      statements
   authorize      capture        edits         (999/277CA)  balance     collections
       │              │              │             │            │             │
   the money      the money      the money     the money    the money     the money
   is a           is a           is a          is a         is a          is a
   PROMISE        PROMISE        CLAIM         RECEIVABLE   DECISION      RECOVERY

   ←──── FRONT END ────→ ←────── MIDDLE ──────→ ←───────── BACK END ─────────→

Read that bottom row again, because it is the most useful thing in this chapter.

In the access and encounter stages, the money is a promise. Nothing has been billed. Nothing is owed. What exists is a set of conditions — is this person covered, by whom, under what benefit, requiring what authorization — which will either be satisfied or not. Every failure here is invisible until much later, and every failure here is cheap to fix now and expensive to fix then.

In the coding stage, the money becomes a claim. The clinical work is translated into codes, and those codes are simultaneously a factual assertion about what happened and a legal certification. The moment a claim goes out the door, the organization has made a statement to a payer, and if the payer is a federal health program, that statement is subject to the False Claims Act. Chapter 5 covers what that means.

On submission, the money becomes a receivable. It is now an asset on the books, sitting in accounts receivable, aging. It is worth less every day. Chapter 31 quantifies how much less.

On adjudication, the money becomes a decision. The payer applies its rules and returns a remittance advice: paid, adjusted, denied, or some combination on different lines of the same claim. This is where most of a business office's work originates.

And in follow-up, the money becomes a recovery — or does not.

The same cycle, as a timeline

Stages are conceptual. Here is what they look like on a calendar, using the file this book will follow for the next thirty-nine chapters.

ACCOUNT 10-4471 — one office visit, from check-in to zero balance
[constructed teaching example; day 0 = Tuesday, March 14]

  DAY   0  ██ date of service · charge capture at check-out · note signed 6:42 p.m.
  DAY   1  █  coding: ICD-10-CM and CPT assigned, claim built
  DAY   2  █  scrubber clears · 837P transmitted to clearinghouse 11:05 p.m.
  DAY   3  █  clearinghouse 999 accepted · payer 277CA acknowledges receipt
           .
           .  ← fourteen days of nothing. This is normal.
           .
  DAY  17  ██ 835 posts: $70.30 paid on three lines
              ONE LINE DENIED — CO-97
  DAY  20  █  denial worked: read, classified, note pulled
  DAY  24  █  level-one appeal submitted with records
           .
           .  ← thirty-five days of nothing. This is also normal.
           .
  DAY  59  █  payer decision letter: appeal upheld in the provider's favor
  DAY  66  ██ second 835: the denied line pays $98.40
  DAY  70  █  patient statement #1: responsibility $47.58,
              less $30.00 collected on day 0 — BALANCE DUE $17.58
           .
  DAY 100  ██ patient payment received. ACCOUNT BALANCE $0.00

  ELAPSED: 100 days, on a clean, correctly coded, in-network claim
           that was denied exactly once.

Look at the white space. Two stretches of that timeline — days 3 through 17 and days 24 through 59 — account for forty-nine of the hundred days, and in both of them the provider is doing nothing because there is nothing to do. The claim is with the payer.

That is the shape of this business. Long periods of waiting, punctuated by short bursts of work in which everything depends on doing the right thing quickly. A denial that sits unworked for two weeks does not cost two weeks — it costs two weeks plus the thirty-five days the appeal will take anyway, and in a practice where the timely-filing deadline for appeals is ninety days, it can cost the entire receivable.

⚠️ Where Claims Die

The single most expensive habit in a small business office is working the queue in the order the accounts appear. The denial on day 17 and the denial on day 74 look identical in a work list. One has seventy-three days of appeal window left and one has sixteen.

A work queue that is not sorted by deadline is a work queue that will eventually write off a collectible account for timely filing, and timely filing write-offs are — in almost every practice that measures them — the single most avoidable category of loss in the entire revenue cycle. Chapter 31 covers how to build a queue that surfaces the right account.

The two clocks

Two deadlines run against every account, they run independently, and confusing them is one of the most expensive mistakes in the back office.

The timely filing clock starts on the date of service and governs how long you have to submit the claim in the first place. It is set by contract — commercial payers commonly allow ninety days to a year from the date of service, Medicare allows a calendar year by statute, and some Medicaid programs are considerably shorter. Miss it and the claim is denied with no appeal on the merits, because the merits are irrelevant: you were late.

The appeal clock starts on the date of the denial — usually the date on the remittance advice or the denial letter, not the date you read it — and governs how long you have to dispute a decision. It is typically shorter than the filing window, frequently much shorter, and it is the one that expires while nobody is looking.

THE TWO CLOCKS — they overlap, and they are not the same clock

  DATE OF SERVICE                                        FILING DEADLINE
  │                                                                    │
  ├────────────────────────────────────────────────────────────────────┤
  │  timely filing window (contract term, e.g. 90 days to 1 year)      │
  │                                                                    │
  │        submit          adjudicate                                  │
  │           │                │                                       │
  │           ▼                ▼ DENIAL                                │
  │                            ├──────────────────┤                    │
  │                            │  appeal window   │                    │
  │                            │ (often 30–180 d) │                    │
  │                            │                  │                    │
  │                            └── starts on the DENIAL DATE, not the
  │                                date you noticed the denial ────────┘

The trap is a denial received late in the filing window. Suppose a claim is submitted on day 5 and denied on day 40 for a correctable reason. If the fix is a corrected claim, you are working against the filing clock and may have plenty of room. If the fix is an appeal, you are working against the appeal clock, which may give you thirty days regardless of how much filing window remains. Two identical-looking denials, two entirely different deadlines, and the difference depends on which remedy applies. Chapters 29 and 30 cover choosing between them.

One practical rule, worth adopting on your first day: write the deadline on the account the moment you touch it, not the date you worked it. A queue annotated with "worked 4/3" tells you nothing. A queue annotated with "expires 6/29" sorts itself.

1.4 Front end, middle, back end: who does what

Organizations divide the revenue cycle into three zones. The names are near-universal; the boundaries move depending on who you ask.

In a five-physician practice, all three zones may be four people, and one of them may do parts of each. In a health system, each zone is a department with a director. The work is identical; only the division of labor changes.

The same three zones, at three sizes

It is worth seeing this concretely, because the job you take will look like exactly one of these and the differences matter enormously to what your day feels like.

THE SAME WORK, THREE ORGANIZATIONS
[constructed teaching example]

  SOLO / SMALL PRACTICE (1–5 providers)
  ┌──────────────────────────────────────────────────────────────────┐
  │  Front desk (2)  ──  registration, eligibility, copays, phones   │
  │  "The biller" (1) ─  coding AND charge entry AND claims AND      │
  │                      posting AND denials AND appeals AND         │
  │                      patient calls AND the aging report          │
  │  Office manager (1) — everything else, plus payroll              │
  └──────────────────────────────────────────────────────────────────┘
   → You will do all of it. You will learn fast. Nobody will check
     your work, which is both the opportunity and the hazard.

  MID-SIZE GROUP (15–60 providers)
  ┌──────────────────────────────────────────────────────────────────┐
  │  Patient access team ─ scheduling, registration, authorizations  │
  │  Coding team ──────── coders by specialty; a coding auditor      │
  │  Billing team ─────── claims, posting, denials, AR, patient      │
  │  Revenue cycle mgr ── the metrics, the payers, the escalations   │
  └──────────────────────────────────────────────────────────────────┘
   → Specialization begins. You will own a queue, not a process.

  HEALTH SYSTEM (multi-hospital)
  ┌──────────────────────────────────────────────────────────────────┐
  │  Patient Access ───── a department. Pre-service financial team.  │
  │  HIM / Coding ─────── inpatient, outpatient, professional, and   │
  │                       specialty coders; CDI is its own team      │
  │  Patient Fin. Svcs ── billing, follow-up, denials, appeals,      │
  │                       underpayment recovery, vendor management   │
  │  Revenue Integrity ── chargemaster, charge capture, edits        │
  │  Compliance / Audit ─ separate reporting line, by design         │
  └──────────────────────────────────────────────────────────────────┘
   → Deep specialization. A career ladder exists. You may never
     speak to a patient or a physician.

There is no correct answer about which is a better place to start. The small practice teaches you the whole cycle in eighteen months and will let you develop bad habits nobody catches. The health system teaches you one segment very well, gives you people to ask, and can make it hard to see how your piece connects to the rest. What is worth knowing on day one is which one you are in, because the question "who owns this problem?" has a different answer in each.

Two structural observations that will save you time later.

The front end causes most of the back end's work. Eligibility failures, missing authorizations, wrong plan identifiers, wrong subscriber information, and unverified coordination of benefits are — across most organizations that measure it carefully — among the largest categories of preventable denial. The people who fix those denials are not the people who caused them, and the people who caused them frequently never learn that they did. A revenue cycle that does not feed denial data back to the front desk is a revenue cycle that will pay for the same error forever. Chapter 24 and Chapter 29 are two halves of this problem.

The middle is where the legal exposure concentrates. The front end can be sloppy and cost money. The back end can be slow and cost money. The middle can produce a claim that is false, and false claims are a different category of problem with a different range of consequences, which include criminal ones. This is why the coder's professional obligation runs to accuracy first and revenue second, and why "my manager told me to" is not a defense. Chapter 5 is blunt about this.

⚖️ Compliance Check

A claim submitted to Medicare, Medicaid, TRICARE, or any other federal health program carries a certification: that the services were rendered, that they were medically necessary, and that the information on the claim is true and complete. That certification is made by the provider organization, but it is built by the coder and the biller.

The False Claims Act (31 U.S.C. §§ 3729–3733) attaches liability to knowingly presenting a false claim — and "knowingly" is defined to include deliberate ignorance and reckless disregard of the truth. You do not have to intend fraud. A coder who systematically appends a modifier without reading the documentation, or who codes from a superbill checkbox without opening the note, is operating in the zone the statute was written to reach.

Chapter 5 covers this in full, along with the Anti-Kickback Statute, the physician self-referral law, and the civil monetary penalty and exclusion authorities. For now, hold one sentence: every code is an assertion of fact, and somebody's signature is under it.

Statutes and regulations change, enforcement priorities shift, and state law adds requirements beyond the federal floor. Verify current requirements with your compliance officer and the primary source before relying on any summary, including this one.

1.5 One encounter, two claims: professional and facility

Back to the two envelopes.

One emergency department visit produced two bills because two different entities furnished two different things, and American healthcare pays them separately.

The hospital furnished the room, the nurses, the triage, the supplies, the equipment, the radiology technologist, the laboratory, the pharmacy stock, the building, and the electricity. That is the facility or technical component, and it is billed on a UB-04 claim form (also called the CMS-1450) by the institution.

The emergency physician furnished their own professional work: the history, the examination, the medical decision making, and the laceration repair performed with their own hands. That is the professional component, and it is billed on a CMS-1500 claim form by the physician's group, which in many hospitals is a separate company entirely.

Both claims may carry the code 99284, and both are correct, because they are describing different things with the same number. On the professional claim, 99284 describes the physician's cognitive work. On the facility claim, 99284 describes the hospital's resource intensity — the nursing time, the room, the equipment — assigned by an internal acuity-leveling methodology that has nothing to do with the physician's decision making and may not even produce the same level. Chapter 16 §16.9 and Chapter 35 §35.6 cover facility acuity leveling in detail.

ONE ENCOUNTER, TWO CLAIMS

                        ┌─────────────────────┐
                        │   THE ED VISIT      │
                        │  Sunday, 7:40 p.m.  │
                        └──────────┬──────────┘
                    ┌──────────────┴──────────────┐
                    ▼                             ▼
        ┌───────────────────────┐     ┌───────────────────────┐
        │   FACILITY COMPONENT  │     │ PROFESSIONAL COMPONENT│
        │   the hospital        │     │ the physician group   │
        ├───────────────────────┤     ├───────────────────────┤
        │ FORM:   UB-04         │     │ FORM:   CMS-1500      │
        │ EDI:    837I          │     │ EDI:    837P          │
        │ PAID BY: OPPS / APC   │     │ PAID BY: fee schedule │
        │ CHARGES: $3,842.00    │     │ CHARGES: $680.00      │
        │ ALLOWED: $1,196.40    │     │ ALLOWED:   $318.60    │
        │ PATIENT:   $439.28    │     │ PATIENT:    $63.72    │
        └───────────────────────┘     └───────────────────────┘
                    │                             │
                    └──────────────┬──────────────┘
                                   ▼
                     ONE PATIENT, TWO STATEMENTS,
                       TOTAL RESPONSIBILITY $503.00

This split is not limited to emergency departments. It appears wherever a service has both a professional and a technical component:

• Radiology. The imaging equipment, the technologist, and the film are technical; the radiologist's interpretation and written report are professional. Chapter 19 §19.1 covers the modifiers — 26 and TC — that carve one from the other.
• Pathology. The laboratory's analysis is technical; the pathologist's interpretation is professional.
• Surgery in a hospital or ambulatory surgery center. The facility bills for the operating room, the anesthesia equipment, the recovery bay, and the implants; the surgeon bills for the operation; the anesthesiologist bills separately again.
• Hospital outpatient clinic visits. In a provider-based clinic — a physician office owned by and billed as part of a hospital — the same visit that would have produced one claim in an independent practice produces two, and the patient's cost-sharing is frequently higher as a result. This is one of the most common and most bitterly resented surprises in American medical billing, and Chapter 34 §34.8 addresses it directly.

⚠️ Where Claims Die

A charge posted to the wrong claim is not a small error. If the facility's supply charge lands on the professional claim, or the surgeon's work lands on the facility claim, the claim will either deny outright or — worse — pay, creating an overpayment that becomes a refund obligation with a sixty-day clock on it (Chapter 31 §31.9).

The practical rule for a new coder: ask whose resources were consumed. If it is people, rooms, equipment, and supplies owned by the institution, it is facility. If it is a licensed professional's own cognitive or procedural work, it is professional. When a service has both, it has both, and the two components are billed by two entities on two forms.

🎓 Exam Watch

The professional/facility distinction shows up in certification exams in three reliable places.

First, in questions about which form to use. CMS-1500 for professional and non-institutional providers; UB-04 (CMS-1450) for institutional. The electronic equivalents are 837P and 837I. Candidates who memorize the form names but not the electronic transaction names lose points in the billing sections.

Second, in modifier questions about 26 and TC. A radiologist reading a study performed at a hospital reports the professional component with modifier 26. The hospital reports the technical component. Nobody reports the global service, because no single entity furnished all of it.

Third, and this is the one that catches people: the exams distinguish the CIC and COC credentials (inpatient and outpatient facility coding) from the CPC (physician/professional coding) precisely along this line. Know which side of it you are studying for. Chapter 39 covers the credentials in full.

1.6 What a coder actually does all day

Strip away the mythology and the job is this: a coder reads clinical documentation and translates it into standardized codes that are accurate, complete, specific, and defensible.

Every word in that sentence is load-bearing.

Reads. Not skims, not takes the provider's word for it, not codes from the superbill checkbox or the appointment type. A coder who codes from anything other than the documentation is not coding. Chapter 4 is about reading a note properly, and Chapter 38 is about what happens when a machine reads it first.

Clinical documentation. The office note, the operative report, the history and physical, the discharge summary, the pathology report, the radiology report, the anesthesia record, the nursing notes where they are codeable. A coder does not know what the provider did; a coder knows what the provider wrote. This is the first theme of this book and it is the hardest thing for clinicians entering the field to internalize, because they can see what obviously happened and are not permitted to code it.

Standardized codes. ICD-10-CM for the diagnosis, CPT and HCPCS Level II for the procedures and services, modifiers to qualify them, and — for inpatient hospital procedures — ICD-10-PCS.

Accurate. The code says what happened. Not more (upcoding), not less (downcoding). Both are errors, and the book is emphatic that the second is not the "safe" version of the first.

Complete. Every reportable condition and service is captured. Chapter 36 shows what an incomplete but accurate code costs under risk-adjusted payment.

Specific. Where the documentation supports laterality, stage, type, or episode, the code carries it. Where it does not, the coder either queries the provider or uses the unspecified code and understands what that costs.

Defensible. Two years from now, in front of somebody who was not there, you can reconstruct the path: this main term, this subterm, verified in the tabular, these conventions, this guideline, this edit. If you cannot say the path, you guessed.

A coder's day, concretely

A DAY IN A CODING QUEUE — five-physician family practice
[constructed teaching example]

  8:00   Open the coding work queue. 61 encounters from yesterday.
         Sort by date of service, oldest first — the charge lag clock
         is already running on the oldest ones.

  8:05   Encounter 1 of 61. Open the note. Read it. Assign:
         diagnoses, then procedures, then modifiers. 4 minutes.
         Post the charges.

  8:09   Encounter 2. The note says "knee injection" and nothing about
         which knee. STOP. This is a query, not a guess. Flag it,
         move on, come back when the provider answers.
         ← This will happen 3 to 6 times today.

  8:12   Encounters 3 through 22. Routine. Established patient visits
         with clear documentation. 3 to 5 minutes each.

  9:40   Encounter 23. A procedure the practice does twice a year.
         Open the CPT book. Read the subsection guideline. Read the
         parentheticals. Check NCCI. 22 minutes for one encounter,
         and it is 22 minutes well spent.

 10:02   Encounters 24 through 44.

 11:30   Three provider queries answered. Go back, finish those.

 12:00   Lunch.

 12:45   Encounters 45 through 61.

  2:30   Queue clear. Now the second half of the job:
         - review 5 charts flagged by the scrubber
         - answer 2 questions from the biller about denials
         - the monthly self-audit sample: 10 charts, scored
         - read the quarterly NCCI update that came out Monday

  4:30   Tomorrow's queue starts populating.

Notice the shape. Most encounters take three to five minutes. A few take twenty. The skill is not speed on the routine ones — the software does most of that work — it is recognizing which ones are not routine and being willing to stop.

📞 On the Phone

The query is the coder's most-used and most-regulated communication, and it is worth previewing here because new coders get it wrong in a specific way.

What a new coder writes: "Doctor, I think this should be a 99214 based on the complexity — can you add that you managed her diabetes and hypertension?"

That is a leading query. It supplies the answer, it names the code, and it asks the provider to document something in order to reach a billing outcome. At scale it is an enforcement exposure and it has ended careers. Chapter 38 §38.3 covers exactly why.

What a compliant query looks like: "The procedure note documents an intra-articular knee injection. The laterality is not specified in the procedure note or elsewhere in the record for this encounter. Please document which knee was injected."

No code named. No answer supplied. A clinical question about the record, answerable in either direction, and the provider is free to answer "left."

The rule, which Chapter 4 §4.9 develops: a query asks what the record does not say. It never proposes what it should have said.

What a coder is not responsible for

New coders — especially those arriving from clinical work — routinely take on responsibilities that are not theirs, and it makes them slower, more anxious, and occasionally noncompliant. The boundaries are worth stating plainly.

A coder is not responsible for the clinical decision. Whether the injection was the right treatment is the provider's judgment. The coder's question is whether the documentation supports the code, not whether the care was correct.

A coder is not responsible for whether the service is covered. Coverage is a payer determination against a policy, and a service can be perfectly coded and entirely non-covered. Chapter 22 develops this at length. The coder's obligation is the accurate code; the biller's is the coverage rule.

A coder is not responsible for the revenue. This is the important one, and it is the one under the most pressure. A coder who is measured on the practice's collections has been given an incentive that runs against their professional obligation. The correct code is the correct code. If the correct code produces less revenue than the practice expected, that is information — usually about the documentation — and not a problem for the coder to solve by choosing a different code.

A coder is not responsible for fixing the note. A coder may query. A coder may educate. A coder may not add to, alter, or interpret the record into something it does not say. Chapter 4 §4.5 covers what a legitimate addendum looks like and who may write one.

What a coder is responsible for is narrow and absolute: the code reflects the documentation, and the reasoning can be reconstructed. Everything else belongs to somebody else.

⚖️ Compliance Check

The pressure described above is not hypothetical, and the Office of Inspector General has been explicit about it for decades in its compliance program guidance: coding staff should not be compensated or evaluated in a way that creates an incentive to code to a revenue target rather than to the documentation.

If you are ever told, in words or by a productivity metric, that a certain level of service is expected regardless of what the notes say, you are being asked to do something that puts both you and the organization at risk. Chapter 5 §5.9 covers what to do about it — including the fact that the person who reports it is protected, and the person who complies is not.

Compliance program expectations and enforcement priorities change. Verify current guidance with your compliance officer and the primary source.

1.7 What a biller actually does all day

The biller's job starts where the coder's ends and is a different discipline entirely.

A biller ensures that a correctly coded encounter becomes a claim that can be adjudicated, gets adjudicated correctly, and is collected in full from every party that owes something.

Where coding is a discipline of accuracy, billing is a discipline of completeness, sequence, and persistence. A coder can be right about everything and still produce a claim that never reaches a human being because the subscriber identification number was transcribed with the letter O in place of a zero.

A biller's work divides roughly in four:

Getting the claim out clean. Claim scrubbing, edit resolution, ensuring every required field is populated and internally consistent, and submitting through the clearinghouse. Then — and this is the part that separates a good biller from a mediocre one — reading the acknowledgment reports. A claim that was rejected at the clearinghouse was never received by the payer, is not in anyone's system, will never be adjudicated, has no appeal rights, and is sitting in a report that in many practices nobody opens. Chapter 27 §27.7 is emphatic about this and so is every business office manager who has found six months of rejections in an unread folder.

Posting what comes back. Reading the remittance advice, applying payments and adjustments to the right lines of the right accounts, and — critically — noticing when the allowed amount is not what the contract says it should be. Chapter 28 covers underpayment identification, which is quiet, unglamorous, and one of the highest-yield activities in the entire revenue cycle.

Working what did not pay. Denials, rejections, no-response claims, and partial payments. Chapter 29 builds the taxonomy and Chapter 30 covers appeals.

Collecting from the patient. Statements, estimates, payment plans, financial assistance, and — sometimes — explaining to a frightened person, in ordinary words, what a deductible is. Chapter 32.

The biller's day

A DAY IN A BILLING OFFICE
[constructed teaching example]

  8:00   Yesterday's electronic remittance advice files. Post them.
         Autoposting handles 80%. Review the 20% it kicked out —
         these are the interesting ones and where the money hides.

  9:15   Clearinghouse rejection report. 7 claims never made it to a
         payer. Fix and resubmit today, because the timely-filing
         clock never stopped running on any of them.

  9:45   Denial work queue, SORTED BY APPEAL DEADLINE, not by age
         and not by dollar amount. Work the ones closest to expiring.

 11:30   Two calls to payer provider services. Combined hold time:
         41 minutes. This is normal and you should have something
         else to do while you wait.

  1:00   Accounts receivable follow-up: everything over 45 days with
         no payer response. Status inquiries, portal checks, calls.

  2:30   Two appeal letters. Records pulled, argument written,
         policy language cited, submitted, and — the step people
         skip — a follow-up task set for 30 days out.

  3:30   Patient calls. Four of them. Three are "what is this bill,"
         one is "I cannot pay this," and that fourth call is the one
         where a financial assistance application should be offered.

  4:15   Credit balance report. Two accounts overpaid. Refunds
         initiated — the 60-day clock started when they were
         identified, not when someone gets around to it.

⚠️ Where Claims Die

Six ways a business office loses money that have nothing to do with coding, ordered roughly by how often they go undetected:

1. Unread rejection reports. The claim never reached the payer. Nobody is waiting on it, because nobody knows it exists.
2. Denials worked in the wrong order. Appeal windows expire while a specialist works chronologically.
3. Underpayments accepted as paid. The remit says "paid," the amount is wrong, and autoposting closed the line.
4. Appeals submitted with no follow-up task. The appeal was mailed and then forgotten; there is no such thing as a payer that calls to remind you.
5. Credit balances left sitting. A compliance exposure disguised as a bookkeeping backlog.
6. Patient balances that were never explained. A statement that does not make sense does not get paid; it gets ignored, then aged, then written off or sold.

Not one of those is a coding error. All six are recoverable. Parts V and VI are about recovering them.

1.8 Where the money leaks, and what each leak costs

Here is the practical center of the chapter, and for readers on the 🏥 Practice Manager track, the most useful page in it.

A single encounter passes six checkpoints on its way to a zero balance. Each one has a characteristic failure, an owner, a cost if it fails, and — the number that actually drives decisions — a ratio between what it costs to prevent and what it costs to fix.

THE SIX LEAKS — one encounter, six places the money can go
[constructed illustrative figures; the ratios are the lesson, not the dollars]

  ┌─ 1. REGISTRATION ──────────────────────────────────────────────────┐
  │  FAILS AS:  wrong plan ID, wrong subscriber, coverage terminated,  │
  │             missing secondary, no authorization on file            │
  │  OWNER:     patient access                                         │
  │  DETECTED:  day 3 (rejection) or day 17 (denial)                   │
  │  PREVENT:   ~1 minute at the desk                                  │
  │  FIX:       15–40 minutes plus a resubmission or an appeal         │
  └────────────────────────────────────────────────────────────────────┘
  ┌─ 2. CHARGE CAPTURE ────────────────────────────────────────────────┐
  │  FAILS AS:  the service is performed and never charged             │
  │  OWNER:     provider / clinical staff / charge reconciliation      │
  │  DETECTED:  frequently NEVER                                       │
  │  PREVENT:   a daily reconciliation of schedule against charges     │
  │  FIX:       cannot be fixed after timely filing expires            │
  └────────────────────────────────────────────────────────────────────┘
  ┌─ 3. DOCUMENTATION ─────────────────────────────────────────────────┐
  │  FAILS AS:  the note does not support the service performed        │
  │  OWNER:     provider, with the coder as the detector               │
  │  DETECTED:  at coding (good), at audit (bad), at deposition (worst)│
  │  PREVENT:   a template and 30 seconds of provider attention        │
  │  FIX:       a query, or a lower code, or a refund                  │
  └────────────────────────────────────────────────────────────────────┘
  ┌─ 4. CODING ────────────────────────────────────────────────────────┐
  │  FAILS AS:  wrong code, missing modifier, wrong units, wrong order │
  │  OWNER:     coder                                                  │
  │  DETECTED:  scrubber (cheap), denial (expensive), audit (worst)    │
  │  PREVENT:   reading the note and the guideline                     │
  │  FIX:       corrected claim, appeal, or refund + corrective action │
  └────────────────────────────────────────────────────────────────────┘
  ┌─ 5. SUBMISSION ────────────────────────────────────────────────────┐
  │  FAILS AS:  rejected at the clearinghouse and never noticed        │
  │  OWNER:     biller                                                 │
  │  DETECTED:  when someone opens the report — or at timely filing    │
  │  PREVENT:   read the 277CA every single day                        │
  │  FIX:       trivial if caught in a week; total loss at 12 months   │
  └────────────────────────────────────────────────────────────────────┘
  ┌─ 6. FOLLOW-UP ─────────────────────────────────────────────────────┐
  │  FAILS AS:  denial unworked, appeal not filed, statement not sent  │
  │  OWNER:     denial specialist / AR / patient financial services    │
  │  DETECTED:  in the aging report, if anyone reads it                │
  │  PREVENT:   a queue sorted by deadline                             │
  │  FIX:       appeal if the window is open; write-off if it is not   │
  └────────────────────────────────────────────────────────────────────┘

Two things about that diagram deserve emphasis.

The cost of fixing a problem rises steeply and monotonically with how late it is found. A wrong plan identifier corrected at the front desk costs a minute. The same error corrected after adjudication costs a denial, a correction, a resubmission, and thirty more days of aging. The same error discovered after timely filing has expired costs the entire receivable. Nothing in the revenue cycle gets cheaper by waiting.

Leak 2 is the one nobody sees. Registration errors produce denials, and denials produce reports, and reports produce meetings. A service that was performed and never charged produces nothing. No denial, no report, no meeting — just an absence. In most organizations that go looking for it, missed charge capture turns out to be larger than the entire denial write-off, and it is invisible until someone reconciles the appointment schedule against the charge file. Chapter 23 §23.9 covers how.

🧮 Run the Numbers

Why prevention beats collection, in one calculation. [constructed illustrative figures]

A practice submits 2,000 claims a month with an average allowed amount of \$142.00. Its initial denial rate is 9% — 180 denied claims a month.

Suppose 60% of those denials are ultimately overturned or corrected and paid, and the rest are written off. Of the \$25,560 in denied allowed value each month (180 × \$142.00), the practice eventually recovers about \$15,336** and loses **\$10,224.

Now suppose front-end work — eligibility discipline, authorization tracking, a handful of scrubber edits — cuts the denial rate from 9% to 5%. That is 80 fewer denials a month. The recovered value barely moves; what changes is the write-off, which falls from \$10,224 to about \$5,680, and the labor, which falls by 80 denials' worth of work every month, forever.

The interpretation: the return on denial prevention is not primarily the money you stop losing. It is the eighty accounts a month that nobody has to touch at all. Chapter 29 §29.8 builds the business case in detail; Chapter 40 finishes it.

(These figures are constructed to make the structure visible. Denial rates vary enormously by specialty, payer mix, and organization — anywhere from low single digits to well above twenty percent. Measure your own; do not adopt anyone else's benchmark, including this one.)

1.9 How this book is organized and how to use it

Forty chapters, eight parts, in the order the work makes sense.

Part I — Foundations (Chapters 1–6). The system, the money, the rules. You will not code a single character until Chapter 7, and that is deliberate: a code is an answer, and you cannot evaluate an answer without the question.

Part II — Diagnosis Coding (Chapters 7–12). ICD-10-CM: structure, the lookup discipline, the Official Guidelines, and three chapters of applied coding across the body systems.

Part III — Procedure Coding (Chapters 13–19). CPT: structure, modifiers, two chapters on evaluation and management, two on surgery, and one on radiology, pathology, and medicine.

Part IV — HCPCS, Edits, and the Price of a Service (Chapters 20–23). The second code set, the edit files that decide what may be billed together, medical necessity, and where \$128.40 comes from.

Part V — Billing (Chapters 24–28). Patient access, the CMS-1500, the UB-04, electronic transmission, and payment posting.

Part VI — Getting Paid (Chapters 29–32). Denials, appeals, accounts receivable, and the patient's share.

Part VII — Facility, Specialty, and Risk (Chapters 33–36). MS-DRGs, APCs, specialty conventions, and risk-adjusted payment.

Part VIII — Audit, Certification, and Career (Chapters 37–40). How the work gets checked, how the tools are changing, how to get credentialed, and where the job goes.

The one instruction that matters more than the rest

Never code from a textbook.

Not from this one. ICD-10-CM is revised every October 1. CPT is revised every January 1. HCPCS Level II is revised quarterly. The National Correct Coding Initiative edit files are revised quarterly. Fee schedules, relative value units, diagnosis-related group weights, ambulatory payment classification rates, and coverage policies change at least annually and sometimes without warning.

Every code in this book is here to teach a structure. Every fee, allowed amount, relative value unit, weight, and payment rate is constructed and labeled. Every patient, provider, practice, hospital, and health plan is constructed and labeled. Use them to learn how the reasoning works. Then go get today's numbers from the current code book, the current fee schedule, and the payer's current published policy.

What does not expire is the structure of the classification, the logic of the conventions, the discipline of the two-step lookup, and the habit of verifying before you assign. That is what a textbook can teach, and it is what this one is built to teach.

🎓 Exam Watch

A word about the certification exams, because it shapes how you should read Parts II through IV.

The CPC, CCS, and CCA examinations are open book — though how the code books reach you differs by exam, by organization, and by delivery mode, and it changes; Chapter 39 §39.8 and your own candidate handbook govern that. What matters here is the consequence of the open-book format: it restructures what is worth memorizing: essentially nothing, and certainly not codes. What is tested is whether you can navigate — whether you can find the right code, apply the conventions, resolve the guideline conflict, and do it fast enough to finish.

Which means the exercises in this book that feel slow and mechanical — main term, subterm, verify in the tabular, check the conventions, check the guidelines — are the exam. Chapter 39 covers preparation, timing, and the rules about what you may write in the margins of a book you carry into the exam room. Read those rules before you annotate anything.

The answers you will need in your first week

Some questions arrive before the chapter that answers them. Here are the short versions, with pointers, so that you are not the person in the break room who cannot answer them.

"Why did the insurance company pay so little?" — Almost always, they did not. The plan paid its share of the allowed amount, and the allowed amount is what the contract says the service is worth. The gap the patient is looking at is the contractual adjustment, which nobody owes. §1.2, and Chapter 2 in full.

"Can we just bill the patient the difference?" — Not on in-network services. That is balance billing and it is prohibited by essentially every network contract. Out of network, the answer used to be yes and in a growing number of situations is now no, because of federal law. Chapter 32 §32.4.

"Why do I have two bills for one visit?" — Because two entities furnished two different things: the facility and the professional. §1.5.

"Can we change the diagnosis so it gets paid?" — No. You may correct a code that was wrong. You may not select a code because of what it pays. The distinction is the entire subject of Chapter 5, and it is the line between a correction and a false claim.

"The doctor says he spent forty minutes with the patient, so it's a level five, right?" — Maybe. Time is one of two permitted ways to select an office visit level since 2021, and it has to be documented as total time on the date of the encounter, and it has to include only countable activities. Chapter 15 §15.8.

"They denied it. Should I rebill?" — Depends entirely on why. A rebill of an unchanged claim is usually a duplicate denial and occasionally looks like something worse. Chapter 29 §29.6 covers corrected claims, voids, and replacements, and Chapter 30 covers when the remedy is an appeal instead.

"Do we need a prior authorization?" — Ask the payer, not a colleague, and document the answer with a reference number and the name of the person who gave it. Chapter 24 §24.6.

"What happens if we're audited?" — Someone who was not there reads your documentation and decides whether it supports what you billed. That is the whole of it, and it is why every chapter of this book returns to the same sentence. Chapter 37.

"Is this code still valid?" — Check the current code book. ICD-10-CM changed on October 1. CPT changed on January 1. HCPCS changed this quarter. Do not answer this question from memory, and do not answer it from this book.

🗂️ The Encounter

Account 10-4471 is now open.

🗂️ The Encounter

This is the progressive project. One encounter, coded and billed across all forty chapters. Every chapter adds a piece; every chapter says honestly what that piece does not settle. Appendix C is the same file, blank, for you to work alongside.

```text ACCOUNT 10-4471 — the file this book follows [constructed teaching example]

PRACTICE Northgate Family Medicine — five physicians, independent, mid-size metropolitan area, ~19,000 encounters a year. One coder. One biller. One practice manager.

PATIENT Established patient, age 58. Seen twice already this year.

COVERAGE Northfield Mutual Health Plan, commercial PPO, in network. $1,500 individual deductible — MET on February 28. $30 primary care office visit copay. 20% coinsurance on other services. $4,000 out-of-pocket maximum.

DATE OF Day 0 — Tuesday, March 14. SERVICE

THE VISIT Scheduled follow-up on three chronic conditions — type 2 diabetes, hypertension, hyperlipidemia — plus a new complaint: six weeks of right knee pain, worsening. Labs ordered. Blood drawn in the office. Right knee injected with 40 mg methylprednisolone acetate.

THE CLAIM Four lines. $367.00 in charges.

THE ARC Submitted day 2. Acknowledged day 3. Adjudicated day 17 — three lines paid, ONE LINE DENIED. Appealed day 24. Overturned day 59. Paid day 66. Patient statement day 70. Zero balance day 100. ```

What this chapter contributes. The frame. You now know that this account will produce four numbers — a charge, an allowed amount, a contractual adjustment, and a payment split between the plan and the patient — and that the whole book is the story of how those four numbers get settled.

You also know the six places this file can lose money, because §1.8 named them. Here they are against this specific encounter:

#	The leak, on Account 10-4471	Where it gets checked
1	Registration: is the plan identifier right, is coverage active, is the deductible actually met?	Ch. 24
2	Charge capture: the injection is performed by a medical assistant after the physician leaves the room. Does it get charged?	Ch. 23 §23.9
3	Documentation: does the note distinguish the chronic-disease management from the knee, in writing?	Ch. 4, Ch. 15
4	Coding: does line 1 carry the modifier that says the visit was separate from the injection?	Ch. 14
5	Submission: does the claim clear the scrubber, and does anyone read the acknowledgment?	Ch. 27
6	Follow-up: when one line denies on day 17, does anyone work it before the appeal window closes?	Ch. 29, Ch. 30

What it does not settle. Everything else. You do not yet know what was wrong with the patient's knee, what codes describe any of it, what the visit is worth, which line will be denied, why, or whether the denial is correct. Those are the next thirty-nine chapters.

Open questions carried forward:

• Q5 — What is actually wrong with the knee? Raised here. The March 14 note documents pain without a definitive diagnosis, and that distinction is going to matter. Resolved in Chapter 22.
• Q6 — Why did the practice charge \$185.00 for the office visit? Raised here. Resolved in Chapter 23.

Conclusion

A patient cuts their hand on a Sunday and receives two bills totaling \$4,522.00. The providers collect \$1,515.00. The patient owes \$503.00. And \$3,007.00 is erased by a contract nobody in the transaction has read.

Everything in this book is an elaboration of that sentence.

What was decided in this chapter. The four numbers and their arithmetic: charge minus allowed amount is the contractual adjustment; allowed amount minus patient responsibility is the plan payment. The six stages of the revenue cycle and what the money is at each one. The three-zone division of labor and the fact that the front end generates most of the back end's work while the middle concentrates the legal exposure. Why one encounter produces two claims. What a coder does and what a biller does, and why they are different temperaments. And the six leaks, with the observation that the cost of a fix rises steeply and monotonically with how late it is found.

What remains open. Nearly everything specific. The chapter has given you a map and no terrain.

The bridge to Chapter 2. The second number — the allowed amount — is the one that matters, and this chapter treated it as if it fell from the sky. It does not. It comes from a contract, which comes from a benefit design, which comes from a set of promises an insurer made to an employer. If you cannot read a benefit design, you cannot predict what a claim will pay, you cannot tell a patient what they will owe, and you cannot recognize an underpayment when it lands in your queue. Chapter 2 is that machinery: premiums, deductibles, copayments, coinsurance, network status, plan types, and the contracts that turn all of it into a number.

Key Terms

Revenue cycle — the complete administrative and financial process of a patient encounter, from scheduling and registration through coding, claim submission, payment, and collection to a zero balance. (Ch.1)

Encounter — a single instance of clinical care: one visit, one admission, one procedure. The unit of clinical work, and not the same thing as a claim or an account. (Ch.1)

Charge — what the provider bills for a service, set unilaterally in a fee schedule or chargemaster. An opening figure, not a price; almost nobody pays it. (Ch.1)

Claim — the standardized request for payment submitted to a payer, on a CMS-1500 or UB-04 or their electronic equivalents. The unit of billing. One encounter can generate two claims. (Ch.1)

Allowed amount — what the contract between provider and payer says a service is worth. The total the provider will receive from all sources combined, and the basis on which patient responsibility is computed. (Ch.1)

Contractual adjustment — the difference between the charge and the allowed amount, written off by the provider under the terms of the payer contract. Never billable to the patient on in-network services. (Ch.1)

Patient responsibility — the portion of the allowed amount the patient owes under their benefit design: deductible, copayment, coinsurance, or a combination. (Ch.1)

Accounts receivable (AR) — money that has been billed and not yet collected; the standing balance of everything outstanding. (Ch.1)

Clean claim — a claim that contains all required information, passes edits, and can be adjudicated without additional information from the provider. (Ch.1)

Remittance advice — the payer's explanation of how a claim was adjudicated: what was allowed, what was adjusted, what was paid, what was denied, and why. Electronic (an 835) or on paper. (Ch.1)

Denial — a payer's decision, after adjudication, not to pay all or part of a claim. Distinct from a rejection, which means the claim was never adjudicated at all. (Ch.1)

Payer — the entity financially responsible for a claim: a commercial insurer, a government program, a self-funded employer plan, or in some circumstances the patient. (Ch.1)

Provider — the entity or clinician furnishing the service. Where the distinction matters, the rendering provider performed the service and the billing provider submits the claim. (Ch.1)

Spaced Review

1. A practice charges \$310.00 for a procedure. The payer's contract allows \$186.40. The patient has met their deductible and owes 20% coinsurance. State all four numbers and both checks.

2. A patient calls to say their insurance "only paid \$90 of a \$400 bill." Before you look anything up, what is the most likely explanation, and what is the one number missing from their description?

3. One emergency department visit produces two bills. Explain to a patient, in two sentences and without using the words "professional" or "technical," why that is not a duplicate.

4. Rank these four failures by how expensive they are to correct, cheapest first, and say why: (a) a coding error caught by the scrubber before submission; (b) a wrong subscriber ID caught at the front desk; (c) a denial discovered ninety-one days after a ninety-day appeal deadline; (d) a service performed and never charged, discovered fourteen months later.

5. Which stage of the revenue cycle is the money a receivable, and what changes about the organization's position at the moment it becomes one?