Answers to Selected Exercises

Worked solutions to the daggered (†) and odd-numbered exercises from each chapter. Try every problem before reading its solution.

Chapter 1

Exercise 1.1

The four numbers are the charge, the allowed amount, the contractual adjustment, and the payment (which splits into patient responsibility and plan payment).

Charge − Allowed amount = Contractual adjustment. Allowed amount − Patient responsibility = Plan payment.

Exercise 1.3

An encounter is one instance of clinical care — a visit, an admission, a procedure. A claim is one request for payment submitted to a payer. An account is the financial record where the money lives.

One encounter, two claims, one account: a hospital emergency department visit produces a facility claim on a UB-04 from the hospital and a professional claim on a CMS-1500 from the emergency physician's group. Both describe the same visit. In many systems they sit on two account numbers under one guarantor, which is why patients receive two statements and believe they have been billed twice.

Exercise 1.4 †

\$46.40. Coinsurance is a percentage of the allowed amount, never of the charge.

  • 20% × \$232.00 = \$46.40 (correct)
  • 20% × \$400.00 = \$80.00 (wrong)

Why it matters: the error overcollects by \$33.60 on this single line. Systematically applied, it creates credit balances the practice is legally obligated to refund, and a knowingly retained overpayment is a compliance exposure, not a bookkeeping backlog (Ch. 31 §31.9). The reverse error — collecting nothing at the desk — converts a payment the patient was ready to make into a receivable that ages and is collected at a discount, if at all.

Exercise 1.5

Stage The money is a…
Access promise
Encounter promise
Coding claim
Submission receivable
Remittance decision
Follow-up recovery

Exercise 1.7 †

Definition without the word "clean": a claim that contains every required data element, is internally consistent, passes the payer's front-end and adjudication edits, and can therefore be processed to a payment decision without the payer needing anything further from the provider.

Three reasons an accurate claim might not qualify: 1. A demographic or coverage defect — invalid subscriber ID, wrong plan, coverage terminated on the date of service. The codes are perfect; the claim is unprocessable. 2. A missing required attachment or authorization number — the service was authorized, but the number is not on the claim, so the payer cannot match it. 3. A missing or invalid identifier — no rendering provider NPI, a taxonomy code the payer requires and did not receive, or a CLIA number absent on a laboratory claim.

None of the three is a coding error, which is the point of the exercise.

Exercise 1.9 †

Line Charge Allowed Contractual adj. Patient (20%) Plan
A 265.00 158.40 106.60 31.68 126.72
B 92.00 51.20 40.80 10.24 40.96
C 18.00 6.75 11.25 1.35 5.40
Total 375.00 216.35 158.65 43.27 173.08

Check 1: 375.00 − 216.35 = 158.65 ✓ Check 2: 216.35 − 43.27 = 173.08 ✓

(Line C's coinsurance is 20% × 6.75 = 1.35 exactly. Where a line produces a fraction of a cent, round at the line and let the total follow; do not round the total independently, or your checks will fail by a penny and you will spend twenty minutes finding it.)

Exercise 1.11 †

  • Contractual adjustment: \$5,120.00 − \$1,438.00 = \$3,682.00
  • Allowed after copay: \$1,438.00 − \$400.00 = \$1,038.00
  • Coinsurance: \$1,038.00 × 0.20 = **\$207.60**
  • Patient responsibility: \$400.00 + \$207.60 = \$607.60
  • Plan payment: \$1,438.00 − \$607.60 = \$830.40

Check 1: 5,120.00 − 1,438.00 = 3,682.00 ✓ Check 2: 1,438.00 − 607.60 = 830.40 ✓

Note that the patient owes \$607.60 on \$5,120.00 in charges — 11.9% — and 42.3% of the allowed amount. The second figure is the meaningful one.

Exercise 1.13

  • Deductible applied: \$120.00
  • Remaining allowed after deductible: \$186.40 − \$120.00 = \$66.40
  • Coinsurance: \$66.40 × 0.20 = \$13.28
  • Patient responsibility: \$120.00 + \$13.28 = \$133.28
  • Plan payment: \$186.40 − \$133.28 = \$53.12

Check: 133.28 + 53.12 = 186.40 ✓

The lesson: early in a plan year, the plan may pay very little on a claim that is fully covered. Nothing is wrong. Patients frequently interpret this as a denial.

Exercise 1.14 †

  • Denied claims per month: 1,400 × 0.11 = 154
  • Allowed value denied: 154 × \$118.00 = **\$18,172.00**
  • Recovered after rework (55%): \$18,172.00 × 0.55 = **\$9,994.60**
  • Written off: \$18,172.00 − \$9,994.60 = \$8,177.40

At a 6% denial rate: 1,400 × 0.06 = 84 denials, so 70 fewer denials per month for staff to touch — 840 a year.

The interpretation, which is the actual point: the recovered dollars barely move, because the same recovery percentage applies to a smaller base. What changes is the write-off (down to about \$4,459) and — more importantly — 840 accounts a year that nobody has to open, classify, research, correct, resubmit, or appeal. The return on prevention is mostly labor, not revenue.

Exercise 1.15 †

(a) Allowed amount = charges − insurance adjustments = \$1,940.00 − \$1,082.60 = \$857.40.

(b) Yes. \$857.40 − \$612.40 (insurance payment) = \$245.00 balance ✓

(c) No. The statement shows only that \$245.00 of the allowed amount was assigned to the patient. It does not say why. You would need the remittance advice or explanation of benefits, which carries the group code and claim adjustment reason code: PR-1 is deductible, PR-2 is coinsurance, PR-3 is copayment. A patient statement almost never distinguishes them, which is a large part of why patients call.

Exercise 1.17 †

Model answer: "That line is for supplies used during your visit. Under our contract with your plan, payment for supplies is included in the payment for the visit itself — so the plan doesn't pay a separate amount for them, and you don't owe anything for them either. It shows on the itemized list because the itemized list records everything that was used. Nothing on that line is your responsibility."

The technical name is packaging, and it is covered in Chapter 34 §34.5. The key teaching point is that "allowed \$0.00" is not the same as "denied," and a patient reading the statement has no way to know the difference.

Exercise 1.19 †

Three specific costs: 1. Terminated coverage. The patient changed jobs; the policy ended on the last day of the prior month. The claim denies as no coverage, and the balance moves to the patient thirty to sixty days later, when they are far less likely to pay it. 2. A changed plan under the same insurer. Same card, same carrier, different product with a different network, different copay, and possibly a different claims address. The claim goes to the wrong payer or the wrong product and denies. 3. New secondary coverage or a change in the coordination-of-benefits order. The claim goes to the wrong payer first and denies for COB.

Most likely: the second. A patient whose employer changed plans at renewal is typically unaware anything changed, hands over a card that looks identical to last year's, and answers "no" honestly when asked whether anything is different. Only the eligibility transaction catches it.

Exercise 1.21

For re-sorting: value is destroyed by deadline expiry, not by age. A \$1,200 denial with sixty days remaining is safe; a \$140 denial with three days is not. An age-sorted queue guarantees that some collectible accounts will be written off for timely filing, which is the most avoidable loss category in the cycle.

What you lose: age-sorted queues naturally surface the oldest and often largest balances first, and they make the aging report legible to management. A deadline-sorted queue therefore needs a secondary sort by dollar value within each deadline band, and a separate report for anything aging past a threshold regardless of deadline.

Exercise 1.22 †

  1. Stop the bleeding first. Find out whether the defect that caused the rejections is still active. If it is a bad payer identifier or a submitter setup problem, claims are still rejecting today.
  2. Establish the full scope. Forty-one is what was found. Pull the complete acknowledgment history and determine the actual date range and count.
  3. Check the timely filing status of every one, individually, against that payer's contract, and triage: correct and resubmit the ones with room, and prepare a timely-filing appeal package with proof of the original submission attempt for any that have expired. Clearinghouse acknowledgment reports are the evidence — preserve them.
  4. Correct and resubmit, in deadline order.
  5. The step people forget: put a daily control in place so it cannot recur — someone opens the acknowledgment report every business day, and the count of claims submitted must reconcile to the count acknowledged. A process that depends on someone noticing is not a control.

Exercise 1.25 †

**B — \$60.00.** Patient responsibility is 20% of the *allowed amount* of \$300.00. Answer A (\$100.00) is 20% of the charge. Answer C is the contractual adjustment. Answer D adds the adjustment to the coinsurance, which is the balance-billing error.

Exercise 1.27 †

B — a rejection. It never reached adjudication, so there is no decision to appeal. It must be corrected and resubmitted, and the timely filing clock never stopped.

Exercise 1.29 †

B — the allowed amount.

Exercise 1.31 †

Model answer (114 words):

Understanding your statement. The "charges" column lists everything that was done, priced at our standard rate. Your health plan and this practice have an agreement setting what each service is worth; that agreed figure is the allowed amount. The difference between our charge and the allowed amount is removed from your account entirely — you do not owe it and neither does your plan. What remains is divided between your plan and you, according to your benefit: your deductible, your copay, and your coinsurance percentage, all calculated on the allowed amount and never on the charge. The "balance due" line is your share. If it does not match your plan's explanation of benefits, call us.

Exercise 1.34 †

Expected: a charge, an allowed amount, a contractual adjustment, and a payment split between plan and patient.

Estimable now: the charge. Chapter 1 states the four claim lines total \$367.00.

Not estimable: the allowed amount depends on the Northfield Mutual contract, which has not been shown. The contractual adjustment is arithmetic on the allowed amount, so it follows. And patient responsibility depends on both the allowed amount and the benefit design — which is known (deductible met, \$30 copay, 20% coinsurance) but cannot be applied to an unknown allowed amount.

The exercise's real point: three of the four numbers are unknowable until you know the contract, and the contract is Chapter 2.

Exercise 1.36 †

Days the practice could have shortened, from the timeline in §1.3:

  • Day 0 → 1 (coding lag): one day is good. Charge lag is measured in most organizations and a one-day lag is not the problem here.
  • Day 1 → 2 (claim build and scrub): one day. Reasonable.
  • Day 17 → 20 (denial sat three days): recoverable — up to 3 days. The remit posted Friday; the denial was worked Monday. That is a weekend, not negligence, but a same-day denial triage process would have started the appeal on day 17.
  • Day 20 → 24 (records assembly, 4 days): recoverable — up to 3 days. Pulling one office note and writing one letter does not take four days; it waited in a queue.
  • Day 66 → 70 (statement lag, 4 days): recoverable — up to 3 days, depending on the statement cycle. Many practices run statements weekly, which builds in this delay by design.
  • Day 70 → 100 (patient payment, 30 days): partly addressable through statement design, an accurate pre-service estimate, and offering payment at the time of service — but not a process delay.

Total recoverable: roughly 9 days of the 100, all of it internal, none of it in the two long stretches where the claim was with the payer. The honest conclusion — and it is the chapter's argument — is that you cannot speed this file up meaningfully once the denial exists. The only large lever is preventing the denial, which would have removed 49 days at a stroke.

Exercise 1.39 †

  • Contractual adjustment: \$367.00 − \$216.28 = \$150.72
  • As a percentage of charge: \$150.72 ÷ \$367.00 = 41.1%

The emergency department example: \$2,645.60 ÷ \$3,842.00 = 68.9% on the facility claim.

Accounting for the difference: hospital chargemaster rates are typically set at a far higher multiple of the expected allowed amount than a physician practice's fee schedule is, for reasons Chapter 23 §23.7–23.8 develops — including that a hospital serves payers whose contracts are percentage-of-charges, and that chargemaster maintenance across tens of thousands of line items lags reality. A physician practice with a few hundred codes tends to set charges at a much tighter multiple. Neither percentage tells you anything about whether either organization was paid appropriately; that is the whole trap of the gross collection rate, and Chapter 23 §23.10 says so.


Chapter 2

Exercise 2.1

Premium — the recurring price of coverage. Never paid to a provider. Deductible — the amount the patient pays for covered services before the plan pays; paid to the provider. Copayment — a flat amount per service type; paid to the provider. Coinsurance — a percentage of the allowed amount; paid to the provider. Out-of-pocket maximum — a ceiling, not a payment; it is never paid to anyone, it only stops further patient liability.

Exercise 2.3 †

Participation means the provider has signed a network contract with an agreed fee schedule — a pricing question. Assignment means the provider accepts payment directly from the payer rather than having the payer send it to the patient — a routing question.

A situation where they differ: a provider who is out of network with a commercial plan may still accept assignment of benefits, so the plan pays the provider directly rather than mailing a check to the patient. There is no contracted allowed amount, the patient's cost share is at the out-of-network tier, and (absent a protection like the No Surprises Act) the balance may be billable — but the payment routing is direct. In Medicare, the two concepts are tightly linked and carry statutory meanings, including the limiting charge; see Chapter 3 §3.4.

Exercise 2.5

A third-party administrator administers a health plan — network, claims processing, member services — without bearing claims risk. The employer bears the risk and chose the benefit design.

Two patients with cards from the same insurer can therefore have materially different coverage because their employers bought different plans. The insurer's logo indicates who processes the claim, not who wrote the rules.

Exercise 2.6 †

Structure At risk for the provider
Fee schedule Volume — paid per service, so revenue depends on doing more
Percentage of billed charges Essentially nothing — the only structure where raising the charge raises the payment
Case rate Cost per episode — an extra three days changes nothing about the payment
Per diem Intensity within the day — length of stay is compensated, what happens during it is not
Capitation The whole population — the provider now bears insurance risk

Exercise 2.9

A work-related injury is excluded from health plan benefits and is covered by the employer's workers' compensation carrier. Health plans exclude it by contract; billing one for a work injury produces a denial and, at volume, looks like something worse.

Before the health plan becomes the payer, a written workers' compensation denial must exist — the carrier must have determined the injury is not compensable. Until then the health plan will (correctly) deny.

Exercise 2.11 †

Calculation Patient Plan Check
(a) 20% × 680.00 136.00 544.00 680.00 ✓
(b) full amount to deductible 680.00 0.00 680.00 ✓
(c) 210.00 + 20% × 470.00 = 210.00 + 94.00 304.00 376.00 680.00 ✓
(d) 210.00 + 30% × 470.00 = 210.00 + 141.00 = 351.00, capped at 250.00 250.00 430.00 680.00 ✓

Case (d) is the one to study: the arithmetic produces \$351.00, but the out-of-pocket maximum has only \$250.00 remaining, so the ceiling binds after the calculation and the plan absorbs the difference.

Exercise 2.13 †

Charge \$240.00:

Allowed Adjustment
(a) flat fee schedule 151.20 88.80
(b) 122% × 129.60 158.11 81.89
(c) 68% × 240.00 163.20 76.80

Charge raised to \$310.00:

Allowed Adjustment Change in allowed
(a) 151.20 158.80 none
(b) 158.11 151.89 none
(c) 210.80 99.20 +\$47.60

What changed: only the contractual adjustment, in two of three cases. Under (c), and only (c), the payment rose. (122% × 129.60 = 158.112 → \$158.11.)

Exercise 2.15 †

Aggregate design, \$5,000 family deductible with \$4,300 met (\$700 remaining): - Deductible: \$700.00 - Remainder: \$1,900.00 − \$700.00 = \$1,200.00; coinsurance 20% = \$240.00 - Patient \$940.00 · Plan \$960.00 · Check: 940 + 960 = 1,900 ✓

Embedded design, this member's \$2,500 individual deductible fully met: - No deductible applies to this member. Coinsurance 20% × \$1,900.00 = \$380.00 - Patient \$380.00 · Plan \$1,520.00 · Check: 380 + 1,520 = 1,900 ✓

Difference: \$560.00 on one claim, from a design distinction that is not printed on the card. This is why §2.2 says read the accumulator response, never the card.

Exercise 2.17 †

(a) The plan is a VALUE HMO and specialist visits require a referral. Without one on file, the claim will deny for lack of referral, and in most HMO designs the patient cannot be billed for a service denied because the provider failed to confirm the referral requirement — the contract typically places that obligation on the participating provider. The correct action is not to see the patient and bill anyway; it is to obtain the referral before the visit or reschedule.

(b) Deductible is met. Specialist copay \$65.00 applies to the office visit. The injection is "all other" — but note the response only itemizes outpatient surgery at 30%; it does not state a coinsurance for an office-based injection. **This is the trap in the exercise.** You cannot compute it from this response. You would call the payer or check the plan document. If the injection falls under a 30% coinsurance, the patient owes \$65.00 + (30% × \$74.00 = \$22.20) = \$87.20 — but that is an assumption, and it should be labeled as one rather than quoted to a patient.

(c) You cannot determine: any allowed amount; whether an injection requires authorization; whether the patient has other coverage; the coinsurance for service categories not listed.

Exercise 2.19 †

Sequence: (1) Confirm the denial is genuinely COB and not a mis-keyed subscriber ID. (2) Check the account for any secondary coverage already on file. (3) If the payer believes other coverage exists and you have no record of it, contact the patient, not the payer. (4) Ask the patient to call their plan's member services and update the coordination-of-benefits record — the payer will generally not accept the provider's word for it. (5) Document the call, set a follow-up, and refile once the payer's COB record is updated.

Whose problem it is: the member's. The payer suspends claims because its COB questionnaire was not returned, and only the member can resolve that.

What not to do: spend hours arguing with payer provider services. They cannot update a member's COB record from a provider call, and a biller who does not know this can lose weeks on it.

Exercise 2.21 †

The answer is no. Routinely waiving a Medicare beneficiary's cost sharing implicates the Anti-Kickback Statute (42 U.S.C. § 1320a-7b(b)) — the waiver can be characterized as remuneration to induce the beneficiary to obtain services — and it can constitute a false statement about the provider's actual charge, since the "charge" is now effectively lower than what is being represented. It also typically breaches the Medicare participation agreement's requirement to collect applicable cost sharing.

The compliant alternative: an individualized, documented financial hardship determination, made under a written policy applied uniformly, based on the patient's actual circumstances rather than on longevity as a customer. The line the OIG has drawn repeatedly is between a case-by-case documented hardship finding (defensible) and a routine or advertised waiver (not).

What to say to the owner: the request is generous and the answer has to be no in this form, but there is a legitimate path, and if the patient genuinely cannot afford the copay we should assess that properly and document it — which protects her and the practice.

Exercise 2.23 †

Financial consequence: an EPO generally has no out-of-network benefit except for emergencies. This is not "more expensive" — it is not covered. The patient would owe the surgeon's entire billed charge, with no contracted allowed amount, no contractual adjustment, and nothing counting toward their deductible or out-of-pocket maximum.

What to do without misrepresenting anything: state that plainly and early. Then help: confirm the network status directly with the plan rather than relying on a directory; ask whether the plan has a process for an out-of-network exception or gap exception where no in-network provider has the needed expertise (many do, and patients rarely know it exists); and offer to identify in-network surgeons with the relevant experience. Do not promise an exception will be granted, and do not tell the patient "it'll just cost a bit more."

Exercise 2.26 †

Most to least:

  1. (b) whether the deductible is met. §2.2 demonstrated this producing a swing from \$80.00 to \$400.00 on the same allowed amount — the largest single lever.
  2. (a) the coinsurance percentage. Real and proportional, but bounded: the difference between 20% and 30% on a \$400 allowed amount is \$40.
  3. (d) whether the plan is self-funded. It usually changes nothing about the arithmetic, but it can change what benefits exist at all and which appeal rights apply — occasionally decisive, usually not.
  4. (c) plan type. Predicts access rules, not cost. An HMO and a PPO with identical benefit designs produce identical patient responsibility. Plan type matters enormously for whether the claim is payable and almost not at all for how much.

The ordering is the point: newcomers rank (c) first because it is the most visible thing on the card.

Exercise 2.27 †

A — the mother's. February precedes July. The birth years (1990 and 1984) are the distractor; the rule uses month and day only.

Exercise 2.29 †

**B — \$125.00.** 25% of the **allowed** amount of \$500.00. Answer A is 25% of the charge. Answer C is the contractual adjustment. Answer D adds the adjustment to the coinsurance, which is the balance-billing error.

Exercise 2.31 †

B — workers' compensation.

Exercise 2.33 †

Model answer (52 words):

"Your copay covered today's office visit. The injection and the lab work go through your insurance separately, and those are subject to your coinsurance — so you'll likely see a small additional balance, probably under twenty dollars. Would you like to take care of that now, or would you rather wait for the statement?"

It sets the expectation, gives a range rather than a figure the practice cannot stand behind, and offers a choice rather than a demand.

Exercise 2.35

Model answer: "Your plan has a deductible, which means you pay the plan's discounted rate for services until you've spent a set amount for the year — and then the plan starts paying its share. You're still getting the benefit of the discounted rate right now; it's just that the plan's payment kicks in later."

Exercise 2.36 †

Line Charge Allowed Adjustment Patient Plan
99214-25 185.00 128.40 56.60 30.00 98.40
20610-RT 150.00 78.60 71.40 15.72 62.88
J1030 18.00 6.28 11.72 1.26 5.02
36415 14.00 3.00 11.00 0.60 2.40
Total 367.00 216.28 150.72 47.58 168.70

Check 1: 367.00 − 216.28 = 150.72 ✓ Check 2: 216.28 − 47.58 = 168.70 ✓

The rounding line is J1030. 20% × \$6.28 = \$1.256. Rounded at the line: \$1.26. Aggregate: 20% × (78.60 + 6.28 + 3.00) = 20% × 87.88 = \$17.576 → \$17.58, and the per-line sum is 15.72 + 1.26 + 0.60 = \$17.58. They agree here by coincidence — the single half-cent rounded up in both approaches. With two or three such lines rounding in different directions they would diverge by a cent or two, which is why the rule is to round at the line, in the payer's order, and reconcile to the remit.

Exercise 2.38 †

Deductible remaining \$900.00, applied in claim line order until exhausted. Allowed total is \$216.28 — less than the remaining deductible, so the entire allowed amount falls within it.

Line Allowed Patient Plan
99214-25 128.40 128.40 0.00
20610-RT 78.60 78.60 0.00
J1030 6.28 6.28 0.00
36415 3.00 3.00 0.00
Total 216.28 216.28 0.00

The patient owes \$216.28. The plan pays \$0.00. The contractual adjustment is unchanged at \$150.72 — it is a function of the contract, not of the benefit, and nothing about the patient's deductible position touches it.

Two further points. The copay may or may not apply before the deductible depending on plan design; many plans waive the copay when the deductible applies, and some collect both. Check the plan document. And the patient's remaining deductible after this claim would be \$900.00 − \$216.28 = \$683.72.

Exercise 2.39

Category 1 — coverage and benefit reasons: the service is not a benefit, a frequency limit was exceeded, an authorization was required and absent, or the patient was not eligible on the date of service.

Category 2 — payment edits: the payer's own rules about which codes may be paid together, in what quantity, and under what circumstances — bundling edits, unit limits, and modifier requirements.

Category 2 is not a coding error. The codes can be entirely correct and the edit still fires, because the edit is a statement about the payer's payment logic rather than about the accuracy of the coding. That distinction is Chapter 21 and Chapter 29, and it is exactly what happens to this claim.


Chapter 3

Exercise 3.1

Pricing — the Medicare Physician Fee Schedule and its relative value methodology, which most commercial professional contracts are written as a percentage of. Edits — the National Correct Coding Initiative and Medically Unlikely Edits, published free and quarterly and adopted by most commercial payers. Coverage structure — NCDs and LCDs, published and citable, and imitated by commercial medical policy. Compliance and audit — the contractor structure, extrapolation methodology, and documentation standards, which commercial special investigations units model.

Exercise 3.3 †

A benefit period begins on inpatient admission and ends after the beneficiary has been out of a hospital or skilled nursing facility for 60 consecutive days. The Part A deductible applies once per benefit period.

A beneficiary can owe more than one Part A deductible in a calendar year. What determines it is the gap between stays, not the number of admissions: two admissions separated by more than 60 days out of an inpatient setting fall in two benefit periods and carry two deductibles. Two admissions 30 days apart fall in one benefit period and carry one. This is the most-tested fact about Part A and the reason "once per year" is the standard wrong answer.

Exercise 3.5

Does: processes and pays claims; publishes local coverage determinations and billing and coding articles; enrolls providers; conducts medical review including prepayment review and Targeted Probe and Educate; decides the first level of appeal (redetermination); publishes bulletins and provider education.

Does not: set national policy or decide national coverage; override or contradict a national coverage determination.

Exercise 3.6 †

Status How paid By whom
Participating 100% of the fee schedule amount Medicare, directly to the provider
Non-participating, assigned 95% of the fee schedule amount Medicare, directly to the provider
Non-participating, unassigned up to the limiting charge (115% of the 95% amount) the beneficiary; Medicare reimburses the beneficiary 80% of the non-par amount
Opt-out whatever the private contract specifies the beneficiary; no claim may be submitted and Medicare pays nothing

Exercise 3.7

An NCD is a nationwide CMS decision, binding on all MACs. An LCD is one MAC's determination for its jurisdiction only, used where there is no NCD or to fill in details an NCD leaves open.

The billing and coding article — the LCD's companion document — usually carries the list of covered ICD-10-CM codes. Reading the LCD and stopping is the most common way to miss the thing you actually needed.

Exercise 3.9

The plan adjudicates instead of the MAC; there is a network; referrals are often required; prior authorization is common and a major denial source; cost sharing follows the plan's design and includes an out-of-pocket maximum that Original Medicare lacks; appeals begin with the plan; and the patient carries the plan's card rather than (or in addition to) the Medicare card.

Exercise 3.10 †

20 employees — attaches to age-65 entitlement with active employment. If the employer has 20 or more employees and the beneficiary is actively working, the group health plan is primary.

100 employees — attaches to disability entitlement. A large group health plan (100 or more employees) is primary for a beneficiary entitled by disability.

The distinction candidates miss: it is active employment, not merely having coverage. Retiree coverage for a 68-year-old does not make the group plan primary; Medicare is primary.

Exercise 3.13 †

Participating amount \$260.00:

Calculation Result
(a) Non-participating amount 260.00 × 0.95 \$247.00
(b) Limiting charge 247.00 × 1.15 \$284.05
(c) Medicare pays a par provider (deductible met) 260.00 × 0.80 \$208.00
(d) Beneficiary owes in (c) 260.00 × 0.20 \$52.00
(e) Non-par unassigned collects the limiting charge, from the beneficiary \$284.05
(f) Beneficiary net out-of-pocket in (e) 284.05 − (247.00 × 0.80 = 197.60) \$86.45

The beneficiary pays \$86.45** net in the unassigned case against **\$52.00 with a participating provider — a difference of \$34.45 — and the provider collects \$284.05 against \$260.00.

Exercise 3.15 †

Charged \$640.00 · approved \$318.00 · Medicare paid \$254.40 · maximum billable \$63.60.

  • Contractual adjustment: 640.00 − 318.00 = \$322.00
  • Medicare's 80%: 318.00 × 0.80 = \$254.40
  • Beneficiary's 20%: 318.00 × 0.20 = \$63.60
  • Check: 254.40 + 63.60 = 318.00 ✓

The assumption the notice is making: that the Part B annual deductible has already been satisfied. If it had not, Medicare would have paid less (or nothing) and the "maximum you may be billed" figure would be higher, because the deductible portion is entirely the beneficiary's.

Exercise 3.17 †

Per encounter, expected collection by payer:

Payer Share Allowed / expected Weighted
Commercial 46% 216.28 99.4888
Medicare 34% 168.24 57.2016
Medicaid (62% of Medicare) 14% 104.3088 14.6032
Self-pay (30% of \$367.00 charges) 6% 110.10 6.6060
Blended per encounter \$177.90

Sum: 99.4888 + 57.2016 + 14.6032 + 6.6060 = 177.8996 → \$177.90

On 1,000 encounters: \$177,900.** Against \$367,000 in charges — a gross collection rate of 48.5%, which tells you almost nothing (Chapter 23 §23.10), and against \$216,280 if every patient were commercial — a difference of \$38,380 on a thousand visits** attributable purely to payer mix.

Medicaid figure: 168.24 × 0.62 = 104.3088. Self-pay: 367.00 × 0.30 = 110.10. (Note that self-pay "collects" more per encounter here than Medicaid does, which is an artifact of the constructed percentages and worth discussing rather than generalizing — real self-pay collection rates on full charges are usually far lower.)

Exercise 3.19 †

  1. Which contractor published it, and whether that contractor has your jurisdiction. An LCD from another MAC does not govern your claims.
  2. The version and effective date. LCDs are revised; the policy in effect on the date of service governs, not the one currently displayed.
  3. Whether there is a companion billing and coding article, which usually carries the diagnosis code list — the LCD alone may not contain it.
  4. Whether an NCD exists for the service, which would supersede or constrain the LCD.

A fifth, worth adding: whether the policy has been retired, which the database will indicate.

Exercise 3.21 †

Send the claim to the Medicare Advantage plan. The patient is enrolled in Part C, so the plan adjudicates, not the MAC.

If you sent it to the MAC: it would be denied, typically with a reason code indicating the claim is not covered by this payer or contractor, and directing you to the correct payer. You would lose the time between submission and denial — commonly two to three weeks — against the plan's timely filing clock, which never stopped running.

Exercise 3.22 †

  1. Revenue per service. Participating pays 100% of the fee schedule; non-participating pays 95% assigned, or up to the limiting charge (115% of 95% = 109.25% of the par amount) unassigned. The unassigned route is the highest gross revenue per service.
  2. Collection burden. Participating and assigned claims are paid directly by Medicare, promptly and reliably. Unassigned claims must be collected in full from individual beneficiaries, who are then reimbursed by Medicare. That is a materially worse receivable with real collection cost.
  3. Patient impact. In the worked example, the beneficiary's net out-of-pocket rises from \$52.00 to \$86.45 on a \$260.00 service. For a population without an out-of-pocket maximum, that is not trivial, and it will affect who chooses your practice.
  4. Administrative consequences. Participating providers are listed in Medicare's directories and receive electronic remittance and direct deposit. Non-participation adds billing complexity and patient explanation.
  5. The risk I would flag. The limiting charge is a legal cap, easily exceeded by a fee schedule that is not maintained, and trivially detectable in data. A practice choosing non-participation must build a control that prevents charging above the limiting charge on unassigned claims, or the revenue advantage becomes a refund obligation with penalty exposure.

Exercise 3.24 †

The problem: Qualified Medicare Beneficiaries may not be billed for Medicare deductibles, coinsurance, or copayments — regardless of whether the state Medicaid program actually pays them. A system that automatically transfers the Medicare patient-responsibility balance to a patient statement will bill them, and the violation is invisible because it happens by default.

The control: 1. Flag QMB status on the account at registration, from the eligibility response, and again from the Medicare remittance advice, which carries a QMB indicator. 2. Suppress automatic patient-responsibility transfer for flagged accounts; route them to a review queue instead. 3. After Medicaid adjudicates, write off any remaining Medicare cost sharing rather than billing it — including when Medicaid pays zero because its rate is below what Medicare already paid. 4. Audit monthly: run a report of statements issued to accounts with a QMB flag. The correct count is zero.

The control has to sit in the system, not in a person's memory, because the failure mode is automation.

Exercise 3.26 †

  1. Check the NCCI procedure-to-procedure edit tables for the code pair. Most commercial bundling logic is adopted from or modeled on NCCI, and this resolves it more often than any other single step.
  2. Read the NCCI Policy Manual chapter for the relevant CPT section. It explains the reasoning, which is what you need for an appeal.
  3. Check the MUE table if the issue is units rather than a pair.
  4. Search the payer's provider portal and published reimbursement policies. Many payers publish more than practices realize; it is simply not indexed well.
  5. Call provider services and ask for the specific policy by name, and ask them to send it. Record the reference number and the representative's name.
  6. Check the contract for a clause incorporating the payer's published policies — which tells you whether the policy is binding on you and whether it may change unilaterally (Chapter 2 §2.6).

What you expect to find: an NCCI edit, or a payer policy derived from one, with a modifier indicator that determines whether the edit may be overridden at all. Chapter 21.

Exercise 3.27 †

B — \$437.00.** \$400.00 × 0.95 = \$380.00; \$380.00 × 1.15 = \$437.00. Answer A (\$460.00) is 115% of the participating amount, which is the standard error.

Exercise 3.29 †

B — the group health plan. Age-65 entitlement, actively working, employer with 20 or more employees.

Exercise 3.31 †

B — a Qualified Medicare Beneficiary. Not every dual eligible falls in the QMB category, and not every Medicaid recipient has Medicare, so A and C are both overbroad.

Exercise 3.33 †

B. An ABN is for a normally covered service expected to be denied as not reasonable and necessary. It is not used for statutorily excluded services (A), and issuing it routinely to everyone (C) is improper and can invalidate it.

Exercise 3.34 †

Model answer (88 words):

"Thank you — this is a Medicare Advantage plan, which means your Medicare benefits are administered by this company rather than by Medicare directly. I'm checking our network status with them now, because we contract with plans individually. If we're not in their network, I want to tell you that before you're seen rather than after, and I'll go over what your options are — including whether the plan has an out-of-network benefit and what it would cost. Give me two minutes to confirm rather than guess."

Exercise 3.37 †

Line Commercial allowed Medicare allowed Medicare as % of commercial
99214 128.40 96.52 75.2%
20610 78.60 63.28 80.5%
J1030 6.28 5.44 86.6%
36415 3.00 3.00 100.0%
Total 216.28 168.24 77.8%

The discount is not uniform. It ranges from 0% on the venipuncture to nearly 25% on the office visit.

What that suggests: the commercial contract is not a flat percentage of Medicare across all services. Different service categories are priced by different mechanisms — the office visit and the procedure come off the physician fee schedule, the drug is priced by a drug methodology, and the venipuncture comes off the clinical laboratory fee schedule, where the commercial payer has simply adopted the Medicare amount. A contract described as "a percentage of Medicare" frequently applies that percentage to only some of its lines, and a practice that models its expected revenue as a single multiplier will be wrong in both directions. Chapter 23.

Exercise 3.39 †

What the practice collects. Medicare pays 80% of \$168.24 = **\$134.59. Medicaid, as secondary, applies its own allowed amount — which the exercise stipulates is below what Medicare already paid — and therefore pays \$0.00**. Total collected: **\$134.59**.

What the patient may be billed: \$0.00.

The rule: federal law prohibits providers from billing a Qualified Medicare Beneficiary for Medicare deductibles, coinsurance, or copayments, regardless of whether the state Medicaid program pays them. The \$33.65 in Medicare coinsurance is not collectible from the patient and must be written off. It is not a bad debt and it is not a courtesy; it is a legal prohibition, and billing it is a violation. See §3.8 and Exercise 3.24 for the control that prevents it.


Chapter 4

Exercise 4.1

A code is a description of what a provider wrote, not of what a provider did. The record is not evidence of the encounter for coding purposes; for coding purposes it is the encounter.

Exercise 4.3 †

The assessment. It is the provider's conclusion about what is wrong, stated in the provider's own words, and it is the section a diagnosis code must be traceable to.

Not the chief complaint, because the chief complaint is the patient's reason for coming. A patient presents with chest pain and the provider concludes gastroesophageal reflux disease. In the outpatient setting a confirmed diagnosis replaces the symptom that led to it (Chapter 9 §9.6), so the assessment governs. Coding from the chief complaint systematically produces symptom codes where definitive diagnoses exist.

Exercise 4.5

Requirements: the provider who furnished the service must sign; the signature must be legible or otherwise identifiable and attributable to a specific individual; it must be dated. Electronic signatures satisfy this with a name, credential, and timestamp.

Four defects: (1) no signature at all; (2) an illegible or unattributable signature; (3) a stamped signature, generally unacceptable for Medicare; (4) a missing signature on the order for a service that requires one — a separate defect from anything wrong with the note.

Exercise 4.6 †

Addendum — new information added after the original entry was completed. Must be clearly identified as an addendum, separately dated and signed, with the original entry intact.

Late entry — documentation of something that happened earlier but was never recorded. Identified as a late entry, dated with the current date, and stating the date of the service being documented.

Amendment/correction — a change to an existing entry. The original content must remain legible and retrievable, the change dated and signed, and the audit trail preserved.

The principle all three satisfy: you may add to the record and you may correct the record; you may never make it appear that the record always said something it did not.

Exercise 4.9 †

The legal health record is what an organization declares by policy to be its official business record — what it would produce in response to a subpoena. The designated record set is a HIPAA term for records used to make decisions about individuals, which patients may access and request amendment of.

The designated record set is generally broader, because it includes billing records and other material an organization might not include in its declared legal health record.

Why a coder cares: what gets produced for an audit is defined by policy rather than by convenience (Chapter 37 §37.7); patients have a right of access and a right to request amendment, which occasionally surfaces as a patient disputing a documented diagnosis; and the audit trail is part of the story either way.

Exercise 4.11

Non-leading (does not supply the answer, name a code, state a financial consequence, or signal a preference); presents the clinical evidence from the record that raises the question; offers clinically reasonable options including where appropriate "clinically undetermined" and "other"; and is documented and retained, with its response becoming part of the record.

Exercise 4.13 †

What you can code: type 2 diabetes mellitus, unspecified — the assessment says "diabetes" and the problem list specifies type 2. Chronic kidney disease, stage 4 — it is on the problem list; whether a problem-list entry alone is codeable for a given encounter depends on whether it was addressed, which this fragment does not show.

What you cannot code: any diabetic kidney disease, and any relationship between the two. The linkage must be documented. (Note: ICD-10-CM's "with" convention creates assumed relationships for certain code pairs — Chapter 9 §9.7 — and diabetes-with-CKD is one of the pairings where the convention has been interpreted to permit assumption in the Tabular. This exercise is deliberately posed before that material, and the safe answer at this point in the book is: do not infer a linkage the record does not state, and check the convention in Chapter 9 before you rely on either answer.)

What you would query: whether the CKD was addressed at this encounter, and — if a linkage matters for reporting — whether the provider attributes the CKD to the diabetes. Also worth querying: the insulin. The medication list includes it and the assessment says "continue current regimen"; long-term insulin use has its own reportable status code (Chapter 12).

Exercise 4.15 †

All three could affect coding.

  • Adhesiolysis requiring 45 additional minutes — may support an increased-procedural-services modifier if the extra work is documented and substantial (Chapter 14).
  • Intraoperative cholangiogram — is a separately identifiable service in some circumstances and bundled in others; the code selected for the cholecystectomy itself differs depending on whether a cholangiogram was performed (Chapter 18).
  • Conversion to an open procedure — changes the code entirely. A converted procedure is generally coded as the open procedure, not the laparoscopic one.

What it demonstrates: the heading named a procedure that, by the end of the report, was not the procedure performed. A coder who codes from the heading would have billed a laparoscopic procedure that did not happen. Read the body. Always.

Exercise 4.17 †

The problem: the documentation asserts a comprehensive review of systems and a complete examination for a nine-minute medication refill. Either the documentation is false, or the visit was far more extensive than the schedule suggests. Almost certainly the former, produced by an auto-populating template.

The compliance exposure: the note supports a level of service the encounter did not contain. The provider signed it. If claims were selected at that level, the organization has submitted claims supported by documentation that asserts work not performed — which is the fact pattern in Case Study 1 and the reason the 2021 revision removed history and examination as office visit level drivers.

What I would do: (1) Code from what is actually supportable — for an office visit since 2021, the medical decision making or the time, neither of which is inflated by the template. A medication refill is a low-level visit regardless of how much text the template produced. (2) Raise the template configuration with whoever owns it, in the terms of §4.6 — the note is asserting things nobody did. (3) If the pattern is organization-wide, this is a compliance matter, not a coding preference, and it goes to the compliance officer.

Exercise 4.19 †

Faults in the original: names the diagnosis wanted, states the financial consequence, offers no alternative, asks for a conclusion rather than a clarification, and signals the preferred answer.

Compliant version:

Clarification is requested regarding the assessment for this admission.

The record documents: · Temperature 102.0°F on hospital day 1 · Intravenous antibiotics administered hospital days 1–4 · [Additional documented clinical indicators — vital signs, laboratory values, and the treating physician's documented observations — should be listed here from the actual record] · The assessment does not further specify the condition being treated

Based on your clinical judgment, can the condition be further specified? ( ) Sepsis ( ) Localized infection — please specify site ( ) Bacteremia ( ) Clinically undetermined ( ) Other: __

Please document your response in the medical record. This query is not intended to suggest any particular response.

Note that the compliant version does not invent clinical indicators. If the record does not contain enough indicators to support the question, the correct action is to ask nothing rather than to construct a case.

Exercise 4.21 †

Outpatient: code the documented signs, symptoms, or findings — not the possible diagnosis. The outpatient guideline prohibits coding uncertain diagnoses. "Possible acute blood loss anemia" supports coding the abnormal hemoglobin or the documented blood loss, not anemia.

Inpatient: code the condition as if it existed. The inpatient guideline permits coding a diagnosis documented at discharge as "probable," "suspected," "likely," or "possible" as though established, because the intent is to capture the diagnostic workup and resources consumed.

The rule that makes them different: ICD-10-CM Official Guidelines Section II/III (inpatient) versus Section IV (outpatient). Chapter 9 §9.5 covers it. This is one of the small number of places where the two settings do exactly opposite things, and it is examined constantly.

Exercise 4.23 †

Options, in order of preference:

  1. Escalate the query through the established process — a second request, a call, or escalation to the physician advisor or department chair if the organization has one. Most query programs have a defined escalation path and a defined timeframe; use it.
  2. Code what is documented and submit. A less specific code that is fully supported is always available and always defensible. The claim is not wrong; it is less specific than it could have been.
  3. Hold the claim only if the timely filing window genuinely permits it and the organization's policy allows. This is rarely the right answer as a deadline approaches.

What is not available: coding the answer you expected the query to produce. An unanswered query is not an answer, and a coder who assigns the code they were hoping for has made the query pointless and created a false record.

Exercise 4.25 †

The answer is no, and it is not a close question.

Three reasons:

  1. The timing becomes part of the record. Even a truthful, properly labeled addendum written after a records request carries a date the reviewer will see. Documentation that appears in response to a request is worth less than nothing evidentially — it invites the reviewer to look harder.
  2. Improperly labeled, it is a false statement. An addendum that is not identified as one, or a note altered to appear contemporaneous, moves the organization from a payment problem to a potential fraud problem. The audit trail will show it.
  3. The correct remedy exists and is cheaper. If the documentation is deficient, the finding is legitimate: accept it, repay what was billed without support, and fix the workflow. Chapter 37 §37.9. A repayment is survivable; a finding that records were altered after a request frequently is not.

What to say: "We send what we have. If some of these are thin, we'll find that out now instead of in a much worse way later — and I'd rather spend the afternoon figuring out which workflow produced the thin ones."

Exercise 4.27 †

The case, addressed to a practice manager:

Right now our notes assert a complete review of systems on every encounter, including visits where nobody asked twelve systems' worth of questions. Three consequences.

First, it is not true, and the provider signs it. That is the exposure, and it is the kind auditors find with a script rather than a reviewer.

Second, it no longer buys us anything. Since the 2021 revision, review of systems does not drive an office visit level. We are carrying the risk of a false assertion in exchange for a benefit that was eliminated.

Third, it makes our notes worse. A reviewer cannot tell our thorough visits from our brief ones, which weakens every appeal we file.

What it costs: a configuration change, and a short adjustment period in which providers fill in the ROS section themselves for the encounters where it matters clinically. There is no revenue impact under the current level-selection rules. The main cost is the conversation with the providers, and the framing that works is that the change makes their notes reflect what they actually do.

Exercise 4.29 †

B.

Exercise 4.31 †

C. Attestation identifies the author of an otherwise unsigned entry. It cannot supply a missing signature on an order (A), cannot add clinical content (B), and does not remedy an illegible note's content (D).

Exercise 4.33 †

B. In the outpatient setting, do not code a probable, suspected, or rule-out condition; code the documented signs, symptoms, or reason for the encounter. The inpatient rule is the opposite — Exercise 4.21.

Exercise 4.35 †

Model answer (98 words):

You know more medicine than I do, and that is going to make one part of this job harder rather than easier. When you read a note, you will see what happened, because you have been in that room a thousand times. The rule is that we code what the provider wrote, not what we can tell they did. Not because your judgment is unreliable — because the code is a statement to a payer about the record, and a stranger reading that record two years from now has only what is on the page. If it is not there, we query. We never supply it.

Exercise 4.38 †

Documented, by claim line:

Line The note supplies
Office visit Four assessed problems with individual plans; three medications reviewed and continued; two tests ordered with stated reasons; an explicit statement that time was not used for level selection
Injection Site (knee), laterality (right), approach (lateral suprapatellar), needle gauge, consent, absence of aspirate, explicit absence of imaging guidance, patient tolerance, dressing
Drug Agent (methylprednisolone acetate) and dose (40 mg)
Venipuncture Explicitly documented: "Blood drawn in office by venipuncture"
Diagnoses Type 2 diabetes mellitus; essential hypertension; hyperlipidemia; right knee pain with an explicit statement that no definitive diagnosis was established

Not documented:

  • Any statement in the assessment that conservative therapy was tried and failed (it is in the HPI)
  • Any statement that the decision to inject was made during this visit
  • Any linkage between the chronic kidney disease on the problem list and the diabetes
  • Whether the vial was single-dose or multi-dose, or whether any drug was discarded
  • Total time (deliberately — the note says time was not used)
  • Any type specification for the hyperlipidemia

Exercise 4.40 †

The sentence: "Six weeks of intermittent NSAID therapy has not adequately controlled symptoms, and the patient's function and sleep remain affected; intra-articular corticosteroid injection is therefore indicated at this visit."

Why a coder may not write it: it is a clinical assertion — that therapy failed and that the injection is therefore indicated — and only the treating provider may make it. Writing it would be creating documentation, which is the line §4.5 and §4.9 both draw.

Who may: the provider, prospectively, as part of how they document this kind of encounter. The coder's legitimate move is education, not authorship: show the provider what a reviewer looks for and where, and let them change what they write going forward. That is a template and training conversation, not a chart-by-chart one.

(A compliant query is a poor fit here, because nothing is ambiguous — the record is clear and complete for coding. The gap is in placement, not in content, and the remedy is prospective.)


Chapter 5

Exercise 5.1

That the services were actually furnished; that they were medically necessary; that the information is true, accurate, and complete; and that the claim complies with applicable law, including the Anti-Kickback Statute and the physician self-referral prohibition.

Exercise 5.3 †

Prong What it is Example
Actual knowledge You know the information is false A biller submits a claim for a visit they know did not occur
Deliberate ignorance You avoid finding out A practice is told its documentation does not support its level 4 volume and declines to review it
Reckless disregard You do not care enough to look properly A distinct-procedural-service modifier is appended by macro to every claim carrying a code pair, with no one reading an operative note (Figure 5.1)

The statute states expressly that no proof of specific intent to defraud is required.

Exercise 5.5 †

Anti-Kickback Statute Stark
Nature Criminal (with civil consequences) Civil
Intent Knowing and willful None — strict liability
Persons covered Anyone Physicians, and entities billing their referrals
Services covered Any item or service payable by a federal health care program Designated health services payable by Medicare
Protection Safe harbors — voluntary; all elements required Exceptions — compliance is mandatory for the arrangement to be lawful

Exercise 5.7

Exclusion prohibits any federal health care program from paying for items or services furnished, ordered, or prescribed by the excluded person — and the prohibition extends to an excluded person employed in any capacity by a provider that bills federal programs, including administrative and management roles.

Why it ends employability: because essentially every American healthcare employer bills a federal program, employing an excluded person exposes them for every claim that person touches. There is no non-billing role that solves it. The exclusion does not restrict a job function; it makes the person unhirable across the sector.

Exercise 5.8 †

  1. Written policies, procedures, and standards of conduct — so the rule exists outside someone's head.
  2. A designated compliance officer and committee — so someone owns it, with access to leadership.
  3. Effective training and education — so the rule reaches the people who apply it.
  4. Effective lines of communication — so a person can report without going through the person they are reporting about.
  5. Internal monitoring and auditing — so problems are found while they are still errors.
  6. Enforcement through well-publicized disciplinary guidelines — so the rule has consistent consequences.
  7. Prompt response to detected offenses and corrective action — so a finding produces a change.

Exercise 5.11 †

  1. It is inaccurate. A code that understates the service misrepresents the encounter as surely as one that overstates it.
  2. It forfeits earned revenue on every instance, permanently, with no offsetting benefit.
  3. It corrupts downstream data — quality measurement, risk adjustment (Chapter 36), utilization analysis, and the practice's own understanding of its work.
  4. It is not a legal defense. A false record is a false record in either direction, and nothing in the False Claims Act's text distinguishes the direction of the error.

The reason the belief persists is that downcoding does not get audited, because nobody audits for underpayment. That is a fact about detection, not about accuracy.

Exercise 5.13 †

(a) False Claims Act. The audit eleven months ago supplies the knowledge element; the continuation supplies the conduct. Intent to defraud need not be proven — this is deliberate ignorance at minimum. Also potentially the Civil Monetary Penalties Law.

(b) Anti-Kickback Statute. Free use of space is remuneration. Intent is required (knowing and willful), but the "one purpose" standard means the arrangement can violate the statute if inducing referrals was a purpose even among legitimate ones. Any resulting claims may also be false claims.

(c) Stark. A financial relationship plus referrals for designated health services with no applicable exception. No intent required — this is the strict liability provision, and "we never meant anything by it" is not responsive.

(d) False Claims Act, via the sixty-day overpayment rule. An identified overpayment retained past sixty days becomes an obligation, and improperly avoiding an obligation to repay is prohibited conduct. Eight months is not close.

(e) False Claims Act, reckless disregard. Also unbundling as a coding matter and potentially the Civil Monetary Penalties Law. Nobody formed an intent; the configuration operated at volume without review.

Exercise 5.15 †

Compromised elements:

  • Element 2 (designated compliance officer) — the officer's independence is destroyed by reporting to the subject of the complaint.
  • Element 4 (effective lines of communication) — a staff member cannot report the physician-owner's coding to a person who reports to that owner. Practically, the channel does not exist.
  • Element 6 (enforcement) — disciplinary guidelines cannot be applied consistently to a person who controls the discipliner's employment.
  • Element 7 (corrective action) — flows from the same problem.

Minimum viable fix for a six-person practice:

  1. An external reporting route. A contracted compliance consultant, an attorney, or an external hotline that reports to all owners jointly rather than to one. This is inexpensive and it is the single highest-value change.
  2. A written recusal rule stating that a compliance matter involving an owner is handled by the external route and that the owner is recused from the review.
  3. External chart review for owner-provider coding, at least annually — because internal review by an employee of the owner is not credible even when it is honest.
  4. Written non-retaliation commitment, signed by all owners.

A six-person practice cannot build a compliance department. It can buy independence for a few thousand dollars a year, and independence is the only element it genuinely cannot manufacture internally.

Exercise 5.17 †

(a) Line 3 carries a distinct-procedural-service modifier asserting that the debridement was separate from the rotator cuff repair. Under the correct coding edits, limited debridement in the same anatomic region as the repair is included in the repair. The operative notes document debridement of the same structures repaired — so the modifier asserts a distinction the documentation does not support. And the modifier was applied by a billing macro, not by a coder reading the note.

(b) Line 2 is an add-on code. Add-on codes describe additional work performed with a primary procedure and are expected to be reported alongside it. They are not subject to the multiple-procedure reduction and do not take modifier 51. Reporting an add-on code with its primary procedure is correct, not unbundling.

(c) Because the defense to an unbundling allegation is contemporaneous documentation that the debridement was distinct — and no operative note documented it. The surgeons' recollection may be accurate and is worth nothing evidentially, because nothing in the record distinguishes those 11 claims from the other 31.

(d) Demand: 42 × \$612.40 = **\$25,720.80. If the payer extrapolated across the full 18 months at the same error rate, the demand becomes the sampled rate projected across the universe of similar claims — which, for a practice performing this procedure regularly, could be several multiples of the sampled figure. Chapter 37 §37.6 works the arithmetic. The sample is not the exposure.**

Exercise 5.19 †

Three questions before this report is filed:

  1. What is the look-back period, and what is the exposure across it? Twenty-five charts is a sample. The population is every claim for that service over the period the pattern existed. Sizing by the sample is the error Case Study 2 warns about.
  2. Are we stopping or holding anything now? Every claim submitted after this report is a claim submitted with knowledge (§5.2). The report changes the practice's legal position on all subsequent claims immediately.
  3. What is the corrective action, who owns it, and by when? "Recommend provider education" is not a corrective action plan. It names no owner, no deadline, and no re-audit.

What happens legally if it is filed and nothing else occurs: the report establishes the knowledge element. Every subsequent identical claim moves from error toward abuse and, with continuation, toward a knowing false claim. The audit becomes the government's exhibit. This is precisely §5.6's point that element 7 is the one organizations fail, and §5.2's point that an unactioned audit finding is the most dangerous document in an organization.

Exercise 5.21 †

Step 1 — Make sure you are right. Re-read the note. Confirm no time is documented anywhere, including in a separate attestation. Confirm the MDM analysis: what problems were addressed, what data, what risk. Check whether the practice has any standing guidance you have missed.

Step 2 — Ask, do not accuse. "I want to make sure I've got this right, because if you spent 45 minutes I don't want to underbill it. The note doesn't document time anywhere, and on decision making I'm getting to a three. Am I missing something in the record?"

Step 3 — Put it in writing. A short email restating the reading and the rule.

Step 4 — Code what is documented. Level 3. Not negotiable.

Step 5 — Escalate if instructed to code the 5 anyway.

Step 6 — Outside advice if the channel fails.

The legitimate path to a level 5: documenting the total time on the date of the encounter, contemporaneously. Under the 2021 framework, time is one of two permitted bases for selecting an office visit level (Chapter 15 §15.8), and 45 minutes of documented total time on the date of the encounter would support a higher level on its own. The physician's problem is not that they did not do the work. It is that the record does not contain the one fact that would prove it, and only they can supply it — prospectively.

Exercise 5.23 †

What you know: essentially all imaging referrals go to a facility that opened six months ago, and a physician-owner referred to "having a piece of" it.

What you do not know: whether the ownership interest is real, what its structure is, whether an exception applies, whether the referral pattern has any other explanation (proximity, scheduling capacity, quality, patient preference, an insurer's steerage), and whether anyone has already disclosed and structured the arrangement properly. A physician may lawfully own an imaging facility; whether these referrals are lawful depends on facts you do not have.

What you should do: report the observation — the referral pattern and the comment — through the compliance channel, factually, without characterizing it. Document that you did, with the date.

What you should not do: investigate it yourself; ask the physician about their ownership; discuss it with colleagues; state to anyone that there is a Stark or kickback problem; or, at the other extreme, decide it is not your business and say nothing. You are not being asked for a legal conclusion. You are the person who noticed, and noticing is the contribution.

Exercise 5.25 †

The exposure: accessing a record without a business reason is a HIPAA violation regardless of whether anything is disclosed. The Privacy Rule permits use for treatment, payment, and operations; curiosity is none of these. It is detected by audit log review, it is one of the most reliable causes of termination in healthcare, and it can carry individual penalty exposure. The absence of disclosure mitigates harm; it does not make the access permissible.

Your obligation: report it through the compliance channel. This is uncomfortable and it is not optional — the organization's Privacy Rule obligations include mitigating known violations, and knowledge held by workforce members is knowledge held by the organization. Say it factually and without characterization, as in 5.23. If your organization has an anonymous route, using it is legitimate.

Exercise 5.26 †

B.

Exercise 5.28 †

B — 60 days.

Exercise 5.30 †

B — payment and health care operations. Minimum necessary does not apply to disclosures for treatment.

Exercise 5.32 †

B.

Exercise 5.33 †

Model answer (138 words):

Subject: Level of service on the 3/14 encounters — my reading

Following up on our conversation so we have a record of where we landed.

I reviewed the six encounters. Each documents one stable chronic problem with a medication refill and no other addressed problems. Under the 2021 office visit guidelines, that supports low-complexity decision making. Total time is not documented on any of the six, so time-based selection is not available.

On that basis I have coded these as level 3. If the encounters involved work the notes do not capture, I would genuinely like to know — the documentation may be understating what is being done, and that is fixable going forward.

Happy to have compliance or an external auditor look at the same six if a second opinion would help.

Exercise 5.36 †

What Figure 4.2 contains that the counterfactual does not:

Sentence Work it does
"Continue metformin 1000 mg twice daily." Prescription drug management for problem 1, individually stated
"Hemoglobin A1c ordered today to reassess control." A test ordered with a stated clinical reason
"Essential hypertension — at goal on current therapy. Continue lisinopril 20 mg daily." Problem 2 assessed and managed independently
"Hyperlipidemia — continue atorvastatin 40 mg daily. Lipid panel ordered today." Problem 3 assessed, second test ordered
The HPI's first paragraph (glucose readings, blood pressure log, negative review of relevant symptoms) The evaluation underlying all three chronic assessments
The cardiac, respiratory, and diabetic foot examination Examination directed at the chronic conditions, not the knee

The sentence doing the most work: "Hemoglobin A1c ordered today to reassess control."

Because it is the clearest evidence of active management independent of the knee. Continuing a medication can be characterized as administrative; ordering a test with a stated diagnostic purpose is an evaluation and a decision, on a problem the procedure had nothing to do with. It is the hardest single item for a reviewer to dismiss.

Exercise 5.38 †

Yes — and this is the point of the question.

The claim itself is accurate. The documentation supports modifier 25. If this single claim were reviewed in isolation, it would pass.

But the practice's process is to append the modifier by rule, without anyone reading a note. That process:

  • produces correct claims by coincidence rather than by determination;
  • will produce incorrect claims wherever the documentation does not happen to support the modifier, at whatever rate that occurs; and
  • constitutes reckless disregard under § 3729(b)(1) with respect to the population of claims — the organization is not looking, at volume, at a question that determines whether its claims are true.

The distinction to hold: an individual claim's accuracy is judged on its documentation. An organization's exposure is judged on its process. A practice whose claims are right by accident has the same knowledge posture as one whose claims are wrong by accident, and the only thing separating them is which way the underlying documentation happened to fall.

This is exactly the fact pattern in Figure 5.1, with a luckier outcome on the sampled claim.


Chapter 6

Exercise 6.1

Book Question Maintained by Changes
ICD-10-CM What was wrong with the patient? NCHS and CMS October 1
CPT (HCPCS Level I) What did the provider do? American Medical Association January 1
HCPCS Level II What was supplied or administered that CPT does not cover? CMS quarterly

Exercise 6.3 †

The two parts used in a fixed order: the Alphabetic Index (look up the condition by name) and the Tabular List (verify it and read the instructions that govern it). Index first, always.

The three specialty tables: the Table of Neoplasms, the Table of Drugs and Chemicals, and the External Cause Index.

At the front: the Official Guidelines for Coding and Reporting — free, reissued annually, binding for the code set under HIPAA, and unread front to back by most working coders.

Exercise 6.5 †

  1. Whether the documentation supports the code. It has not read the note and cannot.
  2. Which of two defensible codes better describes what happened.
  3. Whether a query is needed.
  4. Whether the guidelines' conventions were correctly applied — it will flag a hard conflict and will not catch a judgment error.
  5. Whether the code you entered is the code you meant.

Exercise 6.7

The EHR owns the clinical record: notes, orders, results, medications, problem list, images, audit trail. The PMS owns the financial record: demographics, guarantor, insurance, scheduling, charges, claims, payments, adjustments, accounts receivable, statements.

The coder sits between them — reading left, writing right. In a non-integrated environment the interface between the two is where charges are lost, silently, producing no error and no denial (Chapter 1 §1.8, leak 2).

Exercise 6.8 †

A superbill or encounter form is a checklist of a practice's common codes on which a provider marks what was done.

It is not a coding decision because it is a communication tool — a provider's indication of what happened, not a verified assignment from documentation. Coding from a superbill without opening the note is coding from a checkbox, which is Chapter 5 §5.3's reckless disregard in its most ordinary form.

It decays because it is built once and the code sets change annually and quarterly. A superbill not reviewed since the last two update cycles contains deleted codes, lacks new and more specific ones, and — most dangerously — may carry codes whose descriptors changed while the numbers stayed the same, which produces no rejection at all.

Exercise 6.11 †

  JANUARY 1     CPT: new, deleted, revised codes; revised guidelines;
                new and revised modifiers. Medicare conversion factor
                and fee schedule take effect.

  QUARTERLY     HCPCS Level II updates.
  (Jan/Apr/     NCCI procedure-to-procedure edits update.
   Jul/Oct)     MUE values update.

  OCTOBER 1     ICD-10-CM: new, deleted, revised codes; revised
                Official Guidelines. Hospital inpatient payment year
                begins — new MS-DRG assignments and weights.

  CONTINUOUS    LCDs revised. Payer policies change. Nothing
                announces this to you.

Exercise 6.13 †

The Tabular List. The seventh-character requirement is stated as an instruction at the category level — not at the individual code — so you must be looking at the category in the Tabular to see it. An index entry will not tell you, and this is one of several reasons the two-step rule exists (Chapter 8 §8.1).

Exercise 6.15 †

The Medicare Coverage Database, searched by code. Then, within it: the LCD for the policy, and its companion billing and coding article for the list of ICD-10-CM codes that support medical necessity.

Then verify two things about the version: that the publishing contractor's jurisdiction is yours, and that the effective date covers the date of service.

Exercise 6.17 †

The CPT surgery section guidelines, at the front of the Surgery section. They define what the surgical package includes.

Then, for the specific global period assigned to that code, the Medicare Physician Fee Schedule relative value file, which carries the global period indicator (000, 010, 090, XXX, YYY, ZZZ). Chapter 17 §17.2.

Note that these are two different sources answering two halves of one question — CPT defines what the package is; the fee schedule file says how many days it runs for that specific code.

Exercise 6.19 †

The NUCC 1500 Health Insurance Claim Form Reference Instruction Manual, free from the National Uniform Claim Committee. It is the authoritative field-by-field instruction for the CMS-1500 and it answers questions that no coding reference does. Chapter 25.

Exercise 6.22 †

Two things:

  1. Verify the code in the Tabular List exactly as you would verify a code found in the paper index. The two-step rule does not stop applying because step one happened on a screen.
  2. Re-check the pathway answers against the note. Every answer you gave narrowed the result, and a single answer given from assumption rather than from documentation produces a confidently wrong code with no indication that anything went wrong.

Why the output is not sufficient: an encoder's result carries exactly as much reliability as the weakest answer in the pathway, and the pathway does not show you which answer that was. The output looks authoritative, which makes it more dangerous than a paper error, not less.

Exercise 6.24 †

The half-day project:

  1. Export the edit engine's rule configuration. In most systems this is a menu item and has always been available.
  2. For each rule, document what it changes, on which claims, and to which payers.
  3. For each rule, identify an owner — someone who can explain why it exists and confirm it is still needed. Expect that several will have none.
  4. For each rule, pull a month of affected claims and read ten of them. This is the step that finds things, and it is the step inventories skip. A rule's description tells you what it was meant to do; its output tells you what it does.
  5. Classify: keep (documented, current, owned), delete (nobody can justify), or escalate (it changes the factual content of claims and the change may not be supportable).

The output: a one-page register — rule, what it does, why, owner, last reviewed.

The ongoing control: a quarterly review of the register, with a named owner, and a rule that no new automatic rule is added without an entry in the register. Without that last part, the register is obsolete in a year.

Exercise 6.25

It is the first week of October, so the queue straddles the ICD-10-CM effective date.

What I do differently: check the date of service on every encounter before opening any reference. September 26 through September 30 encounters are coded from the prior year's ICD-10-CM; October 1 onward from the new one. I would physically separate the two groups and work them in blocks rather than interleaved, to avoid switching mental context every chart.

Why: a code is assigned according to the code set in effect on the date of service, not the date of coding. Working across the boundary is the single most reliable source of seasonal error in this profession, and blocking by date eliminates it.

I would also confirm that the encoder, the practice management system, and the scrubber have all three been updated, since they are separate updates that do not always happen together.

Exercise 6.26 †

The conversation: request it directly and frame it as a question about the standard's basis, not as a complaint about the standard.

The evidence I would bring: my own time data broken down by encounter type — showing which categories take longest and why. Whether the difference is concentrated (a specific service, a specific provider's documentation) or general matters enormously to what the answer should be.

What I would ask for, in order:

  1. What is the standard based on? Which setting, which encounter mix, measured how. A standard imported from a different specialty or a different documentation environment is not a standard, it is a number.
  2. How is quality measured, and with what weight? §6.9's rule: any metric improvable by looking less carefully needs a quality metric of equal weight beside it. If quality is not measured, the productivity standard is effectively an instruction to look less carefully.
  3. Is the mix comparable? If my queue carries the complex charts, volume comparisons are meaningless.
  4. A defined ramp, if I am new. Productivity rises with familiarity, and a standard applied from week one to a new coder measures onboarding rather than performance.

What I would not do: meet the standard by not opening notes. That is the point at which a performance problem becomes a compliance problem, and it becomes my compliance problem.

Exercise 6.28 †

The follow-up question: "And if I pick something reasonable and I'm wrong, how would we find out?"

The answer What it tells you
"We audit a sample monthly and you'd get feedback." A functioning quality process. Good.
"The payer would deny it." Partly true and inadequate — a wrong code that pays is never detected this way, and those are the dangerous ones.
"Someone would probably catch it." No process. The word "probably" is the finding.
"We wouldn't." You have located Chapter 5 §5.3's second prong inside your own workflow in your first week. An organization that cannot detect its own errors is not looking, at volume, at a question that determines whether its claims are true.

The question is worth asking in an interview, not just in the first week — and the answer tells you more about the organization than anything else you will hear.

Exercise 6.30 †

The problem: for nine days, the practice is coding services furnished on or after January 1 using an encoder loaded with the prior year's CPT.

The exposure: deleted codes billed (which will reject, and are the least dangerous); new and more specific codes unavailable, producing less specific coding than the record supports; and — the serious one — codes whose descriptors changed while the numbers stayed the same, which produces no rejection and bills the right number for the wrong service.

What I would do between January 1 and January 10:

  1. Escalate the update date. Nine days is a choice, not a constraint, and it should be made deliberately by someone who understands the exposure.
  2. Get the summary of changes and identify which codes the practice actually bills that were deleted, added, or revised. For most practices this is a short list.
  3. Work from the paper book or the CMS files for the affected codes, not from the encoder.
  4. Hold rather than submit claims involving affected codes if the volume is small enough to make that practical.
  5. Flag every claim coded during the gap so that a targeted review can be run after the update, rather than discovering the problem in a denial pattern two months later.

Exercise 6.31 †

D — October 1.

Exercise 6.33 †

C — quarterly.

Exercise 6.35 †

B — inpatient hospital procedures.

Exercise 6.37 †

Update-cycle checklist (applies to both January 1 and October 1; adjust the code set)

# Item Owner When
1 Order current-year code books office manager 60 days prior
2 Confirm encoder update is scheduled for the effective date billing manager 45 days prior
3 Obtain and read the summary of changes lead coder 30 days prior
4 Identify changes affecting codes this practice actually bills lead coder 30 days prior
5 Review and update the superbill / charge entry list lead coder + billing manager 21 days prior
6 Check whether any guideline relied on was revised — not just codes lead coder 21 days prior
7 Update the fee schedule for new/revised codes billing manager 14 days prior
8 Confirm PMS, encoder, and scrubber are each updated — three separate updates billing manager effective date
9 Brief providers on documentation changes the update requires lead coder first week
10 Date-of-service blocking in the coding queue for two weeks lead coder first two weeks
11 Monitor rejections and denials daily for two weeks; treat the spike as the update audit billing manager first two weeks
12 Post-update targeted review of 20 charts using changed codes lead coder week 3

Exercise 6.40 †

Row The distinct question
6 Does the E/M require a modifier to assert that it was significant and separately identifiable? This is a question about what the claim states, answered from CPT's modifier definitions and the NCCI Policy Manual's guidance on modifier use.
7 Is there an edit prohibiting these two codes together, and does its modifier indicator permit an override at all? This is a question about whether the payer's system will pay them together, answered from the NCCI procedure-to-procedure edit table.
9 Is the injection covered for this patient's documented diagnosis? This is a question about coverage, answered from the payer's medical policy or the Medicare LCD and its article.

Why conflating them produces a confident wrong answer: each has a different source, and each can be answered "yes" while another is "no." A coder who finds a modifier indicator of 1 in the edit table and concludes "so I can bill them together" has answered row 7 and said nothing about row 6 (whether the documentation supports the assertion the modifier makes) or row 9 (whether the service is covered at all).

The three failures this produces: appending a modifier that is permitted by the edit and unsupported by the note (Chapter 5's exposure); omitting a required modifier because the service is covered; and billing a covered, properly modified service that a frequency limit excludes.

Exercise 6.42 †

Why no reference appears in row 2: because a code is a description of what the provider wrote (Chapter 4 §4.7). No book, database, encoder, or manual contains that. The note is the only source, and it is not a source you consult — it is the thing everything else is about.

What it implies for the other twelve rows: every one of them presupposes an answer to row 2. Rows 3 and 4 ask which code describes the condition the note documents. Rows 5 through 8 ask about the procedure the note documents. Row 9 asks whether that service, for that documented diagnosis, is covered. Rows 10 through 13 all describe the same encounter.

So the order is not arbitrary; it is a dependency chain. A workflow that begins anywhere other than the note has inverted it — and the characteristic symptom of an inverted workflow is a coder who has selected a code and is then reading the note to see whether it fits, which is Chapter 4 §4.10's warning about reading front to back rather than assessment-first.


Chapter 7

Exercise 7.1

A classification sorts an unbounded set of clinical realities into a bounded set of categories such that every case has exactly one place, with similar cases near each other.

Two constraints follow: every case must have a place — which is why unspecified and "not elsewhere classified" codes exist — and every case must have only one place, which is why Excludes1 notes exist.

Exercise 7.3 †

Neoplasms C00–D49 · circulatory I00–I99 · musculoskeletal M00–M99 · genitourinary N00–N99 · symptoms and signs R00–R99 · factors influencing health status Z00–Z99.

Exercise 7.5 †

Chapters 1–5 (infectious, neoplasms, blood/immune, endocrine, mental) are organized by etiology or category of disease rather than by body system. Chapters 15–17 (pregnancy, perinatal, congenital) are organized by the patient.

The consequence: where a condition could be classified two ways, these chapters take precedence. A malignant neoplasm of the kidney is coded from chapter 2, not chapter 14. And the Tabular tells you — through Excludes notes at the block and category level in the body-system chapters, which is why the two-step rule is not negotiable.

Exercise 7.7 †

A three-character category is a valid code only when it has no further subdivision. I10 is one.

If it is reported when the category does subdivide, the code is invalid and will reject. It is not a less specific version of the right code; it is not a code at all.

Exercise 7.9 †

The placeholder X fills an empty character position so that a required seventh character sits in the seventh position.

The rule: if a code requires a seventh character and has fewer than six characters, X fills every empty position up to the sixth. A three-character category needs three; a four-character code needs two; a five-character code needs one.

Exercise 7.12 †

The pattern: generally 1 = right, 2 = left, 3 = bilateral where provided, 9 or 0 = unspecified.

The warning that matters more: the assignments are not universal. They vary between categories. Some categories provide a bilateral option and some do not. Some use 0 for unspecified and some use 9. The character position varies — M25.561 carries laterality in the sixth character; other categories carry it elsewhere. Verify in the Tabular, for every category, every time.

Exercise 7.16 †

J44.1J → chapter 10, respiratory (J00–J99). J44 → category, other chronic obstructive pulmonary disease. .1 → fourth character, with (acute) exacerbation. Four characters, complete.

Note this is a combination code: it carries the underlying disease and its acute state in one code.

Exercise 7.18 †

N18.31N → chapter 14, genitourinary (N00–N99). N18 → category, chronic kidney disease. .3 → fourth character, stage 3. .31 → fifth character, stage 3a. Five characters, complete.

Exercise 7.20 †

S52.501DS → chapter 19, injury (S00–T88). S52 → fracture of forearm. .5 → lower end of radius. .50 → unspecified fracture of the lower end of radius. .501 → right. Dseventh character: subsequent encounter for fracture with routine healing.

Seven characters. No placeholder needed — the code already has six before the extension.

Exercise 7.22 †

W19.XXXAW → chapter 20, external causes (V00–Y99). W19 → category, unspecified fall. X, X, X → placeholders in positions 4, 5, and 6, which carry no meaning for this code. A → seventh character, initial encounter.

Exercise 7.24 †

Invalid, if the intended code is M25.561. M25.5 is a four-character subcategory that subdivides further; it is not a reportable code.

(Note the nuance the exercise is testing: the question is not "does M25.5 appear in the book" — it does, as a subcategory heading — but whether it is a valid reportable code. It is not.)

Exercise 7.26 †

Invalid. W19 requires a seventh character and is a three-character category, so it needs three placeholders. The correct form is W19.XXXA. As written, the A sits in the fourth position.

Exercise 7.28 †

Invalid. T39.1XA has six characters; the A is in the sixth position. T39.1 needs a placeholder in the fifth position and a sixth character indicating intent, before the seventh character. The correct form for accidental poisoning, initial encounter, is T39.1X1A.

This is the harder of the two placeholder questions, because the error is not a missing placeholder — it is a missing meaningful sixth character, which a coder who has learned "add X until it's long enough" will fill with an X and get wrong.

Exercise 7.31 †

Report both M25.561 and M25.562. This category provides no bilateral code, so bilateral involvement is reported with both the right and left codes.

The plausible wrong answer: M25.569, unspecified knee. It is wrong because unspecified means "the record does not say which," not "both." It understates the condition, it may fail a coverage policy that lists specific codes, and it describes a patient with one affected knee rather than two.

And verify — other categories do provide bilateral codes, and where one exists, reporting right and left separately is the error instead.

Exercise 7.33 †

A combination code (E11.22) would assert that the chronic kidney disease is diabetic — that is, caused by the diabetes.

Whether you may use it depends on a convention this chapter has not yet taught. ICD-10-CM's "with" convention (Chapter 9 §9.7) creates assumed causal relationships for certain code pairings when they appear in the Alphabetic Index under the word "with," and diabetes-with-CKD is among the pairings where that convention has been interpreted to permit the assumption without an explicitly documented link.

So the honest answer at this point in the book is: check Chapter 9 §9.7 before deciding, and do not assume in either direction. What you would need is either an explicit documented linkage, or the applicable convention plus documentation that both conditions were addressed at this encounter.

(Account 10-4471 is not resolved by this reasoning, and Chapter 36 owns it. The note's assessment addresses the diabetes and does not mention the kidney disease at all, which is a separate question from whether a linkage may be assumed.)

Exercise 7.35 †

Why it is a validity rule: a code exists at a defined character length. Reporting it shorter does not produce a less precise version of the same code; it produces a string that is not in the code set. The claim rejects because the code does not exist.

Why always-unspecified is a different error: an unspecified code at its full length is entirely valid. The error there is not validity but accuracy — assigning a valid code that understates what the record documents. That is downcoding (Chapter 5 §5.8), it forfeits nothing on this claim and a great deal downstream (§7.9), and it is not a defense.

The two errors are on different axes, which is why a coder can commit both in the same week without noticing the contradiction.

Exercise 7.37 †

C — seven.

Exercise 7.39 †

D — W19.XXXA.

Exercise 7.41 †

B — a subsequent encounter during routine healing or recovery. Answer A is the standard wrong answer and it is wrong because the character is defined by the kind of care, not by which visit it is.

Exercise 7.43 †

B — sequenced after the underlying condition.

Exercise 7.45 †

Model answer (118 words):

"Initial encounter" sounds like it means the first visit. It does not. It means the patient is receiving active treatment for the condition — evaluation, surgical treatment, setting a fracture, the emergency visit. "Subsequent" means active treatment is finished and the patient is receiving routine care during healing — cast checks, follow-up films, suture removal.

So a patient can have four encounters that are all "initial," because active treatment kept going. And a patient's very first visit to you can be "subsequent," if someone else did the active treatment and you are handling the follow-up.

Ask "what kind of care is this?" — never "which visit is this?"

Exercise 7.48 †

M25.561: chapter 13 (M00–M99, musculoskeletal) → block M20–M25 (other joint disorders) → category M25 (other joint disorder, NEC) → M25.5 (pain in joint) → M25.56 (pain in knee) → M25.561 (right).

Six characters. No seventh character required. Laterality in the sixth.

Exercise 7.50 †

The three places Figure 4.2 documents laterality:

  1. The assessment: "Right knee pain — new complaint this visit."
  2. The examination: "RIGHT KNEE — no effusion appreciated…" with a full description, and "LEFT KNEE — normal."
  3. The procedure note: "Right knee intra-articular injection… Using a lateral suprapatellar approach…"

Why that matters more than the assessment saying "right": because in most notes it does not. §7.9's thirty-second search exists for the ordinary case where the assessment says "knee pain" and the laterality is documented elsewhere or not at all.

Figure 4.2 is what redundantly documented laterality looks like, and seeing it once establishes the baseline against which real notes are read. It also means this particular claim's laterality is not merely defensible but corroborated three ways — which matters if it is ever audited, because a single mention can be a typo and three consistent mentions cannot.


Chapter 8

Exercise 8.1

Alphabetic Index first, Tabular List second, always.

Step one protects against: not finding the code at all, because the classification files conditions under names you would not guess; and missing synonyms, eponyms, abbreviations, and lay terms that the index maps to the same place.

Step two protects against: reporting an incomplete or invalid code (the index prints a dash rather than the whole code); and missing every instruction that governs the code — seventh characters, Excludes notes, companion-code requirements, and laterality options — all of which are printed above the code where the index never takes you.

Exercise 8.3 †

A main term is a condition — what is wrong, not where.

Four other categories of main term: encounter nouns (Encounter, Examination, Screening, Aftercare, History); eponyms (conditions named for a person); abbreviations; and the general disease name where the specific one is filed elsewhere.

Exercise 8.5 †

Appearance Changes the code? Must be documented?
Nonessential in ( parentheses ) after a main term or subterm No No
Essential an indented subterm Yes Yes

Parentheses are permission to ignore; indentation is a requirement to document.

Exercise 8.7 †

Excludes1 — "not coded here." The two conditions cannot occur together; never report both.

Excludes2 — "not included here." The excluded condition is not part of this code, but a patient may have both, and both may be reported when both are documented.

Memory aid: Excludes1 — only one of them. Excludes2 — you may need two.

Exercise 8.9 †

Appears on Requires Sequence
Code first the manifestation code an underlying condition be coded fixed — underlying first
Use additional code the etiology code an additional code be added fixed — this code first
Code also either two codes not fixed — depends on the encounter

"Code first" and "use additional code" are the same relationship viewed from opposite ends and frequently appear as a matched pair.

Exercise 8.12 †

"And" means "and/or." A category titled "bones and joints" covers bones, joints, or both; it does not require both.

"With" means "associated with" or "due to," and it can create an assumed causal relationship between two conditions when they appear together in the Index or in a Tabular instructional note.

"With" gets its own section in Chapter 9 (§9.7) because it is not merely a vocabulary convention — it is the mechanism by which the classification permits a coder to link two conditions without an explicitly documented causal statement, which is a direct and deliberate exception to Chapter 4 §4.7's rule against inference. That is a large enough idea to need its own treatment, and it is the question Chapters 4 and 7 both deferred.

Exercise 8.15 †

Appendicitis. (Not Abdomen, not Inflammation.)

Exercise 8.17 †

Examination — or Encounter. Both are legitimate entry points for a routine physical; they converge.

Exercise 8.19 †

Diabetes. Not Neuropathy and not Nerve. Diabetic complications are indexed under the diabetes main term with the complication as a subterm — which is also how the classification signals that a combination code is likely.

Exercise 8.21 †

Encounter — for antineoplastic chemotherapy. Not Chemotherapy as a procedure and not the cancer itself; the reason for this encounter is the administration of chemotherapy, and the sequencing rule is Chapter 10 §10.5.

Exercise 8.24 †

I10.

"Benign" appears in parentheses as a nonessential modifier. Nonessential modifiers are alternate wording that does not change the code and need not be present in the documentation — so "hypertension," "benign hypertension," and "essential hypertension" all reach the same code.

The intuition this defeats is that more words in the note produce a more specific code. Here they produce nothing at all.

Exercise 8.26 †

Yes, the category applies.

The convention "and" means "and/or." A category titled "Tuberculosis of bones and joints" covers tuberculosis of bones, of joints, or of both. It does not require both to be present.

This convention catches people because ordinary English "and" is conjunctive. In ICD-10-CM it is not.

Exercise 8.28 †

Check whether the two conditions are genuinely unrelated in this patient.

The Official Guidelines provide a narrow exception to Excludes1: where the two conditions joined by the note are unrelated to each other, both may be reported. Where it is unclear whether they are related, the guidance directs that the provider be queried.

What you may not do: decide for yourself that they are unrelated in order to report both. Relatedness is a clinical determination and Chapter 4 §4.7 forbids a coder from supplying one. That is the same error as deciding two conditions are related in order to use a combination code.

So: query if unclear; report both only if the record establishes they are unrelated; otherwise the Excludes1 note governs and you have the wrong code.

Exercise 8.30 †

People misread "code also" as optional — as though it meant "you may also wish to consider."

It is not optional. It requires two codes. What it declines to do is dictate their order, because sequencing depends on the circumstances of the encounter — specifically, on which condition was the reason for the encounter (Chapter 9 §9.9).

So "code also" is the instruction that requires the most judgment: it tells you both codes are needed and hands you the sequencing decision.

Exercise 8.31 †

Wrong turn: looking up Knee (Knee — see condition), or taking the main term code R52 for Pain, which is generalized pain.

The path: Main term Pain(s) → subterm joint → subterm kneeM25.56-. The dash sends you to the Tabular. There: laterality in the sixth character, M25.562 for the left knee. No seventh character required. No Excludes note applies.

Exercise 8.33 †

Wrong turn: looking up Mammogram or Mammography. Those are procedures; this is the diagnosis index. There is no disease here — the encounter itself is the reason.

The path: Main term Screeningmalignant neoplasmbreastZ12.31. Verify in the Tabular. Chapter 21 territory; Chapter 12 §12.9 covers why a person with no complaint has a diagnosis code.

Exercise 8.35 †

The path: Main term Diabetes, diabetic → the index's structure branches by type and complication → type 2, without complication → E11.9. Verify in the Tabular.

What the Tabular adds that the index did not: the E11 category carries instructional notes, including a use additional code instruction to identify certain associated conditions and long-term drug therapy where applicable. Read them. This is exactly the situation in Chapter 8's Case Study 2 — the code is right and there may be a second code the index never mentioned.

The wrong turn: assuming "without complications" from the absence of a documented complication. It is the correct code when the record documents no complication addressed at this encounter — which is a reading of the record, not an inference from silence, and Chapter 9 §9.7 complicates it.

Exercise 8.37 †

Wrong turn 1: the Table of Drugs and Chemicals, poisoning column. The drug was taken as prescribed, so this is an adverse effect, not a poisoning.

Wrong turn 2: reporting only the drug code. An adverse effect is coded with the manifestation first.

The path: code the rash from the main Alphabetic Index (main term Rash, or the more specific dermatitis term the record supports). Then the Table of Drugs and Chemicals → the substance → the adverse effect column → the T-code, with its seventh character, which the table does not display. Sequence: manifestation first, drug code second. Chapter 12 §12.6.

Exercise 8.39 †

B.

Exercise 8.41 †

B — the documentation is specific but the classification has no code for the condition. Answer A describes NOS.

Exercise 8.43 †

B — conditions.

Exercise 8.45 †

C — adverse effect.

Exercise 8.47 †

Model answer (117 words):

Most of them don't take four minutes — most are under two. The four-minute ones are the ones where I open the book and find something.

Last October a category we use constantly picked up a laterality character. The old five-character code became invalid. We caught it in about forty claims because they rejected — but the same update added a "use additional code" note to a different category, and that one doesn't reject. The claim pays and we're just underreporting.

I don't look codes up because I might misremember them. I look them up because the book changes and nothing tells us when. It's the only control we have on the changes that don't announce themselves.

Exercise 8.50 †

Wrong turn 1: KneeKnee — see condition. The index does not index body parts.

Wrong turn 2: Pain → take R52 and stop. R52 is pain, unspecified — generalized pain — and the code is valid, payable, and wrong.

The path: Pain(s) → joint (M25.50) → knee (M25.56-) → Tabular → M25.561 / M25.562 / M25.569 → documentation supports right → M25.561.

What step two produced that step one did not:

Finding Result
Seventh character required? No
Any Excludes note applying to this patient? No
Laterality options and which character carries them Sixth character; 1 right, 2 left, 9 unspecified
Complete code M25.561

Three of the four are negative. The one that is not — the laterality character — was not available from the index at all, which had printed a dash in its place. Without step two there is no complete code.

Exercise 8.52 †

Diagnosis A — M25.561:

Main term Pain(s); subterm joint; subterm knee; index gave M25.56- with a dash. Verified in Tabular category M25: no seventh character required, no Excludes note applicable to this patient, laterality carried in the sixth character. Documentation supports right knee in the assessment, the examination, and the procedure note. Assigned M25.561.

Diagnosis C — I10:

Main term Hypertension; nonessential modifiers (accelerated) (benign) (essential) (malignant) (primary) (systemic) — none required, none present, none affecting the code. Index gave I10 complete at three characters. Verified in Tabular: I10 is a valid three-character code with no further subdivision. Category notes reviewed; none applicable. Assigned I10.

What is different about the second one: the index gave a complete code with no dash, because the category does not subdivide — one of the relatively few three-character codes (Chapter 7 §7.3). And the modifiers were nonessential, so the documented word "essential" changed nothing.

Step two still mattered, for a different reason: I10 sits in a category with substantial instructional content about hypertensive conditions, and confirming that none of it applied is part of the path. A negative finding is a finding, and it is the part of the record that says you looked.


Chapter 9

Exercise 9.1

The Official Guidelines are the rules for assigning and sequencing ICD-10-CM codes. They are approved jointly by the Cooperating Parties — NCHS, CMS, the American Hospital Association, and AHIMA. Their status: required. They accompany and complement the conventions and instructions in the code set, and ICD-10-CM is a national standard under the HIPAA Transactions and Code Sets rule, which brought the conventions and guidelines with it. A code assigned against them is incorrect.

Exercise 9.3 †

The first-listed diagnosis is the condition, problem, or other reason chiefly responsible for the services provided at this encounter.

What determines it: the encounter — why the patient was seen and what was done.

What explicitly does not: severity, chronicity, or how serious the patient's other conditions are. A patient with heart failure, diabetes, and hypertension seen for a wart removal has the wart first.

Exercise 9.5 †

Outpatient (Section IV): do not code diagnoses documented as probable, suspected, questionable, rule out, compatible with, consistent with, or working diagnosis. Code the documented signs, symptoms, abnormal test results, or other reason for the visit.

Inpatient (Section II): code a diagnosis documented at the time of discharge as probable, suspected, likely, questionable, possible, or still to be ruled out as if it existed or was established.

Why they differ: the outpatient rule protects the patient and the record — an office visit is a snapshot, coding a guess as established puts a disease on a permanent record with consequences for future care and insurability, and documented symptoms are usually available to code instead. The inpatient rule captures the workup — an admission consumed substantial resources pursuing a diagnosis, and coding only symptoms would describe a multi-day investigation as though nothing had been determined.

The shared logic: each rule codes what its setting actually establishes.

Exercise 9.7 †

The convention: where "with" or "in" appears in a code title, the Alphabetic Index, or a Tabular instructional note linking two conditions, the classification presumes a causal relationship, and the conditions are coded as related even in the absence of explicit provider documentation linking them.

Two boundaries: (1) the presumption applies only where the classification creates the link — not wherever the word "with" appears in a clinical note; (2) it does not extend to pairings the classification has not made, and extending it is the inference Chapter 4 §4.7 forbids.

What defeats it: documentation clearly stating the conditions are unrelated.

(A third limit: where chapter-specific guidance requires an explicitly documented linkage, that requirement governs and the presumption does not override it.)

Exercise 9.9

Code first instructions; etiology/manifestation pairs; the acute-before-chronic rule; chapter-specific sequencing rules in Section I.C (sepsis, obstetrics, HIV, neoplasms with chemotherapy, poisoning, and others); Section IV's first-listed rule; and Sections II/III's principal diagnosis rule.

Exercise 9.10 †

  1. Specific beats general — a chapter-specific guideline governs over a general one; an instruction at the code governs over one at the category.
  2. The Guidelines beat the code book's conventions.
  3. The Tabular beats the Index.
  4. Explicit provider documentation beats a presumption.
  5. Then: Coding Clinic, then your MAC, then a documented decision with the reasoning recorded.

Deliberately absent: what pays more. It is not a tiebreaker and it is not a consideration.

Exercise 9.11 †

(a) Office — outpatient, Section IV. "Rule out GERD" is not coded. Code the chest pain.

(b) Inpatient discharge summary — Section II. "Probable pneumonia" documented at discharge is coded as if established. Code the pneumonia.

(c) Emergency department, discharged home — OUTPATIENT, Section IV. This is the trap. "Possible appendicitis" is not coded. Code the abdominal pain and nausea.

(d) Office — outpatient. Two things are happening. "Likely musculoskeletal" is uncertain and is not coded; code the chest pain. The GERD is confirmed by prior endoscopy and documented as ongoing — if it was addressed at this encounter it is reportable as an additional diagnosis. The uncertainty attaches to the chest pain's cause, not to the GERD.

Exercise 9.13 †

Code both, acute first.

The three conditions hold: the same condition (systolic heart failure) is documented as both acute and chronic; separate index subentries exist; and they are at the same indentation level. Sequence the acute code first.

(Verify in the current index — heart failure is a category where combination and specificity options have changed, and if a single code fully describes "acute on chronic," that code governs instead under the combination-code rule, Chapter 7 §7.8.)

Exercise 9.15 †

No, you may not code them as related.

The difference from 9.14: in 9.14, the Alphabetic Index links diabetes and the condition under "with," so the classification has made the causal judgment and the presumption applies. Here, the classification has not linked type 2 diabetes and osteoarthritis of the knee — there is no index entry joining them under "with."

With no classification-created linkage, Chapter 4 §4.7 governs: a causal relationship requires provider documentation. Inferring one because it is clinically plausible is exactly the extension §9.7's boundaries forbid and Case Study 1 describes as the most-abused reading of the convention.

The discriminating question is not clinical. It is: did the classification link these two, or did I?

Exercise 9.17 †

The chronic-disease follow-up is the first-listed diagnosis, on the facts as given — the encounter was scheduled for it, and it is chiefly responsible for the services provided.

What would change the answer: if the new symptom drove the bulk of the encounter's work — its own history, examination, diagnostic decision-making, and a procedure — then it may be the condition chiefly responsible for the services, and it would be sequenced first.

And the honest addition: where two conditions are genuinely equally responsible and no rule fixes the order, §9.9 says either may be sequenced first. What is not free is that on a professional claim, each service line must point to the diagnoses supporting that line (Chapter 25 §25.5) — so the sequencing question and the pointing question are different, and the second one is not discretionary.

Exercise 9.19 †

Setting: office — outpatient, Section IV.

Code: the cough, the fever, and the shortness of breath — the documented signs and symptoms.

Do not code: pneumonia. It is documented as "rule out," and Section IV prohibits coding probable, suspected, or rule-out diagnoses in the outpatient setting.

The rule for each: the symptoms are coded because no definitive diagnosis was established (§9.6, and Section IV expressly permits symptom codes in that circumstance). The pneumonia is not coded because of the outpatient uncertain-diagnosis rule (§9.5).

Note what is not an argument for coding it: that antibiotics were started. Treatment initiated on suspicion does not convert a suspicion into an established diagnosis, and the record still says "rule out."

Exercise 9.21 †

Likely cause: the diagnosis supporting the service is not in the first-listed position, and the payer's edit evaluated the first-listed diagnosis against its coverage policy. Everything needed is on the claim, in the wrong order.

The fix: resequence so the diagnosis chiefly responsible for the service is first-listed, and — more precisely — ensure the diagnosis pointers link each service line to the diagnoses supporting it.

The chapter that covers the mechanism: Chapter 25 §25.5, diagnosis pointers and the four-per-line rule. That is the mechanism that would have prevented it, and it is a claim-construction question rather than a code-selection one.

Exercise 9.23 †

What is wrong with it, precisely: the "with" presumption is not a statement about clinical plausibility. It is an instruction attached to specific pairings the classification has already decided about, appearing in a code title, the Alphabetic Index, or a Tabular instructional note. Whether a relationship is clinically plausible is irrelevant to whether the convention applies.

Extending the presumption to pairings the classification has not made is the coder supplying a clinical judgment, which Chapter 4 §4.7 forbids and which no convention authorizes.

The exposure: in a risk-adjustment context, submitting diagnoses the medical record does not support is an active federal audit and enforcement area — OIG audit work, CMS Risk Adjustment Data Validation audits, and Department of Justice matters. The standard applied is whether the record supports the diagnosis, and "a clinician would find it plausible" is not that standard.

The safe formulation to give them: "Did the classification link these two, or did I?"

Exercise 9.25 †

Model case to a practice manager:

The ICD-10-CM Official Guidelines are the rules our coders are legally required to follow, they are free, they are about a hundred pages, and I do not believe anyone here has read them front to back. That is not a criticism of the staff — nobody is given time for it and most coders learn the conventions from the book and the rules from colleagues.

What I would expect one afternoon to change: we would stop coding rule-out diagnoses in the office setting, which I believe we do occasionally. We would sequence more deliberately, which affects medical-necessity denials directly. And we would apply the "with" convention correctly, which matters more every year as our risk-bearing volume grows.

What it costs: four hours of coder time, once, plus an hour each October when the new version comes out. I would like to make the October hour a standing item.

Exercise 9.27 †

B.

Exercise 9.29 †

B — not coded separately.

Exercise 9.31 †

C — code both, acute first.

Exercise 9.33 †

B — outpatient. The emergency department is an outpatient setting for coding purposes when the patient is discharged, regardless of acuity or length of stay.

Exercise 9.34 †

Model answer (114 words):

They look contradictory and they are answering different questions.

In the office, a hedged diagnosis is a guess, and coding it as established puts a disease on someone's permanent record — with real consequences for their future care. You almost always have documented symptoms to code instead, so you code those. Nothing is lost.

In the hospital, a five-day admission spent chasing a diagnosis consumed enormous resources. If the workup ends at "probable" and you code only the symptoms, the record says nothing was determined, and hospital data would systematically understate what hospitals do.

Each setting codes what it actually establishes. The clinic establishes symptoms; the admission establishes a conclusion, however hedged.

Exercise 9.37 †

M25.561 is correct under §9.6 because no definitive diagnosis was established. The note says so explicitly:

"Right knee pain — new complaint this visit. Examination findings are consistent with a degenerative process; no definitive diagnosis established today and no prior imaging of this knee is available."

Where no definitive diagnosis is established, the symptom is coded. This is endorsed by Section IV, it is not a fallback, and it is not a documentation failure.

What would have to be documented for a different code to be correct: a definitive diagnosis stated by the provider — for example, osteoarthritis of the right knee, supported by imaging or by clinical criteria the provider names and applies. Chapter 22 is where that eventually happens, and the resulting code sits in a different block (M15–M19) one block away from where the pain code lives (Chapter 7 §7.2).

Note what would not be enough: the note's own phrase "consistent with a degenerative process." "Consistent with" is on Section IV's list of uncertain-diagnosis terms, and a coder who treats it as a diagnosis has made the exact error §9.5 prohibits.

Exercise 9.39 †

Two distinct questions:

Question 1 — the linkage question. May diabetes and chronic kidney disease be coded as related without an explicit provider statement linking them? Under the "with" convention (§9.7), yes — the Alphabetic Index links them, so the classification presumes the relationship and the presumption is available.

Question 2 — the addressed question. Was the chronic kidney disease addressed, affecting treatment, or requiring management at this encounter? Section IV governs additional diagnoses in the outpatient setting, and the answer is no. The assessment addresses type 2 diabetes, essential hypertension, and hyperlipidemia. The kidney disease appears on the problem list and nowhere in the assessment or plan.

Question 2 is doing the work. A coder who reports E11.22 + N18.31 has answered question 1 correctly and never asked question 2. The linkage convention tells you how to code two conditions if you are coding both; it does not tell you whether to code the second one at this encounter.

E11.9 is therefore correct for March 14.

Exercise 9.40

A code can be correct — accurately describing what this encounter addressed, assigned under the applicable guideline, defensible on audit — and incomplete as a description of the patient, because the patient has a condition that this encounter did not address.

Under fee-for-service, that distinction costs nothing: the claim describes the encounter, the encounter is what was paid for, and the unaddressed condition is irrelevant to the payment.

Under risk-adjusted payment — Medicare Advantage and similar arrangements — it becomes expensive, because the payment model asks a different question: not what did this encounter address but what does this patient's documented burden of illness look like over the year. A condition that exists, is documented, and is never reported on any encounter is invisible to that model.

Chapter 36 owns this, including the MEAT criteria and what the practice should have done.


Chapter 10

Exercise 10.1

(1) Read the chapter-specific guidelines in Section I.C. (2) Read the chapter's opening notes in the Tabular. (3) Skim the block headings. (4) Find the combination codes. (5) Find the sequencing rules. (6) Code the chart, index to Tabular.

Step 1 is skipped most often and is the highest-yield because Section I.C exists precisely where the Cooperating Parties found recurring disputes — reading it first means you meet the answer before you meet the question.

Exercise 10.3 †

The Tabular must instruct it — a "use additional code to identify the infectious agent" note at the category — and the organism must be documented.

Both. Where the organism is not documented, code the infection without it; that is an unspecified code, it is correct, and it is a candidate for a query where the record contains a culture result the provider has not tied to the diagnosis.

Exercise 10.5 †

Sepsis — a systemic infection. Minimum one code: the underlying systemic infection.

Severe sepsis — sepsis with associated acute organ dysfunction. Minimum three codes: the underlying infection, R65.20, and at least one acute organ dysfunction code.

Septic shock — circulatory failure associated with severe sepsis. Minimum three codes: the underlying infection, R65.21, and the organ dysfunction codes.

Exercise 10.7 †

Six columns: malignant primary · malignant secondary · carcinoma in situ · benign · uncertain behavior · unspecified behavior.

Uncertain behavior is a pathological conclusion: the specimen was examined and the pathologist could not classify it as benign or malignant. It is a documented finding.

Unspecified behavior means the documentation does not state the behavior. It is the NOS column.

The distinction: one is the pathologist's uncertainty and one is the record's silence. A coder who uses the uncertain column because they are uncertain has reported a pathological finding nobody made.

Exercise 10.9 †

The malignancy was excised or eradicated; there is no further treatment directed to that site; and there is no evidence of any remaining malignancy at that site.

All three. Conjunctive. A patient on adjuvant therapy fails the second condition and is coded as active.

Exercise 10.11 †

  1. Only the conditions the classification links. A condition the Alphabetic Index does not list under "with" is not presumed related, however plausible.
  2. Documentation stating they are unrelated defeats it.
  3. Where chapter-specific guidance requires an explicitly documented linkage, that governs and the presumption does not override it.

Exercise 10.14 †

  1. G89 is not assigned when the definitive underlying diagnosis is known, unless the encounter is for pain management.
  2. Where the encounter is for pain control or management, the G89 code is sequenced first, with the underlying condition coded additionally.
  3. Where the encounter is for treatment of the underlying condition, code the condition; do not assign G89.
  4. Site-specific and G89 codes may be used together, with sequencing determined by the reason for the encounter.

There is no duration rule for chronic pain. The provider's documentation governs.

Exercise 10.15 †

(a) The MRSA sepsis code per the index and Tabular. One code. No severe sepsis code — no organ dysfunction documented.

(b) A41.9 (sepsis, unspecified organism) first, then R65.20 (severe sepsis without septic shock), then the acute respiratory failure code. Three codes — organ dysfunction is documented and documented as secondary to the sepsis.

(c) The sepsis code. Then stop and query. The encephalopathy is documented; it is not documented as associated with the sepsis. Do not assign R65.20 on the strength of two conditions appearing in the same note.

(d) The underlying infection codes for the pneumonia-related sepsis per the index, then R65.21 (severe sepsis with septic shock), then the acute kidney injury code and the acute respiratory failure code. Four or more codes. Both dysfunctions are documented as secondary to the sepsis.

Exercise 10.17 †

What is sequenced first depends on why the patient is there, and the encounter is described as being for management of hypercalcemia — a complication.

What you would need to check: Section I.C.2's guidance on complications of a malignancy. The guidance addresses specific complications and specifies sequencing for several; it is not a single rule. Read it rather than assuming that "the complication is the reason, so the complication is first."

You would also code the primary breast malignancy and the secondary bone site, because metastatic disease requires both.

Exercise 10.19 †

Code type 2 diabetes without complications — E11.9 — by the type-2 default (§10.6), since no type and no complication are documented.

Two things in that sentence that are not codeable as written:

  1. "Poorly controlled." The classification does not have a "control" axis. It asks about hyperglycemia and hypoglycemia specifically. "Poorly controlled" is a query candidate if the specific state matters — and note that a query is only appropriate where the answer would change the code.
  2. The absent type. It is not an error — the default resolves it — but it is worth noting that the record supported more and did not say it.

Exercise 10.21 †

No, the sole-purpose rule is not satisfied. The encounter included treatment of nausea, so it was not solely for chemotherapy administration.

What follows: Section I.C.2's guidance on complications governs the sequencing rather than the sole-purpose chemotherapy rule. Read it. The general shape is that when the encounter is for management of a complication and not solely for the therapy, the complication may be sequenced first — but the guidance is specific by complication and should be applied rather than generalized.

The teaching point: "solely" is a real word in the guideline and it does work. One additional treated problem defeats the rule.

Exercise 10.23 †

Item 1 — Z85 personal history of malignant neoplasm of the breast, right. All three conditions of §10.5 are met: excised (lumpectomy), no further treatment (radiation completed 2019), no evidence of recurrence. Plus the encounter code for the surveillance imaging.

Item 2 — the new left breast lesion is coded as documented and no further. "Suspicious, biopsy pending" is an uncertain diagnosis in an outpatient setting (Chapter 9 §9.5) — you do not code a malignancy. Code the documented finding: the lesion or mass, from the appropriate category.

Why they are coded differently: the right breast has an established history with all three history conditions satisfied. The left breast has an unresolved finding with no established diagnosis. One patient, two breasts, two entirely different coding situations — and a coder who codes "breast cancer" for this patient has merged them.

Exercise 10.25 †

Code the sepsis. Then query about the acute kidney injury.

The rule: severe sepsis requires acute organ dysfunction documented as associated with the sepsis. Here the AKI appears in the hospital course as a separate statement — "resolved with fluids" — with no documented relationship to the sepsis. It may well have been sepsis-related; it may have been volume depletion from another cause.

What you do not do: assign R65.20 because both conditions are in the same record. That is inference (Chapter 4 §4.7) wearing a clinical costume.

Note also: the AKI is itself reportable as a diagnosis if it meets the criteria for an additional diagnosis in the setting. The query is about the severe sepsis determination, not about whether to code the AKI at all.

Exercise 10.27 †

  1. The Tabular instructs it. Where a "use additional code" instruction exists, reporting the additional code is not optional — Chapter 8 §8.6.
  2. "It doesn't pay" is a statement about one payment model. Under risk adjustment and in facility settings, status and status-adjacent codes can matter substantially (Chapter 36).
  3. It corrupts the record and the data. A patient on long-term therapy whose record never says so is described inaccurately to every downstream user, including the next clinician.
  4. It is exactly the omission an audit finds, because it is mechanical and detectable — and a pattern of omitting instructed codes is evidence about the coding process rather than about one claim.

Exercise 10.29 †

# Item Produces
1 Read Section I.C for this body system the arguments the classification has already had
2 Read the chapter's opening Tabular notes what governs everything below
3 Skim the block headings a map of how the chapter is carved up
4 List the combination codes where the specificity and the money are
5 List the sequencing rules and "code first" instructions most of the errors, pre-empted
6 Identify what documentation this chapter demands that clinicians often omit your query list before you have a chart

Item 6 is not in §10.1's method and is worth adding: knowing in advance what this body system's documentation gaps look like is what turns a slow first chart into a fast fifth one.

Exercise 10.31 †

A — the underlying infection code only.

Exercise 10.33 †

B — the encounter code for antineoplastic chemotherapy.

Exercise 10.35 †

B — type 2.

Exercise 10.37 †

B — the encounter is for pain management rather than for the underlying condition.

Exercise 10.38 †

Model compliant query:

Clarification is requested regarding the assessment for this encounter.

The record documents: · Sepsis, organism unspecified · Acute kidney injury, with creatinine rising from [value] to [value] on hospital day [n] · [Any other documented clinical indicators, quoted from the record]

Based on your clinical judgment, is the acute kidney injury associated with the sepsis? ( ) Yes — acute kidney injury associated with sepsis ( ) No — acute kidney injury due to another cause; please specify ( ) Clinically undetermined ( ) Other: __

Please document your response in the medical record. This query is not intended to suggest any particular response.

Note what it does not do: it does not mention severe sepsis, does not name R65.20, and does not state that the answer affects the DRG. All three would make it leading (Chapter 4 §4.9).

Exercise 10.41 †

E11.9 asserts: type 2 diabetes mellitus, without complications.

It therefore assumes: that no diabetic complication was addressed at this encounter.

Which is true. The assessment addresses the diabetes itself — continues metformin, orders an A1c to reassess control — and addresses no complication. The chronic kidney disease is on the problem list and is not addressed anywhere in the assessment or plan.

Why nothing requires a query: a query is appropriate where documentation is conflicting, ambiguous, incomplete, or clinically inconsistent in a way that affects code assignment (Chapter 4 §4.9). Here the record is clear and complete for what it describes. There is no ambiguity about the diabetes, no missing specificity that the record supports, and no conflict. The record says what it says and the code says the same thing.

(Whether the encounter should have addressed the CKD is a different question, it is not a coding question, and Chapter 36 §36.7 takes it up.)

Exercise 10.43 †

Chart 1 documents type 2 diabetes and stage 3a chronic kidney disease, and both are addressed at the encounter — the medications are being continued for them. So both questions are answered yes: the classification links them under "with" (linkage), and both were addressed (Section IV). The combination code applies, plus the CKD stage code.

Account 10-4471 documents the same two conditions, and the assessment does not address the kidney disease — it appears on the problem list only. So the linkage question is answered yes and the addressed question is answered no. E11.9, and the CKD is not reported for this encounter.

The difference is not clinical and not in the "with" convention. It is in what the assessment says was managed — which is Chapter 9 §9.7's two-question structure, producing different answers because the notes are different.


Chapter 11

Exercise 11.1

Kidney: the relationship is PRESUMED. Hypertension and a condition classifiable to chronic kidney disease are coded with a combination code, and no stated linkage is required. Plus an additional code for the CKD stage.

Heart: the relationship must be STATED or IMPLIED — documented as "due to hypertension" or as "hypertensive." Without it, the two conditions are coded separately.

Exercise 11.3 †

The time rule: an acute myocardial infarction is coded as acute for four weeks (28 days) from onset.

Three states: acute MI (within the 4-week period) · subsequent MI (a new infarction occurring within the 4-week window of a previous one) · old MI (after the acute period, healed, no further care).

The subsequent category applies only to a new infarction during the acute window of the first, and when it is used, both the subsequent and the initial codes are reported, with sequencing depending on the circumstances of the encounter.

Exercise 11.5 †

The acute event — coded from the acute infarction categories.

Sequelae — deficits remaining after the acute phase, coded from the sequelae category with a code identifying each deficit and, where applicable, the dominant or non-dominant side.

Personal history — a patient who had the event and has no residual deficits.

What distinguishes them: whether the acute phase is ongoing, and whether deficits remain.

Exercise 11.7 †

The rule: acute respiratory failure may be sequenced as principal when it is chiefly responsible for the admission; it is a secondary diagnosis when it develops after admission; and where it and another acute condition are both present on admission, the guidance addresses the selection and chapter-specific priority rules elsewhere may govern.

It turns on: why the patient was admitted — Chapter 9 §9.4's "after study" definition applied to a common situation.

It does not turn on: severity. Respiratory failure is frequently the most serious thing present and that is not the test.

Exercise 11.9 †

The rule: pressure ulcers are coded by site and stage, and the stage may be taken from documentation by a clinician other than the provider — a wound care nurse's staging, for example — provided the provider has documented the pressure ulcer itself.

The general form (Chapter 4 §4.3): another clinician may supply a detail; only the provider may supply the diagnosis.

Exercise 11.11 †

No, this is not a transplant complication.

A transplant does not fully restore function, and a patient may have a functioning transplant and chronic kidney disease. The guidance addresses this directly: the CKD is coded, with the transplant status code, and this is not a complication of the transplant.

A transplant complication requires provider documentation that something is wrong with the transplanted organ — and coding one where the patient simply has residual CKD is an error with real consequences in a facility setting.

Exercise 11.13 †

The trimester is determined by the provider's documented weeks of gestation at the time of the encounter.

What does not determine it: the coder's calculation from a due date, the last menstrual period, or the admission date. Additionally, a code identifying the weeks of gestation is reported on most obstetric encounters, and for an admission spanning a trimester boundary the guidance addresses which applies.

Exercise 11.16 †

(a) Hypertension + CKD → the hypertensive chronic kidney disease combination code, plus the code for CKD stage 3. The relationship is presumed; no stated linkage needed. Two codes.

(b) Hypertension + a heart condition, no relationship stated → two separate codes. Code the hypertension, and code the chronic diastolic heart failure with its type and acuity. The combination code does not apply.

(c) "Hypertensive heart disease with chronic systolic heart failure" → the relationship is stated ("hypertensive"), so the hypertensive heart disease combination category applies, plus a code identifying the type of heart failure — because the combination code carries the relationship and not the specificity.

(d) Hypertension + CKD + heart failure documented as hypertensive → the classification provides a combination category for hypertensive heart and chronic kidney disease, plus the heart failure type code, plus the CKD stage code. Read the Tabular instructions at that category; it carries specific direction on the additional codes required.

Exercise 11.18 †

Sequelae of cerebral infarction, with:

  • a code identifying the expressive aphasia following cerebral infarction, and
  • a code identifying the hemiparesis/hemiplegia following cerebral infarction, specifying the affected side and whether it is dominant or non-dominant.

The patient is right-handed and the deficit is left-sided — so the affected side is the non-dominant side. That is documented right there in the note and it is the specificity most commonly missed.

Not an acute infarction code. The event was three years ago.

Exercise 11.20 †

As written: admitted in acute respiratory failure secondary to a COPD exacerbation, so the respiratory failure was present on admission and is a candidate for principal diagnosis. The determination depends on what, after study, was chiefly responsible for occasioning the admission, and Section I.C.10's guidance on respiratory failure with another acute condition addresses the selection. Read it rather than applying a general instinct.

If the respiratory failure had developed on hospital day 3: it would be a secondary diagnosis, and the COPD exacerbation would be principal. The respiratory failure did not occasion the admission — it occurred during it.

Exercise 11.22 †

Elements required:

  1. The obstetric code for gestational diabetes in pregnancy, from chapter 15 — priority over the endocrine chapter.
  2. The trimester character reflecting 32 weeks.
  3. A code identifying the weeks of gestation.
  4. The seventh character identifying the fetus — here, the value for fetus 2, since the condition is documented as affecting fetus 2 in a twin gestation.
  5. A code identifying the multiple gestation itself.

What the seventh character does: it identifies which fetus a condition applies to in a multiple gestation. It is not the episode of care — that is chapter 19's meaning — and it is assigned even in a single gestation, using the value for a single gestation or where the character does not apply.

Exercise 11.24 †

All three conditions are addressed, so all three are reportable (Chapter 9 §9.3).

Conventions applied:

  1. Hypertension + CKD → relationship presumed (§11.1) → the hypertensive chronic kidney disease combination code.
  2. Diabetes + CKD → relationship presumed by the "with" convention (Chapter 10 §10.6) → the diabetes-with-CKD combination code.
  3. CKD stage → an additional code for stage 3b, because the combination codes carry the relationship and not the stage.
  4. Section IV's addressed question (Chapter 9 §9.3) → all three were addressed, so all are reportable.

Read the Tabular at both combination categories for the required additional codes and any sequencing instruction; both categories carry them.

Exercise 11.26 †

You cannot determine it from what is given, and that is the point of the exercise.

Both sepsis and acute respiratory failure are present on admission. What you need is what, after study, was chiefly responsible for occasioning the admission (Chapter 9 §9.4).

Where the rule is: Section I.C.1's sepsis sequencing guidance and Section I.C.10's respiratory failure guidance both bear on it, and the sepsis guidance carries priority instructions of its own. Read both, and where the record does not establish which condition occasioned the admission, that is a query.

What you may not do: pick the more severe one. Severity is not the test.

Exercise 11.28 †

The investigation: pull twenty charts coded to the unspecified heart failure option and determine, for each, whether the record supported more — checking the encounter note, the echocardiogram reports, and prior documentation.

Three possible findings and what each implies:

Finding Implication Fix
The encounter note specified and the coder did not use it a coder problem audit feedback; the thirty-second search
The type is in the chart but not this note a policy problem — may a coder use it? decide the policy; the practice must have an answer
The provider never documented the type anywhere a documentation problem clinician education, and it is the slow, expensive, real fix

The proportions determine the priority, and responding to a documentation problem with coder training addresses the smallest share — which is the most common misdiagnosis in this area.

Exercise 11.30 †

Model compliant query:

Clarification is requested regarding the assessment for this encounter.

The record documents: · Essential hypertension, treated with [medication] · Chronic diastolic heart failure · [Any other documented clinical indicators, quoted from the record]

The relationship between these conditions is not specified in the documentation. Based on your clinical judgment, is the heart failure related to the hypertension? ( ) Yes — hypertensive heart disease with heart failure ( ) No — heart failure due to another cause; please specify ( ) Clinically undetermined ( ) Other: __

Please document your response in the medical record. This query is not intended to suggest any particular response.

Note what it does not do: it does not name a code, does not state the payment consequence, and does not signal a preferred answer. It also asks a real question — the classification genuinely requires a stated or implied relationship here, and the physician genuinely has the answer.

Exercise 11.31 †

B — a combination code, because the relationship is presumed.

Exercise 11.33 †

C — four weeks (28 days).

Exercise 11.35 †

B — a secondary diagnosis.

Exercise 11.37 †

B — chronic kidney disease with a transplant status code, and not a complication.

Exercise 11.39 †

Model answer (104 words):

Hypertension plus kidney disease and hypertension plus heart disease follow different rules, and that is the thing to memorize.

Kidney: the classification assumes the relationship. You use the combination code whether or not anyone wrote a link. Add the stage code.

Heart: somebody has to say so. "Hypertensive," or "due to hypertension." Without it, two separate codes.

Why it is not arbitrary: hypertension and kidney disease travel together closely enough that the classification will assume it. Heart conditions have a lot of other causes, so it will not.

When you see hypertension plus an organ, ask which organ before anything else.

Exercise 11.42 †

Both organ questions, answered:

Heart? No heart condition is documented anywhere in the note. The cardiac examination is documented and normal — regular rate and rhythm, no murmur, no peripheral edema. There is nothing to combine with. And even if there were, §11.1 requires a stated or implied relationship for the heart, which the note does not supply.

Kidney? Chronic kidney disease, stage 3a, is on the problem list, and the hypertension–CKD relationship would be presumed — no stated linkage needed.

Which prior question decides it: Section IV's addressed question (Chapter 9 §9.3). Report additional diagnoses addressed, affecting treatment, or requiring management at this encounter. The assessment addresses hypertension, diabetes, and hyperlipidemia. It does not address the kidney disease.

The presumption in §11.1 tells you how to code hypertension and CKD if you are coding both. It does not tell you whether the CKD belongs on this claim.

Assign I10.

Exercise 11.44 †

The respect in which it is stronger: the diabetes–CKD presumption operates through the general "with" convention (Chapter 9 §9.7), which is a classification-wide mechanism with three stated boundaries. The hypertension–CKD presumption is stated directly in the chapter-specific guidance as a cause-and-effect relationship the classification presumes — and by §9.10's hierarchy, specific beats general. It is the more explicitly and more narrowly stated of the two.

Why the stronger presumption still does not change the answer: because both presumptions answer the linkage question, and Account 10-4471 is decided by the addressed question, which comes first and which neither presumption touches.

That is the point of putting the two side by side. A stronger convention, more explicitly stated, in a different chapter, reaching the same conclusion — because the question that decides this file is not the one either convention answers.


Chapter 12

Exercise 12.1

Chapter 19 asks what happened to the body, plus where in the arc of care. Chapter 20 asks how it happened. Chapter 18 asks what the patient is experiencing when no disease is established. Chapter 21 asks why a person who may not be ill is here.

Three consequences: they frequently require more codes than a body-system chapter would; they carry sequencing rules that override the ordinary ones; and two of them contain codes that may never stand alone.

Exercise 12.3 †

A — the patient is receiving active treatment. D — active treatment is complete and the patient is receiving routine care during healing or recovery. S — the acute phase is over and a residual effect remains.

The character describes the KIND OF CARE. It does not describe the ordinal position of the encounter.

Exercise 12.5 †

Code the residual condition first, then the injury code with the seventh character S.

Why the S code cannot stand alone: it says "this is a leftover from that." It identifies the origin of the residual, not the residual itself. Something has to state what the leftover is — a contracture, a hemiplegia, a chronic pain — and that is the first code's job.

Exercise 12.7 †

Not documented open or closed → CLOSED. Not documented displaced or non-displaced → DISPLACED.

The displaced default runs against intuition, because coders expect defaults to be conservative and "displaced" is the more severe of the two. It is a guideline and it is examined precisely because it surprises people.

Exercise 12.9 †

Depth (first, second, third degree — code the highest degree at each site) · site (with laterality where provided) · extent (percentage of total body surface area, and the percentage that is third degree, reported with a separate code).

Sequencing: the highest-degree burn first, then the other burn sites, then the extent code.

Exercise 12.11 †

Sequence
Poisoning poisoning code first, then the manifestation
Adverse effect manifestation first, then the drug code
Underdosing underdosing code, plus any relapse or exacerbation, plus the reason
Toxic effect toxic effect code first, then the manifestation

Poisoning and adverse effect are inverted relative to each other.

The reason: in a poisoning, the ingestion is the clinical event and the manifestation follows from it. In an adverse effect, the patient presents with a problem and the drug is the explanation for it.

Exercise 12.13 †

Position: never first-listed. Always secondary to the injury or condition they explain.

Frequency: the cause and intent codes are reported as long as the injury is being treated, with seventh characters. Place of occurrence, activity, and status are reported ONCE, at the initial encounter only.

Requirement: ICD-10-CM itself imposes no national requirement for mandatory external cause reporting. Requirements come from state mandates, payer requirements, or the provider's own policy — and for workers' compensation, the work-related status code is frequently not optional.

Exercise 12.15 †

Screening · status · personal history · family history · aftercare · follow-up · observation · counseling and other encounters. (Any six.)

First-listed: when the encounter's reason is not a disease — screening, well visit, aftercare, follow-up, observation. Secondary: when they describe a circumstance affecting care — status codes, history codes.

Exercises 12.18–12.24 †

# Character Reasoning
12.18 A Fracture reduced and casted — this is active treatment
12.19 D Cast check, healing normally — active treatment is complete
12.20 D First visit to this provider, and still D — the character describes the care, not the visit number. This is the item that breaks the intuition.
12.21 A Return to the OR for revision — active treatment resumed
12.22 S Chronic pain attributed to the old injury — a residual effect. Code the pain first, then the fracture code with S.
12.23 K Subsequent encounter, nonunion
12.24 P Subsequent encounter, malunion

Exercise 12.25 †

Adverse effect — the drug was taken as directed.

Codes: the rash first, from the main Alphabetic Index. Then the drug code from the adverse effect column of the Table of Drugs and Chemicals, with its seventh character.

Sequence: manifestation first.

Exercise 12.27 †

Underdosing.

Every code required: 1. The underdosing code for insulin, from the underdosing column, with its seventh character 2. The diabetes with hyperglycemia code — the documented exacerbation resulting from the underdosing 3. A code identifying the reason — underdosing due to financial hardship

The one people omit: the reason code. It is required, and it carries the clinically and administratively important information. A patient underdosing because they cannot afford the drug is a different problem from one who forgot, and the classification distinguishes them.

Exercise 12.29 †

Underdosing — the patient took less than prescribed (in fact, none), which is underdosing rather than poisoning or adverse effect.

Codes: the underdosing code for the antihypertensive; the hypertensive emergency as the documented exacerbation; and a reason code — here, intentional underdosing for a reason other than financial hardship, per the categories the classification provides.

The trap: calling this "noncompliance" and reaching for a behavioral code. The classification has underdosing codes with reason codes, and they are more specific and more useful.

Exercise 12.31 †

The screening Z-code for malignant neoplasm of the colon, first-listed. The patient is asymptomatic and the encounter's reason is the screening itself.

Exercise 12.33 †

The kidney transplant status Z-code, reported as a secondary code. The reason for the encounter is the respiratory infection, which is first-listed; the transplant status is a circumstance affecting the patient's care.

Note also (Chapter 11 §11.8) that a functioning transplant with residual CKD is coded as CKD plus the status code, and is not a transplant complication.

Exercise 12.35 †

Codes and reasons:

  1. The follow-up examination Z-code — surveillance after treatment has concluded, first-listed. Not aftercare: treatment is complete, not ongoing.
  2. The personal history of malignant neoplasm of the colon Z-code — Chapter 10 §10.5's three conditions are met (excised, no further treatment, no evidence remaining).
  3. The screening code does not apply — this is surveillance in a patient with a history, not screening of an asymptomatic person with no history. Verify the current guidance, which addresses this distinction.

Exercise 12.37 †

B — the patient is receiving active treatment.

Exercise 12.39 †

B — the residual condition, then the injury code with S.

Exercise 12.41 †

B — manifestation first, then the drug code.

Exercise 12.43 †

B — once, at the initial encounter.

Exercise 12.45 †

B — the acute fracture code with the appropriate seventh character.

Exercise 12.46 †

Model answer (117 words):

A, D, and S are about what kind of care this encounter was — not about which visit it is.

A means active treatment. D means active treatment is done and this is routine healing care. S means the acute phase is over and something is left behind.

Here is the example that breaks everyone's intuition: a patient's first visit to you, three weeks after someone else set their fracture, for a cast check. It is their first visit to you. It is D, because active treatment is complete and you are doing routine healing care.

And a patient seen four times during active treatment has four encounters coded A.

Ask "what kind of care?" — never "which visit?"

Exercise 12.49 †

Absent Reason
A seventh character M25.561 is in chapter 13 (musculoskeletal). Seventh characters for episode of care live in chapter 19 (injury). This is not an injury.
An external cause code Follows directly — external cause codes explain how an injury occurred, and there is no injury.
A Z-code The encounter's reason is a set of diseases and a symptom. Nothing here is a screening, status, history, aftercare, or non-disease encounter. (Possible exception: a long-term drug therapy status code if the Tabular instructs one — Chapter 10 §10.6 left this open.)
A chapter 18 symptom code M25.561 is the symptom code; it is filed in the musculoskeletal chapter rather than in chapter 18. Chapter 7 §7.2.

Exercise 12.51 †

Minimal change: replace "No known injury" with "Onset following a twisting injury while descending stairs six weeks ago."

What changes:

  • The chapter. The condition is now a traumatic injury and moves from chapter 13 to chapter 19, to a code for a sprain or internal derangement of the knee — which one depends on what the examination and any imaging support, and the note's ligamentous testing is normal and McMurray equivocal, so a specific structural diagnosis is not established.
  • A seventh character is now required. The patient is receiving active treatment — an injection was performed today — so A.
  • An external cause code becomes available: the mechanism (a fall or a twisting injury on stairs), the place of occurrence, the activity, and the status — reported once, at this initial encounter, and subject to whether state or payer requirements make them mandatory.

What does not change: the other three diagnoses, and the procedure coding.

The teaching point: one clause, replaced, moves the encounter between two chapters of the classification, adds a required character, and opens a whole category of secondary codes.


Chapter 13

Exercise 13.1

The American Medical Association maintains CPT. The CPT Editorial Panel decides what codes exist, advised by the CPT Advisory Committee. The RUC — the Relative Value Scale Update Committee — recommends relative value units to CMS. Different bodies, different jobs: the Panel decides what the codes are; the RUC recommends what they are worth.

Exercise 13.3 †

  1. A current professional edition costs money every year, which is a real barrier for a student. A prior year's edition is a legitimate way to learn the structure and must never be used to bill.
  2. Software containing CPT is licensed — encoders, practice management systems, and clearinghouses all pay for it, and it is part of what you are buying.
  3. Textbooks and internal materials may not reproduce the code set. Individual codes and paraphrased descriptors for teaching are one thing; reproducing descriptor runs, sections, or building internal cheat sheets from them is governed by the license.

Exercise 13.5 †

The rule: if a Category III code exists that describes the service, it must be used instead of an unlisted Category I code.

The reason: Category III codes are how the code set collects utilization data on a new service. If everyone reported unlisted codes instead, no data would accumulate, and the service could never build the evidence needed to become a Category I code. Using the Category III code is the mechanism by which a new procedure eventually earns a permanent one.

Exercise 13.7 †

Four kinds of content: definitions of terms used throughout the section; what the codes include (the surgical package being the most consequential example); reporting rules on what may and may not be reported separately; and modifier guidance. Also: unlisted code and special report requirements, and the "separate procedure" designation.

Exercise 13.9 †

Symbol Warns about
new code — it did not exist last year
revised code — the descriptor changed while the number did not
▶ ◀ new or revised text in guidelines or parentheticals — a rule changed
+ add-on code — never alone, exempt from modifier 51
modifier-51 exempt
# resequenced — printed out of numeric order
telemedicine service

The most dangerous is ▲. A revised code produces no rejection: the number survives, the meaning changes, the claim pays, and you have billed a service that was not furnished.

Exercise 13.11 †

Three add-on rules: never reported alone; exempt from modifier 51; permitted primary procedures specified in a parenthetical beneath the code.

The one-way relationship: all add-on codes are modifier-51 exempt, but not all modifier-51-exempt codes are add-on codes. They are two different appendix lists, and a code can appear on the exempt list without being an add-on code.

Exercise 13.13 †

Three rules: use only when nothing else fits — including any applicable Category III code; a special report must accompany it; and it carries no assigned relative value, so the payer must price it individually.

The special report must contain, per CPT's guidelines: a description of the nature, extent, and need for the procedure, together with the time, effort, and equipment necessary. Some sections also address complexity of symptoms, final diagnosis, concurrent problems, and follow-up care.

Exercise 13.18 †

(Answers will vary by edition — the point is what you record.) You should have captured: the complete descriptor including everything before the semicolon; at least two parentheticals — one directing to 20611 when ultrasound guidance is performed, and one prohibiting reporting 20610 and 20611 together for the same joint; and any symbol in the margin.

If you recorded only the descriptor, you did the thing this chapter warns against.

Exercise 13.20 †

(Answers vary.) You should have recorded the + symbol, the descriptor, and — critically — the parenthetical naming the primary procedures the add-on code may accompany. That parenthetical is the thing that makes the code usable, and it is directly beneath the code where it is easy to skip.

Exercise 13.22 †

(Answers vary.) The complete descriptor of the third indented code is everything before the semicolon in the parent code, plus the indented text. If what you wrote begins with a semicolon or reads as a fragment, you have reproduced the error §13.10 describes.

Exercise 13.24 †

Report the Category III code.

What would be wrong with the alternative: an unlisted Category I code is less specific, the guidance is explicit that the Category III code governs where one exists, and — the systemic reason — reporting the unlisted code contributes nothing to the utilization data that would let the service eventually earn a permanent Category I code.

Exercise 13.26 †

No, this is not correct.

An add-on code's permitted primary procedures are specified in a parenthetical directly beneath it. An add-on code paired with a primary that is not on that list has been reported outside its intended use.

What you would check: the parenthetical beneath the add-on code, to see which primaries it may accompany; and then the operative report, to determine whether the procedure actually performed corresponds to one of them. The likeliest explanations are that the primary was coded incorrectly, or that the add-on code is the wrong one for this primary.

Exercise 13.28 †

The error: a code was reported describing ultrasound guidance that the procedure note says was not performed. The claim asserts a service that was not furnished.

The cause: the semicolon convention. The coder read the indented portion — "; with ultrasound guidance" — which fit the code family they were looking at, and did not read the common portion above it or, more importantly, did not check the guidance question against the note before choosing between the two codes.

This is §13.10's stated most-common cause of a descriptor that did not match the service.

Exercise 13.30 †

Report the unlisted procedure code for the appropriate section — generally the code ending in 99.

Alongside it you must produce a special report containing a description of the nature, extent, and need for the procedure, together with the time, effort, and equipment involved.

And understand what happens next: the code carries no assigned relative value, so the payer will price it individually — usually by comparison to a similar coded service — using your special report to do so. A thin special report produces a low payment or a denial, which is why the report is the work rather than an afterthought.

Exercise 13.32 †

The order of operations:

  1. The section and subsection guidelines — front of the section. Ninety seconds.
  2. The parentheticals at and around the code.
  3. CPT Assistant, if your organization subscribes — the recognized source of official interpretation.
  4. The NCCI Policy Manual, if the question is about whether two codes may be reported together — it is free and it explains the reasoning.
  5. The payer's published policy, if the question is coverage rather than coding.
  6. Then colleagues and forums — useful for orientation, never authority, and follow every answer to its source.

Why it is faster as well as more reliable: the guidelines are four pages away and searching is twenty minutes. The habit pays for itself on frequency alone, before any argument about accuracy.

Exercise 13.34 †

  1. Accuracy. Reporting the closest coded service means reporting a code whose descriptor does not describe what was done. That is inaccurate on its face.
  2. Compliance. A claim asserts that the service described by the code's current descriptor was furnished (Chapter 5 §5.1, and Chapter 13 Case Study 2's "the descriptor is the claim"). Reporting a code because it pays better than the accurate one is a false claim, not an aggressive interpretation.
  3. The coverage problem is not solved by coding. If the unlisted code is slow and underpaid, the remedies are prior authorization, a patient financial conversation, a better special report, and appeal — all of which address the actual problem. Substituting a code is the route from a hard case to a false claim, and it is the single most common one.

Exercise 13.35 †

C — Category III.

Exercise 13.37 †

C — an add-on code.

Exercise 13.39 †

B — never reported alone, and exempt from modifier 51.

Exercise 13.41 †

C — Evaluation and Management.

Exercise 13.43 †

B — everything before the semicolon in the code above it.

Exercise 13.44 †

Model answer (116 words):

The guidelines are at the front of each section, they govern every code beneath them, and the index will never take you to them — which is exactly why nobody reads them.

Here is a question they answer. A surgeon performs a procedure and sees the patient twice afterward. Are those visits billable?

The Surgery guidelines define the surgical package: what the procedure's payment already includes. The answer is in there, in a few paragraphs, governing thousands of codes.

Most people who use CPT daily have never read that page. It takes twenty minutes.

When you have a CPT question, go to the front of the section before you search anything. You will find the answer often enough that the habit pays for itself.

Exercise 13.47 †

Code Section Subsection Heading
99214 Evaluation and Management Office or Other Outpatient Services Established patient
20610 Surgery Musculoskeletal System General → Introduction or Removal
36415 Surgery Cardiovascular System Arteries and Veins

The most surprising is 36415 — a venipuncture in the Surgery section.

Why it is there: the Surgery section is where the code set files procedures performed on the body's structures, organized by body system. A venipuncture is a procedure on a vein, so it sits under the cardiovascular system. "Surgery" in CPT is not the lay meaning of the word, and reasoning from the lay meaning is how coders end up searching the wrong section.

(A close second: 20610, a joint injection, also in Surgery, for the same reason.)

Exercise 13.49 †

The two documented negatives:

  1. "No known injury" (Chapter 12) — decides that the knee pain is not an injury, which keeps the code in ICD-10-CM chapter 13 rather than chapter 19, requires no seventh character, and forecloses external cause coding.
  2. "No imaging guidance used" (this chapter) — decides between 20610 and 20611, two CPT codes distinguished by exactly that variable.

Why a negative finding is unusual: clinical documentation is overwhelmingly a record of what was found and what was done. Writing down what was not found, or what was not used, takes deliberate effort and produces no clinical benefit to the writer — the physician knows they did not use ultrasound.

Which is why both clauses are worth noticing. Each is a physician recording an absence, and each one settles a coding question that would otherwise require an inference a coder is not permitted to make (Chapter 4 §4.7).

Exercise 13.50 †

What a coder may conclude: nothing about whether guidance was used.

What a coder may not do: assume that silence means it was not used. That is inference (Chapter 4 §4.7), and it happens to point toward the code the practice would probably prefer, which makes it worse rather than better.

What I would do: first, read the rest of the encounter's documentation — an order, a procedure log, an imaging entry — because §7.9's thirty-second search applies to procedure coding as well. If nothing settles it, query: a short, non-leading question asking the provider to document whether imaging guidance was used and, if so, whether it was permanently recorded.

Note the second half of that question. The descriptor for the guidance code requires permanent recording and reporting, so "we used ultrasound" alone does not settle it either. The query has to ask for both elements, which is the kind of detail that comes from reading the full descriptor rather than the indented portion.


Chapter 14 — Answer Key

Quiz (24 questions)

  1. C — A modifier reports that a service was altered by a specific circumstance without changing the code's definition. It does not change what the code means (A), does not substitute for a code (B), and is not optional documentation (D).
  2. B — Payment modifiers are sequenced before informational modifiers, subject to payer policy.
  3. D — Modifier 99 signals that more modifiers apply than the claim form's four positions can hold.
  4. A — Modifier 25 is appended to the E/M code, not the procedure code. This is the single most common mechanical error with modifier 25.
  5. CFalse. A different diagnosis is not required. The requirement is that the E/M be significant and separately identifiable — above and beyond the usual pre- and post-procedure work.
  6. B — Modifier 25 applies to minor procedures (000- and 010-day global periods). Modifier 57 applies to the decision for major surgery (090-day).
  7. D — Prescription drug management for an unrelated condition supports separability. Positioning the patient (A), obtaining consent (B), and post-procedure instructions (C) are all included in the procedure's payment.
  8. A — Modifier 59 identifies a distinct procedural service and is used to override a bundling edit. It is a last resort.
  9. C — XS: a separate structure. XE is a separate encounter, XP a separate practitioner, XU an unusual non-overlapping service.
  10. B — Modifier 59 is scrutinized because it is the only modifier whose sole function is to defeat a control, it is applied by the party that benefits, and its use is measurable from claims data without any chart.
  11. D — Modifier 51 asks for less money (it triggers the multiple-procedure reduction); modifier 59 asks for more (it overrides a bundling edit). This is the fastest way to keep them straight.
  12. A — Never append modifier 51 to add-on codes or to modifier-51-exempt codes. Add-on codes are already valued as additional procedures.
  13. C — Modifier 26 reports the professional component: the interpretation and the written report. No written report, no professional component.
  14. B — Ownership of the equipment determines who bills the technical component, not the physical location where the service was performed.
  15. D — All three: billed twice, billed by nobody, and billed by the wrong party are the three failure modes of component billing.
  16. A — The bilateral reporting convention varies by payer: one line/one unit, one line/two units, or two lines with RT and LT. Reporting one way for all payers produces silent underpayment.
  17. C — Modifier 24 reports an unrelated E/M during a postoperative period.
  18. B — Modifier 58 is for a planned or staged related procedure. Modifier 78 is for an unplanned return to the operating room.
  19. D — Modifier 78 generally pays only the intraoperative portion and does not restart the global period; modifier 58 generally pays in full and does start a new global period.
  20. A — Modifier 79 reports an unrelated procedure performed during another procedure's postoperative period.
  21. C — Modifier 22 requires documentation and a special report and triggers manual review. It is not an automatic payment increase.
  22. B — Modifier 53 reports a procedure discontinued after induction because continuing threatened the patient's well-being. Modifier 52 reports services reduced at the physician's discretion. (73/74 are the ASC and outpatient hospital equivalents.)
  23. D — Modifier 91 is for a repeat lab test performed to obtain subsequent results. It is not for repeats due to equipment failure or specimen problems.
  24. AGZ. An expected denial with no ABN obtained. The patient may not be billed. GA (ABN obtained) means the patient may be billed.

Exercises (54 items) — selected answers and grading notes

Items 1–10 (modifier identification). Straight recall from §14.4–§14.11. Accept the modifier and require, for full credit, a one-sentence statement of what the modifier asserts. A student who can produce the number but not the assertion has memorized a list, which §14.1 explicitly warns against.

Items 11–18 (modifier 25 application). For each scenario, the student must (a) decide whether 25 applies and (b) quote the specific documentation element that supports the decision. Scenarios 12, 15, and 17 do not support modifier 25 — 12 restates the procedure's indication, 15 documents positioning and consent only, 17 examines the procedure site alone. A student who applies 25 to all eight has learned the wrong lesson and should redo the item set.

Items 19–24 (25 vs. 57). Decided entirely by the global period of the procedure: 000/010 → 25; 090 → 57. Students should be looking up the global period, not guessing. The Medicare Physician Fee Schedule relative value file carries it in a column.

Items 25–32 (59 and X{EPSU}). For each, the student must name the more specific modifier if one exists before defaulting to 59. Items 26 (separate encounter → XE), 28 (separate structure → XS or an anatomic modifier), and 31 (separate practitioner → XP) each have a better answer than 59. Item 30 has no more specific alternative and 59 or XU is correct.

Items 33–38 (51 vs. 59). Answered by asking which direction the money moves. Item 35 is a trap: an add-on code, where neither applies — 51 is prohibited on add-on codes and there is no edit to override.

Items 39–44 (component and laterality). Items 41 and 42 turn on ownership rather than location; item 43 requires the student to name all three bilateral conventions and state that the payer's policy decides.

Items 45–50 (global period set). A decision-tree exercise. The dividing question for 58 vs. 78 is planned or not, and students should say so explicitly.

Items 51–54 (liability modifiers). Item 53 is the important one: no ABN, expected denial → GZ, and the patient may not be billed. Students frequently answer GA because it feels safer; it is not, and reporting GA without an ABN is a false statement.


The Encounter checkpoint — Account 10-4471

Question 1 (open since Chapter 4): Was modifier 25 correctly applied to line 1?

Yes.

The supporting documentation in Figure 4.2, all of it independent of the knee:

  • Three chronic conditions individually assessed with plans stated (type 2 diabetes, essential hypertension, hyperlipidemia)
  • Prescription drug management
  • Two tests ordered with stated reasons
  • A new problem (the knee) evaluated on its own merits, which is itself work above the injection's inherent pre-service evaluation

And 20610 carries a 000-day global period, which makes it a minor procedure — so modifier 25 is the correct modifier and 57 is not.

Two qualifications students should be able to state:

  1. The payer denies the line on day 17 anyway (CO-97/N19). That is a payer policy outcome, not a coding error, and the distinction matters — a coder who "fixes" a correct claim to avoid a denial has made the claim wrong.
  2. The note never states that the decision to inject was made during this visit. It is strongly implied by the sequence, but it is not written. This is why the Chapter 30 appeal must construct the argument from the note's content rather than quote a single sentence — and it is a documentation improvement opportunity, not a coding error.

Grading note: full credit requires both the answer and at least two of the four supporting elements, correctly identified as independent of the knee. A student who answers "yes, because there were other diagnoses" has reproduced the myth §14.4 exists to correct and should not receive full credit.


Chapter 15 — Answer Key

Quiz (26 questions)

  1. C — the cognitive work of the reporting professional, by MDM or by total time.
  2. C — not used for level selection, but a medically appropriate history and/or examination is still required.
  3. B — 99201, deleted effective January 1, 2021.
  4. BNew. Three years to the day; three years and one day is outside the window.
  5. CEstablished. Any professional service within three years counts, in any setting.
  6. B — two of the three elements must meet or exceed the level.
  7. CLow (99213). No level is met by two elements at moderate or above. Working down: problems (high) exceeds low and risk (low) meets low → two elements at low or above → low MDM.
  8. B — at the treatment goal.
  9. Bnot stable, because it is not at treatment goal. This pushes toward the chronic-illness-with-exacerbation-or-progression language, which is moderate.
  10. C — moderate.
  11. C — not addressed. Notation of a problem managed by another without additional assessment or care coordination.
  12. A — one unique test. A panel is one test regardless of analytes.
  13. B — one item. Review of the result is included in the order.
  14. B — a different group practice, or a different specialty or subspecialty.
  15. C — may not be counted. Bill it or count it; not both.
  16. C — a documented interactive discussion with an external professional, not separately reported.
  17. C — count, if documented. The risk element explicitly includes options considered but not selected.
  18. C — moderate.
  19. B — the assessment-and-plan entry. A medication list is an inventory; management is a decision.
  20. C — the reporting professional's own non-face-to-face time on that calendar date.
  21. B28 minutes. Time performing a separately reported service is excluded. (An established patient at 28 minutes is a 99213 by time — which is why the question is asked.)
  22. B99214. The two methods are alternatives; documenting time does not obligate you to use it, and time never caps an MDM-based level.
  23. C — 99205 and 99215 only. The highest level's time must be fully met first.
  24. B — Medicare uses G2212, with a different starting threshold.
  25. C — the physician must provide direct supervision (present in the office suite and immediately available), not be physically present in the examination room.
  26. B — may not be billed incident-to. The new rash is a new problem, which disqualifies the encounter; it must be billed under the NPP's own NPI at 85%.

Exercises

Section A — New versus established

A.1 New. A.2 Established — within three years. A.3 Established. Any professional service counts, including hospital services. A.4 New — four years exceeds the window. A.5 New to the dermatologist. Different specialty, even in the same group. A.6 Established. Same specialty, same group. A.7 New. Different group practice, different tax identification number. A.8 New. An interpretation without a face-to-face encounter generally does not establish the patient. (Grading note: accept a well-reasoned "verify with the payer" as partial credit — this is the item where the CPT rule and individual payer determinations most often diverge, and §15.2's 📞 On the Phone callout is about that call.)

Section B — Problems addressed

B.9 Low. B.10 Moderate — the threshold is two. B.11 Moderate — three exceeds two but does not reach high. B.12 Moderate. Not stable (not at goal), and the medication was increased: a chronic illness with progression or exacerbation. B.13 Straightforward. B.14 Low. B.15 Moderate — one undiagnosed new problem with uncertain prognosis. Students who answer "low, it's only one problem" have misread the grid; this is the most underused entry in the element. B.16 Moderate — acute illness with systemic symptoms. B.17 Arguable, at best low. A blanket statement with no individual status and no individual plan is very thin evidence of problems addressed. (This is Reading 2 in §15.10. Full credit requires naming what is missing: individual status and individual plan.) B.18 Not addressed. Contributes nothing.

Section C — Data

C.19 1 item → minimal. C.20 2 items → limited (low). C.21 3 items → moderate. C.22 1 item → minimal. A panel is one test. C.23 1 item → minimal. The prior panel is the same CPT code — not unique — and review is included in the order regardless. C.24 1 order + 2 unique external notes from 2 unique sources = 3 items → moderate. C.25 1 item → minimal. The partner's note is not external — same group, same specialty. C.26 Limited (low) via Category 2 alone. C.27 Nothing. Separately reported with modifier 26; it may not also be counted. C.28 Category 1: 1 order + 1 external note = 2 items. Category 3: documented discussion with an external professional, not separately reported. Two categories satisfied → extensive (high).

Section D — Risk

D.29 Minimal. D.30 Low. D.31 Moderate — prescription drug management. D.32 Not prescription drug management. A list is not a decision; this contributes nothing to the risk element on its own. D.33 Low — minor surgery with no identified risk factors. D.34 Moderate — minor surgery with identified patient risk factors, documented. D.35 High — decision regarding hospitalization, considered and not selected, documented. D.36 Moderate — diagnosis or treatment significantly limited by social determinants of health, documented and shaping the plan.

Section E — Time

E.37 33 minutes (25 + 8, both on the date, both the physician's). Established → 99214. E.38 15 minutes. Staff time never counts. E.39 28 minutes99213. E.40 28 minutes99213. E.41 99214 (30–39). Under pre-2021 rules, time could be used only if more than half the encounter was counseling or coordination of care — here 20 of 35 minutes is more than half, so it would also have qualified; the difference is that today no such test applies at all. E.42 New patient, 47 minutes → 99204 (45–59). E.43 99213. 29 minutes is inside 20–29. No rounding. E.44 99214. MDM supports it; the two methods are alternatives and time does not cap an MDM level.

Section F — Prolonged, split/shared, incident-to

F.45 58 minutes established: 99215 requires 40–54. 58 exceeds 54 but a complete additional 15-minute increment beyond the 99215 threshold has not accrued. Report 99215 alone. (Grading note: the point of this item is that "over the range" is not the test — the test is a complete additional increment. Accept full credit only if the student says so.) F.46 Medicare uses G2212 instead of 99417, and its threshold starts later still — so the answer is unchanged here, but the code would differ if it applied. F.47 No. 38 minutes does not even reach 99215's 40-minute threshold; prolonged services attach only to the highest level. F.48 Yes, provided the remaining conditions are met — established patient, established plans of care, direct supervision, no new problems. F.49 No. The rash is a new problem. Bill under the NPP's own NPI at 85% rather than 100%. F.50 An overpayment, accruing on every encounter where an established patient raises something new. Direction: the practice is paid more than it was entitled to. Chapter 5 §5.8's sixty-day rule attaches once it is identified. It has no financial signal — the claims pay.

Section G — Integration

G.51 (This is Account 10-4471.) Problems moderate (3 stable chronic illnesses; also 1 undiagnosed new problem with uncertain prognosis). Data limited/low (2 unique tests ordered). Risk moderate (prescription drug management). Two of three at moderate → 99214. Single change that would move it: one more Category 1 item would make data moderate too — which would not change the code, since the level is already moderate. The change that would move it DOWN is removing the individual assessments (Reading 2). To move it up would require a high element in two places — e.g., a documented decision regarding hospitalization plus a high problems element.

G.52 Problems low, data minimal, risk moderate. Two of three at low → 99213 by MDM. But 34 minutes documented, established → 99214 by time. Report 99214. Single change: remove the documented time and it is a 99213.

G.53 New patient. Problems moderate (undiagnosed new problem with uncertain prognosis). Data moderate (3 unique tests). Risk moderate (prescription drug management). Three of three at moderate → 99204. Single change: any two elements at high would make it 99205.

G.54 Problems moderate (chronic illness with exacerbation — worsening symptoms, dose increased). Data moderate (2 orders + 1 external note = 3 Category 1 items). Risk HIGH (decision regarding hospitalization, considered and declined, documented). Two of three at moderate → 99214. Single change: if the problems element reached high — e.g., documented as a severe exacerbation, or as posing a threat to life or bodily function — two elements would be high and the visit would be a 99215. This item exists to show that a single high element gets you nothing, which students find genuinely surprising.

G.55 Problems straightforward, data minimal, risk low. Two of three at straightforward → 99212.

G.56 Problems at best low (blanket statement, no individual status or plan). Data limited/low. Risk moderate at most, if the refills are documented as decisions. Two of three at low → 99213. Single change: individual status and plan per condition → problems moderate → 99214. One sentence per problem.

Section H — Integration with the rest of the book

H.57 In Reading 4 the entire visit is the evaluation leading to the injection. Chapter 14 §14.4's test is whether the E/M is significant and separately identifiable — above and beyond the usual pre- and post-procedure work. With no work independent of the knee, there is nothing above and beyond. Note that the different-diagnosis question never arises; the diagnosis is irrelevant in both directions.

H.58 Expected shape: "I can't do that. A total time in the record is a factual statement offered to a payer in support of payment, and stating a time nobody measured is exactly what §5.3 calls reckless disregard. If the visits really do run 40 minutes, document the actual time on each one and we'll use it — that's the road the rules give us, and it's a better position than an estimate." Grade for: identifying the statement as factual, naming the standard, and offering the legitimate alternative. A response that simply refuses gets partial credit.

H.59 It appears because the physician is documenting a fact about the encounter that determines which selection method the coder may use. It removes the time road and forces MDM — and in doing so it removes ambiguity. A note that is silent about time is not the same as a note that says time was not used, and the second is more useful to the coder and to a reviewer. (Accept students who note that this is unusual and that most notes are silent; the point is what the sentence accomplishes.)

H.60 Expected shape: a message that describes the structure of the assessment rather than asking for content — "when each condition has its own line with a status and a plan, the note reflects the work you already did; a blanket 'chronic conditions stable' doesn't." Grade hard for the line Chapter 5 §5.6 draws: the message must not ask the physician to add anything that did not happen. A message that says "please add more detail so we can bill 99214" fails.


The Encounter checkpoint — §15.13

Account 10-4471, March 14, established patient, is a 99214.

Element Level Basis
Problems Moderate 3 stable chronic illnesses addressed (2+ is the threshold); independently, 1 undiagnosed new problem with uncertain prognosis
Data Limited (low) 2 unique tests ordered — A1c, lipid panel. The panel is one test
Risk Moderate Prescription drug management — 3 medications continued with documented decisions

Two of three at moderate → moderate MDM → 99214.

Time is unavailable — the note states "Time was not used for level selection on this encounter."

The CKD problem-list entry is not addressed and contributes nothing. (Do not let students code or discuss a diabetes–CKD relationship here. Chapter 36 owns it.)

Grading note: full credit requires the level, all three element scores, and an explicit statement that the low data element does not reduce the level. Students who write "data is only low so it's a 99213" have made the error the two-of-three rule exists to prevent, and it is worth correcting individually.


Chapter 16 — Answer Key

Quiz (26 questions)

  1. C — the same MDM framework introduced for office visits in 2021, extended in 2023.
  2. B — two claims, professional and facility, with two patient balances.
  3. B — the first face-to-face service of the stay by that professional or their same-specialty group partner.
  4. Binitial care. "Initial" is the consultant's first service, not the admission.
  5. C — an initial hospital care service only; the office work rolls into it.
  6. B — an outpatient service.
  7. B — the physician's documented expectation at the time of the decision.
  8. C — generally does not apply. Observation days do not count toward the three-day inpatient requirement.
  9. B — only before discharge, following utilization review with physician concurrence.
  10. A — once per stay, by the attending, for the date of the actual discharge.
  11. B — documentation of the time.
  12. B — permissible when each service is reasonable and necessary and the record shows what each professional managed.
  13. B — a denial of one of the two claims, which is defensible. A reviewer reading two identical assessments cannot tell what the second professional contributed.
  14. B — a specialty enrollment problem. Same-specialty determination is made by how the professionals are enrolled, not by what they practice.
  15. B — request, render, report.
  16. B — Medicare has not recognized them since 2010; report the setting-appropriate E/M instead.
  17. B — still a consultation if the three Rs are met. Initiating treatment is explicitly permitted.
  18. C — neither a new/established distinction nor a time option.
  19. B — the medical decision making documented, including what was ruled out.
  20. B — a critically ill or injured patient and high-complexity decision making, regardless of location.
  21. C — the appropriate E/M service for the setting. Under 30 minutes is not critical care and there is no partial 99291.
  22. B — pulse oximetry.
  23. B — may be reported with modifier 25 on the E/M when the documentation shows the sequence.
  24. C — the facility's own written criteria, based on resources consumed.
  25. B — packaging. Not a denial, and working it as one wastes substantial time.
  26. B — they were not addressed by the emergency physician. Chapter 15 §15.5's definition.

Exercises

Section A — Initial versus subsequent

A.1 Initial hospital inpatient or observation care (99221–99223). First service of the stay by that professional. A.2 Subsequent (99231–99233). A.3 Subsequent. Same group, same specialty — the group has already provided the initial service. (This is the weekend-handoff error in §16.2's ⚠️ Where Claims Die.) A.4 Initial. Different specialty; it is the cardiologist's first service. A.5 Subsequent. Same group, same specialty as the cardiologist who saw the patient Wednesday. A.6 Initial. Different specialty again. A.7 Initial hospital care only. The office visit rolls into it and may raise its level. A.8 The emergency physician reports an ED visit; the hospitalist reports initial hospital inpatient or observation care. Different professionals, different services, both reportable. The roll-in rule applies to the same professional.

Section B — Observation and status

B.9 Observation is a hospital service that is outpatient in status, regardless of bed location or duration. B.10 Care expected to span at least two midnights generally supports inpatient admission. Applied prospectively — to the expectation at the decision point. B.11 Yes, appropriate. The benchmark is expectation-based; an unexpected improvement does not retroactively invalidate a documented expectation. B.12 The expectation and its basis are not documented. At risk: the inpatient status itself, and therefore the difference between inpatient and outpatient payment — plus the ability to defend the determination at all. B.13 Skilled nursing facility coverage generally does not apply, because the qualifying stay must be three consecutive inpatient days and observation days do not count. B.14 Under outpatient status, self-administered drugs are frequently not covered, so the hospital's administration of her home medications is billed to her at hospital pricing. B.15 Condition Code 44. Requires the determination before discharge, physician concurrence, and documentation. B.16 Condition Code 44 is unavailable after discharge; a different self-audit process applies, and the window for the first mechanism has closed.

Section C — Discharge day management

C.17 99238. Everything described is consistent with more than 30 minutes and none of it states it. A reviewer does not estimate. C.18 99239. One sentence. C.19 Thursday — the date of the actual discharge. C.20 No. Only the attending performing the discharge reports it, once per stay. The consultant reports a subsequent care service. C.21–C.24 (see Section D)

Section D — Concurrent care

D.21 Permissible. Requirement: each service reasonable and necessary, with the record showing what each professional was managing. D.22 One of the two claims will likely deny, and the denial is defensible — the reviewer cannot tell what the cardiologist contributed. D.23 Enrollment. Whether two professionals are "the same specialty" is determined by how they are enrolled with the payer, not by what they practice. Chapter 25. D.24 The diagnosis pointers. Different pointers to different diagnoses are the fastest signal a payer's system has that two same-date services are distinct.

Section E — Consultations

E.25 Yes — all three Rs. E.26 No — no request; the patient self-referred. E.27 No — no written report back. E.28 Yes — initiating treatment is permitted and does not convert it. E.29 No — that is a transfer of care; report an ordinary E/M. E.30 The setting-appropriate E/M — an office visit or hospital care code. E.31 99244. E.32 The request and the report fail most often. A missing request looks like a self-referral or a scheduled appointment with no documented origin; a missing report looks like a visit with no correspondence in the chart.

Section F — Emergency department

F.33 No new/established — the department serves anyone at any hour and has no ongoing patients in the relevant sense. No time option — ED work is interleaved by design, so total time on the date is not a meaningful measure for one patient. F.34 No. The medical decision making documented, including what was ruled out. F.35 High — a decision regarding hospitalization, considered and not selected, documented. Chapter 15 §15.7 counts options considered but not selected. F.36 Problems moderate (undiagnosed new problem with uncertain prognosis), data minimal (one unique test), risk moderate (prescription drug management). Two of three at moderate → 99284. F.37 Risk falls to low; only one element reaches moderate; two of three at low → 99283. F.38 99281; its office analogue is 99211.

Section G — Critical care

G.39 No. Location does not make care critical; the patient is not critically ill. G.40 Yes, if the patient is critically ill and the work is high-complexity. G.41 Not critical care. Report the appropriate E/M for the setting. G.42 95 − 20 = 75 minutes. 99291 covers 30–74. The remaining 1 minute is not a full additional 30. Report 99291 and the central line. (Verify against any payer-published time-to-units table.) G.43 The pulse oximetry line denies as bundled; it is on the critical care inclusion list and is a standing edit at most payers. G.44 Yes, with modifier 25 on the E/M, provided the documentation shows the sequence — an evaluation when the patient did not require critical care, then deterioration, then critical care.

Section H — The two claims

H.45 Professional: CMS-1500 / 837P. Facility: UB-04 / 837I. H.46 The professional level from medical decision making; the facility level from the facility's own written acuity criteria based on resources consumed. Independent determinations. H.47 That the facility is likely not applying its own criteria — it is copying the physician's level. It is itself a finding. H.48 Written · consistently applied · resource-based · reproducible · auditable. Auditable is the practical test, because a facility whose criteria live in someone's head or in a nine-year-old file cannot demonstrate any of the others. H.49 Not a denial — packaging. Payment is included in the primary service. Do not work it as a denial. H.50 A revenue code says where — which department or cost center. A CPT code says what. H.51 Provider-based billing. Consequence: two claims and generally higher patient cost-sharing for the same service in the same building. H.52 Expected shape: "You had one visit, but two organizations provided part of it. The physician bill covers the doctor's own work; the hospital bill covers the room, nursing, supplies, and equipment. Both went to your plan, and your benefits were applied to each separately." The sentence not to say: "That's just how it works."

Section I — Integration

I.53 The rule is Chapter 15 §15.5's: a problem is addressed when it is evaluated or treated at the encounter by the professional reporting the service, and notation of a problem managed by someone else, without additional assessment or care coordination, is not addressed. The emergency physician did not assess, manage, or plan for the diabetes, hypertension, or hyperlipidemia. I.54 The prescription. It moves the risk element from low to moderate, giving two elements at moderate. I.55 Claims 1 → 2; allowed \$216.28 → \$1,023.60; patient \$47.58 → \$204.72; knee treated yes → no. One sentence: the ED encounter costs roughly five times as much, does not treat the problem, and the office visit still has to happen. I.56 The argument is that site of service is one of the largest determinants of cost, and that it is decided by circumstance far more often than by choice. Plan-design features that exist because of it: urgent care benefit tiers, nurse triage lines, after-hours access requirements, telehealth benefits. I.57 Modifier 25. Documentation must show the sequence — an evaluation at a time when the patient did not require critical care, then deterioration. Two notes describing one continuous episode do not qualify. I.58 Part B. Two consequences: self-administered drugs frequently not covered, and observation days not counting toward the skilled nursing facility three-day inpatient requirement.


The Encounter checkpoint — §16.10

The counterfactual: Account 10-4471's patient, same knee, emergency department, Sunday.

Professional claim: problems moderate (1 undiagnosed new problem with uncertain prognosis) · data minimal (one unique test — the knee radiograph) · risk moderate (prescription drug management). Two of three at moderate → 99284. (99283 if no prescription is written.)

The three chronic conditions score NOTHING. The emergency physician did not address them.

The money, both claims: charges \$2,897.00** · allowed **\$1,023.60 · patient \$204.72 · plan \$818.88**. Against the office encounter's **\$216.28 allowed and \$47.58 patient.

And the knee is not injected — the office encounter still has to happen, bringing the total to \$1,239.88.

Grading note: full credit requires the level, the reason the chronic conditions score nothing, and the observation that the ED visit is additive, not substitutive. A student who concludes that "the patient should have gone to the office" has missed the chapter's stated point — it was a Sunday, the office was closed, and the argument is about plan design and site-of-service economics, not about the patient's judgment. Correct that reading explicitly if it appears; it will.


Chapter 17 — Answer Key

Quiz (26 questions)

  1. C — the visit at which the decision for surgery was made is excluded.
  2. B — writing off the decision-for-surgery visit. Nothing denies, because nothing is submitted.
  3. B — a minor procedure with no postoperative days.
  4. B — one preoperative day, the day of surgery, and 90 days after.
  5. B — an add-on code, included in another code's global period.
  6. C — the global period indicator. 000/010 minor, 090 major. A lookup, not a judgment.
  7. B — the body governs, and you query.
  8. C2.6 cm. 0.4 + 1.8 + 0.4.
  9. B — systematically undersizes, because tissue shrinks in formalin. The error is invisible and permanent.
  10. B — the repair.
  11. B — coded separately, each with its own measurement.
  12. B — layered closure, or single-layer closure of a heavily contaminated wound requiring extensive cleaning.
  13. A — simple is included; intermediate and complex are separately reportable.
  14. B — reported separately; at intermediate complexity the trunk and the hand are in different anatomic groupings. This is the subtle error.
  15. B — includes the lesion excision.
  16. B — the deepest tissue actually removed.
  17. B — a single physician must act as both surgeon and pathologist.
  18. B — the pathology is not separately reported; the repair is.
  19. C — a large joint.
  20. B20610. 20611 requires permanent recording and report; guidance alone is not enough.
  21. B — the fracture site was not surgically opened. It says nothing about whether the fracture was compound.
  22. B — an E/M plus the splint application. They are stabilizing and referring, not managing through healing.
  23. B — the application is included; the casting material is separately reportable.
  24. B — always includes diagnostic arthroscopy.
  25. B — only when performed alone, or independently of and unrelated to other services at the same session.
  26. B — the operative notes did not establish a distinct anatomic region, and the defense could not be built retroactively.

Exercises

Section A — The surgical package

A.1 Included. A.2 Excluded — modifier 57 for a major procedure. A.3 Included. A.4 Included. A.5 Included — typical postoperative follow-up. A.6 Excluded — modifier 78. A.7 Excluded — modifier 58. A.8 Excluded — modifier 24.

Section B — Global periods

B.9 Minor procedure, no postoperative days. Consequences: modifier 25 rather than 57 applies to a same-day E/M; and there is no postoperative period, so a later related visit is an ordinary billable E/M. B.10 Minor, 10 postoperative days. B.11 One preoperative day — the day before surgery. B.12 The global concept does not apply to the code. B.13 The payer determines the global period; typically unlisted codes. B.14 The code is included in another service's global period; add-on codes. B.15 The Medicare Physician Fee Schedule relative value file, published by CMS. It is free. B.16 Modifier 25 is at issue. Modifier 57 is definitely wrong — 57 is for the decision for major (090) surgery.

Section C — Reading the operative report

C.17 Preoperative diagnosis, postoperative diagnosis, the procedure heading, then the body — which is the source of truth. C.18 Code the body. The layered closure is an intermediate repair, separately reportable, and the heading omitted it. C.19 Query. You may not code a procedure the body does not document. C.20 Postoperative — it is what the encounter established. The preoperative diagnosis is what was suspected.

Section D — The measurement rule

D.21 0.3 + 1.2 + 0.3 = 1.8 cm. D.22 0.5 + 2.0 + 0.5 = 3.0 cm. D.23 The rule specifies the narrowest margin: 0.2 + 0.8 + 0.2 = 1.2 cm. (Students who use 0.4 have read "margins" and not "narrowest.") D.24 Excision: 2.6 cm (1.8 + 0.4 + 0.4). Repair: 2.6 cm (the defect). They are the same number by coincidence, not by rule — full credit requires saying so. The 2.3 cm pathology figure is used for nothing. D.25 Three separate excision codes, each measured 0.2 + 1.0 + 0.2 = 1.4 cm. Not added. D.26 No. Benign versus malignant comes from pathology, and the code families differ. Holding is correct, not a delay. D.27 Downward — formalin shrinks tissue, so the specimen is smaller than what was excised, which undersizes and undercodes. D.28 No specimen, therefore no pathology report. The destruction family must distinguish benign from malignant on clinical grounds.

Section E — Repairs

E.29 Simple: one-layer closure of a superficial wound. Intermediate: layered closure, or one layer of a heavily contaminated wound requiring extensive cleaning. Complex: more than layered — scar revision, extensive undermining, retention sutures. E.30 Intermediate. The second half of the definition. E.31 Simple: no, it is included. Intermediate: yes, separately reportable. E.32 One code, 5.5 cm — same classification, same anatomic grouping. E.33 Two codes: 3.0 cm and 1.5 cm. At intermediate complexity the trunk and the hand fall in different groupings. E.34 Two codes — different classifications are never added, even on the same body part. E.35 Simple. For intermediate you would need documentation of a layered closure, or of extensive cleaning and removal of particulate matter. "Irrigated" is neither. E.36 One code — adjacent tissue transfer, which includes the lesion excision.

Section F — Grafts, debridement, Mohs

F.37 By the square centimeters of the defect, primary plus secondary. It includes the lesion excision. F.38 The recipient site. F.39 Depth and area. The deepest tissue actually removed determines depth. F.40 No. "Down to fascia" describes what is exposed. Fascial debridement requires that fascia was debrided. F.41 Same depth → add: 27 sq cm, coded as the first 20 plus one add-on unit. F.42 Not Mohs — Mohs requires one physician acting as both surgeon and pathologist. Report an excision plus a separately reported pathology service.

Section G — Musculoskeletal and joint injections

G.43 Large. G.44 20610. 20611 requires permanent recording and report; guidance alone does not support it. G.45 One unit. The unit is the joint, not the injection. G.46 Two services — and Chapter 14 §14.8's bilateral and laterality rules now apply, including the payer-varying bilateral convention. G.47 The fracture site was not surgically opened. No — a compound fracture can receive closed treatment. G.48 The fracture was reduced — fragments manipulated into position — and it must be documented as such. G.49 E/M plus splint application and supply. Global fracture care would assert that the emergency physician had undertaken ninety days of fracture management. G.50 Global fracture care. Now included for 90 days: all normal follow-up visits and subsequent cast changes.

Section H — Casting and arthroscopy

H.51 Application: included. Material: separately reportable. H.52 Nothing — a replacement cast during the global period is included when the physician is reporting global fracture care. H.53 Explain that the application is included and has not been billed, and that what is on the claim is the supply, which is separately payable — offering the line and the code. Check the payer's own policy first, since some contracts bundle it. H.54 Surgical arthroscopy always includes diagnostic arthroscopy. H.55 Medial, lateral, patellofemoral. The note must name the compartment because several codes are written in terms of compartments and distinctness between procedures turns on it. H.56 Reportable only when performed alone or independently of other services at the same session. Example: diagnostic arthroscopy, which is why it is never reported alongside a surgical arthroscopy.

Section I — Code the note, twice

I.57 First pass: excision, right shoulder, 0.5 + 2.2 + 0.5 = 3.2 cm, benign/malignant pending pathology. Second pass: the body documents deep dermal sutures plus skin closure — a layered closure — an INTERMEDIATE repair, separately reportable, measured by the defect (3.2 cm). The heading omitted it. Two lines; hold line 1 for pathology.

I.58 First pass: arthroscopic partial medial meniscectomy. Second pass: the chondral debridement was performed in the lateral compartment — a different compartment from the meniscectomy — which is exactly the fact that makes a separate report potentially supportable, subject to the NCCI edit and its modifier indicator. The note named the compartment. That is the whole difference from Account 31-2245. Also: the diagnostic inspection is not separately reported.

I.59 (Account 10-4471.) 20610 — large joint (knee), no imaging guidance. Plus J1030 for the drug. Second pass: the lidocaine is local anesthesia and is inside the surgical package — not reported. "No aspirate obtained" confirms this was an injection rather than an aspiration-and-injection. Global period 000.

I.60 First pass: three lacerations. Second pass: forearms are both intermediate and both in the same groupingadd: 5.5 cm, one code. The scalp is simple — different classification → its own code, 4.0 cm. Two codes, not three and not one. "All wounds irrigated" does not make the simple repair intermediate.

Section J — Integration

J.61 The operative notes did not establish a distinct anatomic region, and the defense cannot be built retroactively. The sentence: "Debridement was performed in the subacromial space, anatomically distinct from the repaired supraspinatus insertion." J.62 Modifier 57. 25 is wrong because 25 applies to minor procedures (000/010); 57 applies to the decision for major (090) surgery. J.63 A documented negative. It closes the question of 20610 versus 20611 — without it, the note is silent about guidance, and silence requires a query. J.64 Expected shape: count, per surgeon, the number of major procedures performed and the number of E/M services reported with modifier 57 in the preceding period. A surgeon with substantial 090-day volume and near-zero modifier 57 is either referring in every case or writing off the decision visit. Grade for identifying a countable proxy — students who answer "review charts" have not designed an audit.


The Encounter checkpoint — §17.2 and §17.7

20610 carries a 000-day global.

Included: the immediate pre-procedure evaluation after the decision to inject · positioning · consent · the 1% lidocaine (local anesthesia) · the injection · the dressing · post-procedure instructions. No postoperative days at all.

Not included: the significant, separately identifiable E/M (line 1, modifier 25) and J1030, the drug — a supply, not a service.

Two settled questions: 000 → minor → modifier 25, not 57. And the lidocaine is absent from the claim because it is inside the package — a practice billing it separately is billing for something it has already been paid for.

And 20610 rather than 20611 because the note states "No imaging guidance used."

Grading note: full credit requires the lidocaine observation. Students consistently miss it, and it is the item that demonstrates whether they understood "the package" or merely memorized "000 = no postoperative days."


Chapter 18 — Answer Key

Quiz (26 questions)

  1. B — the value of the diagnostic base procedure of that family.
  2. B — not separately reported.
  3. B — one snare code. Same technique, multiple lesions.
  4. C — generally two codes, one per technique, subject to the edits.
  5. BZ12.11. The reason the patient came did not change.
  6. B — the therapeutic code, because that is what was done.
  7. D — duration of symptoms is not one of the five.
  8. C — the open procedure only.
  9. B — they bundle the catheter placement, injection procedures, and imaging supervision and interpretation.
  10. B — which components were involved: generator, leads, or both.
  11. B — a duplicate.
  12. C — three: male genital, pathology, and radiology.
  13. B — instrumentation and bone graft.
  14. A — antepartum care, delivery, and postpartum care.
  15. B — routine urinalysis.
  16. C — each reports the components it actually provided.
  17. B — in full.
  18. C — by descending value, highest first.
  19. C — an underpayment that pays, with nothing appearing in a work queue.
  20. B — how the bilateral payment rules apply to that code.
  21. C — postoperative management only.
  22. B — each reports the same procedure code with the applicable modifier.
  23. B — two surgeons each performing a distinct part, each documenting an operative report.
  24. B — (base + time + modifying units) × conversion factor.
  25. B — when the anesthesiologist begins preparing the patient for induction.
  26. B — with administration of the sedating agent.

Exercises

Section A — Endoscopic base-code rule

A.1 Additional endoscopic procedures from the same family are reduced by the value of that family's diagnostic base procedure. A.2 Because every endoscopic procedure in a family includes getting the scope to where the work happens, and doing three things through one scope does not require inserting the scope three times. The base is the shared work. A.3 The ordinary reduction pays additional procedures at a percentage; the base-code rule subtracts a fixed value. They are different mechanisms and do not both apply. A.4 No. Parallels Chapter 17 §17.9: surgical arthroscopy always includes diagnostic arthroscopy. Both derive from the "(separate procedure)" designation. A.5 No — different families. Which reduction applies between two codes depends on the code set's family definitions, not on anatomic similarity. A.6 The multiple procedure indicator in the Medicare Physician Fee Schedule relative value file.

Section B — Colonoscopy

B.7 One. B.8 Two — one per technique, subject to the edits. B.9 Generally two, different techniques on different lesions. B.10 How far the scope went and why it stopped; the note must document the extent and, for a complete examination, the landmarks establishing that the cecum was reached. B.11 First-listed diagnosis Z12.11; procedure code the therapeutic (snare removal) code. B.12 The procedure code describes what was done; the diagnosis describes why the patient came, and a finding during a screening does not retroactively change the reason for the encounter. B.13 Modifier 33 and modifier PT. B.14 D12.5 — benign neoplasm of sigmoid colon. Chapter 34 §34.11 owns the financial resolution.

Section C — Hernia, conversion, digestive

C.15 Which hernia · initial or recurrent · reducible or incarcerated/strangulated · patient age · mesh implantation. C.16 "Recurrent." From the surgeon's side it is background — the reason the case was scheduled as it was — rather than a finding of the operation. C.17 Separately reportable with some repairs and included in others. There is no principle to reason from; read the code and its parenthetical. C.18 The open procedure only. C.19 Justified: documented additional work — adhesions, distorted anatomy, substantially increased time — described in a special report. Not justified: the conversion itself. C.20 Both are a fact the surgeon holds that the code depends on and that nobody has told them to dictate. Remedy in both: a one-page list of load-bearing sentences for the surgeons.

Section D — Cardiovascular, urinary, nervous

D.21 Organized by structure, then approach. D.22 Report the catheterization code, which bundles them. It appears on exams because older references list the components separately. D.23 Which components — generator, leads, or both. D.24 Per vessel or territory; the note must name the vessel. D.25 Errors: modifier 50 on an already-bilateral code (a duplicate), and a unilateral code reported once for a bilateral procedure (an underpayment). Avoid both by reading the descriptor and checking the bilateral surgery indicator. D.26 Three: male genital (the biopsy), pathology (the specimen), radiology (the guidance). D.27 Approach · level(s) · what was done · instrumentation and bone graft. D.28 It means reporting guidance separately alongside them is unbundling. Compliance consequence: it is detectable from claims data alone, with no chart required.

Section E — Maternity

E.29 Antepartum care, delivery, postpartum care. E.30 Any four of: visits for problems unrelated to the pregnancy · complications of pregnancy requiring additional care · laboratory other than routine urinalysis · ultrasounds · amniocentesis · fetal non-stress tests. E.31 Practice A reports antepartum care by visit count; Practice B reports delivery, or delivery plus postpartum depending on what it provided. E.32 Because coverage at the first prenatal visit may not be coverage at delivery, and the claim goes to the plan current at billing for care provided under a plan that is not. E.33 Counting the antepartum visits. The antepartum codes are divided by number of visits, so the count is the code. E.34 Honest answer: filing limits run from the date of service, which raises a real question about which date of service a nine-month package has. The real answer is in the payer's policy — read it before you need it.

Section F — Multiple procedures and line order

F.35 Highest-valued procedure paid in full, additional procedures at a reduced percentage. Assume nothing — verify by payer. F.36 Add-on codes and modifier-51-exempt codes. F.37 The multiple procedure indicator in the Physician Fee Schedule file. F.38 Descending value, highest first, because payer systems may apply the reduction in the order the lines appear. F.39 Highest-first: 1,200 + 400 + 200 = \$1,800.** Lowest-first: 400 + 400 + 600 = **\$1,400. Difference \$400. F.40 Nothing. The claim pays, the adjustment posts, the account closes.

Section G — Bilateral, split global, teams

G.41 One line/modifier 50/one unit · one line/modifier 50/two units · two lines RT and LT. G.42 How the bilateral payment rules apply to that code — including whether the code is already bilateral by descriptor, which is the eligibility question that precedes the convention question. G.43 56 preoperative management only · 54 surgical care only · 55 postoperative management only. G.44 The same procedure code, each with the applicable modifier. G.45 It could have, in principle — but it requires an agreed, dated transfer of care between two organizations that had never spoken, which is the coordination failure the case study was about. A mechanism that depends on coordination cannot fix a coordination failure. §17.7's answer — an E/M plus a splint, claiming nothing about the next ninety days — requires no coordination at all. G.46 Each surgeon performed a distinct part requiring their own skill set. Each must document their own operative report; one note signed by both does not establish it. G.47 80 is a surgeon assisting; AS is a non-physician assistant (PA, NP, CNS). The payment differs, and reporting one under the other misstates who performed the service. G.48 Several physicians of different specialties, plus support personnel, working as a team on a highly complex procedure.

Section H — Anesthesia and sedation

H.49 (base units + time units + modifying units) × conversion factor. H.50 Begins when the anesthesiologist begins preparing the patient for induction; ends when the patient may be safely placed under postoperative supervision. Source: the anesthesia record, not the operative report. H.51 6 base + (90 ÷ 15 = 6) time + 1 modifying = 13 units × \$22.00 = \$286.00. H.52 91 ÷ 15 = 6.07. 6 units or 7 depending on the payer's rounding rule, which this book cannot supply — it is published, per payer, and differs. H.53 P3, P4, P5 generally. H.54 Add-on codes for anesthesia complicated by extreme age, extreme hypothermia, controlled hypotension, or emergency conditions. Chapter 13 §13.7 applies: never reported alone, never modifier 51. H.55 Drug-induced depression of consciousness in which the patient responds purposefully to verbal commands, maintains a patent airway without intervention, and maintains adequate cardiovascular function. Not general anesthesia; not monitored anesthesia care (also acceptable: not minimal sedation). H.56 With administration of the sedating agent. Also required: continuous face-to-face attendance and an independent trained observer.

Section I — The Encounter

I.57 No reduction. Line 1 is an E/M, not a surgical procedure — a separately identifiable service with modifier 25, not a second procedure. Line 3 is a drug, a HCPCS Level II supply. Line 4, 36415, is a routine venipuncture and is not a surgical procedure subject to the reduction. Exactly one surgical procedure — line 2 — and the reduction requires two. I.58 The bilateral methodology applies; the multiple-procedure reduction does not. Under conventions A or B it is one line, adjusted bilaterally. I.59 Not a second line — a units question. J1030's descriptor is per 40 mg, and two knees at 40 mg each is two units on one line. Chapter 20 §20.4 owns the rule. I.60 The bilateral surgery indicator lookup would have answered whether the code was bilateral-eligible; reading the payer's provider manual would have supplied the convention. The lookup prevents one half of the failure and the reading prevents the other.


The Encounter checkpoint — §18.12

No multiple-procedure reduction is applied to Account 10-4471, because the claim contains exactly one surgical procedure.

Line Code Why it is not a second procedure
1 99214-25 an E/M — separately identifiable, not a procedure
2 20610-RT the only surgical procedure
3 J1030 a drug — HCPCS Level II supply
4 36415 routine venipuncture — not subject to the reduction

The both-knees counterfactual (constructed — did not happen): bilateral methodology, not multiple-procedure; one line under conventions A or B; J1030 doubles in UNITS, not in lines.

Grading note: full credit requires walking all four lines. A student who answers "no, because there is only one procedure" without saying why the other three are not procedures has the right answer and has not demonstrated the reasoning — and the reasoning is the entire point of the checkpoint.


Chapter 19 — Answer Key

Quiz (26 questions)

  1. B — supervision where required, and the interpretation and written report.
  2. C — does not exist. No written report, no professional component.
  3. B — whoever owns the equipment.
  4. C — the PC/TC indicator.
  5. Bwithout contrast. Oral contrast alone does not make a study "with contrast."
  6. C — intravascularly, intra-articularly, or intrathecally.
  7. B — one code, "without contrast followed by with contrast."
  8. C — the limited study. A defined element not documented makes it limited.
  9. C — per a defined number of fractions.
  10. B — included; reporting it separately is unbundling.
  11. C — the thirteen individual tests. The panel is not reportable unless every component was performed.
  12. B — unbundling, and easily detected without any chart.
  13. C — the separately identified and separately submitted specimen.
  14. B — identifies specific drugs and quantities.
  15. C — the specimen collection only.
  16. B — referring or ordering provider.
  17. C — the ordering physician is not enrolled with the payer. That belongs with credentialing (Chapter 25).
  18. B — personally by the provider, during the encounter, on a specimen not easily transportable.
  19. B — a CLIA-waived test performed by a waiver site.
  20. Cescalate. The site performed a test its certificate does not cover; resubmitting sends a new claim for the same problem.
  21. C — a medically necessary repeat performed to obtain subsequent results.
  22. BMedicine. Cardiovascular surgery is in the Surgery section.
  23. B — an alternative to the E/M office visit codes.
  24. C — the chemotherapy. Hierarchy overrides chronology.
  25. C — both the vaccine product code and the administration code.
  26. B1 unit. Total the timed minutes first: 8 + 8 = 16, which falls in the 8–22 band.

Exercises

Section A — Components

A.1 Hospital reports 71046-TC; the radiology group reports 71046-26. A.2 The practice reports 71046 — global, no modifier. A.3 Practice reports 71046-TC; the interpreting physician reports 71046-26. A.4 The practice reports nothing. Ordering is not performing. A.5 None. There is no professional component without a written report. A.6 The mobile unit, because it owns the equipment. Location does not decide it. A.7 The Medicare Physician Fee Schedule relative value file; the column is the PC/TC indicator. A.8 It asserts a service that does not exist — an interpretation and report for a code that has no professional component to report.

Section B — Radiology

B.9 Modality · body part · number of views · contrast. B.10 Without contrast. B.11 Contrast administered intravascularly, intra-articularly, or intrathecally. B.12 One — "without contrast followed by with contrast." B.13 The code — plain radiography codes are frequently divided by view count. B.14 The limited study. B.15 Consultation and clinical treatment planning · simulation · medical radiation physics and dosimetry · treatment delivery · treatment management, which is the one reported per a defined number of fractions. B.16 The radiopharmaceutical, reported with a HCPCS Level II code — Chapter 20.

Section C — Imaging guidance

C.17 (1) Is guidance named in the descriptor? → included. (2) Does a separate code exist for the procedure with guidance? → use that code. (3) Otherwise, is there a standalone guidance code? → separately reportable if its own requirements are met. C.18 No — it is included, and reporting it separately is unbundling. C.19 Question 2. A separate code exists: 20611 (with guidance) versus 20610 (without). Do not report guidance separately. C.20 Permanent image recording and a report. Stated previously at Chapter 14 §14.7 (the professional component) and Chapter 17 §17.7 (20611). One sentence: no report, no service.

Section D — Panels and pathology

D.21 Report a panel only if every component was performed; and do not unbundle a panel you did complete. D.22 The thirteen individual tests. D.23 Unbundling. Easy to find because the component pattern is visible in claims data with no chart required. D.24 Report the closest panel without exceeding what was done, then report the additional tests individually. Never build a panel from components. D.25 The specimen — each separately identified and separately submitted. Count containers. D.26 One container = one specimen; two labeled containers = two. D.27 Culture (per specimen or source) · identification (per isolate — here, two) · susceptibility (frequently per antibiotic or per plate). D.28 Presumptive indicates presence or absence of a drug or class; definitive identifies specific drugs and quantities. Pattern: large uniform definitive panels on standing orders, detectable because panel size and its uniformity across patients are visible in claims data alone.

Section E — Ordering, performing, CLIA

E.29 The performing entity bills. The ordering physician appears as the referring/ordering provider, by name and NPI — that is their entire role. E.30 The reference laboratory bills the tests; the practice bills the specimen collection. E.31 A test performed by an outside laboratory and billed by the reporting entity. E.32 Blank field · wrong person's identifier · ordering physician not enrolled · name/identifier mismatch. The third cannot be fixed by billing — it belongs with credentialing. E.33 Certificate of Waiver · Certificate for Provider-Performed Microscopy · Certificate of Compliance · Certificate of Accreditation. E.34 Performed personally by the provider, and during the patient encounter, on a specimen not easily transportable. E.35 A CLIA-waived test performed by a waiver site. E.36 Escalate — the site performed a test its certificate does not cover, which is a compliance problem. Do not resubmit; every resubmission is a new claim for the same problem.

Section F — Repeats and units

F.37 A repeat performed to obtain subsequent results. Not for: equipment failure · specimen problems · confirming a result · normal quality control. F.38 No. A code whose descriptor is "per hour" handles repetition through units, not through modifier 91. F.39 What is the unit? How many were performed? Do the answers match the claim? F.40 Too few units → underpayment. Too many units → overpayment. Both are invisible on the remittance.

Section G — The Medicine section

G.41 Cardiovascular studies are in Medicine; cardiovascular surgery is in Surgery. G.42 93000 is the global ECG with interpretation and report; 93010 is the interpretation and report only. They encode the professional/technical distinction — the same distinction §19.1 encodes with modifiers 26 and TC. G.43 General ophthalmological services — intermediate and comprehensive examinations for new and established patients; an alternative to the E/M office visit codes. G.44 A defined list of elements plus initiation of a diagnostic and treatment program. Chapter 15's standard is "medically appropriate," a clinical judgment; the eye codes use a checklist. G.45 Antigen preparation and injection — separate services, correctly on separate lines. G.46 The panel rule (§19.4) — components bundled into a more comprehensive study may not be reported alongside it.

Section H — Injections and infusions

H.47 Chemotherapy > therapeutic/prophylactic/diagnostic > hydration; and infusions > pushes > injections. H.48 Hierarchy. H.49 Chemotherapy = initial (plus add-on units for additional hours) · antiemetic = sequential push · hydration = subsequent. H.50 1030–1235 = 125 minutes → the initial hour plus one full additional hour. The remaining 5 minutes do not make a second add-on unit. H.51 Duration is unknown, so an infusion cannot be supported over a push and no add-on units can be supported. What remains is a single administration code. H.52 Initial — the primary service, selected by hierarchy, generally one per encounter per access site. Sequential — a different substance, after the initial, same access. Concurrent — at the same time as another.

Section I — Immunizations

I.53 Two — the vaccine product code and the administration code. I.54 The administration. A pure underpayment that never denies. I.55 Not necessarily. A vaccine supplied free through a public program may not be billed; the practice may still bill the administration. Adding the product would be billing for a vaccine somebody else paid for. I.56 Counseling by the physician or QHP — not clinical staff — documented.

Section J — Timed codes

J.57 Untimed codes are reported once per date regardless of duration. Timed codes are reported in units, commonly 15 minutes, and require constant attendance or direct one-on-one contact. J.58 Total all timed minutes on the date, then convert: 8–22 = 1 · 23–37 = 2 · 38–52 = 3 · 53–67 = 4 · 68–82 = 5. J.59 1 unit (8 + 8 = 16, in the 8–22 band). The common wrong answer is 2, produced by converting each service separately and adding the units. J.60 That the services are medically necessary and the documentation in the record supports it. Appending it automatically at a threshold is the same failure as an auto-appended modifier 59: a configuration making a factual assertion about a record that nobody has read — Chapter 14 §14.1, and Chapter 5 §5.3's reckless disregard.

Section K — The Encounter

K.61 On the reference laboratory's claim. The entity that performed the test bills it; Northgate collected and sent. K.62 36415, the venipuncture. \$14.00 charged, \$3.00 allowed. K.63 CLIA — does Northgate's certificate cover both tests, and is a modifier QW version applicable? The panel rule — 80061 requires that every component be performed. Units. K.64 Either specimen handling is not separately payable under this contract (correct not to bill) or it is payable and the practice is not billing it (Chapter 15 §15.9a). A practice finds out by reading the contract or asking the payer — waiting never resolves it.


The Encounter checkpoint — §19.12

Account 10-4471's claim carries 36415 and not 83036 or 80061.

Why The entity that PERFORMED the test bills it (§19.5). Northgate collected the specimen and sent it out
Who bills 83036 and 80061 the reference laboratory, directly, with the ordering physician as referring provider
What Northgate bills 36415 — \$14.00 charged, **\$3.00 allowed**
Not on the claim either 99000 — specimen handling; a payer question nobody has asked

The in-house counterfactual raises three questions: CLIA certificate coverage · the panel rule for 80061 · units. And the decision is a business decision about volume — certificate fees, proficiency testing, analyzers, reagents, personnel, and daily quality control against what the tests actually pay.

Grading note: full credit requires the rule ("the performing entity bills"), the identification of the reference laboratory as the biller, and the observation that Northgate's entire revenue from two laboratory orders is \$3.00. Students who answer only "the lab bills them" have the fact and not the rule. The \$3.00 is what makes the in-house question interesting, and students who notice it unprompted have understood the section.


Chapter 20 — Answer Key

Quiz (26 questions)

  1. B — CMS.
  2. B — published free.
  3. B — quarterly.
  4. C — J.
  5. B — S and T.
  6. B — the origin.
  7. B10 units. 100 ÷ 10.
  8. B — the 80 mg code, one unit. Use the code that matches the dose where one exists.
  9. B1 unit. Whole units only; a fraction cannot be reported.
  10. B — a five-fold underpayment that pays and is invisible.
  11. B — drug name, dose, and route in the narrative, and generally the NDC.
  12. B — average sales price plus a percentage add-on.
  13. B — drug amount discarded and not administered to any patient.
  14. A — zero drug amount discarded.
  15. B — a claim with no JW line was ambiguous between "nothing wasted" and "waste not reported."
  16. C — single-dose containers.
  17. B — add up to the container.
  18. B — it is evidence that an order was written; the medical record must independently support the need.
  19. C — rented.
  20. B — the item is rented for a defined number of months, after which ownership generally transfers or the arrangement converts.
  21. B — CMS adopted a different threshold than CPT's and needed a code to carry it.
  22. C — the beneficiary's risk status, which determines the coverage rule. The procedure is identical.
  23. B — a labeler, product, and package size.
  24. B — frequently different numbers in different units of measure, and that is correct.
  25. B — valid but generally not separately payable, because the tray is a usual supply.
  26. D — not medically necessary as documented.

Exercises

Section A — Structure and families

A.1 Level I is CPT; Level II is HCPCS Level II. A.2 CMS. It is published free — unlike CPT, which is copyrighted and sold (Chapter 13 §13.2). A coder with no budget can hold the entire Level II code set. A.3 Quarterly. The failure is a terminated code still in a charge master, denying on the first claim of the new quarter, worked as a one-off, recurring indefinitely. A.4 One letter followed by four digits. A.5 A permanent code is maintained through the public quarterly process with a formal application procedure; a temporary code is established quickly where no permanent code exists, and may become permanent, be replaced, or persist. A.6 J. A.7 E. A.8 L. A.9 T. A.10 S.

Section B — Ambulance

B.11 First character = origin; second = destination. B.12 Residence → hospital. B.13 Scene of an accident → hospital. B.14 Because nobody can pretend RH is a billing preference. It is a statement of physical fact, which is what every modifier is supposed to be (Chapter 14 §14.1) and what modifiers are most often used as if they were not.

Section C — J-code units

C.15 40 ÷ 40 = 1. C.16 120 ÷ 40 = 3 units of the 40 mg code — or, where an 80 mg code exists, 80 mg code × 1 + 40 mg code × 1, per payer policy. C.17 100 ÷ 10 = 10. C.18 75 ÷ 25 = 3. C.19 75 ÷ 100 = 0.75 → 1 unit. The limitation: you cannot report a fraction of a unit, and the shortfall cannot be expressed at all. C.20 The 80 mg code, one unit. The error to avoid is two units of the 40 mg code, which describes the same milligrams and is a pattern edits look for. C.21 Units question: 60 mg administered ÷ the descriptor's dosage. Waste question: 40 mg remained in a single-dose vial → a JW line. C.22 Too few units → invisible underpayment. Too many units → overpayment, caught by MUEs. C.23 Chapter 21 — medically unlikely edits. C.24 Drug name, dose, and route in the narrative, plus generally the NDC. C.25 They price manually because the code identifies nothing, so a person must read the narrative. They should be temporary because when a specific code is established the unclassified code becomes wrong, and the practice is generating manual-review claims for no reason. C.26 Average sales price plus a percentage add-on, republished quarterly.

Section D — Waste

D.27 JW: drug amount discarded and not administered to any patient. JZ: zero discarded. D.28 Because a claim with no JW line meant either nothing was wasted or nobody reported the wastetwo very different facts that looked identical. D.29 No. A multi-dose vial holds doses for more than one patient; its remainder is not waste. D.30 J1030 with the administered units + a JW line with the discarded units. Check: the two must add up to the 40 mg container. D.31 Administered 75 ÷ 25 = 3 units; JW 25 ÷ 25 = 1 unit; 3 + 1 = 4 units = 100 mg = the container.No JZ. D.32 One line, 3 units, and JZ. No waste from a multi-dose vial. D.33 In the medical record. The claim is the assertion; the record is the evidence (Chapter 5 §5.4). D.34 It is a formula, and formulas are not observations — waste is a physical event that either happened or did not.

Section E — DMEPOS

E.35 Withstands repeated use (excludes disposables) · serves a medical purpose · not useful absent illness or injury (excludes comfort items) · appropriate for use in the home (excludes facility-only equipment). E.36 A written order with the beneficiary's name, the item, the prescribing practitioner and identifier, and the order date. E.37 Independent support in the medical record for why this patient needed this item, in the terms the item's policy requires. E.38 Documentation is not evidence of the qualification; it IS the qualification. E.39 NU new purchased · UE used purchased · RR rented. E.40 A rental running a defined number of months, after which ownership generally transfers or the arrangement converts. Track the rental month — payment and the arrangement change over its course. E.41 Continued medical need. The framing is useful because it makes the recurring obligation visible: the record must support the need each time, not once at the beginning. E.42 It limits who may furnish certain items in certain areas to contracted suppliers. It relates to §20.10's theme because a correct claim from a non-contracted supplier is still not payable — a code existing is not the same as being permitted to furnish the item.

Section F — G, Q, S, T

F.43 (1) CPT has no code — a Medicare-specific benefit such as the annual wellness visit. (2) Medicare needs a different ruleG2212 versus 99417. (3) Medicare needs a distinction CPT would not makeG0105 / G0121. F.44 CPT created 99417 with one threshold; CMS adopted a different threshold and created its own code to carry it. The service is the same; the rule is not. F.45 The beneficiary's risk status, which determines the applicable screening frequency limitation. It is a coverage distinction, not a procedural one. F.46 G. Because G-codes are frequently placeholders — they get replaced by CPT codes, or retired when a measurement program changes. F.47 S and T. F.48 Q.

Section G — NDC

G.49 An NDC identifies a product in a package (labeler, product, package size); a J-code identifies a dosage. They describe different things, so the claim carries two quantities in two units of measure. G.50 No, and they should not be expected to match. G.51 Format (leading zeros/segments) · a stale NDC · a mismatched unit-of-measure qualifier · a quantity copied from the wrong identifier. G.52 No — it is a factual error. The claim reports a product that was not administered. G.53 Store the correctly formatted NDC, its unit of measure, and its conversion factor against the charge master line, so the claim assembles them rather than a person retyping them. G.54 Because the format conversion is mechanical and a human doing it by hand will get it wrong at a predictable rate that does not improve with experience. Training addresses skill; this is not a skill problem.

Section H — Payability

H.55 Any four: local anesthesia in a package · usual dressings, sutures, drapes · the surgical tray · routine office supplies consumed in a visit. H.56 Casting and splinting materials · drugs · implants and devices · items dispensed for home use. H.57 Bundled · not a benefit at all · not recognized by this payer · not medically necessary as documented. H.58 The fourth. H.59 Concede that the item is not separately payable under this contract, agree to remove the charge master line, and ask whether it is excluded across the board or only for facility claims. Do not appeal — the code is correct and the payment policy is that it is bundled, and both are true. H.60 Who is paying. Three approaches: by memory (fails on vacation, untraceable error rate) · by a payer-specific rule in the claim system (works, and is what most organizations should do) · by separate charge master entries with payer mappings (more maintenance, more control, where large organizations end up).

Section I — The Encounter

I.61 40 ÷ 40 = 1 unit. The enabling sentence: Figure 4.2's procedure note documents "methylprednisolone acetate 40 mg." ("Steroid injected" would support no units at all.) I.62 JZ. 40 mg supplied, 40 mg administered, nothing discarded. The claim as coded on Day 1 carries J1030 with no modifier — an incomplete assertion rather than an overpayment. I.63 Local anesthesia is inside the surgical package for 20610 (Chapter 17 §17.2). The principle: a drug being codeable in HCPCS Level II does not make it separately payable. I.64 \$18.00** is a charge set by the practice — **Chapter 23 §23.7** owns it. **\$6.28 is an allowed amount derived from a published quarterly average sales price file.


The Encounter checkpoint — §20.4

Account 10-4471, line 3: J1030 × 1. \$18.00 charged, \$6.28 allowed.

Units 40 mg administered ÷ 40 mg descriptor = 1
Waste 40 mg supplied, 40 mg given → JZ, not JW
On the claim J1030, no modifier — an incomplete assertion
The lidocaine not on the claim — inside 20610's surgical package

Grading note: full credit requires the arithmetic, the JZ conclusion, and the observation that the units are computable only because the note states the dose. Students who answer "one unit because one injection" have reached the right number by the wrong route and will get the next one wrong.

Do not accept "bill JW for the leftover" — there was no leftover. This is exactly Case Study 1's failure in miniature, and it is worth pointing out when a student produces it.


Chapter 21 — Answer Key

Quiz (26 questions)

  1. B — published by CMS, free, updated quarterly.
  2. B — the code that is not separately payable when reported with Column One.
  3. B — practitioner services and outpatient hospital services.
  4. C — no modifier will override under any circumstances.
  5. B — a modifier may override if circumstances justify it and documentation supports it.
  6. B — a permission, not an authorization.
  7. Bthere is nothing to appeal to. The appeal was not poorly written.
  8. B — the maximum units of service for a code, per beneficiary, per date.
  9. B — a date-of-service edit, policy-based, that cannot be exceeded.
  10. B — MAI 2.
  11. C — report the additional units on additional lines with appropriate modifiers, where clinically justified.
  12. B — a published maximum invites billing up to it.
  13. B — published by CMS, free, updated annually.
  14. B — services integral to a procedure are included in it and not separately reportable.
  15. B — local anesthesia administered by the operating physician.
  16. C — only the completed procedure.
  17. B — "Was this separate?"
  18. B — "Did both of these actually happen?"
  19. B — already written and already signed.
  20. B — the note affirmatively documents debridement of the structures that were repaired. (A is a weaker and less accurate statement of the problem.)
  21. CXS, separate structure. Use the specific modifier where one applies.
  22. B — the edits are public, so not looking is deliberate ignorance.
  23. B — per claim.
  24. B — a private party brings an action on the government's behalf and shares in the recovery.
  25. B — does not guarantee payment; other payers apply their own edits.
  26. C — three.

Exercises

Section A — What the edits are

A.1 CPT contains codes that overlap because procedures genuinely contain other procedures, and a code set describing services cannot enumerate every combination that would double-count. Somebody has to write down which combinations are not payable together. A.2 Yes, in advance. What follows: a payer telling you before you bill exactly which combinations it will not pay, and why, is unusually fair — and a practice surprised by an NCCI denial had not looked. A.3 Nothing. Free download. A.4 The claim does not survive: the file was public, free, and searchable the entire time. This is §21.10's deliberate-ignorance point in miniature. A.5 Column One is the payable code; Column Two is the code not separately payable with it. A.6 No, the direction is fixed. A claim reporting both is paid on Column One and denied on Column Two, regardless of line order. A.7 Practitioner services and outpatient hospital services. Using the wrong one gives a wrong answer confidently, because the same pair may be edited in one setting and not the other. A.8 Column One code · Column Two code · effective date · deletion date · modifier indicator · (and the setting-specific file you are in). The modifier indicator decides whether an override is possible.

Section B — The modifier indicator

B.9 Nothing. No modifier will override, under any circumstances. B.10 It permits a modifier to be accepted by the system if circumstances justify it and documentation supports it. It does not say the edit should be overridden. B.11 The edit does not apply — it has been deleted, and the indicator keeps the historical row readable. B.12 No. There is nothing to appeal to. B.13 Bundled — remove the charge. B.14 It has asserted that the minority case is its normal case. A payer sees it as a modifier frequency rate on a code pairing, from claims data, with no charts.

Section C — MUEs

C.15 Units — the maximum units of service for a code, per beneficiary, per date, per provider. C.16 Anatomic considerations · code descriptors · CMS policy · nature of the service · claims data analysis. C.17 A claim line edit; units above the MUE may be reported on additional lines with appropriate modifiers where clinically justified. C.18 A date-of-service, policy-based edit — absolute. Do not appeal; find the units error. C.19 A date-of-service, clinical-benchmark edit — appealable with documentation. C.20 MAI 1: 3 on one line, the remaining 5 on additional lines with modifiers if justified. MAI 2: do not appeal; 8 is not possible — find why the system said 8. MAI 3: appeal with documentation. C.21 Because a published maximum invites billing up to it. No — the dose or the anatomy decides the units; an MUE is a detection threshold, not a target. C.22 They should have looked up the MAI first. Now: split the historical denials by MAI, stop appealing the MAI-2 category entirely, and redirect the time — which is Case Study 1.

Section D — Policy and principles

D.23 CMS's statement of the policies behind the edits. Free, updated annually. D.24 A general correct coding policies chapter followed by chapters corresponding to the CPT sections. D.25 It tells you what the edit protects (so you know what would genuinely separate the services) · it frequently answers the question outright · and it is what a reviewer will read. D.26 Services integral to the performance of a procedure are included in it and not separately reportable. D.27 Any six: prepping/shaving/cleansing · draping and positioning · IV access · sedation where not separately reportable · local/topical/regional anesthesia by the operating physician · surgical approach and exposure · surgical cultures · wound irrigation · closure and dressings · splints at the operative site. D.28 The greater procedure only. D.29 Sequential procedures — attempted one way, completed another; report only the completed one. D.30 Local anesthesia by the operating physician is integral. Reasons given so far: Chapter 17 §17.1/§17.2 (the surgical package), Chapter 20 §20.10 (usual supplies; a code existing is not a code being payable), and Chapter 21 §21.6 (standards of practice). Three chapters. D.31 Comprehensive/component: one code's service includes the other's. Mutually exclusive: the two could not reasonably both have been performed, or are two ways of doing the same thing. D.32 "Was this separate?" and "Did both of these actually happen?" A distinctness modifier asserts separateness, which is an answer to the first question and irrelevant to the second.

Section E — The override decision

E.33 Stop at step 3. Simple repair is included in excision; there was no separate circumstance because the closure genuinely was part of the excision. Remove the line. E.34 All four steps pass. Different lesion, different site, intermediate rather than simple. Override with XS. E.35 Stop at step 2/3 — and note this is mutually exclusive, not comprehensive/component. A modifier answers the wrong question. One of the two codes is wrong. E.36 All four pass. The note names a different anatomic region, says so explicitly, and states a separate indication. E.37 Stop at step 3. "Debridement performed" establishes nothing. E.38 Stop at step 3 — and this is worse than E.37: the note affirmatively documents the thing the edit exists to prevent being billed twice. E.39 Stop at step 1. Indicator 0. No statement by any surgeon overrides it. E.40 All four pass; the specific modifier is 25 and it is already correct. E.41 XS — separate structure. XS says why; 59 says only "somehow distinct" (Chapter 14 §14.5). E.42 Reject it. Asking eighteen months later is asking someone to remember. The defense is contemporaneous documentation and cannot be built retroactively, and this falls outside Chapter 33 §33.5's query rules.

Section F — The shoulder claim

F.43 Line 2, 29826 — an add-on code with a ZZZ indicator. An add-on and its primary are a required pairing, not a bundling question. F.44 Column One 29827, Column Two 29822, indicator 1. F.45 That debridement in the same anatomic region as a repair is not separately reportable. F.46 Step 3. "There was no supporting sentence" is not right because it understates the problem: the note affirmatively documents debridement of the repaired structures — it establishes the opposite of what the modifier asserts. F.47 For the thirty-one: two lines (29827-RT, 29826-RT). For the eleven: three lines, with the debridement modified. F.48 XS. Separate structure is what was true, and Chapter 14 §14.5 requires the specific modifier where one applies.

Section G — The False Claims Act angle

G.49 Actual knowledge · deliberate ignorance · reckless disregard. Not looking at a public file falls under deliberate ignorance. G.50 The edits are public · the pattern is quantifiable from claims data · penalties attach per claim and unbundling is repetitive · qui tam suits commonly originate with an employee who noticed a macro. G.51 The pattern and the response. A single unbundled claim is an error; the same combination on every claim for eighteen months is a configuration. G.52 It knows. Chapter 5 §5.8's sixty-day rule attaches on identification, and the organization is no longer arguing about whether it knew. G.53 A provision permitting a private party to bring an action on the government's behalf and share in the recovery. G.54 Report the pattern, not an instance · in writing, promptly, keeping a copy · to compliance. Do not pull thirty charts to check first.

Section H — Non-NCCI edits and appeals

H.55 Payers that adopt NCCI (in whole or part; Medicaid has its own files) · payers with proprietary edits · payer medical policies functioning as edits. H.56 No. Account 10-4471's line 1 was overridden correctly under NCCI and denied on day 17 by a commercial payer applying its own policy. H.57 A proprietary edit. Ask: is this NCCI or plan-specific? · which policy or rule? · is it published, and where? · is it modifier-eligible, and which modifier? H.58 "NCCI allows this." NCCI is not their rule set, and asserting it invites a conversation about a file that does not govern. H.59 Indicator 0 (no) · indicator 1 with supporting documentation (yes) · indicator 1 without (no) · MAI 2 (no) · MAI 1 or 3 (workable) · proprietary (get the policy first). Three say do not appeal. H.60 Redirect it to charge correction — faster, cheaper, and correct — and to the categories that can actually be won.

Section I — The Encounter

I.61 Column One 20610, Column Two 99214, indicator 1. I.62 That an E/M on the same date as a procedure is included unless it is significant and separately identifiable above and beyond the usual pre- and post-procedure work. Modifier 25's test, verbatim — the modifier and the edit are two halves of one policy. I.63 Three chronic conditions individually assessed with plans · prescription drug management · two tests ordered with stated reasons · a new problem evaluated independently. Three of the four have nothing to do with the knee. I.64 The override was correct under NCCI; the payer applied its own edit policy and denied. Both are true because they are different rule sets. The day-59 appeal succeeds because the documentation that justified the modifier is the same documentation that wins the appeal — you build it for the claim, not for the appeal.


The Encounter checkpoint — running the edit for 99214 + 20610

Step Result
1. Indicator 1 — a modifier may override ✓
2. Policy Manual "…unless significant and separately identifiable above and beyond the usual pre- and post-procedure work"modifier 25's test verbatim
3. Documentation ✓ three chronic conditions with plans · prescription drug management · two tests ordered — none about the knee
4. More specific modifier? No — 25 is the specific modifier, already applied

The override is correct. The payer denied it anyway on day 17 (CO-97 / N19).

Grading note: full credit requires all four steps and the observation that a correct override is not a guaranteed payment. Students who conclude the practice made an error have missed the chapter's most important distinction — NCCI is Medicare's rule set, and this was a commercial payer applying its own.

Do not accept "the payer was wrong." The payer applied a policy it is entitled to apply, and the practice won on appeal because its documentation satisfied a stricter standard. Both parties behaved defensibly, which is the point.


Chapter 22 — Answer Key

Quiz (26 questions)

  1. B — a payer's determination, under published criteria, that it will pay.
  2. C — both.
  3. B — the payer already knows; the question is whether the record contains what the policy requires.
  4. B — the Social Security Act, § 1862(a)(1)(A).
  5. B — an exclusion from payment.
  6. B — binding nationwide.
  7. B — have no NCD. That is why local determinations exist.
  8. B — only when the beneficiary participates in an approved study or registry.
  9. B — a Medicare Administrative Contractor, for its jurisdiction.
  10. C — the billing and coding article.
  11. B — the response to comments.
  12. C — anyone, with supporting evidence.
  13. C — no published criteria govern; the general standard applies. This is the normal case.
  14. B — will deny.
  15. B — the diagnosis is wrong and a supporting, documented diagnosis exists.
  16. B — coding to the policy rather than to the record.
  17. B — denies. Sixteen days, not twelve months.
  18. D — the referring physician's signature is not an ABN requirement.
  19. B — improper.
  20. A — Option 1.
  21. B — the beneficiary.
  22. B — no ABN required; GY, and GX if a voluntary notice was given.
  23. B — the practice reports GA, asserting a valid notice that is not valid, and bills on paper that shifts nothing.
  24. B — confirms medical necessity criteria as presented, but not eligibility, benefits, or that the service matched.
  25. B — never going to be covered on that record.
  26. B — correct; a diagnosis established later does not reach backward.

Exercises

Section A — The distinction

A.1 A clinical determination is a professional judgment under a standard of care. A coverage determination is a payer's decision under a contract or statute, against published criteria. A.2 Chapter 20's medically appropriate braces; a standard-of-care treatment excluded from a benefit package. A.3 An annual screening in a patient who had one last month; imaging before required conservative therapy. A.4 No. The criterion is the policy's criteria applied to the record. A.5 It does nothing — the payer already knows the physician ordered it; that is why there is a claim. A.6 Expected shape: "The record documents [the specific facts the policy requires]: [quote them]. Policy [X] requires [Y], and the record establishes it at [location]." A.7 Not medically necessary as documented. A.8 Because the other three — bundled, not a benefit, not recognized by this payer — are settled by rules that exist independently of the record. Only medical necessity is established by what the record contains.

Section B — The statutory standard

B.9 Social Security Act § 1862(a)(1)(A). B.10 As an exclusion. It matters because Medicare does not list what it pays for — it pays for covered benefits and excludes what is not reasonable and necessary. That is why coverage determinations describe WHEN a service is covered. B.11 Preventive care — a service that is neither diagnostic nor therapeutic falls outside the phrase, which is why each Medicare preventive benefit required its own statutory addition. Chapter 34. B.12 No. The content comes from coverage determinations — NCDs and LCDs.

Section C — NCDs, LCDs, and articles

C.13 A nationwide, binding CMS determination whether Medicare covers an item or service. Not numerous — a few hundred. C.14 Covered · not covered · covered with conditions. The third is most operationally important because "covered when [criteria] are met" is an instruction, and the criteria are what documentation must satisfy. C.15 Coverage conditioned on the beneficiary participating in an approved clinical study or registry. It imposes registry participation and reporting requirements, sometimes specific codes or modifiers, and they are not optional. C.16 A contractor's determination within its jurisdiction. "Jurisdictional" means the same service may be governed by different LCDs in different states. C.17 No. C.18 The operational detail: the CPT/HCPCS codes, the ICD-10-CM codes that support medical necessity, documentation requirements, and utilization expectations. C.19 The billing and coding article. C.20 Proposed LCD published → comment period → open meetings and advisory committee → final LCD with response to comments → notice period → reconsideration available. C.21 The response to comments — it states what objections were raised and why the policy did or did not change, which tells you what arguments have already been tried. C.22 Anyone may request revision of an existing LCD with supporting evidence. It is "the only door" because it is the sole mechanism in the book by which the person doing the work can change the rule rather than comply with it.

Section D — Finding the policy

D.23 Identify the payer → look for an NCD → look for an LCD in your jurisdictionread the billing and coding article → if nothing is found, the general standard applies. D.24 §22.10 — the commercial medical policy. D.25 No published criteria govern. The general reasonable-and-necessary standard applies and the record's clinical rationale supports it. This is the normal case, not a problem. D.26 Search the Medicare Coverage Database by CPT code, filtered to your state; then find the diagnosis list inside the article. D.27 Is there a different, TRUE diagnosis that IS supported and IS documented? If yes → the coding was wrong, correct it. If no → the service was never covered for this patient. D.28 Only when the alternative diagnosis is a condition the patient genuinely has and it is documented in the record. Then the original coding was incomplete.

Section E — Linkage

E.29 Diagnosis pointers (Chapter 25 §25.5). E.30 The line denies. The pointer is the linkage. E.31 The diagnosis is wrong (fixable) · the diagnosis is right and does not support the service (not fixable). E.32 Reading the record first and then finding the code is coding. Reading the covered list first and then searching the record is selecting a code because it pays. E.33 The assessment never states that conservative therapy failed. The information — six weeks of intermittent ibuprofen with partial relief — is in the history of present illness, not the assessment. Location matters because a reviewer skimming the assessment will not see it and a structured review will not find it. E.34 No. A coder may not relocate the physician's reasoning. The correct handling is a documentation improvement conversation — Chapter 38 §38.3 — one sentence in the assessment.

Section F — Frequency and ABNs

F.35 Per calendar year · per rolling 12 months · per N years · per lifetime · per episode. F.36 Calendar year: payable (new year). Twelve months: denies (16 days). F.37 Calendar year: payable. Twelve months: denies by one day. F.38 From the last date of service. Your system may not know because the service may have been performed elsewhere and paid by the same payer. F.39 No. Eligibility and benefit inquiries can sometimes answer it (Chapter 24 §24.3). F.40 In advance · specific as to service and reason · a cost estimate · a choice. F.41 Option 1 (furnish, bill Medicare) · Option 2 (furnish, do not bill) · Option 3 (do not furnish). The beneficiary selects. F.42 Option 1 preserves; Option 2 destroys; Option 1 is almost always better for the patient. F.43 A routine ABN and a blanket ABN. Structural reason: an ABN's function is to inform a beneficiary of a specific, expected noncoverage so they can decide — a form everyone signs for everything informs nobody of anything. (Also acceptable: an ABN for a statutorily excluded service, or one given after the fact.) F.44 No. GY, plus GX if a voluntary notice was given. F.45 Because the practice reports GA — asserting a valid notice that is not valid — and bills the patient on paper that shifts nothing, producing a document showing it knew a notice was required and produced a defective one. F.46 If statutorily excluded: no ABN was required, the patient may be billed, apologize for not telling them in advance. If expected denial with no valid ABN: the patient may not be billed — remove it. What determines it: whether the service was a benefit at all.

Section G — Coded wrong versus never covered

G.47 Coded wrong. Correct the claim. G.48 Never going to be covered on this record. G.49 Never going to be covered. G.50 Never going to be covered — the frequency criterion is not met. (Verify the last date of service; if the eight months is wrong, it becomes a different question.) G.51 Coded wrong. Add the pointer and resubmit. G.52 Neither, exactly — it is an authorization mismatch (Case Study 1), and the path is a post-service review, not a medical necessity appeal. G.53 Three appeals asking a payer to reach a conclusion its own published criteria forbid. The record says what it says. G.54 A phone call to the referring office · four more weeks of documented conservative therapy · a resubmission. G.55 Expected shape: "The plan requires six weeks of documented conservative therapy and the referral shows four weeks of NSAIDs plus a patient report of physical therapy. If Dr. — can document two more weeks with dates and outcome, we can resubmit and it should approve." G.56 "The MRI was denied." It does not tell them what to do.

Section H — Commercial and prior authorization

H.57 It states coverage criteria, lists codes, and frequently lists supporting diagnoses — the function of an LCD plus its billing and coding article. H.58 No. It does not confirm eligibility on the date of service, benefit availability, or that the service performed matched the service authorized. H.59 A conversation between the treating physician and a payer's physician reviewer. The coder's role: know it exists, know the deadline, get it scheduled. H.60 Because a conversation surfaces facts a form did not ask for — a physician can state a decisive clinical fact in ten seconds that nobody knew to put in writing.

Section I — The Encounter

I.61 No. (1) The patient is covered by a commercial PPO and the ABN is a Medicare instrument. (2) Even for a Medicare patient, there was no specific individualized expectation of denial — 20610 for M25.561 in a symptomatic patient is an ordinary covered service — so an ABN would have been improper. I.62 No — it was an edit denial asserting the E/M was incidental to the procedure (Chapter 21 §21.9). An ABN would not have addressed it, would not have shifted liability, and could not have been justified in advance. I.63 No. Chapter 12 §12.3: code to the highest degree of certainty established at that encounter. On March 14 no definitive diagnosis existed and no imaging had been obtained. I.64 Both are answers about what was true at the time, and in both the temptation is to reason backward from what happened later. The record is evidence of what was known when it was written.


The Encounter checkpoint — Q3 and Q5, both CLOSED

Q3 — an ABN? NO, for two independent reasons.

The patient is commercial the ABN is a Medicare instrument and has no effect on commercial liability
Even for Medicare no specific individualized expectation of denial existed → a routine ABN would have been improper

And the day-17 denial was CO-97 / N19 — an EDIT denial, not a necessity denial.

Q5 — the knee is M17.11, established by imaging obtained after March 14. And M25.561 was CORRECT for March 14, because no definitive diagnosis had been established.

Grading note: for Q3, full credit requires both reasons. Students who give only the commercial one have the right answer for an incomplete reason and will get the Medicare version wrong. For Q5, full credit requires the statement that a later diagnosis does not reach backward — a student who says the March claim should be corrected has made the error the checkpoint exists to prevent, and it is worth correcting individually.


Chapter 23 — Answer Key

Quiz (26 questions)

  1. B — a contracted rate.
  2. B — a ratio expressing resources relative to other services.
  3. B — practice expense.
  4. B — practice expense (facility and non-facility).
  5. B — a specialty society survey, a committee recommendation, and CMS acceptance or modification.
  6. B — at the national average.
  7. B — relative cost.
  8. C — one, national.
  9. B — RVU changes must not increase total spending beyond a statutory threshold.
  10. B\$96.52.
  11. B — the conversion factor came down more.
  12. B — in the summer, with a comment period.
  13. B — the practice expense RVU.
  14. B — the facility supplied the overhead and bills separately.
  15. C — on-campus outpatient hospital.
  16. B — a wrong payment on an otherwise perfect claim.
  17. Dnone.
  18. B — different percentages. The realized rate depends on service mix.
  19. B\$90.00. Payers pay the lesser of billed and allowed.
  20. B — does not increase contracted payment; inflates the gross rate's denominator and sets what a self-pay patient is asked for.
  21. B — a historical artifact adjusted by across-the-board increases, with no current method behind it.
  22. B — applying the same multiple to every code rather than raising everything by a percentage.
  23. B — self-pay discounts under a written, consistently applied policy.
  24. B — they leave no record anywhere in the billing system.
  25. B — roughly halves.
  26. Brise.

Exercises

Section A — The three numbers

A.1 \$185.00 the **charge** (a decision) · \$128.40 the allowed amount (a contract) · \$96.52 Medicare's allowed amount (an equation). A.2 The Medicare figure. You need the code's RVUs, the locality GPCIs, and the conversion factor — all free. A.3 The contract. A.4 The charge. A.5 (1) You cannot evaluate a contract you cannot price. (2) You cannot detect an underpayment without knowing what was owed. (3) The fee schedule is the reference every other number is described against. A.6 The gap between "we have a contract" and "we know what our contract pays."

Section B — RVUs and the formula

B.7 Work — physician time, skill, effort, judgment, stress. Practice expense — overhead. Malpractice — liability. B.8 Practice expense, because the answer depends on who supplied the overhead. B.9 Malpractice. B.10 A productivity measure; physician compensation is frequently expressed in dollars per work RVU. B.11 A code is created → a specialty society surveys its members → a multispecialty committee recommends values to CMS → CMS accepts, modifies, or rejects → the value appears in the proposed then final rule → periodic review of potentially misvalued codes. B.12 Because there is no instrument that measures physician effort — the values express how a code's work compares to other codes', as assessed through survey and committee. What follows: expecting them to behave like measurements will mislead you. B.13 A formal category of codes identified for revaluation. Their RVUs can go down. B.14 (1.92 × 1.000) + (0.89 × 1.008) + (0.13 × 1.005) = 1.92000 + 0.89712 + 0.13065 = 2.94777; × \$32.7442 = **\$96.52. B.15 (1.92 × 1.050) + (0.89 × 1.120) + (0.13 × 1.400) = 2.01600 + 0.99680 + 0.18200 = 3.19480; × 32.7442 = \$104.61.** **Malpractice moved most in percentage terms (+40%)** and least in dollars — which is the point about the smallest component being the most variable. **B.16** 2.94777 × 31.0000 = **\$91.38. The conversion factor fell 5.33%; the payment fell 5.33%. B.17 Because the change is proportional and universal — one number moves every payment in the fee schedule by the same percentage. There is no code-level negotiation; there is one lever. B.18 Budget neutrality.** If other codes were revalued upward, the conversion factor is adjusted downward to offset — and a 4% RVU increase against a larger conversion factor decrease produces a net decrease.

Section C — GPCIs, conversion factor, rulemaking

C.19 The locality is at the national average. C.20 Cost. It matters because the adjustment does not claim the service is worth more in one place — it claims it costs more to provide, which is a defensible empirical claim rather than a value judgment. C.21 One. C.22 That RVU changes not increase total spending beyond a statutory threshold. It makes the pool essentially fixed, so increases must be offset. C.23 A rule can raise the RVUs for a set of codes and reduce the conversion factor to maintain budget neutrality. Both statements describe the same rule. C.24 Proposed rule (summer, with comment period) → comments close → final rule (~November) with responses to comments → effective January 1. C.25 The responses to comments. C.26 LCD development and NCD reconsideration (Chapter 22 §22.3–§22.4). All three are open, on a calendar, and almost nobody in the field participates.

Section D — Site of service

D.27 The practice expense RVU. D.28 Because the facility supplied the overhead and bills separately for it. D.29 No — it moves. The facility bills for its own costs on the facility claim. D.30 The place of service code. D.31 Office 11 · inpatient hospital 21 · on-campus outpatient hospital 22 · emergency department 23 · ambulatory surgical center 24. D.32 The place of service changes 11 → 22, and the physician's payment drops because the facility now bills separately. D.33 Office→facility is an underpayment — accrues silently, expires under timely filing. Facility→office is an overpayment — Chapter 5 §5.8's sixty-day rule attaches on identification. D.34 Compare the place of service on your claims against where the service was actually rendered, for one month. (And, for organizations generating both claims: a facility claim and a non-facility place of service for the same encounter cannot both be right.)

Section E — Building and comparing

E.35 [(work × work GPCI) + (PE × PE GPCI) + (MP × MP GPCI)] × conversion factor. E.36 99214 133.03% · 20610 124.21% · J1030 115.44% · 36415 100.00%. E.37 216.28 ÷ 168.24 = 128.55%. E.38 The blended rate is 128.55% and not one line is at 128.55%. E.39 No. The practice doing more E/M earns above 128.55%; the one doing more laboratory earns below it. The same contract is a different contract for a different practice. E.40 Price your own top twenty codes by volume against Medicare, compute the percentage for each, weight by your volume. An afternoon in a spreadsheet.

Section F — Charges

F.41 A charge below the allowed amount caps the payment at the charge. F.42 \$90.00. F.43 No. The patient's responsibility is computed from the allowed amount, not the charge. A low charge only reduces what the payer pays — a transfer from the practice to the insurer. F.44 No. It inflates the gross collection rate's denominator · it sets what a self-pay or out-of-network patient is asked for · and it becomes the number quoted in public discussions of health care prices. F.45 Nobody at the practice can derive it. A historical artifact from a fee-schedule reference product, adjusted since by across-the-board increases, never re-derived. F.46 185.00/96.52 = 191.67%; 150.00/63.28 = 237.04%; 18.00/5.44 = 330.88%; 14.00/3.00 = 466.67%. No consistent multiple exists. F.47 It sits above every contracted rate, so it caps nothing — and it is doing that by accident. F.48 Price your Medicare schedule → find your highest contracted rate per code → set one multiple of Medicare that clears it → apply the same multiple to every code → review annually → write it down with a date and an owner. F.49 Step 4. Across-the-board percentage increases preserve and multiply every existing distortion; a single consistent multiple re-derived from the fee schedule flattens them in one pass. F.50 The same service carries the same charge regardless of payer, with payer differences living in the allowed amount. F.51 Self-pay discounts · financial assistance · prompt-pay discounts. Condition: a written, consistently applied policy. F.52 Routinely waiving patient cost-sharing · charging an uninsured patient the full chargemaster amount while every payer pays a fraction.

Section G — Chargemaster and charge capture

G.53 Scale (tens of thousands versus hundreds of lines) · it includes items, not just services · it has no single owner. G.54 Terminated codes still in the file · dead items · across-the-board adjustments · lines that were never payable. A4550 illustrates the fourth. G.55 A machine-readable file of standard charges — gross charges, payer-specific negotiated rates, discounted cash prices, and de-identified minimum and maximum negotiated charges — plus a consumer display of shoppable services. G.56 Pricing other organizations' contracts against Medicare, which was not previously possible. G.57 The bill. Responding mechanisms: financial assistance policies · discounted cash prices · good faith estimates. G.58 Never entered · never interfaced between systems · entered after the cycle closed · entered against a closed or wrong account · removed by an edit or rule. G.59 Because it leaves no claim, no denial, no queue item, and no report line — you cannot reconcile against a record that does not exist. Detection must come from outside the billing system. G.60 Schedule → charges · signed notes → charges · clinical logs → charges · supply and pharmacy usage → charges. The second is one join and should be built first.

Section H — Collection rates

H.61 Gross = payments ÷ charges. Net = payments ÷ what you were entitled to collect after contractual adjustments. H.62 The gross rate roughly halves; the net rate is unchanged; performance did not change at all. H.63 It raises it. The underpaid amount is written off as a contractual adjustment, leaving the denominator — so the ratio improves as the problem worsens. H.64 Lost charges · underpayments written off as contractual · undercoding. The ratio measures how well you convert entitled revenue into received revenue. The three measurements that answer what it cannot: charge capture reconciliation (§23.9) · coding audit (Ch. 35) · underpayment comparison (Ch. 28 §28.8).


The Encounter checkpoint — Q6, CLOSED

Why did Northgate charge \$185.00 for a 99214?

Nobody at the practice can derive it.

(Constructed history.) The charge originated from a fee-schedule reference product years ago and has been increased by across-the-board percentage adjustments since. No current method produces \$185.00.

Not a multiple of Medicare:

Line Charge Medicare Ratio
99214 185.00 96.52 191.67%
20610 150.00 63.28 237.04%
J1030 18.00 5.44 330.88%
36415 14.00 3.00 466.67%

What it does correctly, by accident: \$185.00 is **above Northfield's \$128.40 and Medicare's \$96.52, so it caps nothing** — which is the charge's one essential function.

Grading note: full credit requires the honest answer and the observation that the charge is nonetheless performing its function. Students who answer "it was set at some multiple of Medicare" have not done the arithmetic; the four ratios disprove it and computing them is the exercise.

Do not accept "the practice charges high to get more money." §23.7 disposes of this: a higher charge produces no additional payment from any contracted payer. A student who believes otherwise has missed the one rule in the section.


Chapter 24 — Answer Key

Quiz (26 questions)

  1. B — at registration.
  2. C — roughly 90 to 1.
  3. C — no denial at all; a patient who never receives a bill and an account that ages.
  4. C — "Has anything changed?"
  5. B — January. Plan years turn over, employers change carriers, deductibles reset.
  6. B — a patient safety matter, because medical identity theft contaminates the victim's record.
  7. B — the eligibility and benefit inquiry.
  8. B — 278.
  9. B — reflects claims the payer has processed, and therefore lags.
  10. B — ask the patient for too much.
  11. B — the payer has no other coverage on file.
  12. C — at scheduling, 48–72 hours before, and on the day of service.
  13. C — at scheduling.
  14. B — who the patient sees.
  15. B — a non-binding advance review.
  16. C — the patient's copayment amount is not part of the authorization scope.
  17. B — a number, not a record.
  18. B — it reflects the payer's records; the questionnaire asks the patient.
  19. B — an overpayment, to which the sixty-day rule attaches on identification.
  20. C — workers' compensation.
  21. C — routinely waiving patient cost-sharing.
  22. B — method of payment, stating the amount as a fact.
  23. B — the allowed amount.
  24. C\$84.88 (78.60 + 6.28, the full allowed amount, with no deductible met).
  25. B — \$47.58.
  26. C — asking what the visit was for.

Exercises

Section A — The cost of an error

A.1 Registration (ask again, retype — no claim exists) · scrubber (claim held, corrected, released) · clearinghouse (a rejection; a report is worked, corrected, resubmitted — and only if somebody reads the report) · adjudication (a denial; work queue, research, correction, resubmission, with the timely filing clock running) · after timely filing. A.2 0.5 · 3 · 12 · 30–60 (commonly), across several touches. A.3 Roughly 90 to 1. In minutes rather than dollars because minutes are what a staffing decision is made in, and because whatever the loaded rate is, the same number multiplies both sides — the ratio survives it. A.4 The entire allowed amount. A.5 It would need a fully loaded labor rate, which Chapter 31 §31.7 publishes. Chapter 40 owns the conversion for Account 10-4471 specifically, and this chapter deliberately does not perform it. A.6 The saving is visible and the cost is not. The saving appears in the front-end budget where it is measured; the cost appears as denial volume in a different department, overtime in a third, and lost revenue in a category that appears on no staffing report at all.

Section B — Registration fields

B.7 She may be "Elizabeth" on the policy → subscriber not matched. Ask: "How does your name appear on your insurance card?" B.8 June 31 does not exist and the transposition means the patient does not exist to the payer → front-end rejection. Read the date back. B.9 Cards get reissued and plans change identifiers on renewal. Copy from the card in hand. B.10 Many adults are covered as a dependent on a spouse's policy → the claim goes to a policy the patient is not on. Ask who holds the policy. B.11 A payer may have dozens of products; the claim is routed on a guess. Capture the group number and the plan name from the card. B.12 See B.15. Read the street address back. B.13 Workers' compensation is likely primary → billing the health plan is billing the wrong payer. Ask the accident/injury questions. B.14 The record is complete for a situation that no longer exists. Ask the scripted question. B.15 None. It produces a patient who never receives a bill, an account that ages, and eventually a collection action against someone who was never told — Case Study 1. B.16 O/0 · I/1 · S/5 · B/8. B.17 January — plan years turn over, employers change carriers, deductibles reset. B.18 "Has anything changed with your insurance, address, or phone since we saw you?" About ten seconds.

Section C — Identity

C.19 Verifying that the person present is the person on the coverage. C.20 A claim for services the coverage holder did not receive (a billing dispute) · permanent contamination of the victim's medical record · a patient harmed by information that is not theirs. C.21 The record contamination — unwinding it is difficult, sometimes impossible, and the victim frequently discovers it during care they need. C.22 A question, not an accusation. Names change, cards are old, and most mismatches are ordinary — but a practice with no identity step has no way to notice the one that is not.

Section D — Eligibility

D.23 270 = the eligibility and benefit inquiry; 271 = the response. D.24 Active status · plan and group · copayment · deductible and amount met · coinsurance · other coverage on file · sometimes referral/authorization requirements. D.25 That coverage will still exist on the date of service · a current deductible · whether the service is medically necessary · anything the payer chose not to populate. D.26 Because it reflects claims the payer has processed, not claims incurred. It errs toward asking the patient for too much. D.27 That the payer has no other coverage on file — a statement about the payer's records. D.28 No. Chapter 22 requires the governing coverage policy and its supporting diagnosis list. D.29 At scheduling · 48–72 hours before · day of service. D.30 Scheduling: no coverage, wrong payer, non-contracted plan, an authorization requirement. 48–72 hours: terminations, plan changes, a deductible figure fresh enough to estimate from. Day of: yesterday's termination. D.31 At scheduling — the only point the encounter can still be rearranged. D.32 Batch submits the whole schedule and returns a file — used for the pre-visit sweep. Real time answers one patient in seconds — used at the desk. D.33 It is early enough that a problem can be addressed and late enough that the answer is still true. D.34 As of what date? · What is this response silent about? · What did the payer say versus what did my system display?

Section E — Referrals, authorizations, and who obtains them

E.35 A PCP's direction of a patient to a specialist. Generally the PCP's to issue. E.36 A payer's advance approval of a specific service. About what. E.37 Generally a synonym for prior authorization; sometimes a distinct admission notification. Ask what it means in that payer's contract. E.38 A non-binding advance review of coverage. Not binding. E.39 Expected shape: "They're two separate things and a visit can need both. The referral is your primary doctor saying it's okay for you to see us — that's about who. The authorization is your insurance approving the specific procedure — that's about what. We have the first one. I'm checking whether the plan requires the second, and I'll call you back today either way." E.40 Authorization number · date obtained · issuing person or system · approved codes · approved date range · approved units/visits · approved facility · approved rendering provider. E.41 Codes · date range · facility · rendering provider — the four that drifted. E.42 Because the payer's next question after "we have an authorization" is for what, on what date, at what site, by whomand a practice holding only a number cannot answer. E.43 Authorizations obtained for one thing and used for another · authorizations that had expired · authorization numbers entered that were never obtained — a false statement on a claim. E.44 No universal answer — it varies by payer and market. E.45 The party who knows the codes is best placed · the party who does not get paid without it has the incentive · whoever obtains it must communicate the scope. E.46 The scope — date range, units, codes, facility, provider — to whoever bills it.

Section F — MSP and cost-sharing

F.47 Whether another payer is primary to Medicare. F.48 Group health through current employment (own or spouse's, subject to employer-size rules) · work-related injury → workers' compensation · accident → auto, no-fault, or liability · black lung · VA-authorized services · the ESRD coordination period. F.49 Because it reflects the payer's records, which are frequently wrong; the questionnaire asks the patient. F.50 It is an overpayment; Chapter 5 §5.8's sixty-day rule attaches on identification, and Chapter 31 §31.9 covers the recoupment. F.51 Workers' compensation is primary. The fall occurred at work, and workers' compensation is generally primary for treatment of a work-related injury — that question comes before the Medicare-versus-group-health analysis entirely. F.52 Two. The work-related injury, and independently the large-employer group health plan covering her through a spouse's current employment. F.53 Collect copayments, coinsurance, and deductibles at the time of service · offer payment plans · offer financial assistance under a written policy · offer prompt-pay or self-pay discounts under a written policy. F.54 Routinely waive cost-sharing. The word is "routinely" — an individualized hardship determination under a written policy is a different thing, and the difference is a written policy and a record.

Section G — Asking, clearing, estimating

G.55 "Your copay for today is \$30.00. How would you like to take care of that?"* — it states the amount as a fact, does not ask permission, and **the question is about method rather than about whether.** **G.56** Asking within earshot of others · insisting when someone says they cannot · quoting a number you cannot stand behind. **G.57** Stop pressing; **offer a payment plan (Chapter 32 §32.7) or financial assistance (§32.8).** **G.58** Identity/demographics · coverage for the date of service · coordination of benefits · referral · authorization with scope · medical necessity screening · estimate · patient informed · collection attempted or arrangement made. **G.59** **Medical necessity screening.** It catches a Chapter 22 §22.11 problem **before** the service rather than after, applying Chapter 22's coverage-policy apparatus in advance. **G.60** 78.60 × 0.20 = **\$15.72; 6.28 × 0.20 = \$1.26**; total **\$16.98. G.61 \$84.88 — the full allowed amount, since nothing has been applied to the deductible. A five-fold difference. G.62 Expected shape: "That assumes your deductible is met, which our check this morning says it is. If a claim from another provider is still processing, this could be higher, and the statement will show you why." Grade for naming the specific thing that could move*, not for generic hedging.

Section H — Measurement

H.63 Clean claim rate · front-end denial rate · eligibility verification rate for the date of service · authorization capture rate with scope · point-of-service collection rate. H.64 Front-end denial rate. H.65 Of encounters that generated a front-end denial, what percentage had a completed clearance checklist? High → the checklist is missing an item (the process ran and the claim denied anyway). Low → the checklist is not being completed (staffing, workload, or training). H.66 It predicts that a front-end problem will be experienced as a back-end volume problem, and the organization will respond by adding back-end staff — which works and costs roughly ninety times as much staff time per instance. The fix is routing the existing report: front-end denials, classified by cause, sent weekly to the people who cause them, with accounts attached, as feedback rather than discipline.

Section I — The Encounter

I.67 Verified eligibility for the date of service · asked whether anything had changed · correctly determined no referral required · correctly determined no authorization required for an established-patient office visit · collected the \$30.00 copay. **I.68** **Nothing on the schedule said a procedure might happen**, so no authorization screening for 20610 was possible. **Not an error** — a question nobody had written down. **I.69** \$30.00 copay on the office visit, plus 20% coinsurance on 20610 (\$15.72), J1030 (\$1.26), and 36415 (\$0.60) = **\$47.58, leaving \$17.58 billed after the fact. I.70 Ask what the visit is for · screen the likely procedure against the authorization list · frame the copay as a copay. The third** would have made the day-70 statement expected.


The Encounter checkpoint — §24.11

Rewind Account 10-4471 to check-in, Tuesday March 14.

Done right eligibility verified for the date of service · "anything changed?" asked · no referral required (correctly determined) · no authorization required (correctly determined) · \$30.00 copay collected
Missed nothing on the schedule said a procedure might happen
Consequence \$30.00 collected against **\$47.58 actual → \$17.58** billed → statement day 70

And the honest note: 20610 did not require prior authorization under Northfield Mutual's policy. That is luck, not process — nobody checked.

Grading note: full credit requires students to say the front desk did not make an error. A student who answers "they should have collected \$47.58" has misunderstood the section — nobody could have known the injection would happen. The miss is a question that was not asked, and the chapter is explicit about the distinction.


Chapter 25 — Answer Key

Quiz (26 questions)

  1. B — 837P.
  2. B — the National Uniform Claim Committee.
  3. B — the scanner is calibrated not to see the form's own lines.
  4. B — item 4.
  5. B — employment, an auto accident, or another accident.
  6. B — asserts that a signed authorization exists and is current.
  7. C — 17b.
  8. D — twelve.
  9. B — A through L.
  10. B — a duplicate.
  11. A — the prior authorization number or the CLIA number.
  12. B — six.
  13. C — four.
  14. B — four.
  15. C — the practice's charge.
  16. B — supplemental information including NDC data for drug lines.
  17. B — denies.
  18. B — an individual, the person who performed the service.
  19. B — an organization.
  20. C — identity, and nothing else.
  21. B — the supervising physician's NPI, paid at 100%.
  22. B — the service was performed somewhere other than the billing address.
  23. B — accept the allowed amount as payment in full.
  24. B — how that payer requires the standard transaction to be populated.
  25. B — blank, because nobody referred her.
  26. B — B, the diabetes.

Exercises

Section A — What the form is

A.1 The professional claim; the 837P. A.2 The NUCC; the reference instruction manual, free. A.3 (1) The electronic claim carries the same data in a different container, and rejection messages name items. (2) It is the industry's shared vocabulary — payers, clearinghouses, and vendors describe problems by item number. A.4 An item names the form; a loop or segment names the 837P. A.5 Because a paper claim is processed by optical character recognition, and the scanner is calibrated not to see the red lines — it reads what is in the boxes. A.6 Handwriting · anything outside its box · highlighting · correction fluid (also acceptable: staples through the data area). They all create marks the scanner misreads. A.7 The rigid field positions and the fixed six service lines — both are consequences of machine reading rather than design choices. A.8 Because items changed between versions, and payer instructions reference specific versions.

Section B — Items 1–13

B.9 1a. B.10 2. B.11 4. B.12 6. B.13 10a–10c. B.14 9. B.15 11d. B.16 Item 2 = the child; item 4 = the parent; item 6 = CHILD. B.17 That a signed and current authorization exists. Three others: GA (a valid ABN is on file, Ch. 22) · JW (this much was discarded, Ch. 20) · KX (the documentation supports necessity, Ch. 19). B.18 Either there is no other coverage, or nobody asked. It matters because the secondary claim, the coordination-of-benefits information, and whether a balance is genuinely the patient's all depend on which it is.

Section C — Items 14–23

C.19 17b. C.20 21. C.21 19. C.22 22. C.23 23. C.24 20. C.25 A qualifier saying what the date is — onset, injury, or last menstrual period. The same date means different things under different qualifiers, and a date without one is a number with no meaning. C.26 Twelve, labeled A through L, plus the ICD indicator. C.27 A duplicate — and the original problem is still unfixed. C.28 The prior authorization number or the CLIA certificate number. What you are billing determines which; laboratory claims need the CLIA number (Ch. 19 §19.6).

Section D — Item 24

D.29 24B. D.30 24D. D.31 24E. D.32 24F. D.33 24G. D.34 24I/24J. D.35 Six. More services become multiple claims — and Ch. 18 §18.8's sequencing means the highest-valued procedure belongs on the first line of the first claim. D.36 Four. For a fifth, report modifier 99 and put the additional modifiers in item 19. D.37 The charge. It matters because payers pay the lesser of billed and allowed (Ch. 23 §23.7) — a charge below the allowed amount caps the payment. D.38 NDC data for drug lines · narrative descriptions for unlisted codes · supplemental provider identifiers · anesthesia minutes (any three).

Section E — Pointers

E.39 Twelve in item 21; four per line. The asymmetry means a claim can carry diagnoses that support no line and lines that cannot reach every diagnosis — and coders reflexively point everything at everything. E.40 Letters in the 02/12 version; older habits produce numbers. E.41 Point letters · point only what supports that line · sequence matters · a line pointed at a non-supporting diagnosis denies. E.42 The line denies, even though a supporting diagnosis is on the claim (Ch. 22 §22.6). E.43 Office visit → A B C (if the note supports all three being addressed — Ch. 15 §15.5). Spirometry → A. Venipuncture → C. E.44 It is three false statements instead of one true one. "It denies" is not the primary objection because the claim now asserts clinical relationships that do not exist — and the pointer is the medical necessity linkage. E.45 The blood was drawn for the hemoglobin A1c, a diabetes test. Pointing it at the knee would assert that a venipuncture treats knee pain. E.46 A pointer is a claim about why a service was performed — if you would not say the sentence out loud, do not point the line.

Section F — Providers and identifiers

F.47 Rendering (24I/24J) · billing (33, 33a, 33b) · service facility (32, 32a, 32b). F.48 Rendering is a person; billing gets paid. F.49 When the service was performed somewhere other than the billing address. F.50 Type 1 = an individual. Type 2 = an organization. F.51 Type 1 in the rendering field (24J); Type 2 in the billing field (33a). F.52 Identity. Not enrollment · not participation · not eligibility to be paid. F.53 Specialty. Ch. 15 §15.2's new-versus-established test and Ch. 16 §16.2's initial-versus-subsequent test both turn on specialty as the payer has it recorded. F.54 The supervising physician's, paid at 100%. F.55 That a physician performed or supervised the service under conditions that did not exist. An overpayment. F.56 That the provider accepts the allowed amount as payment in full. In network it reports a fact (the contract already requires it); out of network it is a decision.

Section G — Rejections

G.57 A rejected claim was never adjudicated — it did not reach the payer's processing. A denial is a decision the payer made about a claim it processed. G.58 Patient not found · subscriber/relationship · referring provider · diagnosis problems · pointer problems · billing provider · missing required field. G.59 Six of seven. That the rejection report is Chapter 24's argument arriving in a different form. G.60 Blank · wrong person · not enrolled with the payer · name/NPI mismatch. The third cannot be fixed by billing — it is a credentialing matter, and resubmitting will not change it. G.61 A payer's published document stating how it requires the standard transaction populated. The NUCC manual says what an item is for; the companion guide says what this payer requires in it. G.62 Bilateral reporting conventions (Ch. 14 §14.8) and proprietary edit policies (Ch. 21 §21.11).

Section H — Read a claim you did not build

H.63 Items 4 / 9 / 11d. The claim says other coverage exists and supplies no other insured. Either 11d is wrong or 9 and 4 are incomplete. H.64 Item 17. Nobody referred the patient to themselves — a data-entry default that introduces a rejection cause where none existed. H.65 Items 24B and 32. Place of service 22 with a blank item 32 asserts a hospital outpatient service performed at the billing address. Ch. 23's Case Study 1 — and this line pays wrong without denying. H.66 Item 24G. Two units of a timed therapy code requires 23 minutes of total timed services (Ch. 19 §19.11), and the claim asserts it. H.67 Item 27. Non-assignment from a contracted group misrepresents the practice's own agreement. H.68 They will find nothing — the codes are fine. They will miss four of the five errors, all of them non-clinical fields. The lesson: on a denied claim, the instinct is to check the codes, and the codes are usually fine.

Section I — The Encounter

I.69 ICD indicator 0 (ICD-10-CM). A = M25.561 · B = E11.9 · C = I10 · D = E78.5. I.70 Line 1 (99214-25) → A B C D, because the E/M addressed all four problems, which is what made it separately identifiable. Line 2 (20610-RT) → A, the knee. Line 3 (J1030) → A, the drug went into the knee. Line 4 (36415) → B, the blood was drawn for the A1c. I.71 Item 17 blank — the performing physician is the patient's own PCP; nobody referred her. Item 20 "no" — the reference laboratory bills 83036 and 80061 on its own claim (Ch. 19 §19.12). Item 29 \$30.00 — the copay collected at check-in (Ch. 24 §24.11); omitting it would ask the payer for money already collected. I.72 The lidocaine (Ch. 17 §17.1's package · Ch. 20 §20.10's usual supplies · Ch. 21 §21.6's standards of practice — three independent reasons) · 83036 and 80061 (Ch. 19 §19.12) · 99000 (Ch. 19 §19.12 — Northgate has never asked whether it is payable).


The Encounter checkpoint — §25.10

Account 10-4471's CMS-1500, built from twenty-four chapters of decisions.

Field Value Decided by
21 A M25.561 · B E11.9 · C I10 · D E78.5, indicator 0 Chs. 7–12
24B 11 on every line Ch. 23 §23.5
24D line 1 99214 + 25 Ch. 15 §15.13 · Ch. 14 §14.4 (Q1)
24E A B C D / A / A / B §25.5
24F the charge Ch. 23 §23.7 (Q6)
24G 1 on J1030 Ch. 20 §20.3
17 blank nobody referred her
20 no Ch. 19 §19.12
28 / 29 \$367.00 / \$30.00 Ch. 6 §6.1 · Ch. 24 §24.11

Grading note: full credit on I.70 requires a justifying sentence per line, not just the letters. A student who gives "A B C D / A / A / B" has memorized the answer; a student who can say why line 4 points at B has understood the section.

And do not accept "line 1 points at all four because there are four diagnoses." It points at all four because the E/M addressed all four, which is Ch. 15's problems element and Ch. 14's modifier 25 evidence appearing as a claim field. If the note had addressed only the knee, line 1 would point at A alone — and modifier 25 would be unsupportable (Ch. 15 §15.10, Reading 4).


Chapter 26 — Answer Key

Quiz (26 questions)

  1. B — CMS-1450.
  2. B — 837I.
  3. B — the National Uniform Billing Committee.
  4. C — form locators.
  5. B — hospital, outpatient.
  6. C — a replacement of a prior claim.
  7. B — a duplicate.
  8. B — the department or cost center that provided it.
  9. C — emergency room.
  10. B — drugs requiring detailed coding, with a HCPCS code and units.
  11. B — generally not required on most lines.
  12. B — the payment system; the DRG derives from diagnoses and procedures.
  13. C — occurrence span codes.
  14. D — a value code. (A count is an amount.)
  15. B — an inpatient admission changed to outpatient before discharge.
  16. B — where the patient went at the end of the stay.
  17. B — a per-diem amount rather than the full DRG.
  18. B — a mismatch between two fields that must agree.
  19. B — the patient control number, which the payer returns on the remittance.
  20. B — chiefly responsible for the encounter, established after study.
  21. B — non-covered charges.
  22. C — the attending provider.
  23. B — bundled into the inpatient claim in defined circumstances.
  24. B — compatible with the rule; it was correct as a standalone claim and should not have been one.
  25. B — falls, because the practice expense moved to the facility.
  26. C — nearly doubles.

Exercises

Section A — Why institutions bill differently

A.1 UB-04 and CMS-1450. The same form. A.2 837I; the professional counterpart is the 837P. A.3 The NUBC — National Uniform Billing Committee. It publishes the Official UB-04 Data Specifications Manual, and no, it is not free — it is a subscription publication, unlike the NUCC's manual for the CMS-1500. A.4 Form locators (FL). A.5 A physician sells professional work — evaluation, judgment, a procedure performed. An institution sells a place with things in it: a staffed unit, an operating room, a pharmacy, nursing hours, a bed for the night. A.6 (1) The unit of billing is frequently the STAY rather than the service — an inpatient claim can list forty charges and be paid one DRG amount. (2) Charges are grouped by DEPARTMENT, hence revenue codes. (3) Much of what the payer needs to know is not a service at all, hence the circumstance codes. A.7 Two claims and two patient balances — Ch. 16 §16.1. A.8 Was the patient admitted from the emergency department · did they leave against medical advice · was this a readmission · what covered days remain (any three).

Section B — The form locators

B.9 FL 1–13 who and where · FL 14–41 the circumstances · FL 42–49 the charges · FL 50–65 the payers · FL 66–75 the diagnoses and procedures · FL 76–81 the providers and the rest. B.10 FL 4 (type of bill — what kind of claim this is) and FL 6 (statement covers period — what dates it covers). B.11 FL 42–49, the charge block — twenty-two lines per page, and a claim can run to multiple pages. The final page carries FL 47's total and revenue code 0001. B.12 FL 3a is the PATIENT CONTROL NUMBER, the facility's identifier for this encounter or account. FL 3b is the MEDICAL RECORD NUMBER, its identifier for this person. A patient with eleven admissions has eleven control numbers and one medical record number. B.13 Autoposting breaks — the payer returns FL 3a on the remittance, and a medical record number in that field returns an identifier that does not identify an account. Ch. 28 §28.7's process depends on it. B.14 FL 67 principal — what was chiefly responsible, established after study. FL 69 admitting — what was suspected at admission. FL 70 reason for visit — why the patient presented, on outpatient claims. B.15 That nobody is populating them thoughtfully. A hospital's admissions do not routinely confirm the initial impression — chest pain becoming acute myocardial infarction is the normal case, and the disagreement is the story of the admission. B.16 Charges the payer is not being asked to pay. Omitting a known non-covered charge is worse because it removes the payer's record of it — and on the patient side, it removes the basis for billing the patient at all.

Section C — Type of bill

C.17 0 leading zero · 1 hospital · 3 outpatient · 1 admit through discharge. C.18 0 · 1 hospital · 1 inpatient Part A · 1 admit through discharge. C.19 2 skilled nursing · 3 home health · 7 clinic (including RHCs and FQHCs) · 8 special facility (including hospices and ambulatory surgical centers). C.20 1 inpatient Part A; 3 outpatient. C.21 1 admit through discharge · 7 replacement · 8 void/cancel. C.22 A sequence of interim claims — first, continuing, last. They must be submitted in order and must not overlap. C.23 A duplicate, not a correction — and the original problem is still unfixed. C.24 A blank item 22 (the resubmission code) on a professional resubmission. Same failure, different form. C.25 0131. C.26 0118.

Section D — Revenue codes

D.27 A revenue code says WHERE — the department or cost center. A HCPCS code says WHAT — the service or item. D.28 0250 pharmacy · 0270 medical/surgical supplies · 0300 laboratory · 0320 diagnostic radiology · 0450 emergency room · 0636 drugs requiring detailed coding. D.29 The TOTAL line, appearing once, on the last page. D.30 The ACCOMMODATION — private, semi-private, ward — and the LEVEL OF CARE — general medical/surgical, intensive care, coronary care, nursery. D.31 Lines under more than one accommodation code, with the units on each showing how many days at that level. D.32 FL 48, non-covered charges — generally a non-covered differential, and one of the few places a facility bills a patient for something the payer correctly declined. D.33 Add the units across the accommodation lines; they should reconcile to the statement-covers period, allowing for the discharge-day convention. When they do not, something about the dates or the transfers is wrong. D.34 Because 0636 identifies a specific drug in a specific quantity where 0250 is pharmacy generally. 0636 requires a HCPCS code and units on the same line — and the units are Ch. 20 §20.3's arithmetic, dose administered ÷ the descriptor's dosage. D.35 0320, diagnostic radiology — not 0450. The revenue code follows the DEPARTMENT that performed the service, not the department the patient arrived in. D.36 The chargemaster. (1) A terminated HCPCS code on a chargemaster line, which denies on every claim carrying it. (2) A revenue code the payer does not accept for that type of bill. (3) A line whose revenue code requires a HCPCS with none mapped. None is a coding decision; all three are maintenance problems wearing a claim's clothes.

Section E — Circumstance codes

E.37 Condition (FL 18–28) — a circumstance that is true. Occurrence (FL 31–34) — a date something happened. Occurrence span (FL 35–36) — a date range. Value (FL 39–41) — an amount. E.38 Fact · date · range · amount. E.39 Because a CMS-1500 describes services performed on a person, and everything it needs fits in a code, a modifier, a date, and a pointer. A UB-04 describes an EPISODE inside an institution, and an episode started somewhere, lasted a period, was interrupted, ended in a disposition, and consumed benefit days. None of that is a procedure. E.40 Date of injury → OCCURRENCE · four covered days → VALUE · a qualifying stay March 2 to March 5 → OCCURRENCE SPAN · an inpatient admission changed to outpatient before discharge → CONDITION (Condition Code 44) · the Part A deductible amount → VALUE. E.41 Covered days, because "days" feels like a span. It is not a range with a start and an end — it is a NUMBER, and the families are distinguished by shape, not subject matter. E.42 The report that an inpatient admission was changed to outpatient before discharge. A CONDITION code. E.43 OCCURRENCE SPAN. The field matters because Ch. 16 §16.3's three-day qualifying-stay requirement arrives on the claim as this field — the benefit depends on it. E.44 Registration (admission source and type) · the unit (discharge status) · utilization review (Condition Code 44) · the business office (value codes for benefit amounts).

Section F — Discharge status and providers

F.45 Where the patient went at the end of the stay. F.46 01 · 02 · 03 · 07 · 20 · 30. F.47 A hospital that transfers a patient rather than discharging them may be paid a per-diem amount rather than the full DRG — under defined circumstances, for defined DRGs, when the length of stay is below the geometric mean. F.48 01 on an actual transfer OVERSTATES the payment; a transfer status on an actual discharge UNDERSTATES it. Both are wrong on a claim that is otherwise perfect, and neither denies. F.49 Because 30 means "still a patient," which is only true on an interim claim. It must agree with FL 4's frequency digit. F.50 01 where the record documents a transfer · 30 on a non-interim claim · a facility whose distribution of discharge statuses differs markedly from comparable facilities, which is measurable from claims data with no chart. F.51 Reconcile FL 17 against the discharge summary, on a sample, on a schedule. A coder can run it, and it is one of the few facility-side checks nobody is running. F.52 FL 76 attending — primary responsibility during the stay. FL 77 operating — the surgeon. FL 78/79 other — with a qualifier stating the role. F.53 FL 77, when a surgical procedure is reported in FL 74. A claim with a procedure and a blank FL 77 is internally inconsistent. F.54 None of them. The institution bills — FL 1's name and address and FL 56's NPI carry that. Ch. 25's rendering-versus-billing confusion produces the same denials here.

Section G — Dates and windows

G.55 The from and through dates for the services on this claim. (1) Every service date must fall within it. (2) Interim claims must not overlap. (3) It is not the same as the stay on an outpatient claim — a series claim covers a month of visits, correctly. G.56 They overlap on March 10, double-counting a day. The payer will reject or recoup it. G.57 Outpatient services furnished by a hospital — or a wholly owned or operated entity — within three days before an inpatient admission are, in defined circumstances, bundled into the inpatient claim rather than billed separately. G.58 One day, for psychiatric, rehabilitation, long-term care, and certain other excluded facilities. G.59 Diagnostic services in the window are generally bundled. Non-diagnostic services are bundled when they are RELATED to the admission, with an attestation mechanism for stating that they were not. G.60 It does not work, and it is not actually a disagreement. The claim was correct as a standalone claim; the rule says it should not have been a standalone claim. Those two statements are compatible.

Section H — The Encounter as a facility claim

H.61 Very little, and that is the point. Same four codes — 99214-25, 20610-RT, J1030, 36415. Place of service becomes 22 instead of 11, and the professional payment drops, because the practice expense RVU is now the facility value. H.62 A second claim — a UB-04. Type of bill 0131. H.63 0510 clinic (the facility charge) · 0636 drugs/detail carrying J1030 with units · 0300 laboratory (the venipuncture). Plus 0001, the total line. H.64 M25.561, the right knee pain — the reason for the encounter. The other three (E11.9, I10, E78.5) follow as other diagnoses. H.65 Total \$361.00** *(148.60 + 212.40)*, which is **1.67×** the independent \$216.28. Patient \$84.52** *(\$30.00 copay + 20% of \$60.20 = \$42.04, plus 20% of \$212.40 = \$42.48), which is 1.78× the independent \$47.58. H.66 It is for making one thing unmistakable: the claim's shape is determined by who owns the building, not by what happened to the patient. It is NOT an argument that the conversion is improper — hospital outpatient departments carry costs an independent office does not. It is an argument that the patient cannot see any of it.*

Section I — Reading a claim

I.67 FL 4 · FL 6 · FL 17 · FL 42 · FL 67 · the codes. The codes come last, because they are usually fine — the same lesson as Ch. 25 §25.9. I.68 The type of bill's frequency digit · the discharge status, entered by someone who is not a coder · a revenue code that does not match the charge. I.69 It is the medical record number, not the patient control number. FL 3a is per encounter. The remittance will return an identifier that does not identify an account, and the claim will not autopost. I.70 The discharge status is wrong. Correct value 02 or 62, depending on the receiving facility — Community Rehab suggests 62, an inpatient rehabilitation facility, and the receiving facility's type settles it. The direction is OVERPAYMENT. I.71 Whether those are drugs requiring detailed coding, which belong under 0636 with a HCPCS code and units rather than 0250. I.72 The principal diagnosis is implausible. Essential hypertension as the condition chiefly responsible for an eight-day admission, with COPD with acute exacerbation secondary, is very likely a sequencing error. Ch. 33 §33.2 governs, and the error costs the facility a great deal.


Chapter 27 — Answer Key

Quiz (26 questions)

  1. B — the format of defined electronic health care transactions.
  2. B — situational.
  3. B — the companion guide.
  4. B — code sets and identifiers.
  5. B — eligibility inquiry and response.
  6. C — 278.
  7. A — 835.
  8. B — the file was syntactically valid.
  9. B — the payer accepted the claim into adjudication.
  10. B — the file followed the rules of the format, and nothing about content.
  11. B — the form's data with the boxes removed.
  12. B — revenue codes.
  13. B — the paper CMS-1500.
  14. B — a level in the hierarchy of information.
  15. B — the service-line level.
  16. C — the diagnosis pointers.
  17. C — the referring provider's NPI.
  18. B — you have a defect you will never find until something changes.
  19. B — well-formed and plausible, and nothing about adjudication.
  20. B — ERA enrollment, which is separate.
  21. B — was never adjudicated and is not in the payer's system.
  22. C — does not stop the clock.
  23. B — a payer acknowledgment naming the claim.
  24. B — no universal mechanism; partial solutions and persistent fax.
  25. B — an eligibility answer is a lookup; a claim requires adjudication.
  26. B — acceptance is not adjudication.

Exercises

Section A — What HIPAA did and did not standardize

A.1 Standard formats for defined electronic health care transactions, using the X12N implementation specifications. A.2 Standardized: the format · the segments · the element names · the order · the code sets. Not standardized: which situational elements a payer requires · what a payer does with them · the payer's own edits · how the payer names a problem · what the payer will accept as an attachment. A.3 Required · situational · not used. Situational causes the trouble, because the guide says "required when X" and payers differ on what X is. A.4 The companion guide. Ch. 14 §14.8 (bilateral conventions) · Ch. 21 §21.11 (proprietary edits) · Ch. 25 §25.9 (required fields). A.5 Standard code sets (ICD-10-CM, ICD-10-PCS, CPT, HCPCS Level II, CDT) and standard identifiers (NPI, EIN). A.6 Chapters 7 through 20. A.7 The transaction, the code set, or the identifier. A terse message may not distinguish a terminated CPT code from a Type 2 NPI in a rendering field from a malformed date — and knowing there are three different things that can be wrong is most of the diagnosis. A.8 A version change of the adopted standards, requiring simultaneous change by every payer, provider, vendor, and clearinghouse, with a compliance date everyone must hit together. It changes what elements exist and what is required. A.9 They add requirements on top of the standards, chiefly about what a response must actually tell you. They exist because "compliant" and "useful" turned out to be different things — an eligibility response saying "active coverage" and nothing about the deductible satisfies a format and answers none of Ch. 24's questions.

Section B — The transaction set

B.10 270 · 271 · 276 · 277 · 278 · 835. B.11 The professional, institutional, and dental claim transactions. B.12 The 999 is the implementation acknowledgment — was the file syntactically valid. The TA1 is the interchange acknowledgment — was the envelope readable. B.13 The 277CA is a claim acknowledgment: did the payer accept the claim into adjudication. A 277 is a claim status response. Exams use the similarity deliberately. B.14 Odd asks, even answers. B.15 The 835; Chapter 28. B.16 The enrollment transaction, employer to plan. A biller cares because it is why an eligibility answer can be wrong — coverage information reaches the payer through it. B.17 A 277. It does not contain the CARC and RARC codes, which arrive on the 835 (Ch. 28 §28.4). B.18 The 270/271. B.19 278 and 276. B.20 TA1 · 999 · 277CA.

Section C — The 837

C.21 "…the form's data with the boxes removed." C.22 Revenue codes · the circumstance code families (condition, occurrence, occurrence span, value) · and the institutional claim's own structures generally. (Ch. 26 §26.4, §26.6.) C.23 Diagnosis pointers per service line. The institutional claim links diagnoses to the claim rather than to each line, which is why Ch. 26 has no pointer discussion. C.24 No. The practical limit is the payer's and it is far higher. A system that says a claim must be split is likely imposing the paper form's limit on a transaction that does not have it — ask whether it is the payer's rule or the software's. C.25 SV101-3 through SV101-6. The four-modifier rule is in the transaction, not a paper limitation — which is why modifier 99 exists. C.26 A loop is a level. A segment is a line of data inside a loop. A data element is one field inside a segment. C.27 "At the service-line level, the diagnosis pointers." C.28 "At the subscriber level, in the name segment, the identifier is missing" — item 1a, the insured's ID number.

Section D — Reading a rejection

D.29 2300 HI = item 21, the diagnoses · 2400 SV102 = item 24F, the line charge · 2310A NM109 = item 17b, the referring provider's NPI · 2010AA NM109 = item 33a, the billing NPI · 2400 SV101-3 = item 24D's first modifier position. D.30 Qualifier HC (HCPCS) · code 99214 · modifier 25 · charge 185.00 · units 1 (basis UN) · pointers 1:2:3:4. D.31 No — the same information. Item 24E uses letters A–L; the transaction uses positions in the HI segment as numbers. A biller who learned pointers as letters should recognize them as numbers. D.32 That the position exists and is unpopulated. Every position is always there; it is the value that is absent — which is why a payer can reject an element you never filled in. D.33 The principal diagnosis in item 21 is not a valid code. Likely causes: a deleted code (Ch. 20 §20.1's quarterly updates) or a lookup error (Ch. 8). D.34 A modifier in item 24D's first position is not a valid modifier value. It does not say the modifier is inappropriate — a payer rejecting an invalid modifier says the value is not a modifier; a payer denying modifier 25 says it disagrees. Ch. 14 versus Ch. 29, arriving on different transactions. D.35 The subscriber's date of birth is missing. A registration failure (Ch. 24), fixable in thirty seconds on the day it arrives. D.36 A service line points at a diagnosis that is not on the claim. The transaction can tell that a pointer refers to nothing. It can never tell that a pointer refers to the WRONG thing — and only the second kind costs a denial. D.37 Item 17 should be blank — nobody referred her (Ch. 25 §25.10). A system auto-populating the performing physician creates this rejection out of nothing; the fix is to empty the field. D.38 (1) Is there supposed to be a referring provider at all? (2) Is the NPI a Type 1? (3) Is it ten digits and does it check-digit? (4) Is the provider in the payer's file? The fourth cannot be fixed by billing — it is a credentialing matter, and resubmitting will not change it.

Section E — Clearinghouses and enrollment

E.39 An intermediary that accepts claims from providers, validates and formats them, routes them to the correct payer, and returns acknowledgments and remittances. Even with a standard format, a practice billing sixty payers would need sixty connections, enrollments, and credential sets. E.40 Connectivity · validation · routing · translation. E.41 The claim your system produced and the claim the payer received are not byte-identical. (1) You cannot reproduce the payer's copy from your system — Ch. 25 CS1 lived in that gap for four months. (2) A problem your system generates never surfaces as a problem, so you have a defect you will never find. (3) The fix can be wrong — a default applied on your behalf is a guess. E.42 It is faster, and it does not consume a timely-filing day the way a round trip does. E.43 No. Passing proves the claim is well-formed and plausible. It predicts nothing about adjudication — Ch. 21's subject arriving one layer later. E.44 The companion guide is authoritative; the edit list is usually more current. Not a contradiction — read both. E.45 EDI (to send claims) · ERA (to receive the 835) · EFT (to receive the money). Per payer, not per practice. E.46 ERA enrollment. Ch. 28 §28.7's autoposting is impossible without it, and this is the most common reason a practice does not have it. E.47 The list of which payers you are EDI-, ERA-, and EFT-enrolled with. The gaps are the payers where your money and your remittance are arriving by the slowest available method — unnoticed, because the checks keep coming. E.48 Every payer enrollment must be redone · every report changes name and format · every defect the old clearinghouse was silently repairing arrives unrepaired. The third is never planned for. Instructions: run both in parallel if the contracts permit, and read the first two weeks of rejections line by line — it is the only clear list anyone gets of what their own system produces wrong.

Section F — Acknowledgments

F.49 TA1 — was the envelope readable? 999 — was the file syntactically valid? 277CA — did the payer accept the claim into adjudication? F.50 Accepted · accepted with errors · rejected. F.51 "…your claim is in the payer's system." The 999 says the file was grammatically correct; only the 277CA says the payer took the claim. F.52 Wrong member number · provider not on file · patient not found (any three of this kind). F.53 Thirty-eight transmitted; thirty-six submitted. The difference matters because a practice reading only the TA1 and 999 lines concludes all thirty-eight are with the payer — and two never will be unless somebody acts. F.54 Returned, not processed, data content error, National Provider Identifier, rendering provider. The three parts: status category code · status code · entity identifier. F.55 Because "invalid NPI" is not actionable and "invalid NPI — referring" is. A rejection naming the referring provider points at item 17b, one claim. A rejection naming the billing provider is a rejection of everything, because that value is identical on every claim you send — an emergency, not one claim's problem. F.56 How to retrieve a transmitted 837 · where the 999 and 277CA live for a claim or batch · what the report is called, who receives it, how often · retention and retrieval of old ones. Ch. 25's practice spent four months unable to answer a reasonable question because nobody had made this call.

Section G — Rejection versus denial

G.57 Never adjudicated / adjudicated · not in the payer's system / in it with a claim number · nothing to appeal / appeal rights and deadlines · correct and resubmit as new / appeal or corrected claim · timely filing keeps running / filing was met by the original. G.58 The timely filing row. It is counterintuitive because a denial is visible, tracked, worked, and appealable, and a rejection sits in a report — so the more dangerous of the two is the one that looks less serious. G.59 Because CARCs and RARCs describe adjudication decisions and a rejection was never adjudicated. It is described by the 277CA's status category and status codes — which is why denial and rejection reports cannot be merged without care. G.60 Because it never reached adjudication, so it never denied. A practice with an excellent denial rate and an unread rejection report is measuring half its failures, and the unmeasured half moves the measured one in the flattering direction. G.61 Day 1: about two to three minutes (read, correct, resubmit). Day 120: investigation, retrieval, a filing determination, and possibly a write-off or an exception request — a different order of magnitude, and sometimes the answer is nothing. The principle: a defect costs roughly its distance from the point of origin — Ch. 24 §24.1's ratio. G.62 Because it is evidence that nobody has been reading the report, which means there are others. You do not find one. G.63 (1) A payer acknowledgment naming the claim — the payer's own record. (2) A clearinghouse transmission report. (3) The practice management system's claim history. (4) A written record of a call. Most practices offer the third because it is the one on the screen, and it records an intent to send. G.64 The payer's. The only acceptance you can document is the resubmission's, dated after the window closed. Defenses: work rejections within days, and know your shortest window — the ninety-day payer is the one that will cost you money.

Section H — Attachments, modes, status

H.65 The 275 exists with incomplete adoption · esMD handles Medicare records requests and is not a general attachment solution · payer portals and clearinghouse attachment services work and are not standardized · and a great deal still moves by fax. H.66 The claim is submitted electronically and the document is faxed or mailed; both arrive; neither references the other in a way the payer's system can act on. Defenses: identify the document (claim number, or patient/provider/dates) · use the payer's stated method · record the submission. H.67 Batch accumulates claims and transmits a file, typically nightly. Real time sends one transaction and answers in seconds. Claims are batch and eligibility is real time because an eligibility answer is a lookup and a claim requires adjudication against benefits, edits, provider files, and history. H.68 A claim with no acknowledgment and no remittance after a reasonable interval, and confirming status before working a claim. H.69 It generates enormous volume and answers a question the 835 will answer anyway; some payers throttle it. The sharper criticism: it substitutes for reading acknowledgments you already have — a practice running status inquiries on claims whose 277CA rejections it has not opened is asking the payer about claims the payer never received. H.70 Read acknowledgments daily; use the 276 for claims genuinely unaccounted for.

Section I — The Encounter through the pipeline

I.71 Day 0 (Tue, Mar 14) service, charge capture, \$30.00 copay, note signed 6:42 p.m. · Day 1 (Wed, Mar 15) coder reviews, codes assigned, claim built, pointers set · Day 2 (Thu, Mar 16) scrubber clean, 837P transmitted 11:05 p.m. · Day 3 (Fri, Mar 17) 999 accepted, 277CA accepted. I.72 The note and the charges — but no claim. It is the most consequential day because every fact the claim will assert was created on it. I.73 11:05 p.m., in the nightly batch. It tells you most of the three days is waiting for a batch and for a coder, not processing. I.74 No. Acceptance is not adjudication — the 999 and 277CA confirm a valid file and a received claim, not a payment decision. I.75 The scrubber checked the claim against rules, the clearinghouse checked the file against a format, and the 277CA confirmed receipt. None of them evaluated whether this payer, on this contract, will pay an E/M with modifier 25 on the same day as a minor procedure. I.76 Because the fourteen days between acknowledgment and remittance dwarf it. A day saved at submission is real and small; the elapsed time lives elsewhere.


Chapter 28 — Answer Key

Quiz (26 questions)

  1. B — 835.
  2. B — explanation of benefits.
  3. B — a group code, a CARC, and an amount.
  4. B — charge equals paid plus the sum of the adjustments.
  5. B — the provider absorbs it under the contract and may not bill the patient.
  6. B — coinsurance.
  7. B — coordination of benefits.
  8. B — silent revenue loss with no error message.
  9. B — a contract violation and possibly a compliance matter.
  10. B — the contractual adjustment.
  11. B — the benefit is included in the payment for another service already adjudicated.
  12. B — it says information is missing without saying what.
  13. B — incidental to the primary procedure.
  14. B — at the line level.
  15. B — it carries the group code, CARC, and RARC that explain why.
  16. B — money that was never collectible under the contract.
  17. B — looks paid in full, with nothing in any denial log or work queue.
  18. B — ERA enrollment, which is separate and per payer.
  19. C — see an underpayment.
  20. C — arrives as a payment and appears on no exception report.
  21. B — raising it.
  22. B — building the expected allowed amount per line from the contract.
  23. B — systematic; a configuration applying to every claim of that type since it was made.
  24. B — post claims in full and post the offset as a separate provider-level transaction.
  25. B — not yet the patient's.
  26. B — CO-45 of \$56.60 and CO-97 of \$128.40.

Exercises

Section A — The remittance

A.1 Remittance advice (general) · ERA (electronic) · SPR (standard paper). A.2 The 835. A.3 The ERA is machine-readable and can be posted automatically; the SPR must be keyed or scanned. That is the whole practical difference and it is a large one. A.4 Check/EFT · claim · service line · (and) provider-level adjustments. A.5 The payment amount. A.6 A group code, a CARC, and an amount. A.7 Charge = paid + the sum of the adjustments, on every line. A posting that does not balance means an adjustment has been missed — and the missing one is frequently the interesting one. A.8 FL 3a, the patient control number. It makes autoposting possible. A.9 The 837 is the claim going out; the 835 is the remittance coming back.

Section B — The EOB

B.10 The remittance goes to the provider; the EOB goes to the patient. B.11 Different purposes (a benefit vs. a payment) · the charge is prominent · "you may owe" is an estimate · it arrives on its own schedule. B.12 The benefit — what the plan covered, the member's cost sharing, the deductible consumed, the maximum remaining. None of it is yours. B.13 Because it is the largest number on the page, and the patient does not know a charge is not a price (Ch. 23). B.14 No. The plan does not know what the practice collected at check-in, what a secondary will do, or whether the practice will bill at all. B.15 Date of service and provider · amount billed · allowed/eligible expense · plan paid · deductible, coinsurance, copay applied · running deductible and out-of-pocket accumulators · reason/remark · "what you may owe." The accumulators — you do not have them, and a deductible not yet met on the date of service is frequently why a bill is bigger than expected. B.16 (1) "Let's look at the same claim" — start with the number the patient is holding. (2) "You paid \$30.00 on March 14; here is where that shows"* — **this resolves it nine times in ten.** (3) *"Your plan's document is an explanation of benefits, not a bill."* (4) *"The remaining \$17.58 is coinsurance on the injection, the drug, and the lab draw."

Section C — Group codes

C.17 CO contractual obligation · PR patient responsibility · OA other adjustment · PI payer initiated reduction. C.18 The group code decides who owes; the CARC decides why. C.19 No for CO. Yes for PR. C.20 PR-1 deductible · PR-2 coinsurance · PR-3 copay. C.21 Coordination of benefits. C.22 The ABN (Ch. 22 §22.7), and the modifiers GA / GX / GY / GZ. C.23 A balance the patient owed has been written off. Nobody notices, because a contractual adjustment is exactly what a contractual adjustment is supposed to look like — and it is invisible even to an audit of the claim, because nothing about the claim is wrong. C.24 A patient has been billed for money the contract says they do not owe. Worse because it is a contract violation, may violate state balance-billing protections, and at scale is a compliance matter rather than a billing error (Ch. 32 §32.4). C.25 A posting rule mapping a CARC to a destination without checking the group code. Ch. 27's Case Study 2 — a configuration making an assertion nobody chose. C.26 Pull a month of adjustments by group code and reason code and look for any CARC appearing under more than one group code. It works because a CARC's meaning does not change with the group code — where one appears under two, one of them is coming from a rule rather than from the remittance.

Section D — CARCs and RARCs

D.27 A CARC states why an amount was adjusted; a RARC provides additional explanation. The CARC carries the amount. D.28 CO-45 charge exceeds the contracted amount · CO-97 the benefit is included in another service's payment · CO-16 lacks information needed for adjudication · CO-18 duplicate · CO-29 filing limit expired · CO-151 the information does not support this many services. D.29 N19 procedure code incidental to the primary procedure · MA130 incomplete or invalid information, no appeal rights. D.30 Because "lacks information" names nothing. The RARC names the missing element. D.31 It converts every CO-16 into a phone call, and it is your report's configuration — a settings problem masquerading as a payer problem. D.32 "The office visit was part of the injection." D.33 It is wrong because Ch. 15 §15.5 documented three chronic conditions separately assessed and Ch. 14 §14.4's modifier 25 is on the line asserting exactly that. D.34 "Line 1 denied" leads to resubmission or a write-off. The sentence leads to an appeal that wins. D.35 CO-16/M76 — a diagnosis is missing or invalid; correct and resubmit as a corrected claim, not an appeal, because nothing was decided about the service. PR-204 — not a benefit of this plan; the patient is held liable, and Ch. 22 §22.7 decides whether you may actually collect (GA yes, GZ no). CO-29 — filing expired; before writing it off, ask whether the claim was REJECTED earlier and resubmitted late, because that makes it a preventable administrative write-off with a name attached. CO-151 — a units or frequency assertion; check the units against the documentation first, because the two possible findings go in opposite directions. D.36 One. A practice that routes all denials to one queue and works them the same way is doing three of these four wrong.

Section E — Posting

E.37 Charge − CO − OA/PI − PR = payment, and charge − allowed = the contractual adjustment; allowed − patient responsibility = the payment. E.38 Because every later question is a line-level question: Ch. 29's root cause, §28.8's underpayment detection, Ch. 36's quality reporting. E.39 Systems that compute an expected contractual adjustment and post the difference. It destroys §28.8's detection, because your expectation is supposed to be the thing being tested against the remittance rather than the thing being recorded. E.40 Because they carry the group code, the CARC, and the RARC — a process that skips them has skipped precisely the lines that need attention. E.41 Nothing. The payer adjudicates the claim and reports a PR adjustment for the copay; it does not know or care that you already have the money. E.42 It must apply the existing payment against the new patient responsibility. If it does not, a second balance is created and the patient is billed for something already paid — a posting sequence problem, not a philosophy problem. E.43 Because a mismatch found before posting is a question; found after, it is an investigation. E.44 150.00 − 71.40 − 15.72 = 62.88 ✓. Bill the patient \$15.72** and nothing else. **E.45** **An underpayment of \$6.40 on the allowed amount. Nothing denied, nothing was flagged, and the line balanced perfectly — a line can be internally consistent and wrong.

Section F — Adjustments versus write-offs

F.46 The difference between the charge and the contracted allowed amount. It was never collectible. F.47 A decision to stop pursuing money you were entitled to collect. Somebody decides it. F.48 Because contractual adjustments belong in the denominator adjustment and write-offs are performance (Ch. 23 §23.9). Posting everything as "adjustment" makes the collection rate uninterpretable. F.49 The account looks paid in full. The claim balances; the patient owes nothing. Nothing appears on an aging report, in a denial log, or in a work queue. F.50 "…a write-off." F.51 Contractual · administrative (preventable) · small balance · charity/financial assistance · bad debt. F.52 Administrative (preventable) — they are the practice's own failures, priced. Ch. 29 §29.7 builds the report. F.53 Because they are different things: charity is a policy decision about a patient's ability to pay; bad debt is a failure to collect from someone who could. Mixing them misstates both, and financial assistance reporting depends on the separation (Ch. 32 §32.8).

Section G — Autoposting and underpayments

G.54 Volume accuracy · speed · consistency. G.55 ERA enrollment. An enrollment gap — somebody enrolled to send claims and never enrolled to receive the remittance. G.56 It posts denials as adjustments · applies group codes from rules · cannot see an underpayment · handles the exceptions worst. G.57 Where autoposting routes what its rules cannot classify. It contains the interesting items by construction — offsets, unmatched payments, reversals, unclassifiable denials. It is unowned because it is not anybody's job, it generates no alert, and payments still post every day it is not worked. G.58 "Who works it and how many items are in it right now?" and "What is the oldest item?" The second is diagnostic — in a healthy practice it is measured in days. G.59 It does not deny · does not reject · appears on no exception report. It arrives as a payment. G.60 Because the net collection rate is payments over what you should have collected, and "should have collected" is normally computed from the allowed amount the payer reported. A low reported allowed amount shrinks the denominator along with the numerator, so the ratio improves. G.61 Expected allowed · actual allowed · variance · threshold · classify. Step 1 is the whole difficulty, because it requires the contracts in a computable form. G.62 Because not one line is at the blend. 133.03% / 124.21% / 115.44% / 100.00%, blended 128.55% — a blended check finds every line wrong and no line wrong. G.63 Contract loaded wrong · claim wrong · payer wrong. Contract is most common on a first pass. Payer produces recovery and is systematic — it is a configuration, applying to every claim of that type since it was made. G.64 \$6.40 × 40 = **\$256.00/month\$3,072.00/year**; over 26 months, **\$6,656.00. The duration represents how long the payer's configuration has been wrong, and recovery is bounded by the contract's reconsideration window**, not by when you noticed.

Section H — Offsets, reversals, and the balance that moves

H.65 A takeback is a payer recovering a prior overpayment; an offset is the mechanism — reducing a future payment instead of requesting a check. They appear in the provider-level adjustment section. H.66 Interest on late claims · capitation payments · penalties · advance payments and their recovery (also acceptable: balance-forward mechanics). H.67 \$612.40 was offset against a prior overpayment. Post every claim at its full remitted amount, post the offset as a separate provider-level transaction referencing the original claim, then reconcile. H.68 Dozens of accounts carry small false balances · the original overpaid claim is never corrected · §28.8's detection reports variances on every line of that remittance, which is noise you generated. H.69 A reversal carrying the original amounts inverted, followed by the corrected adjudication. Posting only the correction doubles the payment; stopping at the negative leaves the claim unpaid. H.70 The primary adjudicates and produces a PR balance → that balance is not yet the patient's → the secondary receives the claim with the primary's remittance information and applies its benefit → what remains is the patient's. H.71 Billing the patient after the primary (the most common improper patient bill) · not billing the secondary at all · assuming crossover where it does not happen. H.72 Because a QMB may not be billed for Medicare cost sharing (Ch. 3). It is prohibited, not merely awkward.

Section I — The Encounter's first remit

I.73 Day 17, Friday, March 31. \$70.30.** **I.74** L1 185.00 − 128.40 − 56.60 = **0.00** ✓ · L2 150.00 − 71.40 − 15.72 = **62.88** ✓ · L3 18.00 − 11.72 − 1.26 = **5.02** ✓ · L4 14.00 − 11.00 − 0.60 = **2.40** ✓. **I.75** **CO-45 \$56.60 (the spread between the \$185.00 charge and the \$128.40 allowed) and CO-97 \$128.40** (the entire allowed amount taken away as bundled). **The payer priced the visit and then declined to pay for it** — not a contradiction, but how a bundling denial looks on a remittance. **I.76** **\$128.40, not \$185.00, because **you are owed the allowed amount, not the charge** (Ch. 23 §23.7). **I.77** **Payment posted \$70.30 · patient responsibility created \$17.58 · open denied amount \$128.40. I.78 Nowhere. The E/M line paid nothing and produced no PR-3, because the payer never adjudicated a copay on a visit it never paid. The \$30.00 stays on the account as a credit. **I.79** **Day 66**, when the second remittance pays the E/M **\$98.40 and reports the \$30.00 as PR-3.** **I.80** (1) **The account did not look broken** — three lines paid, the arithmetic balanced, an EFT arrived. (2) **The \$128.40 had to be routed somewhere on purpose — posted as a contractual adjustment it disappears; posted as a denied amount it becomes Ch. 29's day-20 work item and Ch. 30's day-24 appeal. (3) Nothing in the pipeline could have prevented it. A process recording "payment received" would have been telling the truth and would still have lost \$128.40 — which is the chapter's argument that posting is a decision, not a record.


Chapter 29 — Answer Key

Quiz (26 questions)

  1. B — is an adjudication decision with appeal rights.
  2. B — rejections, which never generated a remittance line.
  3. C — four.
  4. B — another practice's claim.
  5. B — whether the money can still be obtained.
  6. C — hard and preventable.
  7. B — time.
  8. B — deadline.
  9. B — what produced the denial.
  10. C — five.
  11. A — one.
  12. C — three.
  13. C — a catch-all "other."
  14. B — worked, resubmitted, and denied again indefinitely.
  15. B — one investigation.
  16. B — closed, categorized, and removed from the queue.
  17. B — 7.
  18. D — 8.
  19. B — forfeit the appeal rights attached to the original determination at some payers.
  20. B — root cause and outcome.
  21. B — a category is unwinnable.
  22. B — a category with a zero-percent success rate.
  23. A — 25% by line and 100% by claim.
  24. B — 43% of denials.
  25. B — answering the question it asks.
  26. B — this payer denies this pairing predictably, and a process could have stopped it.

Exercises

Section A — Denial versus rejection

A.1 A denial is an adjudication decision not to pay: the payer received the claim, processed it, and decided. A rejection is a claim that never reached adjudication — it failed at the clearinghouse or the payer's front end. A.2 The denial has appeal rights. The denial stopped the timely filing clock; a rejection never did. A.3 A rejection is corrected and resubmitted as a new claim; a denial as a corrected claim (item 22 / frequency 7). Swapping them produces a duplicate in one direction and an unappealed loss in the other. A.4 A rejection arrives in an acknowledgment report (Ch. 27 §27.6); a denial arrives on a remittance. A.5 Rejections are not in it, because a rejection never generated a remittance line — so a well-run denial operation can still lose claims steadily. Ch. 27's Case Study 1. A.6 The person who works denials also works rejections, and both counts appear on the same report. A.7 Because they arrive on different clocks — a rejection surfaces within days of submission, a denial when the payer adjudicates (fourteen days later for Account 10-4471). A daily task and a weekly one should not be scheduled as one job.

Section B — The taxonomy

B.8 Eligibility (front end) · authorization (front end) · coding (coder or edit) · documentation (the note) · timely filing (the process) · coverage/necessity (policy) · duplicate (the workflow). B.9 Four. Eligibility and authorization, which routinely outnumber every coding denial combined. B.10 Duplicate — it frequently means somebody else's claim (Ch. 17 CS2). B.11 As member not found, coverage terminated, not covered under this plan, or an OA group code pointing at another payer. The tell is that nothing about the claim is wrong. B.12 A SCOPE problem — the authorization exists and does not cover what was done. Ch. 24 §24.6: the number without its scope is a number, not a record. B.13 Code selection · modifier · units. They have different owners and different fixes. B.14 It is the only family where the claim may be entirely correct and the answer still lives in a chart. B.15 CO-29 timely filing · process · almost never winnable. CO-197 authorization · front end · rarely winnable after the fact. PR-204 coverage/benefit · policy · not winnable by argument. CO-18 duplicate/workflow · workflow · usually resolvable. CO-16 with an invalid rendering provider ID credentialing · not billing · not winnable by anyone in the billing office. CO-50 documentation or coverage · requires reading the record. B.16 CO-50 is the one worth an argument on the merits. The CO-16 credentialing item belongs to a different department. B.17 "Was this claim rejected earlier and resubmitted late?" If so it is a preventable administrative write-off with a cause, not a contractual one.

Section C — Hard, soft, preventable

C.18 Hard/soft = whether the money can still be obtained. Preventable = whether the practice could have stopped it. C.19 (See §29.3's grid.) Soft/preventable: missing modifier, wrong POS. Soft/not: an unpredictable payer edit, retroactive eligibility change. Hard/preventable: timely filing, no authorization obtained. Hard/not: a genuinely non-covered service, a patient never eligible. C.20 Hard and preventable — money lost entirely to process, on a claim that was otherwise correct and that nobody ever got to argue for. C.21 (See C.19.) C.22 No. Ch. 24 §24.10: the front end's failures are usually questions nobody had written down. The alternative framing is that preventability is a statement about the process, not about a person — and reporting it as the second stops the data being accurate. C.23 Time, specifically the deadline. It follows that the queue must sort by deadline. C.24 Account 10-4471. The code, modifier, and documentation were all correct and the appeal was won — and a scrubber rule would have stopped the denial from occurring. C.25 Because a category nobody will admit to is a category nobody can fix — practices systematically under-record preventability when it is heard as blame.

Section D — Root cause and triage

D.26 The remedy is what you did about this claim; the root cause is what produced it. D.27 It records "corrected and resubmitted" — true, useless, and it will happen again, because the remedy is not the cause. D.28 Training (Chs. 13–14) · template (Chs. 4, 15) · edit (Chs. 21, 27) · payer policy (external) · chargemaster (Ch. 26 §26.5). D.29 Bundled · not a benefit at all · not recognized by this payer · not medically necessary as documented. Only the fourth is arguable. D.30 Indicator 0 → do not appeal · indicator 1 with supporting docs → appeal · indicator 1 without → do not appeal, correct · MAI 2 → do not appeal · MAI 1 or 3 → workable · proprietary → get the policy first. Three say do not appeal. D.31 Coded wrong (fixable) versus never going to be covered (not fixable by coding; the question is whether the patient was told in advance). D.32 Four reasons → edit branch → necessity test. About ninety seconds. D.33 It is not that it wins appeals. It is that it stops you writing the ones that cannot be won, which frees time for the ones that can. D.34 (See §29.4's list of fifteen.) D.35 Because a catch-all collects a third of everything, and the third it collects is the interesting third. D.36 Because it is not fixable by billing. A credentialing denial routed to a biller will be worked, resubmitted, and denied again indefinitely. D.37 Because a list assuming every denial is your fault leaves §28.8's payer findings nowhere to go, and they will be miscategorized as coding problems. D.38 A terminated HCPCS, an unaccepted revenue code, or a required-HCPCS line with none mapped. The denial names the line, not the cause — a chargemaster problem wearing a claim's clothes.

Section E — Working the queue

E.39 Deadline · category · dollar. E.40 Because §29.3's expensive quadrant is created by time, not difficulty. A \$2,000 denial with sixty days left is safer than a \$180 denial with four. E.41 Because twelve denials with the same reason code from the same payer are one investigation — working them individually costs twelve times as much and produces no root cause. E.42 Close them immediately, categorize them, and report them. RARC MA130 says explicitly that there are no appeal rights. E.43 Read the remittance codes · run the triage · classify the root cause · decide · act and record both · report the pattern if it is larger than the claim. E.44 Because afterwards you will remember the remedy — classifying after acting produces a log full of remedies. E.45 Report a pattern, not an instance, to somebody who can change the process — Ch. 21 §21.10. E.46 How many items · what is the oldest and why · how many closed as "no action" · what is in here that nobody in this department can fix. E.47 The team closed 138 and resolved 49 — measure resolved, not worked. And "no action: 0" means nothing is being closed as unwinnable, so the queue is overstating recoverable work. E.48 Yes. Descending-by-charge makes the deadline invisible and lets hard, small, or old items sink. The 287-day item is a symptom of the sort order, not of capacity.

Section F — Corrected claims

F.49 Professional: item 22, code 7 to replace, code 8 to void. Institutional: FL 4 frequency 7 to replace, 8 to void. F.50 A duplicate — the payer has two claims, denies the second, and the original problem is unfixed. It is the same failure because both fields do the same job on their respective forms. F.51 Replace when the claim should exist and be different. Void when it should not exist at all — wrong patient, wrong provider, wrong date. F.52 The original claim number, which returns on the remittance (Ch. 28 §28.1). F.53 A corrected claim says "here is different information." An appeal says "your decision was wrong about the information you had." F.54 It can restart timely filing arguments and, at some payers, forfeit the appeal rights attached to the original determination. F.55 Units → correct and resubmit, coding-units. CO-97/N19 with documentation → appeal, edit-payer. No authorization on a completed service → usually close (hard, preventable); ask about retroactive authorization first, authorization. Duplicate with no internal match → investigate outward, duplicate/workflow. MA130 → close, and categorize. Not enrolled → escalate out of billing, credentialing.

Section G — The log and the numbers

G.56 DOS · denial date · payer · provider · code and modifiers · charge and allowed · group code · CARC · RARC · root cause · preventable? · action · outcome · date resolved. G.57 Root cause and outcome. They are what turn individual claims into knowledge about a practice. G.58 (Definitions per §29.7.) G.59 Because the two numbers are identical until a category is unwinnable, and that is exactly where you need to look. A team that worked 400 and resolved none was fully occupied by the wrong measure. G.60 It means reporting the overturn rate per category rather than in aggregate. An average of a winner and a loser tells you about neither, and it concealed a zero-percent category for a year. G.61 Because rejections never reach adjudication and so never deny — Ch. 27 CS1's denial rate improved every month the practice lost more money. G.62 The practice's own process failures, priced in dollars. Ch. 28 §28.6 created the category for this report. G.63 Lines or claims · zero-pay only or any non-contractual adjustment · adjudicated or submitted. G.64 25% by line; 100% by claim. G.65 Because a line paid at a reduced rate with a CO-151 was partially denied and would not be counted. G.66 Pick one definition and write it down; never change it silently · report lines for operational work · treat external benchmarks as comparisons of definitions. G.67 Because the published rate was computed under somebody else's three choices. §29.9 recommends comparing yourself to yourself. G.68 6.4% (267 ÷ 4,180) · registration 71 + authorization 44 = 115 of 267 = 43% · 69.3% preventable (185 ÷ 267) · overturn 57 ÷ 84 = 67.9%, reported as 68%.

Section H — Prevention and the case for it

H.69 The front end (eligibility, authorization, registration accuracy) · the template (documentation) · the edit (the scrubber). H.70 The template — it improves the record rather than the claim. H.71 A modifier denial is preventable at the edit only if the information needed is on the claim. When the answer is in the note, it is a template problem wearing an edit's clothes, and a scrubber rule for it stops claims it cannot resolve. H.72 It must tell somebody what to do. Otherwise it converts a denial into a held claim — better, and not free. H.73 A denial costs you every time it happens. An edit costs you once. H.74 An edit may stop a claim and ask a question; it may not answer it. Acceptable: "modifier 25 may be required — has a separately identifiable service been documented?" Unacceptable: a rule that appends modifier 25. H.75 \$25,720.80. Eleven of forty-two were in fact separately documented and defensible, but had not been documented that way at the time and could not be proved after the fact. H.76 A dollar figure for a period · name the process, not the person · the smallest possible fix · a comparison rather than a benchmark · ask for a measurement rather than a commitment. H.77 Because a benchmark from a source nobody trusts becomes an argument about the benchmark, and a category that is being measured usually improves before anything changes — which is not a trick, since measuring it is itself a process change. H.78 Worth something: ask what would change the answer (a stated threshold converts a refusal into a condition) · keep the measurement running · do the part you control. Not worth anything: escalating past the person who declined, early — it converts a priorities disagreement into an authority conflict. Write it down because a dated record of a declined correct analysis is how the finding gets acted on eighteen months later.

Section I — The Encounter's CO-97

I.79 Day 20, Monday, April 3. I.80 CO — the patient may not be billed. 97 — the service is included in another service's payment. N19 — incidental to the primary procedure. "The payer has asserted that the office visit was part of the injection." I.81 Bundled, which would ordinarily end the analysis with nothing to appeal. I.82 Modifier indicator 1 — a modifier may override. The claim carries modifier 25. So the question is whether the documentation supports the override, and the branch concludes APPEAL, quoting the Policy Manual. I.83 Three chronic conditions each separately assessed with a plan · prescription drug management, three medications reviewed and continued · two laboratory tests ordered with stated clinical reasons · a new problem with its own history, examination, and independent management decision. Elements 1 through 3 have nothing to do with the knee. I.84 Root cause: EDIT — PAYER ("E/M with minor procedure, same day"). SOFT. Decision: appeal. I.85 14 + 31 + 13 = 58 minutes. I.86 Both are true because "preventable" means a process could have stopped it, not that anyone was wrong. The claim was correct at every step and won on the merits; this payer denies this pairing predictably, so a scrubber rule recognizing the pattern and attaching supporting detail — or a template placing the three chronic conditions where a reviewer would see them — would have changed the outcome without changing the claim's correctness.


Chapter 30 — Answer Key

Quiz (26 questions)

  1. B — the allowed amount.
  2. B — forfeit the appeal rights attached to the original determination.
  3. C — a phone call, four more documented weeks, and resubmission.
  4. C — proof the claim was filed on time, such as a payer acknowledgment.
  5. B — the specific, executable request.
  6. B — a reviewer who has read the rule reads your facts as evidence rather than as a story.
  7. B — the note, the NCCI Policy Manual, and the payer's own published policy.
  8. B — only the demonstration is new work; citations live in a maintained paragraph library.
  9. B — uses only facts already documented, arranged so their consequence is visible.
  10. B — amendments are dated and attributed, and a reviewer will discount the note or refer the file.
  11. C — the date of the determination being appealed.
  12. B — ERISA and the DOL claims-procedure regulation.
  13. C — the plan participant; the provider typically acts as authorized representative.
  14. B — redetermination, reconsideration, ALJ, Council, judicial review.
  15. B — the MAC, by staff not involved in the initial determination.
  16. B — 120 and 180 days.
  17. C — the ALJ hearing.
  18. B — all evidence by the reconsideration; later evidence excluded absent good cause.
  19. B — moving the appeal to the next level when the current level misses its decision timeframe.
  20. C — the treating physician.
  21. B — the gap, named.
  22. C — medical judgment.
  23. C — four months from the final internal adverse determination.
  24. B — forwarded automatically to an independent review entity.
  25. B — your filing deadlines and the payer's decision deadlines.
  26. D — when the money posts and the outcome flows back to the denial log.

Exercises

Section A — Deciding whether to appeal

A.1 A formal request that a payer reverse an adjudication decision, through a defined review process, arguing the decision was wrong. It requires a decision (rejections have none), an argument that it was wrong, and a defined process with a clock. A.2 Because there is no adjudication to reverse — the claim never got decided. Chapter 29 §29.1 (drawn first in Ch. 27 §27.7). A.3 CO-45 \$56.60 priced the visit at \$128.40 against the \$185.00 charge; CO-97 \$128.40 then removed the allowed amount. You are owed the allowed amount, not the charge — the appealable amount is \$128.40. A.4 At some payers a corrected claim closes the original determination and forfeits its appeal rights; the corrected claim adjudicates fresh, sometimes against a fresh timely filing argument. Chapter 29 §29.6. A.5 A phone call to the referring office, four more documented weeks of conservative therapy, and resubmission (Ch. 22 §22.11). An appeal argues about the record, and the record showed four weeks against a six-week requirement — no letter can change what the record says. A.6 When you hold proof of timely filing — ranked in Ch. 27 §27.7: a payer acknowledgment naming the claim (the 277CA), then a clearinghouse transmission report, then system history. One exhibit, short letter. A.7 Same reason code, opposite decisions: the CO-29 with a 277CA is appealed and won; the CO-29 without proof is closed and counted as a preventable write-off. The evidence, not the category, decided. A.8 CO-45 is the contract working — the spread between charge and allowed. Appealing it is appealing your own signature. If the allowed is wrong against the contract, that is an underpayment (Ch. 28 §28.8) worked through the contract's dispute provisions. A.9 The minutes (58 across three touches — Ch. 29 §29.10), the overturn rate (68% — Ch. 29 §29.7), and the allowed amounts at stake (Chs. 2, 23, 28). Chapter 40 §40.2–§40.3 assembles them, answering Q4. A.10 Outcome-by-category data that reveals a category with a zero (or near-zero) overturn rate in a quarter instead of a year — the control Chapter 21's Case Study 1 lacked.

Section B — What an appeal must contain

B.11 Identification · the determination being appealed (date + reason code) · a specific request · the argument against the payer's own standard · the evidence, listed and enclosed · timeliness through the designated channel. B.12 So a reviewer who agrees can act in one step. Good: "Reprocess line 1, 99214-25, and pay at the contracted allowed amount of \$128.40." Bad: "We respectfully request reconsideration of this claim." B.13 The window is the deadline; the channel is the door. An appeal mailed to the claims address is scanned as correspondence — or treated as a duplicate claim — and tolls nothing. B.14 A corrected claim says "here is different information"; an appeal says "your decision was wrong." A records response answers a payer's pre-decision documentation request — no determination exists, so no appeal rights are running. A grievance is a complaint about service or conduct, not a request to reverse a determination. B.15 Because the claim has not been adjudicated — you are still in claim processing. CARC 252 (an attachment is required) is the code family, and its clock is running. B.16 Every filing window at every level runs from it. B.17 "Reconsideration" is a Medicare term of art (level 2, the QIC); commercial payers use the same word for whatever their manual says it means. Read the process, not the label.

Section C — The appeal letter

C.18 Header · ask · standard · demonstration · evidence map · close. C.19 A reviewer who has just read the standard reads your facts as evidence against it; a reviewer who reads facts first reads a story, and stories lose to edits. C.20 Header = the RE block; ask = "reprocess line 1… \$128.40"; standard = the paragraph citing the payer policy, the Policy Manual, and the indicator; demonstration = the four numbered elements plus the item-4 paragraph; evidence map = ENCLOSURES; close = the 45-day commitment and contact. C.21 Because §30.1's trap is real: a filing read as a corrected claim can forfeit appeal rights. The sentence tells the payer how to process the document. C.22 The office note, the NCCI Policy Manual, and the payer's own published policy — Chapter 6's toolkit table, row 13. C.23 Re-read the note against the elements (6) · pull the payer policy (5) · pull Manual language and the indicator from the paragraph library (3) · draft the demonstration (10) · assemble, submit, file proof, calendar (7). 6+5+3+10+7 = 31 ✓. Only the demonstration is new because only it is about this patient. C.24 Maintained boilerplate of recurring citations — Policy Manual language for common edits, payer policy cites, the proof-of-filing paragraph — reviewed when the quarterly NCCI edits and the annual Manual revision land (and the code sets: ICD-10-CM October 1, CPT January 1, HCPCS quarterly). C.25 Nothing in the letter was created for the appeal — the facts existed on day 0 and the rules were published before filing. "You do not build it for the appeal. You build it for the claim." C.26 Minimum necessary (Ch. 5 §5.7): the payer reviewing a March 14 denial has no need for the full chart — and a reviewer handed forty pages reads none of them. C.27 (Model answer.) Header identifying the claim and the CO-29 determination; ask: reprocess as timely filed; standard: the payer's own filing rule from the manual; demonstration: one paragraph — claim transmitted [date], acknowledged by your 277CA [date], within the filing period; evidence map: exhibit 1, the 277CA; close: response commitment. One page.

Section D — Evidence

D.28 The note proves the facts; the policy proves the standard the payer owes itself; the manual proves the national standard; the edit proves what the payer's machinery permits. D.29 It converts the appeal from a disagreement into an audit of the payer's compliance with itself. D.30 It confirms the routine pre- and post-work of a minor procedure is not separately reportable (the payer's side — and why the appeal never rests on the knee evaluation alone), and it confirms a significant, separately identifiable E/M is reportable with modifier 25 with no different-diagnosis requirement (your side). D.31 "The indicator is 1, and here is the documentation the override requires." The indicator opens the door; the note walks through it. D.32 Because the sources revise on a schedule and an appeal citing stale language invites a response citing current language: NCCI Policy Manual annually, NCCI edits quarterly, HCPCS Level II quarterly, ICD-10-CM October 1, CPT January 1. D.33 Constructing an argument arranges facts already documented so their consequence is visible — advocacy. Constructing a record adds the missing sentence after the fact. The line: nothing enters the record because the appeal needs it. D.34 New complaint this visit · no prior imaging of this knee available · focused history and examination with a differential impression recorded · management options discussed at this encounter · injection elected the same day with consent documented in the procedure note. Conclusion: the evaluation that produced the decision happened at this encounter. Stronger than a quotation because it forecloses the "scheduled procedure visit" counterargument and depends on no single sentence the provider happened to write. D.35 Amendments are dated, attributed, and flagged in the legal health record (Ch. 4 §4.5); a reviewer sees a post-denial addendum asserting exactly the disputed element and discounts the note — or refers the file. Compliant alternatives: retrospectively, construct the argument from what is documented (D.34); prospectively, a template prompt that asks the question at the point of care (Ch. 29 §29.8, Ch. 38 §38.3). D.36 An appeal to a federal program is a statement to the government about a claim; a pattern of appeals asserting documentation that does not say what the letters claim is a false-record theory, not persistence.

Section E — Commercial levels, deadlines, and ERISA

E.37 Typically one or two internal levels — level one a first human review with the documentation, level two a fresh reviewer, often clinical, and usually the final internal step. After: external review for medical judgment; the contract's dispute provisions for money. E.38 The deadline discipline applied to the appeal itself: every level's filing window runs from the date of the determination being appealed. E.39 The edit fired on codes; the appeal supplies the record the edit never saw. E.40 Denials autoposting as contractual adjustments generated no work items, and the appeal windows — running from each remittance's determination date — expired unobserved. E.41 Determination day 17 (Fri Mar 31); filed day 24 (Fri Apr 7) = 7 of 180 days; status check day 45 (Fri Apr 28), 21 days after submission; payer commitment day 69 (day 24 + 45); decision day 59 (Fri May 12). 59 − 17 = 42 days ✓. E.42 Because a claim's value decays while it waits (theme 6) and the log works by date — not because the window pressed. E.43 ERISA; state insurance law — e.g., the state's prompt-pay statute and its external review process. E.44 At least 180 days; the documents, guidelines, and criteria the denial relied on, free of charge on request — which is how you obtain the self-funded plan's version of the policy the letter must argue against. E.45 The member's. The provider exercises them as the member's authorized representative, under the plan's designation procedure; the network contract's dispute channel is separate. E.46 To the Department of Labor, citing 29 C.F.R. § 2560.503-1 in writing — not to the state insurance department, which lacks jurisdiction. E.47 Because the answer chooses the deadline, the standard, the reviewer, and the regulator — Case Study 2 is the price of not asking.

Section F — The five levels

F.48 Redetermination — the MAC · reconsideration — the QIC · ALJ hearing — OMHA · Medicare Appeals Council — the Departmental Appeals Board · judicial review — federal district court. F.49 120 · 180 · 60 · 60 · 60 days. F.50 Level 3 (ALJ), again at level 5 with a higher threshold. Verify the current figures — they adjust annually. F.51 Rede- before recon- (alphabetical), MAC before QIC. F.52 Level 1 is the same contractor taking a second look with different staff; the QIC is a different organization whose whole function is second-level review. F.53 The Office of Medicare Hearings and Appeals, an HHS office separate from CMS; the ALJ level is a genuine adjudication with testimony, outside the claims apparatus. F.54 The fourth level, within the HHS Departmental Appeals Board; reviews ALJ decisions on request or own motion. F.55 A civil action in federal district court; the gates are the 60-day window and the higher amount in controversy. F.56 Moving the appeal to the next level when the deciding level misses its statutory timeframe. F.57 Free, comparatively fast, decided on the record you assemble — and where documentation appeals are won; the upper levels are for extrapolations, patterns, and statutory fights. F.58 The provider's own right on assigned claims; CMS-1696 when appealing on the beneficiary's behalf or through a representative. F.59 The remittance advice; the beneficiary's is the Medicare Summary Notice (Ch. 3 §3.9).

Section G — Redetermination, reconsideration, evidence

G.60 The beneficiary, the Medicare number, the specific items and dates of service, what is disputed, a signature — §30.2's list turned into fields. G.61 Because the form gets the appeal into the system and the attachment wins it; for a coverage denial the standard is the NCD or LCD itself, argued element by element (Ch. 22 §22.6's linkage discipline). G.62 The decision per service, the reason tied to the governing policy, and the next level with its deadline. It does not give you money — payment arrives on a later remittance and must be reconciled there. G.63 Post the favorable half when the adjustment posts; re-run the triage on the upheld half against the stated reason — if the record genuinely lacks the required element, close and prevent rather than reconsider. G.64 All evidence the appellant wants considered goes in by the reconsideration; later evidence may be excluded absent good cause. G.65 Evidentially, the reconsideration is the hearing — the ALJ decides on a record that substantially closed at level 2. G.66 Because it inverts the system's design; a good-cause finding, before the judge will even consider the held-back document. G.67 Everything it cited — the note and the remittance excerpt — on day 24, at level one. Nothing was saved for later because nothing needed to be.

Section H — Peer-to-peer, external review, tracking

H.68 The treating physician. The payer's medical director will not discuss clinical judgment with a billing office; a covering partner answering "I'd have to check the chart" spends the call's only currency. H.69 Prior authorization and concurrent review — before the determination hardens. The Encounter's denial is a post-service documentation question decided by reading, not conversation. H.70 The decision at issue · the standard · the facts that meet it · the gap, named · logistics. Practices skip the gap — and the reviewer finds it anyway, on the call, with the physician unprepared. H.71 Date, time, reviewer's name, reference number, outcome, commitments — immediately. Verbal approvals without reference numbers have a way of not existing at adjudication. H.72 Review of a final adverse determination by an accredited independent review organization, for medical-judgment questions and rescissions; unlike every internal level, its decision binds the plan. H.73 Insured: the state's external review process. Self-funded: the federal external review process — state review generally cannot reach an ERISA plan. H.74 Four months from the final internal adverse determination; internal exhaustion first (with urgent-care and process-failure exceptions). H.75 Pricing/underpayment disputes → the contract's dispute provisions (Ch. 28 §28.8); the Medicare ladder → §30.6–§30.7. (Also: bundling edits, timely filing — not medical judgment.) H.76 Its five levels are the external machinery built in — QIC, ALJ, and Council all sit outside the MAC. Medicare Advantage auto-forwards an upheld plan-level appeal to an independent review entity without the enrollee asking. H.77 Yours (filing deadlines) and theirs (decision commitments). Tracking only yours = filing on time and then waiting indefinitely. H.78 Open the row at the decision to appeal (prevents the unfiled-appeal gap where windows run on nobody's calendar) · work by date (expiration is the only irreversible event) · follow up on a schedule (confirms the appeal is in the system as an appeal; timestamps the payer's clock) · resolved only when the money posts (a favorable letter is a promise; the outcome must reach Ch. 29's log). H.79 Six past the payer's response deadline — the payer's commitments cost it nothing because nobody tracks them. Nine with no follow-up date — nine appeals running on memory; the over-90 bucket is their destination. Three favorable decisions unposted — won money not collected. Four with no level recorded — filing deadlines that cannot be computed; those are the rows that expire.

Section I — The Encounter

I.80 Day 24, Friday, April 7; 31 minutes: re-read the note 6, payer policy 5, paragraph library 3, draft the demonstration 10, assemble/submit/calendar 7. I.81 The record documents a significant, separately identifiable E/M: three chronic conditions each separately assessed with a plan, prescription drug management, two labs ordered with stated reasons, and a new problem with its own history, exam, and management decision. The spine: elements 1–3 have nothing to do with the knee. I.82 New complaint this visit · no prior imaging of the knee available · focused history and exam with a differential impression · options discussed at this encounter · injection elected the same day with documented consent → the evaluation that produced the decision happened here. Made necessary by frozen gap #2: the note never states the decision to inject was made during the visit. I.83 The office note (the EHR — the only clinical record enclosed), the NCCI Policy Manual (free, CMS), the payer's own published policy (the provider portal). Left out: the rest of the chart — minimum necessary. I.84 Decision day 59 (upheld in the provider's favor); paid day 66: plan \$98.40 + patient \$30.00 = **\$128.40** ✓, the full allowed amount. **I.85** Chapter 14 answered Q1 on the documentation; day 59 added the confirmation only a payer could give — **a human reviewer, reading the note, agreed.** **I.86** **Q4** — could the denial have been prevented, and what did the chase cost? **Chapter 40** owns it. On the record: the 58 minutes (Ch. 29 §29.10), the 68% overturn rate (Ch. 29 §29.7), the \$128.40 (Chs. 2, 23, 28), and the loaded labor rate coming in Ch. 31 §31.7.


Chapter 31 — Answer Key

Quiz (26 questions)

  1. B — it contains contractual adjustments that will never be collectible by anyone.
  2. C — insurance AR versus patient AR.
  3. A — \$128.40 denied and on appeal, plus \$17.58 patient responsibility.
  4. B — an account's age resetting when it is rebilled or touched.
  5. B — old credits camouflage old debits, and are themselves the compliance problem.
  6. B — total AR ÷ average daily charges.
  7. C — 51.5 (2,920,000 ÷ 365 = 8,000; 412,300 ÷ 8,000 = 51.5).
  8. B — improves it, indistinguishably from collecting faster.
  9. C — write the definition on the dashboard and run both versions across the seam.
  10. B — its decomposition into components with different causes.
  11. D — \$12,700 of insurance balances with no activity on record.
  12. B — deadline.
  13. B — the charge is arbitrary; the allowed amount is what the claim can actually retrieve.
  14. B — an event-fed queue.
  15. D — a promise to check back in thirty days (the metronome).
  16. B — the weakest proof; memory, not evidence.
  17. A — \$36.00 per hour = \$0.60 per minute.
  18. B — written off at posting under a uniform policy: 5.90 > 4.15.
  19. B — instances, never patterns.
  20. B — the Anti-Kickback Statute and the CMP's beneficiary-inducement provisions.
  21. B — a symptom with three diagnoses.
  22. A — reported and returned within sixty days of identification.
  23. B — an obligation actionable under the FCA's reverse-false-claim provision.
  24. B — could have paid and, after genuine effort, did not.
  25. C — before collection activity: determine, then pursue.
  26. B — the underpayment variance findings, because a silent underpayment raises the rate.

Exercises

Section A — What AR actually is

A.1 Money earned and not yet collected — an inventory of promises with a decay rate. It is not revenue (that was earned at service) and it is not cash (that arrives later); it is the gap between them. A.2 Because AR posts at charges, and Chapter 23 §23.7 established that charges are arbitrary opening figures; the contractual share was never collectible by anyone and represents no failure when it disappears. A.3 The contractual adjustment comes off and what remains is an allowed amount somebody actually owes — so young AR is mostly air and expectation; adjudicated AR is mostly money. A.4 Insurance AR versus patient AR. Insurance AR runs on adjudication schedules and dies by timely filing and appeal deadlines, worked by portal/phone/appeal; patient AR runs on statement cycles and household budgets, worked by statements, plans, and placement. A.5 \$128.40 insurance AR — line 1, denied, appeal pending (Chapter 30's workflow) — plus \$17.58 patient AR — coinsurance on lines 2–4, awaiting a statement (Chapter 32's workflow). 128.40 + 17.58 = 145.98 ✓. A.6 It was collected at check-in on day 0; money in the drawer is not a receivable. A.7 "Every day a claim sits, it is worth less." Collectability falls steeply and nonlinearly: a balance pursued in the first 30–60 days collects at a multiple of the rate after 120; agency recoveries return a minority of face value, less the contingency fee. No decimal places because the honest sources give ranges that vary by specialty, payer mix, and study — false precision here is a Tier-2 violation. A.8 Net AR solves the gross-inflation problem by stating AR at expected value — but it requires maintained expected-allowed tables (Chapter 28 §28.8's machinery) and discipline about what "expected" means per payer, or it becomes a second gameable number.

Section B — The aging report

B.9 0–30, 31–60, 61–90, 91–120, 121+ (conventions, in thirty-day steps). B.10 Aged from what date? Split by what? Are credits netted? B.11 Re-aging: the account's age resets on rebill or touch. Defensible for genuinely new obligations (a secondary claim that could not exist before the primary paid); as a default it makes badly worked AR look perpetually young — a diary of clicks, not a measurement. B.12 A credit in an old bucket reduces that bucket, camouflaging exactly the old debits you need to see; and the credits themselves are §31.8–§31.9's compliance problem, which netting hides. B.13 198,400 + 94,850 + 48,200 + 31,150 + 39,700 = 412,300 ✓; over 90 = 31,150 + 39,700 = 70,850; 70,850 ÷ 412,300 = 17.2% ✓. B.14 Because this month's 31–60 is next month's 61–90: working the middle buckets prevents the over-90 number, which is cheaper than curing it. B.15 Compare this month's 31–60 with last month's 0–30 to see whether each bucket drains before it ages forward — the conveyor, not the snapshot. B.16 Innocent: fast payers and disciplined follow-up; a young practice whose AR has not had time to age. Worrying: aggressive write-offs exiting old AR before it can be seen (§31.3's game); re-aging resetting clocks on touch. B.17 It locates money in time. It says nothing about money in space — whose it is, what it is worth net of contractuals, what has been done. That is the queue's job.

Section C — Days in AR

C.18 Total AR ÷ average daily charges. Choices: gross or net of credits (numerator); write-off timing (numerator); denominator window (365-day vs 90-day trailing); and both terms are stated at charges. C.19 Honest: 412,300 ÷ (2,920,000 ÷ 365 = 8,000) = 51.5. Credits netted: (412,300 − 28,600) ÷ 8,000 = 383,700 ÷ 8,000 = 48.0. Ninety-day denominator: 766,500 ÷ 90 = 8,516.67; 412,300 ÷ 8,516.67 = 48.4. Post-write-off: (412,300 − 67,900) ÷ 8,000 = 344,400 ÷ 8,000 = 43.1. C.20 Netting shrinks the numerator with money the practice owes; the practice looks faster because it is holding other people's money — the flattery rewards exactly the failure §31.9 penalizes. C.21 Whatever just happened to charge volume — a strong quarter deflates the metric, a slow one inflates it, and readers hear "collection speed" either way. The 365-day window is more stable; the rule is one window, written down, forever. C.22 The write-off removes old AR from the numerator instantly; nothing on the metric distinguishes that from payment. The write-off report, by category and dollars, must be read beside it. C.23 A uniform fee increase raises numerator and denominator and roughly cancels. Charge-capture failures do not cancel: lost charges shrink the denominator and make collection look slower — the metric is not independent of Chapter 23 §23.9. C.24 Under 40 commonly targeted, under 35 strong (practices; hospitals computed differently). Cautions: verify current sources, and a benchmark was computed under someone else's definitions — use for questions, compare yourself to yourself. C.25 HFMA's standardized revenue cycle metric definitions; they exist because definitional games made cross-organization comparison meaningless. C.26 Credits netted where they were not before; a different denominator window; legacy AR left out of the conversion. Run both computations in parallel across the seam and write the definition down. C.27 Chapter 29: "denial rate" varies by lines/claims, zero-pay/any-adjustment, adjudicated/submitted — Account 10-4471 is 25% by line, 100% by claim. Days in AR has the same disease: one practice, one afternoon, 51.5/48.0/48.4/43.1. C.28 Per §31.11 note [1]: "Gross AR, credits not netted, divided by trailing-365-day average daily charges. Write-offs this period, by category, are reported beside this metric and must be read with it. This definition does not change silently."

Section D — Over-90 and the queue

D.29 The tail: two practices with identical days in AR can have completely different amounts of fossilizing AR, because the metric is an average. D.30 16,400 + 21,300 + 9,850 + 10,600 + 12,700 = 70,850 ✓. Urgency: (1) 12,700 no-activity — losing rights now; (2) 10,600 pre-collection — decision owed; (3) 9,850 appeals — tracked, verify the tracker; (4) 21,300 payer project — managed, keep the pressure; (5) 16,400 payment plans — fine. D.31 The \$12,700 with no activity: appeal windows and filing deadlines burn while it sits. D.32 Old AR with a documented cause and an owner (plans, projects, pending appeals) is a normal portfolio position; old AR nobody can explain is the only kind that represents pure loss in formation. D.33 Low-as-symptom: aggressive write-offs at 90 days produce beautiful aging and an eroding net collection rate. Rising-as-improvement: a practice that starts appealing denials it used to abandon ages while the appeals pend — the aging is the cost of recovering money. D.34 Subtract what is not money: credits → §31.8's dedicated queue; dead items → closed, categorized, counted; unownable items (credentialing, chargemaster, contract loading) → routed to owners. D.35 Deadline (only a date converts recoverable to unrecoverable by itself) · event due (commitments from prior touches) · category (twelve of a kind are one investigation and often one call) · expected value at the allowed amount (the honest tiebreak, kept fourth so big old claims cannot outrank small dying ones). D.36 Because the charge is arbitrary (Chapter 23 §23.7) and the allowed amount is what the claim can actually retrieve; a charge-sorted queue chases sticker prices. D.37 Aging-fed queues meet problems when buckets age; event-fed queues meet them when events fire: acknowledgment gaps (Ch. 27 §27.6), expected-adjudication windows, call commitments, remittance triggers. "An aging report finds money at ninety days; a status event finds the same money at twenty." D.38 All three sort first by the thing that destroys value fastest — for denials and AR alike that is a date, because time alone converts soft to hard (Ch. 29 §29.3) and recoverable to unrecoverable (§31.5). D.39 Dollars resolved per hour and touches per resolution. Counting touches produces touches — the metronome. D.40 Three identical "in process" notes: no pend reason obtained, no date, no reference, no escalation despite a visible pattern by call two. Prescription: §31.6's call discipline, and pre-authorized escalation on the next contact.

Section E — Follow-up

E.41 Portal/276-277 (nearly free; answers "does the payer have it and where is it") → the call (expensive, so purposeful: negotiation, reasons, commitments) → escalation (supervisor · provider relations · project claims · contract remedies · state prompt-pay complaint). E.42 Status and location; they cannot negotiate, explain, or commit — "in process" is most of their vocabulary. E.43 The specific pend reason · whether anything is needed from the practice · a date it will adjudicate by · a reference number · a name — plus pre-authorization to escalate next time. E.44 Refuse it as an answer: "pended for what specifically," "what date," "what happens if it doesn't," then reference number and name. E.45 Lowest. Call documentation is memory for your own next touch and pre-authorization for escalation — not evidence for a payer dispute; for evidence, get a document (reprocessing, written request, portal record). E.46 The payer employee who owns the practice relationship, reachable outside the call center; patterns are theirs ("41 claims pended past your window," as a spreadsheet). A project claim is a payer's batch-handling of a systemic problem — one file instead of 41 calls. E.47 State laws requiring insurers to pay clean claims within defined windows, with interest, enforced by insurance departments. Self-funded ERISA plans generally sit outside state insurance regulation (Ch. 2 §2.5). The ladder's existence changes payer behavior on the rungs below it — a practice that never escalates teaches payers what it tolerates. E.48 A date or a decision. Chapter 32.

Section F — Small balances

F.49 Wage plus payroll taxes, benefits, workstation, software, space, supervision — the full cost of an hour of work. §31.7: \$36.00/hour = \$0.60/minute, a constructed teaching figure; your own comes from payroll and overhead. F.50 All collection-function cost ÷ collections. Low single digits as a percent of collections for practices (Tier 2 — verify). Warning: it improves when you stop doing the work, so never read alone — §31.3's write-off game in a cost hat. F.51 Cycle: 1.75 + (2 × 0.60 = 1.20) = 2.95. Two cycles: 5.90. Threshold: about \$5.00** — the two-cycle cost, rounded, written, uniform. **F.52** \$4.15: 5.90 > 4.15, write off at posting under policy. \$14.85: 14.85 − 5.90 = 8.95 margin — pursue two cycles, then re-decide against the *next* touch's cost. \$2.40 payer variance: 4 minutes of research alone costs 2.40 — do not rebill the instance, but classify it first, because 2.40 × 1,150 = \$2,760.00 is a contract-loading question pursued once at pattern level (Ch. 28 §28.8). **F.53** Compare the remaining balance to the cost of the next touch only; money already spent is spent and is not an argument for spending more. **F.54** Give up on instances, never patterns — the \$2,760 arithmetic; Chapter 28 §28.8's expected-versus-actual comparison is the only measurement that sees it. F.55 So the total by payer and reason can be read — a categorized write-off is data (Ch. 28 §28.6); an uncategorized one is amnesia. The manager, monthly. F.56 Uniform · cost-justified in writing · modest · unadvertised · coexisting with genuine collection effort and documented hardship handling. The Anti-Kickback Statute and the Civil Monetary Penalties Law (beneficiary inducement). F.57 The threshold is a business judgment about your money's pursuit cost. A credit is someone else's money; on federal accounts §31.9 attaches a statute, and the refund's processing cost is not a defense. F.58** Right: pursuit below cost is a donation, and chasing trivial sums does damage goodwill. Dangerous: \$25 by feel, non-uniform, undocumented, possibly covering federal cost sharing, and applied to patterns. The policy: a written threshold derived from actual costs, uniform, with pattern classification before any insurance write-off and hardship screening on the patient side.

Section G — Credits, unapplied cash, sixty days

G.59 A balance below zero. Causes: two primaries paid (COB/crossover) · patient overcollection at the desk · payment posted to the wrong account/line · adjustment posted twice · a reprocessing pair half-posted. Causes 3 and 4 (and 5 when it is mechanical) are posting errors — money owed to no one. G.60 Because the fix differs by diagnosis — corrected posting, patient refund, or payer refund — and refunding before researching sends checks to the wrong parties, turning one error into two. G.61 9,300 + 7,850 + 8,900 + 2,550 = 28,600 ✓. The compliance lines: \$6,140 on federal-program accounts, and the oldest federal credit at 194 days — if any of it is an identified overpayment, the sixty-day clock did not wait for the report. G.62 Money received and banked but never matched to an account (miskeyed online payments; EFT without ERA; unmatchable checks). The cash is safe; the lie is everywhere else — open balances generate statements to people who paid and follow-up on payers who paid, and every AR metric reads high. G.63 ERA/EFT enrolled separately per payer (Ch. 27) — money arrives without its remittance. Fix: complete both enrollments so remittances arrive with their money; put an account number on every payment channel. G.64 A credit balance is what the ledger shows: a negative number. An overpayment is what the law sees once you know why: money you are not entitled to keep. G.65 Report and return within 60 days of identification (or the cost report due date where applicable); after that, the retained overpayment is an FCA obligation (reverse false claim). G.66 Identified: the provider has determined — or should have, with the diligence the current rule requires — that it received an overpayment; quantification is part of the exercise, not a postponement device. Never a defense: declining to look. Instruction: verify the current text of 42 CFR 401.305 with the compliance officer. G.67 A systemic overpayment implies more claims than the ones found, possible conduct issues, and a report-versus-self-disclosure decision that changes protocols and protections — Chapter 37 §37.9. Stop, preserve the analysis, involve compliance and counsel before money or paper moves. G.68 Read the demand: claims, reason, amount, deadline, appeal rights. Verify: pull the six claims and remittances — two show no duplicate payment. Split the response: repay (or allow offset on) the four true duplicates, posted to the original claims; appeal the two disputed ones within the recoupment-pausing window, with the remittance evidence. Log all six; ask what produced four duplicates — the pattern question. G.69 Filing the first-level appeal within the short window in the demand pauses recoupment through the first two appeal levels; that window is days long and separate from the appeal's own longer filing limit — miss it and the offset runs while you appeal. Verify current timelines. G.70 Post refunds and recoupments to the claims they belong to (never as a haircut on the remittance they rode in on); date-stamp identification contemporaneously — what was found, when, how quantified, when repaid.

Section H — Bad debt, charity, dashboard

H.71 Bad debt: could have paid, did not after genuine effort — a collection cost. Charity care: could not pay per the FAP — forgiven, and never properly in collections at all. Therefore: screen before pursuing, always. H.72 Reasonable efforts to determine FAP eligibility — notice, plain-language publicizing, an application window — before extraordinary collection actions: credit reporting, debt sale, lawsuits, liens, garnishment. H.73 Charity buried in bad debt makes collection performance look weak and understates community benefit; bad debt dressed as charity does the reverse and can corrupt cost-report and public reporting figures. Two codes, two reports, two meanings. H.74 Screen every account against the FAP before placement · choose and govern the agency as your agent (FDCPA exposure travels) · set the rules on credit reporting and litigation · reconcile monthly and pull back on new hardship information. Delegation-not-disposal: the agency acts for the practice; the conduct and the consequences remain the practice's. H.75 Paid medical collections and small-balance medical collections removed from bureau reports; longer delays before reporting; further rulemaking in motion. Conclusion: a weakening threat that was always a poor collection tool — verify current status before relying on any of it. H.76 As a refusal (routes to bad debt) or as information (opens the FAP conversation). The protection is the application — documented criteria uniformly applied — not suspicion on the phone; and the screening rule exists for the patient who says nothing. H.77 Definitions printed on the page (Ch. 29 §29.7) · every metric paired with its blind-spot detector (Chs. 23 §23.10, 27 §27.7, 28 §28.6/§28.8) · trend against yourself (Ch. 29 §29.9) · test one story a month against forty rows (Ch. 28 CS1, Ch. 29 CS1) · a person who reads it is the control (Ch. 27 CS1). H.78 Days in AR ↔ blind to surrender ↔ the write-off report. Net collection rate ↔ blind to (raised by) silent underpayment ↔ underpayment variance found. Denial rate ↔ blind to rejections, which never deny ↔ rejection rate. Collections ↔ blind to self-inflicted losses ↔ preventable administrative write-offs. H.79 Because a rate without a definition is not information: Account 10-4471 is 25% by line and 100% by claim, both correct. Printing the definition is what makes the number mean one thing. H.80 The oldest federal credit: 194 days and rising — it carries a statute (§31.9), while 17.2% carries only a benchmark, and its decomposition (page 2) shows most of it known and managed. Story-testing: pull the accounts behind "days in AR improving" and confirm the improvement is drainage, not write-offs — forty rows, one afternoon.

Section I — The Encounter

I.81 Day 17: 0–30 bucket. Day 47: 31–60. Day 62: 61–90. Left AR on day 66 when the second remittance posted. I.82 66 − 17 = 49 ✓ — from the CO-97 denial posting (day 17) to the second remittance paying \$98.40 and moving \$30.00 to patient responsibility (day 66). I.83 No — the aging report is a lagging indicator that would first have flagged the line around day 107, long after resolution. The queue surfaced it twice: the denial event on day 17 (routing into Ch. 29's process, touch 1 on day 20) and the appeal-tracking follow-up event at day 45 (touch 3, Ch. 30 §30.10's tracker). I.84 Staff attention: 58 minutes, stated in minutes (Ch. 29). The rate that converts minutes to dollars: \$36.00/hour = \$0.60/minute, published §31.7. Time value: \$128.40 arrived 49 days after denial, 64 days after submission — float transferred to the payer, no prompt-pay remedy because the payer adjudicated timely. The conversion not performed: minutes × rate — Chapter 40's, exclusively. **I.85** The \$17.58 became patient responsibility on day 17 but was first billed on day 70 (statements held until the account resolves); the patient paid on day 100 — 30 days after being asked, 100 days after service. Date-of-service aging measured the practice's sequencing choice and called it patient slowness. Lesson: every aging number is an answer to "aged from when," and the basis must fit the question being asked. I.86 The 58 minutes across three touches (Ch. 29 §29.10) · the 68% overturn rate (Ch. 29 §29.7) · the \$128.40 allowed amount (Chs. 2, 23, 28) · the \$36.00/hour = \$0.60/minute loaded rate (§31.7). Chapters 1–39 may not multiply the minutes by the rate, divide by the overturn rate, or draw the appeal-versus-prevent conclusion — the assembly is Chapter 40's.


Chapter 32 — Answer Key

Quiz (26 questions)

  1. B — insured when the care was delivered.
  2. B — the allowed amount and the benefit design.
  3. C — \$84.52 (1.78×).
  4. B — a polyp found and removed converts the procedure to diagnostic.
  5. C — uninsured and self-pay patients.
  6. B — billed substantially more than the good faith estimate.
  7. C — the difference between the charge and the allowed amount.
  8. B — the anesthesiologist; the ancillary list can never consent.
  9. C — a qualified payment amount or applicable state law.
  10. C — the plan and the provider.
  11. B — not yet reached by the federal act; state law governs.
  12. D — individual patient out-of-pocket history is not in the file.
  13. B — a compliant online price-estimator tool.
  14. B — \$47.58 responsibility, a \$30.00 credit, \$17.58 due.
  15. B — the visible credit line.
  16. C — the balance was not final until day 66.
  17. C — "what if I can't pay this?"
  18. B — must not be placed, reported, or escalated.
  19. A — recourse, and what the patient signs.
  20. D — §501(r) does not require forgiving all balances.
  21. B — the likeliest qualifiers are the least likely to complete an application.
  22. C — a potential Anti-Kickback / beneficiary-inducement problem.
  23. A — third-party debt collectors.
  24. C — financial assistance and presumptive-eligibility screening.
  25. B — the opening of a negotiation the caller does not know they are allowed to have.
  26. C — before the injection was performed, from information already in the system.

Exercises

Section A — The patient as payer

A.1 Eligibility verification → the estimate · remittance advice → the statement · the payer contract → the payment plan · the coverage policy → the financial assistance policy. A.2 \$503.00** = \$250.00 ED copay + \$189.28 (20% of the remaining facility allowed, 1,196.40 − 250.00 = 946.40) + \$63.72 (20% of the professional allowed \$318.60). Check: 250.00 + 189.28 + 63.72 = 503.00 ✓ A.3 Statement still in the mail · wrong address · a contradicting EOB · a bill not understood · a bill understood and unpayable. Same symptom, five root causes, no reason code. A.4 The insured. Deductibles/coinsurance on large allowed amounts, surprise out-of-network gaps (pre-2022), and revenue cycle errors — the five case studies (observation stay, maternity package, standing order, drifted authorization, returned envelope). A.5 Structural: no contract obligates the patient and no remittance explains nonpayment. Behavioral: a payer's obligation survives its forgetting; a patient's willingness decays with time, confusion, and distance from the care. A.6 Ch. 16 CS1 (observation), Ch. 18 CS1 (maternity global), Ch. 19 CS1 (standing order), Ch. 22 CS1 (drifted authorization), Ch. 24 CS1 (returned envelope). Thread: the revenue cycle's failures land disproportionately on people who cannot see them coming and have no leverage when they arrive. A.7 A patient who understands a bill and can manage it pays it; one who is confused or frightened calls, delays, and defaults. So the respectful design — estimate, honest statement, offered plan, mentioned FAP — is also the one that collects more at lower cost. A.8** E.g.: "Most patients who don't pay were never given what a payer gets automatically — a price in advance, an explanation in plain words, and terms they could meet. Most medical debt belongs to people who had insurance and did everything right. Before we call it a choice, we should check whether we ever made paying possible."

Section B — Estimates

B.9 The planned service · the contracted allowed amount · the benefit design (from the 271) · the year-to-date accumulators — the last is invisible to the practice (the 271 lags). B.10 The allowed amount; the charge is not what anyone pays (Ch. 1 §1.2, Ch. 23), so cost sharing computed from it is fiction. B.11 Deductible met: 78.60 × 20% = 15.72; 6.28 × 20% = 1.26; \$16.98**. Not met: the full allowed, 78.60 + 6.28 = **\$84.88. Checks: 15.72 + 1.26 = 16.98 ✓ · 84.88 ÷ 16.98 ≈ 5 — the five-fold swing from one lagging field. B.12 Plain-language service names with codes · the allowed-amount arithmetic shown · the benefit inputs dated · the specific assumptions that could move the number · the setting · the translated contractual adjustment ("you never owe it") · a phone number worth calling before the visit. (Any five.) B.13 Provider-based departments bill twice and cost sharing rises: \$47.58 vs. \$84.52, difference \$36.94** (≈78% more). *Check: 84.52 − 47.58 = 36.94 ✓* **B.14** "Is that clinic provider-based?" If yes: the patient will receive two claims, and their share will likely be materially higher — both facts owed before the visit, not on the statement. **B.15** "If a polyp is found and removed, the procedure becomes diagnostic, and cost sharing may apply that would not apply to a screening alone." Account **22-9107** — the promised-free screening that produced a bill. **B.16** ICD-10-CM October 1 · CPT January 1 · HCPCS Level II and NCCI quarterly · fee schedules annually. A stale claim costs the practice a denial; **a stale estimate costs the patient's trust in every future number the practice states.** **B.17** Any faithful version of Ch. 24 §24.9's sentence: "Based on what we know today, your share should be around \$17. If the deductible situation is different than our check showed, or the doctor does something more, that changes — and the statement will show you exactly how it was figured." B.18** Because the patient sees a \$150.72 gap between charge and allowed and, untranslated, reads it as either an error or a threat; the line prevents the "why was I charged \$367?" call. (For the injection-only figure the same logic applies at its scale.)

Section C — The No Surprises Act

C.19 Balance billing bills the difference between charge and allowed — above the allowed amount. Cost sharing (copay, deductible, coinsurance) lives inside the allowed amount. C.20 In network — by contract (payment-in-full clause; Ch. 2 §2.3). Medicare — participation/assignment rules and the limiting charge (Ch. 3 §3.4). Medicaid — program billing restrictions (Ch. 3 §3.7). C.21 Uninsured and self-pay patients. The advanced explanation of benefits for insured patients is in the statute but awaits rulemaking — verify current status. C.22 Description of the primary service · itemized expected items/services · applicable codes · expected charges · provider identity · required disclaimers (estimate-not-contract; dispute process). C.23 Patient-provider dispute resolution: an uninsured/self-pay patient billed substantially above the GFE (defined threshold — verify) takes the bill to an IDR entity, which can hold it toward the estimate. C.24 Emergency services (through stabilization) · out-of-network providers at in-network facilities · air ambulance. Ground ambulance is not yet covered federally. C.25 The qualified payment amount — in general terms the plan's median contracted rate for the service in the area — the usual basis for the protected patient's in-network cost sharing. C.26 For the patient who genuinely chooses an out-of-network provider. Never: emergency services before stabilization · the ancillary specialties · where no in-network alternative exists at the facility. C.27 Anesthesiology is on the ancillary list for which consent is categorically unavailable — the patient cannot meaningfully choose their anesthesiologist, so the law does not let a form pretend they did. C.28 Plan versus provider; baseball-style (each submits an offer, the arbitrator picks one); the patient's liability was already fixed at in-network cost sharing, so nothing in IDR concerns them. C.29 Wrong basis (charge, not QPA/state standard) · likely an illegal balance bill if anything above in-network cost sharing is claimed · violation exposure with a federal complaint process. Cost sharing should be computed from the QPA or applicable state law, at in-network levels. C.30 A statement-side edit that flags any patient balance on a claim meeting protection criteria (emergency POS, OON provider + in-network facility, air ambulance) that exceeds the in-network cost-sharing calculation — stopping the statement the way a scrubber stops a claim.

Section D — Price transparency

D.31 The machine-readable file of all standard charges and the consumer-friendly shoppable-services display. Five charge types: gross charge · payer-specific negotiated rate · de-identified minimum · de-identified maximum · discounted cash price. D.32 A service that can be scheduled in advance; a compliant online price-estimator tool can substitute for the display. D.33 Widespread early shortfall (missing files, missing rates, unusable formats) → warning letters → corrective action plans → escalating civil monetary penalties scaled to hospital size, with penalty notices published. D.34 Plan-side machine-readable files and member cost tools; the negotiated rate is public from both the hospital's and the payer's side. D.35 Answer patients honestly · audit your own file (Ch. 26 §26.5's chargemaster errors are now published errors) · read the market (expected-allowed data for §28.8, comparators for §23.6). D.36 §23.8's caller — someone who understood the system correctly. The wrong reception is defensiveness; the right one confirms the observation, explains the mechanism, and offers the cash price and the FAP. D.37 Expected allowed amounts and comparator rates now exist in bulk for your own and competitors' contracts — the underpayment method gains a data source and the negotiation gains a benchmark.

Section E — The statement

E.38 Who is billing me · what was it for · what did insurance do · what have I already paid · what do I owe now · what if I can't pay it · how do I pay or ask. The sixth is omitted — and its absence sends the patient who cannot pay into silence and the account into aging. E.39 Responsibility \$47.58** · credit **\$30.00 (day-0 copay) · **\$17.58 due** · issued **day 70** (Tue, May 23). *Check: 30.00 + 15.72 + 1.26 + 0.60 = 47.58; 47.58 − 30.00 = 17.58 ✓* **E.40** The visible credit line — "Payment received March 14 — thank you: −\$30.00." It reconciles the three documents the patient may hold (EOB \$17.58, responsibility \$47.58, check-in receipt \$30.00). Payer-side twin: **item 29** (Ch. 25) — omitting the copay asks the payer for money already collected; a credit-less statement asks the patient. **E.41** The appeal was pending; the balance went final only when the second remittance posted on day 66 (Ch. 28 §28.11). A day-20 statement would have billed a copay on a visit line the payer had not paid — and the day-66 remittance would have contradicted it, teaching the patient the practice's numbers are provisional. **E.42** Never before the remittance posts (prevents billing a number the patient does not owe) · promptly once final (prevents pure aging and emotional distance from the care). **E.43** A bill for named services on a date is a fact that can be checked; codes alone make the patient take the amount on faith — and patients do not extend that faith. **E.44** Each must name its biller, say the physician and facility bill separately, and reference the same visit — otherwise the second statement reads as a duplicate (Ch. 16 §16.9's warning). **E.45** The charge is the number the EOB also showed prominently; the patient concludes they owe it, or that the practice inflated it — Ch. 28 §28.2: the largest number on the page is one nobody will pay. **E.46** *(Graded on: all seven questions present; credits shown; assistance line unconditional; services in words; insurance activity summarized; issue-timing note.)* **E.47** Estimate expectations set at check-in (\$30.00 collected) · statement held until final · all three numbers reconciled on one page · services named · credit visible · assistance line present · thirty-day payment with no call — the cheapest collection event in the cycle.

Section F — Plans and assistance

F.48 Terms in writing · a floor the patient names and keeps · automated installments where consented · the collection machinery frozen while current. F.49 Eleven at \$36.61 + one at \$36.57: 11 × 36.61 = 402.71; 402.71 + 36.57 = 439.28F.50 Each cycle costs real money to render and post (Ch. 31 §31.7's arithmetic from the other side); but a floor above capacity is a plan designed to fail — a defaulted plan costs more than a smaller kept one. F.51 Is there recourse (does the practice buy back defaults)? What does the patient sign? Deferred interest: "zero percent — unless any balance is left at the end, in which case interest is charged on the whole amount, backdated, at a high rate." F.52 Frozen: no placement, no reporting, no escalation. A patient keeping a promise must never be processed as one breaking it. F.53 A written FAP with criteria and application method (plus plain-language summary) · wide publicity · charges to eligible patients limited to amounts generally billed · reasonable efforts to determine eligibility before any ECA. F.54 Against the chargemaster being the uninsured patient's price — Ch. 23 §23.8's patient, for whom the gross charge was the bill. AGB ties the ceiling to what insurers actually pay. F.55 An ECA: credit reporting, selling the debt, lawsuits, liens, garnishments. Reasonable efforts to determine FAP eligibility, on the regulated notice-and-application timetable, must precede them. F.56 Granting assistance without an application, from data: means-tested enrollment, prior determinations, credit-derived distress indicators, returned mail (also homelessness, deceased-no-estate). The application fails its targets because poverty, illness, and displacement destroy capacity for paperwork — every barrier filters out exactly the intended population. F.57 Anti-Kickback Statute and the CMP beneficiary-inducement provisions: a routine waiver looks like an inducement and misstates the actual charge. Compliant path: individualized, documented, need-based determinations under a uniform written policy — or a genuine failed collection effort. F.58 Estimate before the service (expectations) · assistance stated on every statement (the drawer problem) · presumptive screening before placement (so charity care is never chased as bad debt — the Ch. 31 §31.10 distinction, applied in time to matter).

Section G — Collections

G.59 The FDCPA governs third-party collectors; it generally does not reach the original creditor in its own name. State statutes fill the gap — and behaving as if the FDCPA applied is rarely wrong. G.60 Paid medical collections removed; small medical balances unreported; a year's waiting period; further federal rulemaking attempted and litigated. A strategy premised on credit-report leverage is increasingly premised on nothing — and it was always the crudest tool. G.61 Written agreement limiting permitted actions · scrubbed placements · recall rights, exercised · complaint reporting read by someone with authority · periodic conduct audit at Ch. 37's standard. G.62 Balances in active dispute · on a current plan · pending an FAP determination · protected under the No Surprises Act. G.63 A payment-likelihood score from payment history, balance, coverage, and credit data. Direction one: pressure routed by score. Direction two: assistance screening routed by score. §32.8 requires the second first, because financial distress predicts both nonpayment and FAP eligibility — the same signal, two readings. G.64 The remittance shows recovery minus a contingency fee consuming a third or more. Missing: the lost patient and family (revenue is a stream of visits), the decade-lived review, the complaint, and the staff who updated their view of the mission statement. G.65 Because collections is downstream failure: every placed account is an estimate not given, a statement not understood, a plan not offered, a screen not run — Ch. 29's prevention argument with a person attached. G.66 Chapter 26 — the discharge-status file, detectable from a claims distribution outside before anyone inside could see it. (Ch. 23 CS2's due-diligence finding also accepted.)

Section H — Explaining the bill

H.67 Their document first · the services in words · the four numbers once · every credit out loud · answer the fear behind the question · never defend the system / blame the patient / dodge via the payer · one concrete next step, kept. H.68 Because the caller's footing depends on their document being taken seriously; an explainer working from the account view corrects the caller instead of orienting them, and the call becomes an argument about whose paper is real. H.69 (Graded on: fear defused first; \$3,842.00 identified as the pre-insurance charge, never owed; \$439.28 decomposed as 250.00 + 189.28; second bill explained as the physician's separate claim, \$63.72; \$503.00 stated as final and complete; plan and FAP offered unprompted; no jargon; checks foot.) H.70 (Graded on: caller's premise confirmed — screenings are covered without cost sharing; polyp removal explained as the conversion, and as good medicine; phase-down stated with the verify-current caveat, \$153.00 vs. \$204.00 at the illustrative percentage; no blame anywhere; the §32.2 sentence acknowledged as what should have happened.) H.71 (Graded on: "No — the denied amount is not yours" stated early; CO explained as the payer-practice lane, patient may not be billed; the appeal mentioned as in progress; no statement until the balance is final; what the patient will eventually owe — \$47.58 total responsibility less the \$30.00 already paid — previewed honestly.) H.72 Never defend the system ("that's how insurance works") · never blame the patient ("you should have checked your plan") · never dodge via the payer ("that's your insurance company's problem — call them"). H.73 The opening of a negotiation the caller does not know they are allowed to have. The person who understands it offers the two doors — the plan and the assistance screen — before being asked.

Section I — The Encounter

I.74 Day 70 (Tuesday, May 23): responsibility \$47.58, credit \$30.00, due \$17.58. Paid day 100 (Thursday, June 22). **I.75** At scheduling: \$30.00 copay + \$0.60 venipuncture coinsurance = \$30.60, plus the change-sentence. In the room, before consent: injection + drug at 20% of \$84.88 allowed = \$16.98. Check: 30.60 + 16.98 = 47.58 ✓ I.76 The injection was decided during the visit — Ch. 24 §24.9 established no desk estimate could include it; the procedure note (Figure 4.2's consent discussion) records the in-room decision. I.77 No — she is insured, and the statutory GFE reaches the uninsured and self-pay (the insured advanced-EOB awaits rulemaking; verify current status). It does not matter because every number was in Northgate's system on day 0; the missing element was the habit of saying them, not a legal obligation. I.78 A check-in receipt for \$30.00 (day 0), then payer EOBs (first remit ~day 17 showing \$17.58 of coinsurance amid a denial that was not her problem; second after day 66) — and nothing from the practice until day 70. The sequence invites "insurance says \$17.58, you say \$47.58" — Ch. 28 §28.2's staged call. I.79 Charges \$367.00 · allowed \$216.28 · plan \$168.70 · patient \$47.58 · adjustment \$150.72 · balance \$0.00 on day 100. Open: Q4 — could the denial have been prevented, and was it worth fighting? — answerable only by Chapter 40.


Chapter 33 — Answer Key (daggered † and odd-numbered exercises)

The quiz's own answer key lives in quiz.md's collapsed block. Everything below uses the book's constructed teaching figures; all real-world values expire annually — verify in the current IPPS final rule.

Exercise 33 — A.1 (odd)

Before: for its reasonable costs — the hospital spent, reported, and was reimbursed. Since: for the classified stay — one predetermined amount per discharge, set by the MS-DRG the coded record groups to.

Exercise 33 — A.3 (odd)

At minimum two claims. The institutional claim (UB-04/837I), paid under IPPS by DRG — Chapters 26 and 33 — and at least one professional claim (CMS-1500/837P) for the physicians' services, paid under the fee schedule logic of Chapter 23. One encounter, two payment machines — Chapter 16 §16.9's split at full scale.

Exercise 33 — B.5 † (odd)

The cholecystitis. The deciding words are "established after study" (with "occasioning the admission" doing the rest): the pain is what the patient presented with; the cholecystitis is what the workup established as the reason the admission was needed. The pain is an integral symptom of the established condition and is not separately reported (Ch. 9 §9.6). (The surgery also flips the grouper's surgical partition — but that is a payment consequence, not a reason for the sequencing.)

Exercise 33 — B.7 † (odd)

The discretion: where two or more conditions each meet the principal diagnosis definition and neither the circumstances of admission, the workup and therapy, the Tabular's conventions, nor the Guidelines' sequencing instructions establish one over the other, either may be sequenced first. What bounds it: the discretion exists only when the record genuinely supports co-responsibility — here the physician documented "admitted for management of both," both POA, both treated — and any applicable chapter-specific sequencing instruction (respiratory failure has such guidance; read the current text) is checked first. What rides on it: the choice selects the DRG family — the COPD family (190–192) or the heart failure family (291–293) — and the two families price differently. That is why the discretion must be exercised from the record and documented reasoning, never from the weights: choosing by payment is selection the record does not support.

Exercise 33 — B.9 (odd)

The definition requires the condition to have occasioned the admission — a day-3 condition occasioned nothing; the admission predates it. The claim tells the payer when it arose through the POA indicator: the day-3 condition reports POA = N.

Exercise 33 — C.11 † (odd)

Part one: nothing — the MCC already sets the tier, and severity does not stack; dropping or keeping the CCs leaves this claim's payment identical. Part two, the three reasons they stay: (1) Section III makes conditions that were evaluated and treated reportable — completeness is the coding standard, not payment relevance; (2) the full record feeds the case mix index, quality measurement, and risk adjustment (Ch. 36), all of which read what payment ignores; (3) the record's integrity is the audit defense — a claim trimmed to its payment-relevant codes is a claim that has been edited by an incentive, which is exactly the pattern reviewers look for.

Exercise 33 — C.13 (odd)

The MCC is J96.01 — acute respiratory failure with hypoxia — POA = Y, producing the "with MCC" tier: DRG 190. Absent that code, with at least one documented CC remaining, the stay would group to the "with CC" tier — DRG 191 — this book's \$1,867.44 step (§33.5, §33.10).

Exercise 33 — D.15 † (odd)

The correction: a surgical DRG is defined by the presence of an OR-designated procedure code, not by whether surgery colloquially happened or where. The deciding inputs are the ICD-10-PCS procedure codes on the institutional claim and CMS's OR designation for them in the MS-DRG Definitions Manual — some bedside procedures carry the designation, some OR-performed procedures do not, and the CPT code on the professional claim plays no role in the grouping.

Exercise 33 — D.17 (odd)

(1) Pre-MDC check: not a transplant/tracheostomy case — pass. (2) MDC: principal J18.9 maps to the respiratory MDC. (3) Surgical partition: no OR-designated procedure — medical path; within it the principal diagnosis selects the simple pneumonia and pleurisy family (193/194/195). (4) Severity split: no MCC, no CC among the secondaries → DRG 195, simple pneumonia and pleurisy without CC/MCC.

Exercise 33 — E.19 † (odd)

Weight × \$6,200.00
1.1015 \$6,829.30
0.8003 \$4,961.86
0.6555 \$4,064.10

Differences: 6,829.30 − 4,961.86 = \$1,867.44 (the MCC's value, 190 vs 191) · 4,961.86 − 4,064.10 = \$897.76 (the CC's value, 191 vs 192) · 6,829.30 − 4,064.10 = \$2,765.20 (the full spread). Check: 1,867.44 + 897.76 = 2,765.20 ✓

Exercise 33 — E.21 † (odd)

Labor share at the new market: 4,216.00 × 1.1000 = \$4,637.60. New base rate: 4,637.60 + 1,984.00 = \$6,621.60**. DRG 190 there: 6,621.60 × 1.1015 = **\$7,293.69. Checks: 4,637.60 + 1,984.00 = 6,621.60 ✓ · 6,621.60 + 662.16 (×0.1) + 9.93 (×0.0015) = 7,293.69 ✓ Interpretation: the same DRG, the same patient, a different labor market — only the base rate moved.

Exercise 33 — F.23 † (odd)

Sum of weights: 1.1015 + 1.1015 + 0.8003 + 0.6555 + 2.4500 = 6.1088. CMI = 6.1088 ÷ 5 = 1.2218 (1.22176). Average payment = 1.22176 × 6,200.00 = \$7,574.91. Cross-check by individual payments: 6,829.30 + 6,829.30 + 4,961.86 + 4,064.10 + 15,190.00 (= 2.4500 × 6,200.00) = 37,874.56; ÷ 5 = \$7,574.91

Exercise 33 — F.25 (odd)

"Raise the CMI" hands the coding department a target it can move by only two paths — legitimate capture of documented severity, or capture past what the record supports — and it rewards both identically, which is how DRG creep programs are born (Case Study 2). The legitimate instruction underneath it: "ensure the coded record captures all the severity the documentation supports — in both directions — and close documentation gaps through compliant queries." That version moves the CMI only as a side effect of accuracy, which is the only movement that survives an audit.

Exercise 33 — G.27 † (odd)

(a) Y — conditions arising during the outpatient ED encounter, before the inpatient admission order, count as present on admission. (b) N — the admission skin assessment affirmatively documents intact skin; the day-2 finding is hospital-acquired on this record's own chronology. (c) W — the provider was asked and answered that onset is clinically undeterminable; W reports exactly that and is treated like Y. (U would have been the answer only if the documentation were insufficient and a query had not resolved it.) (d) Exempt — external cause codes are on the POA-exempt list; no indicator is reported.

Exercise 33 — G.28 †

(a) The CAUTI is on the HAC list with POA = N, so it cannot serve as the MCC; the severity split runs on what remains — one documented CC — and the stay lands in the "with CC" tier. (b) In the stand-in arithmetic: with-MCC would have paid \$6,829.30; the with-CC tier pays \$4,961.86; the HAC provision's consequence on this claim is **\$1,867.44. (c) The response: "The POA indicator reports the record's clinical chronology, and this record's admission assessment answers the question — I can't revisit an indicator because of its payment effect. If you believe the timing is genuinely unclear clinically, the compliant path is a query to the provider that asks the open question and accepts any answer." Chapter 38 §38.3 governs that query. (Changing the N for the money would be a false statement on a federal claim — Ch. 5.)

Exercise 33 — G.29 (odd)

The HAC payment provision (DRA 2005) works claim by claim through the POA indicator: a HAC-list condition with POA = N or U cannot serve as a CC/MCC on that claim's severity split. The HAC Reduction Program (ACA) works hospital by hospital: it reduces overall payment by a percentage for hospitals in the worst-performing quartile on hospital-acquired-condition measures. One mechanism prices a claim; the other grades an institution.

Exercise 33 — H.30 †

AMLOS = (2 + 3 + 4 + 5 + 26) ÷ 5 = 40 ÷ 5 = 8.0 days. GMLOS = (2 × 3 × 4 × 5 × 26)^(1/5) = 3,120^(1/5) ≈ 5.0 days (since 5⁵ = 3,125). The one 26-day stay dragged the arithmetic mean to a value that describes no patient in the set, while the geometric mean stayed beside the cluster where the typical case lives. The payment rules key on the geometric mean because it is the honest "expected stay" for the ordinary case — an average meant for pricing must not be steered by the outliers that outlier policy handles separately.

Exercise 33 — H.31 † (odd)

(a) Discharge status 02 (acute-to-acute transfer) and LOS 3 ≤ GMLOS − 1 = 4.0 → the rule applies. (b) Per diem = 9,300.00 ÷ 5.0 = \$1,860.00**; day 1 doubled = **\$3,720.00; total = 3,720.00 + 1,860.00 + 1,860.00 = \$7,440.00. Check: 7,440.00 < 9,300.00 ✓ (c) A 5-day stay is not at least one day below the GMLOS, so the transfer policy does not apply and the hospital is paid the full \$9,300.00. And the cap is why the answer could never exceed that: had the per diems been computed anyway (3,720.00 + 4 × 1,860.00 = 11,160.00), payment is the lesser of the per-diem total and the full DRG — a transferring hospital is never paid more than a discharging one.

Exercise 33 — H.33 (odd)

The outlier payment begins only after the hospital's estimated costs exceed the DRG payment plus an annually set fixed-loss threshold, and beyond that point covers only a percentage of the excess. Estimated costs are derived from the claim's charges through the hospital's cost-to-charge ratio — the one place the inpatient claim's charge lines touch payment. Because the hospital absorbs the full fixed-loss amount before the first outlier dollar and continues sharing costs after it, an outlier stay always ends at a loss relative to costs — the policy trims catastrophe; it does not reward it.

Exercise 33 — I.35 † (odd)

0DTJ4ZZ: 0 = Medical and Surgical section · D = gastrointestinal body system · T = Resection (cutting out all of a body part) · J = appendix · 4 = percutaneous endoscopic approach · Z = no device · Z = no qualifier — the classic laparoscopic appendectomy teaching example. If the operative report documented removal of only a portion of the structure, the character to review first is the third — the root operation — because the documented objective would then be Excision (a portion), not Resection (all): that boundary is the most-tested distinction in PCS, and the body-part definitions in the PCS tables decide which side a given anatomy falls on.

Exercise 33 — J.37 (odd)

Defensible: reviewing records that grouped without an MCC is a legitimate audit starting point — under-capture concentrates there (§33.3's reversed loss), and finding documented-but-uncoded severity is exactly what review is for. Not defensible: querying only where the answer would raise payment, and compensating the activity on the CMI. A one-directional query stream tied to a payment metric is a severity-harvest program — Case Study 2's enforcement pattern — regardless of how compliant each individual query reads. The rewrite: "We will audit a sample of admissions across all severity tiers for agreement between documentation and coded severity. Where documentation supports severity that was not captured, we will code it; where coded severity is not supported, we will correct it, including corrections that lower the DRG. Where documentation is ambiguous in either direction, we will issue compliant, non-leading queries per policy (Ch. 38 §38.3), track query rate, agreement rate, and direction, and report all three to compliance quarterly. No individual compensation will be tied to CMI." The distinguishing feature is bidirectionality with evidence — a program that can show an auditor its down-queries is a documentation-integrity program; a program with none is a creep program with better stationery.

Exercise 33 — J.39 (odd)

C. The severity tier selects a different MS-DRG with a different relative weight, and payment is weight × base rate — the only choice that changes either factor. (A) and (B) change nothing within the ordinary range: the payment is prospective and charge-independent (charges reach payment only through the outlier computation, which "within the ordinary range" excludes). (D) is paid separately, on a professional claim, under a different system entirely.

Exercise 33 — J.40 †

The coder's summary (counterfactual lens; the real Account 10-4471 is unchanged): Principal diagnosis — the right hip fracture, a code from the S72.- category for the documented site, with seventh character A (initial encounter — Ch. 12 §12.4); this book's roster carries no specific S72 code and the category-level answer is the correct discipline. External cause story: W19.XXXA (unspecified fall, initial encounter) and Y92.009 (place of occurrence), POA-exempt. Secondaries under Section III, all POA = Y: E11.9, I10, E78.5 — evaluated and managed during any surgical admission (home medications continued, perioperative monitoring). The CKD 3a problem-list entry is reportable only if this stay documents engaging it — and per this book's canon, no diabetes–CKD linkage may be coded or assumed (that is Chapter 36's, and the stay's record would have to establish it through the provider). The procedure: reported by the hospital in ICD-10-PCS — structurally, a Medical and Surgical section code whose root operation is Replacement if a prosthesis took the joint's place, or a different root operation for internal fixation; either carries OR designation, which is the load-bearing fact. The grouper step it changes: the surgical partition — the stay takes a surgical DRG family. The resulting shape: with her chronic, stable secondaries and nothing of MCC gravity, the severity split lands without MCC — the shape of MS-DRG 470 (major hip and knee joint replacement without MCC) if the repair is a replacement. Why it cannot be priced, two sentences: She is commercially insured, and whether Northfield pays this admission by MS-DRG, per diem, or a negotiated case rate is a term of the hospital's contract (Ch. 2 §2.6) — not derivable from the chart. And even under Medicare logic, DRG 470's current weight is an annual published value this book deliberately does not fake — the classification is the coder's; the price belongs to the contract and the current year's table.


Chapter 34 — Answer Key (daggered † and odd-numbered exercises)

The quiz's own answer key lives in quiz.md's collapsed block. Everything below uses this book's constructed teaching figures. Every real-world value expires: OPPS rates, weights, packaging thresholds, and status indicators annually by rule; the Outpatient Code Editor and the NCCI edits quarterly. Verify at the source.

Exercise 34 — A.1 (odd)

OPPS: the unit of payment is the service, grouped through its HCPCS code to an ambulatory payment classification. The Medicare Physician Fee Schedule: the unit is also the service, but it is priced individually from its own relative value units rather than grouped (Ch. 23). IPPS: the unit is the classified stay — one MS-DRG for the whole admission (Ch. 33).

Only IPPS lets the diagnosis codes set the price: the principal diagnosis maps the major diagnostic category and the secondary diagnoses drive the severity split. Under OPPS and under the fee schedule, the diagnosis justifies and the procedure code prices — medical necessity is the diagnosis's whole job there (Chapter 22's apparatus applies in full force), and a coder who brings Chapter 33's diagnosis-weighting instincts to an outpatient chart will over-invest in the diagnosis list and under-invest in the procedure codes, units, and modifiers.

Exercise 34 — A.2 †

Reason one, prospective. APC relative weights are recalibrated every year from hospitals' own claims and cost data, and packaged charges are part of that data. A facility that stops reporting charges on packaged items is systematically arguing its own future rates down. This year's packaged charge is an input to a future year's weight.

Reason two, internal. The chargemaster (Ch. 23 §23.8) and the cost report still need the resource truth. The claim is not the only thing reading those lines.

Chapter 33 §33.1 made the identical argument for charges on an inpatient claim under DRGs, where the payment likewise does not read the charge lines. The argument transfers whole.

Exercise 34 — A.3 (odd)

Clinical laboratory tests (their own fee schedule), therapy services (their own), and ambulance (its own) — all furnished by the hospital outpatient department and none priced by OPPS. The announcing letter is status indicator A: right building, different machine. The line pays, with that other system's rules riding along; reconcile it against that schedule, not against Addendum B.

Exercise 34 — B.5 † (odd)

  LINE  SI   WHAT IT IS                            WHAT THE BILLER DOES
   1    V    paid separately (its own visit APC)   post the payment; it generates coinsurance
   2    T    paid separately, discounting applies  predict FIRST: if another T is on the claim,
                                                   the lower-rated one pays 50% — a "shortfall"
                                                   that is the rule, not an underpayment
   3    N    packaged — never pays on its own      post as a contractual outcome; do not queue
                                                   it as a refusal, do not appeal it, and do not
                                                   let anyone strip the charge next time
   4    Q1   conditionally packaged                do not adjudicate this line alone — read the
                                                   whole claim; packaged if an S/T/V service
                                                   shares the date, otherwise separately payable
   5    A    paid, but not under OPPS              expect a different allowed amount and a
                                                   different rulebook; reconcile against that
                                                   fee schedule
   6    C    inpatient-only — not payable here     escalate immediately; the surgical episode's
                                                   payment fails with it, and the error was made
                                                   at scheduling, not at coding

Exercise 34 — B.7 (odd)

The two lines meet conditional packaging — the Q family of status indicators (Q1 for the venipuncture-class line, Q4 for conditionally packaged laboratory tests). On the claim that also carries a surgical procedure, both package: their money is inside the procedure's rate. On the claim that carries nothing else, the same codes may pay separately, and the laboratory line pays under the clinical laboratory fee schedule rather than under OPPS at all.

The discipline: an outpatient facility claim must be read as a whole document — the same discipline Chapter 26 §26.10 taught for the UB-04, now with money attached. A line's fate is decided by its neighbors.

And the corollary that matters more: splitting one encounter's services across two claims to un-package them is not a workaround, it is a false claim — the same-session logic of Chapter 21 §21.6, here enforced by a letter.

Exercise 34 — B.8 †

The two-times rule: within an APC, the highest-cost significant item may not cost more than twice the lowest, with defined exceptions CMS must justify.

The visible consequence: APC families come in levels — level 1 through level 5 emergency department visit APCs, levels of skin procedures, levels of imaging, levels of gastrointestinal endoscopy. The rule forces cost-dissimilar services apart even inside one clinical family.

What "a level 4 gastrointestinal endoscopy APC" asserts: the family is GI endoscopy, and the level reflects that a snare polypectomy costs the facility more to support than a diagnostic look. 45385 and 45378 are the same clinical family and different resource levels — and the level travels with the HCPCS code, not with the diagnosis, the patient, or the indication.

Exercise 34 — B.9 (odd)

What it means: status indicator C marks a procedure on the inpatient-only list — one Medicare pays for only when furnished in the inpatient setting.

What it does: the line is not reduced and not repriced. It is not paid, and as a rule the payment for the whole surgical episode fails with it.

Where it must be prevented: at the scheduling desk, when the case is booked. The list is public and the lookup takes seconds.

Why the coder is the wrong control: by the time a coder sees status C, the preventable error has already been committed. The procedure has been performed, the patient cannot be retroactively admitted, and Chapter 16 §16.3's two-midnight framework governs what an admission would have required in the first place. This is the rare failure where prevention is not merely better than collection — it is the only move that exists.

Exercise 34 — C.11 † (odd)

   REV   DESCRIPTION            CODE     CHARGE     ALLOWED
   0450  Emergency room         99284   2,485.00     742.00
   0270  Med/surg supplies        —       318.00       0.00  (packaged)
   0250  Pharmacy                 —        96.00       0.00  (packaged)
   0300  Laboratory               —       243.00      62.40
   0320  Radiology — diagnostic  73090     700.00     392.00
   0001  TOTAL                           3,842.00   1,196.40

   checks:  2,485.00 + 318.00 + 96.00 + 243.00 + 700.00 = 3,842.00 ✓
            742.00 + 0.00 + 0.00 + 62.40 + 392.00       = 1,196.40 ✓

The three sentences. "Two of those lines carry real charges and allowed exactly zero because their money is already inside another line — the suture tray, the gauze, the lidocaine, and the tetanus toxoid were paid for inside the \$742.00 the visit line allowed. The remark on them says packaged, and packaging is a pricing method, not a refusal: nothing was adjudicated against us, nothing is appealable, and there is nothing on the claim to correct. Post them as a contractual outcome, leave the charges on the claim next time, and keep them out of any metric that counts refusals."

Exercise 34 — C.13 (odd)

The test: what payment method sits behind this line? Not what the reason code says — the same CO-97-family code announces both situations.

On Account 10-4471, the line was a professional E/M with modifier 25, and the payer's bundling decision was an adjudicated refusal of a service that had its own allowed amount: appealable, and in fact overturned on the documentation (Ch. 30). On an outpatient facility claim, a supply line under a packaging method is a priced line whose price is zero by design: there is no separate allowed amount to fight for, because the money is already in another line's rate.

Same letters, opposite dispositions. The question the test is actually asking is: is there a separate allowed amount that the payer declined to pay, or is there no separate allowed amount at all?

Exercise 34 — C.14 †

Five categories OPPS packages: (1) supplies used in a procedure; (2) drugs below the annual per-day cost threshold; (3) anesthesia, recovery, and observation associated with a procedure; (4) imaging guidance; (5) add-on services in various defined categories. (And, under §34.6's comprehensive APCs, nearly everything adjunctive to the biggest procedures.)

The flippable one: drugs. The per-day cost threshold is set each year by rule, and a drug's price moves. A drug that packaged last year can be separately payable this year, or the reverse, with no change whatsoever in how it is used or documented. That is why J1030's status in the Encounter checkpoint is a lookup rather than a constant, and why "we always got paid for that drug" is not evidence about this rate year.

Exercise 34 — C.15 (odd)

\$0.00. Beneficiary and patient cost-sharing is computed on the allowed amount, and a packaged line has no separate allowed amount — so it generates no coinsurance, no matter how large the charge on it is.

The principle: packaging pulls small lines out of the patient's bill and the separately payable lines put larger ones in. Packaging is, among other things, the reason that emergency department bill was not worse.

Why it complicates the estimate (Ch. 32 §32.2): an estimate built by adding up charges will badly overstate, and an estimate built from a fee schedule alone will not know which lines package. A defensible outpatient estimate has to know the payment method, not just the codes — and on a claim with conditional packaging it has to know what else will be on the claim.

Exercise 34 — D.16 †

   (a) national payment      1.4000 × 85.00                  =   $119.00

   (b) wage adjustment (labor share 60%, wage index 1.0500):
       labor portion         119.00 × 0.60   =  71.40
       non-labor portion     119.00 × 0.40   =  47.60     (check: 71.40 + 47.60 = 119.00 ✓)
       adjusted payment      (71.40 × 1.05) + 47.60
                             = 74.97 + 47.60               =   $122.57

   (c) coinsurance at 20% of the unadjusted amount:
       patient               119.00 × 0.20                  =    $23.80
       program               119.00 − 23.80                 =    $95.20
                                                 (check: 23.80 + 95.20 = 119.00 ✓)

Same skeleton as Chapter 33 §33.5 — weight × rate, labor share × wage index — applied per APC instead of per stay. Note that only the labor portion moves with the wage index; the non-labor portion does not.

Exercise 34 — D.17 † (odd)

   procedure 1 (highest RATE)   1,020.00 × 1.00   =  $1,020.00
   procedure 2                    450.00 × 0.50   =    $225.00
   procedure 3                    260.00 × 0.50   =    $130.00
                                                     ─────────
   claim total                                       $1,375.00
                        (check: 1,020.00 + 225.00 + 130.00 = 1,375.00 ✓)

   all three as status S (no discounting):
                        1,020.00 + 450.00 + 260.00 =  $1,730.00
   the discount is worth  1,730.00 − 1,375.00      =    $355.00
                        (check: 225.00 + 130.00    =    $355.00 ✓)

The rule: ranking is by payment rate, not by billed order and not by charge. The pricer sorts for you — but a coder who predicts \$1,730.00 will read the remittance as an underpayment and waste a follow-up call, and one who predicts a professional-side reduction pattern (Ch. 18 §18.8) will misread it differently. Predict from this system's rules, then reconcile (Ch. 28 §28.8).

Exercise 34 — D.19 † (odd)

What pays: the J1 primary service's comprehensive APC rate — once, for the claim.

What packages: the laboratory test, the low-cost drug, the recovery-room charge, the adjunct procedure, and the technical component of the surgical pathology. Under a C-APC the packaging is claim-scoped: services that would have paid separately on their own claim package silently when they share a claim with a J1 service.

The complexity adjustment: defined combinations of a J1 primary service with specified other services can move the claim to a higher-paying C-APC. The combinations are listed annually. The structural point to carry: even inside "one payment per claim," the coding of the secondary services still matters, because designated combinations reprice the claim.

The service not on this claim: the pathologist's professional interpretation. It is on a professional claim (§34.8) and the C-APC does not touch it. One encounter, two claims — the boundary holds even when one payment has swallowed everything on one side of it.

Exercise 34 — E.21 (odd)

Two jobs: the Outpatient Code Editor edits the claim — validity of codes for the date of service, age and sex conflicts, units against MUE values, revenue-code-to-HCPCS consistency, inpatient-only procedures, services not payable in this setting, the hospital versions of the NCCI procedure-to-procedure and medically unlikely edits, and the claim-level assembly checks a multi-department document accumulates — and it assigns the status indicator, the APC, and the payment flags that drive the pricer.

Update cycle: quarterly, in step with the code sets and edit files it enforces.

The one thing it never does: decide anything. It executes what the coding fed it, on that quarter's rules.

The counterpart: Chapter 33 §33.4's grouper, which likewise executes coding decisions rather than making them. When either produces a strange result the diagnostic path is identical — check what went in and which version it met — and the version question is sharper here, because the editor turns over four times a year rather than once.

Exercise 34 — E.22 †

(a) Packaged supply line — post and move on. A contractual outcome, not a variance. Do not queue it as a refusal, do not appeal it, do not "fix" the claim by removing the charge next time, and decide on purpose whether packaged lines are inside your denial-rate definition (Ch. 29 §29.7's denominator discipline) — then write the decision down.

(b) The line item denial — this is the one with appeal rights. It was adjudicated. But the first move is not the appeal, it is the documentation: pull the record. If the units are wrong, correct and rebill; the obligation to bill what the record supports did not change because software objected. If the record genuinely supports the units, review the MUE adjudication indicator and the NCCI Policy Manual before resubmitting or appealing (Ch. 21 §21.4, §21.8).

The two-paragraph argument, if the documentation supports it: paragraph one — what was performed, how many times, and on what dates, quoting only the relevant portion of the record (minimum necessary — the record excerpt, not the chart); paragraph two — why the reported units are correct against the code's descriptor and what the MUE adjudication indicator permits, with the policy citation and the documentation attached. If the documentation does not support the units, there is no appeal to write: correct the units, rebill, and route the cause — a charge-capture or configuration problem — to whoever owns it.

(c) The claim returned to provider — correct and resubmit, now. Nothing was adjudicated, so nothing is appealable, and this is the one running out of calendar: for timely filing purposes a returned claim is a claim that has not been successfully submitted (Ch. 27 §27.7). An account sitting in a queue mislabeled "denial — pending appeal" ages toward the filing deadline while everyone waits for an appeal that cannot exist.

Exercise 34 — E.23 † (odd)

Defect 1 — 73090 at 4 units on one date of service. A two-view forearm X-ray is not furnished four times in one encounter; the units exceed what the descriptor and the medically unlikely edit support. Caught by the Outpatient Code Editor, as a units edit.

Defect 2 — revenue code 0636 with no HCPCS code. Revenue code 0636 is drugs requiring detailed coding; the entire meaning of the code is that a HCPCS code accompanies it. Caught by the OCE — revenue-code-to-HCPCS consistency, which is Chapter 26 §26.5's pairing rule enforced by software.

Defect 3 — FL 67 carries one symptom code and no additional diagnoses. Nothing on this claim establishes why the radiology was needed. Caught by the payer, after adjudication, as a medical-necessity denial (Chapter 22). The editor checks validity, not justification — this is the class of problem software cannot see and a human should have.

Defect 4 — nobody catches it. Whether 99284 is the level the hospital's own written criteria support for the resources this encounter actually consumed. There are no national facility E/M leveling criteria (§34.8). The only test is an auditor asking to see the facility's written criteria and evidence of their consistent application — which is exactly the question an auditor should ask, and exactly the question a payer analyst comparing facility and professional levels does not.

The line that looks like a defect and is not: revenue code 0270 with no HCPCS code. Supplies are packaged; there is no code to report and no payment to lose, and the \$402.00 charge belongs on the claim for the two reasons in A.2. (Worth predicting rather than fixing: the 0300/80048 line will likely allow \$0.00 as conditionally packaged under Medicare's current rules — an expectation, not an error.)

Exercise 34 — F.25 (odd)

What each levels. The physician's 99284 levels the clinician's medical decision making (Ch. 16 §16.6). The facility's 99284 levels the department's resource intensity — the nursing time, the room, the equipment, the supplies the encounter consumed.

Who writes the rules. The professional side is governed by national rules. The facility side is governed by each hospital's own internal guidelines, because CMS has never published national facility E/M leveling criteria; the hospital must apply its criteria consistently, and the results must reasonably relate resource use to levels.

What the auditor asks to see: the facility's written criteria, and evidence that they are applied consistently — not whether any single chart "looks like a level 4."

What the payer analyst has misunderstood: the two levels are produced by two different rulebooks — one national, one local — and they can legitimately differ on the same visit. A "mismatch" report comparing them is asking the wrong question.

Exercise 34 — F.26 †

What it is: G0463, a single HCPCS Level II G-code for a hospital outpatient clinic visit of any level. On a Medicare clinic encounter the facility reports it instead of an E/M level.

Why it exists: CMS concluded that facility clinic-visit resources did not vary enough by E/M level to price five ways. One flat facility code, one visit APC.

What the physician reports for the same visit: 99202–99215, leveled on medical decision making or time under the national rules. One visit, one leveled code and one flat one.

What it tells you about the relationship: Medicare invents vocabulary where CPT's does not fit its payment policy — Chapter 20 §20.6's G-code logic exactly, the same reason G2212 exists beside 99417. CPT is maintained by the AMA to describe services; HCPCS Level II G-codes exist for what Medicare needs to pay differently.

Exercise 34 — F.27 (odd)

A model answer; the register matters as much as the content.

"You haven't been billed twice — you've been billed by two different people for two different things, and I'm sorry nobody explained that in advance. The statement from the physician group is the doctor's own fee for seeing you and making the decisions. The statement from the hospital is the clinic's own bill — the room, the nurse, the supplies, the equipment — because that clinic is part of the hospital rather than an independent office, which is a fact about how it's organized and not about your care. I'll be straight with you: that arrangement does generally cost a patient more than the same visit in an independent office would, and it is legal and very common, and you had no way to know it walking in. What I can do right now is send you both statements broken out line by line so you can see exactly what each one is for, check whether either has been processed correctly, and tell you what our financial assistance policy and payment plans cover before anything is due."

The failure modes to avoid: "that's the hospital's bill, not ours" (true, useless, and it makes her call three more people); and pretending the arrangement does not cost her more, which she will discover and which costs the explanation its credibility.

Exercise 34 — G.28 †

   hospital outpatient department   12.0000 × 85.00   =  $1,020.00
   ambulatory surgery center        12.0000 × 42.50   =    $510.00
                                       (check: 510.00 × 2 = 1,020.00 ✓)

   beneficiary coinsurance at 20%:
      hospital                       1,020.00 × 0.20  =    $204.00
      ASC                              510.00 × 0.20  =    $102.00
   difference to the patient          204.00 − 102.00 =    $102.00 ✓

The third site: the physician's office. A procedure safely performed there generates no facility claim at all — just the professional claim at Chapter 23's non-facility rate, which carries the practice expense the building would otherwise have billed.

What the patient can see of any of this from the waiting room: nothing. That is not an argument that the differentials are improper — they have rationales (standby capacity, EMTALA obligations, sicker patients) — it is the reason Chapter 32 §32.2's estimate discipline exists.

Exercise 34 — G.29 (odd)

Medicare: the ASC bills its facility fee on the professional claim format — a CMS-1500/837P — with place of service 24. Not a UB-04.

Many commercial payers: the institutional format, type of bill 831 (Chapter 26 §26.3's first digit 8, special facility).

The biller who assumes either is universal manufactures rejections at whichever payer wants the other format — and they are front-end rejections, which means no adjudication, no appeal, and a timely-filing clock still running (Ch. 27 §27.7). The same center, two claim formats, decided by payer.

Exercise 34 — H.31 † (odd)

How far it reaches: the three calendar days before the inpatient admission, plus the admission date itself.

The exception: one day for hospitals excluded from IPPS — psychiatric, rehabilitation, long-term care, and the other Chapter 33 §33.1 exclusions.

Which entities: the admitting hospital or any entity it wholly owns or operates — the clause that does the real damage, because it reaches physician practices and other departments whose billing staff may not know the ownership structure.

The two classes:

  • Diagnostic services: always bundled. No relatedness test, no attestation, no exceptions by argument. The Wednesday chest X-ray before a Friday admission belongs to the admission.
  • Non-diagnostic services: bundled when related — and the rule presumes they are. The hospital may bill an unrelated non-diagnostic outpatient service separately only by attesting the unrelatedness on the claim with condition code 51, and the attestation must be defensible from the record, because it is the only thing standing between the claim and the presumption.

Operationally, the outpatient claim disappears. The window services' diagnoses and charges are combined onto the inpatient claim. If the outpatient claim already went out — the common case, since nobody knew on Wednesday that Friday would produce an admission — the hospital adjusts or cancels it and rebills the combined inpatient claim. Separately billed window services are overpayments, and identified overpayments start Chapter 31 §31.9's sixty-day clock.

The professional side of an owned entity reports modifier PD.

Exercise 34 — H.33 (odd)

The modifier: PD — a diagnostic or related non-diagnostic service furnished in a wholly owned or operated entity within the window. It pays the professional work at the facility rate and folds the technical resources into the admission.

Why it is a corporate-structure problem, not a coding problem. The window's reach is defined by ownership, and ownership is known to a completely different set of people than billing rules are. The failure is never that somebody misread the rule; it is — as Chapter 26 put it — that the people who knew the ownership structure and the people who knew the billing rule were different people. The window is a rule about corporate structure applied by billing software, and somebody who knows both has to configure it.

Chapter 26's Case Study 2 is built on this clause. And the defensible posture is unglamorous: an automated hold on outpatient claims pending the window, a human review of relatedness before any condition code 51, and a periodic self-audit matching outpatient claims to subsequent admissions across every owned entity on the tax structure, not every entity the billing office remembers. Ownership analysis is a legal question — verify with compliance and counsel.

Exercise 34 — I.35 † (odd)

   FL 4   TYPE OF BILL     131  (hospital outpatient, admit through discharge)

   FL 42  REV   DESCRIPTION        FL 44 HCPCS + MOD    FL 47 CHARGE
   0750   GI services              45385-PT             [facility charge]
   0710   Recovery room               —                 [charge]
   0250   Pharmacy                    —                 [charge]
   0270   Med/surg supplies           —                 [charge]
   0310   Laboratory — pathology   88305                [charge]
   0001   TOTAL

   FL 67  first-listed:  Z12.11        additional:  K63.5

At the time of service, FL 67 reads Z12.11 first — the screening intent survives the polyp (Ch. 12 §12.9) — with K63.5 additional, because "tubular adenoma" is tomorrow's fact and the pathology is not back.

What the pathology report changes: on the completed record, with pathology in hand, the facility coder reports the confirmed D12.5 (benign neoplasm of sigmoid colon) as the finding code. The first-listed Z12.11 does not move, the procedure code does not move, and the modifier does not move.

Lines expected to allow \$0.00: the recovery room, the pharmacy, the supplies, and the pathology line's technical component — because 45385-PT maps to a level 4 GI endoscopy comprehensive APC (status J1), and a C-APC pays once for the claim. Every one of those zeroes is §34.5, not a refusal. (The pathologist's professional interpretation is on a professional claim and is untouched.)

Exercise 34 — I.36 †

   facility payment rate  [constructed]                       $1,020.00

   the old seam — standard 20%, deductible waived:
      patient      1,020.00 × 0.20      =    $204.00
      program      1,020.00 − 204.00    =    $816.00   (204.00 + 816.00 = 1,020.00 ✓)

   under the CAA 2021 §122 phase-down, at an ILLUSTRATIVE 15%:
      patient      1,020.00 × 0.15      =    $153.00
      program      1,020.00 − 153.00    =    $867.00   (153.00 + 867.00 = 1,020.00 ✓)

   the step is worth to this patient    204.00 − 153.00 =  $51.00

The deductible is waived in both cases. That protection comes from the screening benefit and is carried across the conversion by modifier PT; it does not depend on the phase-down and does not change with the percentage.

What the biller must verify before quoting anybody anything: this calendar year's phase-down percentage. The schedule steps down by calendar year toward zero, and a quoted figure from last year is Chapter 32 §32.2's estimate discipline failing in a new costume. (Secondarily: the \$1,020.00 itself is a constructed teaching rate — the real one is in the current OPPS Addendum B.)

Exercise 34 — J.37 (odd)

(a) What is genuinely sympathetic. The patient was invited in by a benefit that promised her nothing to pay, she did nothing wrong, the finding was the point of the screening, and the bill will feel like a broken promise. The scheduler is reacting to a real seam, not inventing a grievance.

(b) What would be false. G0121 reports a colorectal cancer screening colonoscopy that stayed a screening. The moment the snare came out, the service performed stopped matching the descriptor: a therapeutic procedure was furnished, and a claim reporting G0121 would assert that it was not. That is coding the intent instead of the service — sympathetic, and false — on a claim that is a legal attestation (Chapter 5).

(c) The mechanism the system actually provides. Modifier PT on the diagnostic code: it tells the payer to keep the screening benefit's cost-sharing protections attached to the converted service — the deductible is waived, and the coinsurance follows the CAA 2021 §122 phase-down stepping toward zero. Commercial plans generally run the same logic through modifier 33. The sympathy has an approved answer; it just isn't the G-code.

(d) The two sentences. "I can't report the screening code, because the doctor removed a polyp and the claim has to say what was done — but the rule you're reaching for exists: modifier PT keeps her screening protection on the diagnostic code, so her deductible isn't touched and her share is the reduced, phased-down amount rather than a full twenty percent. Let me pull this year's percentage and send you the exact number she'll owe, so whoever talks to her next has it right."

If the request comes from someone senior: do the same thing, and then put in writing — to your compliance officer, briefly and without accusation — what was requested, what you reported and why, and the policy basis. Not because the person is dishonest; because a coding decision that was pressured and undocumented is indistinguishable, two years later, from one that was chosen.

Exercise 34 — J.39 † (odd)

C. A return to provider is a disposition, not a decision: the claim was sent back unprocessed, no adjudication occurred, and no appealable determination exists — so the claim must be corrected and resubmitted rather than appealed.

The most expensive wrong answer to believe is D. A returned claim does not stop the timely filing clock; for filing purposes it is a claim that has not been successfully submitted (Ch. 27 §27.7). An account filed under "denial — pending appeal" ages quietly toward the deadline while everyone waits for an appeal that cannot exist — the whole reason §34.7 insists the OCE's dispositions are a vocabulary. (A fails because there was no adjudication and therefore no appeal rights; B fails because it concedes an adjudication that never happened.)

Exercise 34 — J.40 †

The line-by-line prediction (the Chapter 26 §26.9 provider-based counterfactual; the real Account 10-4471 is unchanged):

  • The visit line — a V-type line: separately payable. Its own visit APC. Generates patient coinsurance. Under Medicare specifically, the facility would not report 99214 at all: the clinic visit is G0463, one flat facility code for any level (§34.8), while the physician's claim still says 99214-25.
  • The injection, 20610-RT — a T-type line: separately payable, subject to discounting had a second such procedure been on the claim. There is not one (Ch. 18 §18.12 made the same finding on the professional side), so it prices in full under its APC. Generates patient coinsurance.
  • The drug, J1030 — status N: packaged. A \$6.28-class drug sits far below any year's drug packaging threshold. On the professional claim J1030 was a paid line (\$5.02 plan, \$1.26 patient); on the facility claim the same vial allows \$0.00 separately, and its money lives inside the procedure line's rate. Generates no coinsurance — and the line still belongs on the claim, with its real charge, because future APC weights are listening (§34.3).
  • The venipuncture and the lab handling — Q-type conditional packaging. Packaged in the presence of the visit and the procedure on this claim; payable under a different system had they arrived alone. No coinsurance on this claim either way. The reference laboratory's own claims for 83036 and 80061 are untouched (Ch. 19 §19.12).

The three cost-sharing arithmetics for the same injection in the same room: (1) the independent office under Northfield's commercial contract — patient \$47.58; (2) the provider-based conversion under the same commercial contract — patient \$84.52 against a \$361.00 total, 1.78 times the first; and (3) Medicare's OPPS coinsurance rules on those facility lines — the per-APC phase-down toward 20% and the per-service cap at the inpatient deductible (§34.2), which is a third answer again.

Why it cannot be priced from a published table, in two sentences. The dollar figures here are Northfield's constructed contract, not a derivation from any year's Addendum B, and this book does not fake a current rate lookup (§34.2). And the counterfactual is a lens, not an event: the real Northgate remains an independent practice, and the real Account 10-4471 has one claim, four lines, and a \$0.00 balance on day 100.


Chapter 35 — Answer Key (daggered † and odd-numbered exercises)

The quiz's own answer key lives in quiz.md's collapsed block. Everything below uses this book's constructed teaching figures. Every real-world value expires — ICD-10-CM each October 1, CPT each January 1, HCPCS Level II and the NCCI edits quarterly, payer policy continuously. Verify at the source before any of this touches a real claim.

Exercise 35 — A.1 (odd)

(1) The volume slice — twenty codes are most of the work; a specialty's code set is narrow and deep where a general practice's is broad and shallow. (2) The payment convention — the unit being purchased: a service, a session, an episode, a unit of time, an acuity level, or a calendar window. (3) The source document — a catheterization report, an operative report, an anesthesia record, a therapy flowsheet, an immunization record; not an office note. (4) The policy landscape — a handful of coverage documents govern most of the specialty's money. (5) The documented words — "complete," "with manipulation," "permanent recording and report," "counseling provided by the physician."

The one that produces errors on every claim is (2), the payment convention. The other four produce a wrong code on one claim; the convention produces a wrong shape on all of them, and it does so quietly, because nothing about it triggers an edit.

Exercise 35 — A.2 † (daggered)

Source document: the anesthesia record — not the operative report. Obtain: ten real anesthesia records, blank and completed, plus the practice's anesthesia billing worksheet if one exists.

What is bundled into what: one anesthetic produces one anesthesia service, reported with the code carrying the highest base unit value, regardless of how many procedures the surgeon performed. Obtain: the current CPT Anesthesia section guidelines (which also define anesthesia time and physical status reporting).

Unit of payment: units of time, added to base units and modifying units and multiplied by an anesthesia conversion factor. Obtain: the published base unit values, and each major payer's increment and rounding rule in writing.

Which policies govern: Obtain Medicare Claims Processing Manual Pub. 100-04, Chapter 12 for the anesthesia payment rules and the medical-direction requirements; the MAC's anesthesia articles; and each major commercial plan's published anesthesia policy (physical status recognition varies).

Top twenty codes: Obtain a twelve-month frequency report of the group's anesthesia codes, sorted by volume and separately by charge dollars.

Exercise 35 — A.3 (odd)

What transfers: the Alphabetic Index and Tabular List discipline (Ch. 8 §8.1); the Official Guidelines and their sequencing rules (Ch. 9); CPT's section guidelines and parentheticals (Ch. 13 §13.4, §13.6); every modifier rule, and modifier 25 and 59 in particular (Ch. 14 §14.4, §14.5); the NCCI procedure-to-procedure edits and MUEs (Ch. 21); medical necessity as a coverage concept (Ch. 22 §22.1); the claim forms; and the fact that the money comes from a contract. A coder who is good at the general work is most of the way there.

What does not transfer: the specialty's volume slice, its payment convention, its source document, its concentrated policy landscape, and its documentation vocabulary — §35.1's five. The largest mistake new specialty coders make is the opposite of the colleague's claim: abandoning their own discipline at the exact moment it is most valuable.

Exercise 35 — B.5 † (odd)

In the office, with the group's own equipment and technician, and the cardiologist's signed interpretation: 93000 — the complete service. Both halves belong to the billing entity.

Move the tracing to a hospital emergency department and nothing clinical changes, but the code does: 93010, interpretation and report only. The group did not own the machine, was not in the room, and paid for none of it; the hospital reports the technical side on its own claim.

The transferable point: what selects among the three electrocardiogram codes is who owned the equipment and who produced the signed interpretation — facts about business arrangements, not about the patient (Ch. 19 §19.1's four arrangements).

Exercise 35 — B.6 (odd)

Consequence: the practice cannot support a professional component. "Interpretation and report" requires a separate, retrievable, signed written interpretation — findings, conclusion, reader, date. A number or an initial on the tracing is not a report, and three hundred claims a month rest on a document that does not exist.

The same principle elsewhere: Ch. 14 §14.7 (the professional component generally — no report, no service) and Ch. 17 §17.7 (20611's "permanent recording and report," which is what separates it from 20610).

The fix is not a coding fix. It is a dictation workflow that produces a retrievable interpretation per tracing, and until it exists the correct behavior is to not report the professional component — which is also the honest way to make the case for building it.

Exercise 35 — B.7 † (odd)

The code: 93458 — left heart catheterization with coronary angiography. Answer the two axes: what was catheterized? the left heart (retrograde across the aortic valve, left ventricular pressures). What was imaged? the coronary arteries. No intervention, so nothing from the intervention families.

The three tempting components: the catheter placement, the injection procedures, and the imaging supervision and interpretation. All three are inside the descriptor.

The authority: Ch. 18 §18.4 — the catheterization codes were restructured to include them, and a reference that reports them separately predates the restructuring. Reporting them separately is unbundling (Ch. 21 §21.10's theory), and it is the exams' standard trap.

(Note also what the report does not support: left ventricular pressures are not a ventriculogram. Do not read an angiographic service into a hemodynamic one.)

Exercise 35 — C.9 (odd)

The fork (Ch. 17 §17.7): a physician treating a fracture may report global fracture care — one code, a 090-day global period, including the initial treatment, the first cast or splint, and normal follow-up through healing — or an E/M service plus a casting or splinting procedure, with no global period and subsequent visits billable.

What §35.3 adds: the decision is documented in the plan, in ordinary clinical English — "will follow in this office until union" versus "splinted; referred for definitive management" — and the physician makes it, not the coder. Where the plan is silent, the coder queries the treatment plan (Ch. 4 §4.9; Ch. 38 §38.3 owns the compliant form) rather than guessing, and the practice-level answer is a written rule so that a macro does not decide.

Exercise 35 — C.10 † (daggered)

Note A — global fracture care. The plan states definitive management through healing with a follow-up schedule and an anticipated duration. Global period: 090 days. The immobilization application is included and not separately reportable; the supply is separately reportable (Ch. 17 §17.8). Still to query: the treatment type — closed, open, or percutaneous, and with or without manipulation — because the fracture care codes are divided by it and the note does not state it (Ch. 17 §17.7).

Note B — E/M plus splint. The plan states stabilization and referral, with no follow-up here. No global period. The splint application is separately reportable, the supply is separately reportable, and the E/M is reported at the level the documented decision making supports, subject to Ch. 14's modifier rules. Nothing to query — the note says what it needs to say.

The lesson: reporting global fracture care on Note B would assert ninety days of management that will not happen, and would collide with the receiving practice's claim (Ch. 17 §17.7's ⚠️).

Exercise 35 — C.11 (odd)

(a) Modifier 24 — an unrelated E/M service during the postoperative period; it asserts that this visit is not postoperative care. (b) Modifier 58 — a planned or staged return; it restarts the global period. (c) Modifier 78 — an unplanned return to the operating room for a related complication; it does not restart the global period. (d) Modifier 79 — an unrelated procedure by the same physician; a new global period begins for that procedure.

The pairing to memorize: 58 is planned and restarts; 78 is not planned and does not (frozen at Ch. 14 §14.9; mechanics at Ch. 17 §17.2).

Exercise 35 — C.12 † (daggered)

(a) Payment is not evidence of correctness because modifier 24 defeats the edit that would otherwise deny the line. The claims paid because the modifier was there. A 100% payment rate on auto-modified claims measures the modifier's effectiveness, not the claims' accuracy — the same structure as Ch. 29's Case Study 2, where denials genuinely fell for a bad reason.

(b) Each of the 214 claims asserts, in the practice's own words, that the visit was unrelated to the surgery. The routine two-week postoperative check is related to the surgery, so a share of those assertions are false statements on claims submitted for payment (Ch. 5 §5.1).

(c) The same mechanism: the auto-appended modifier of Ch. 14 §14.1; the prefilled E/M time of Ch. 15; the fracture-care macro of Ch. 17 §17.7; the modifier-59 macro behind Account 31-2245's audit (Ch. 21 §21.9); the automatic KX attestation of Ch. 19 §19.11; the routine ABN producing GA on every claim (Ch. 22); and the auto-inserted modifier 25 attestation of Ch. 29's Case Study 2. A configuration making an assertion nobody chose.

(d) The control: a weekly report of every E/M service coded inside a global period, reviewed by a person who opens the notes. It is a control rather than a report because a human decides on each one — Ch. 27's Case Study 1 stated the principle exactly: a report is not a control; a person who reads a report is a control. Turning the automatic append off is the other half, and it is the half that fixes the cause.

Exercise 35 — C.13 (odd)

Three, with their governing sections: the casting or splinting supply (Ch. 17 §17.8) — a charge-capture error, and money left behind routinely; laterality, RT/LT or the bilateral convention (Ch. 14 §14.8) — a coding error, and in orthopedics it is on nearly every line; and procedures documented inside a narrative rather than in a separately headed operative report — a charge-capture error, since nothing was coded wrong, something was simply never coded (Ch. 23 §23.9).

Exercise 35 — D.15 † (odd)

(a) Report what the practice furnished: the antepartum care actually provided, by visit count (9 weeks to 31 weeks), using the antepartum-care codes divided by number of visits. If the practice furnished any services outside the package during that time, those are reported separately.

(b) Do not report the global package (59400 or 59510) — the practice did not provide the delivery or the postpartum care — and do not report the antepartum visits as ordinary office visits, which is the familiar-code error.

(c) The visit count. It should have been recorded at each visit, by the person who roomed the patient, on the episode log. Reconstructed from the chart in month nine it takes about an hour per patient and is never as accurate — visits documented under other headings get missed, and the count is the entire basis of the claim.

(d) Eligibility verification (Ch. 24 §24.3), which should run on a schedule across the episode rather than once at intake. A patient who relocated at 31 weeks very likely changed coverage, and the practice is about to bill a plan that may not have covered the care.

Exercise 35 — D.17 † (odd)

(a) The preventive medicine service (the age-banded, new-or-established code) plus a problem-oriented E/M at the level the documented decision making supports, with modifier 25.

(b) Ch. 14 §14.4's standard: the second service must be significant and separately identifiable, documented with its own history, examination as appropriate, assessment, and plan — work beyond the preventive service's own content. A different diagnosis is not required; separate documented work is.

(c) The explanation of benefits will most likely show the preventive service processed at 100% under the preventive benefit and the problem-oriented E/M applied to the deductible or coinsurance. Two sentences at check-out: "Today's visit had two parts — the annual exam, which your plan covers in full, and the new problem we worked up, which is billed separately and goes through your regular benefits." / "That means you may see a small balance for the second part; it is not a billing error, and I can show you which line it is if a statement arrives." (Ch. 32 §32.10.)

Exercise 35 — E.19 † (odd)

The claim, in order:

  1. The preventive medicine servicenew patient, age 6 → the 5–11 age band of the new-patient preventive range (99381–99387). The note documents the required content: comprehensive age-appropriate history and examination, screening, anticipatory guidance, immunization status reviewed.
  2. The two vaccine products — one product code per vaccine.
  3. The administrations90471 for the first and 90472 for the second. Not the counseling-based family: the note documents no counseling by the physician or other qualified health care professional, and that family requires it and requires it documented (Ch. 19 §19.10).

No problem-oriented E/M and no modifier 25 — the note documents no separately identifiable problem, and adding one would be an assertion the record does not support.

What must be confirmed outside the medical record: the supply source of each dose. The vignette states practice-purchased stock, so both products are billable. Had either dose come from a public supply program, the practice may bill only the administration for it (Ch. 19 §19.10) — an inventory fact, not a charting fact.

Exercise 35 — E.21 † (odd)

   Doses ......................................... 900
   Encounters missing the administration line
      900  ×  0.07  ................................ 63
   Administration allowed ...................... $24.80

   63  ×  $24.80  =  $1,562.40

Checks: 900 × 0.07 = 63 ✓ · 63 × 24.80 = 1,562.40 ✓

The harder half: it appears on no report. Not the denial log — nothing denied. Not the aging report — nothing is outstanding. Not the rejection report — the claims were accepted. Not the underpayment variance — the lines that were billed were paid correctly. A charge that was never created has no record anywhere in the billing system, which is why it cannot be found from inside the billing system.

It can only be found by comparing two counts from two systems: doses out of inventory (or out of the immunization record) against administration lines out of the billing system. That is the general shape of every silent underpayment in this book — Ch. 28 §28.8's method, which begins by constructing the expectation rather than by examining the result.

Exercise 35 — F.23 (odd)

No new-versus-established distinction, because an emergency department is available to anyone at any hour and does not have patients in the ongoing sense. No time-based selection option, because ED work is interleaved by design — a physician manages several patients at once, is interrupted continuously, and returns — so total time on the date is not a meaningful measure of one patient's care (Ch. 16 §16.6).

What the second removes: the time-based alternative Ch. 15 §15.8 supplies in every other outpatient E/M family. The medical decision making documentation carries the entire level, with no fallback — which is why the "what was being ruled out" paragraph is worth so much in an ED chart.

Exercise 35 — F.24 † (daggered)

   Triage and initial vital signs ................ 1
   Repeat vital sign sets, three ......... 3 × 1 =  3
   Continuous cardiac monitoring ................. 3
   Intravenous line established .................. 3
   Intravenous medications, two .......... 2 × 3 =  6
   Specimen collection and handling .............. 1
   Discharge teaching and follow-up .............. 1
                                                 ──
   TOTAL ........................................ 18   →  band 13-18  →  99284

Check: 1 + 3 + 3 + 3 + 6 + 1 + 1 = 18 ✓

What you can conclude: the facility level is 99284, produced by a written rule from documented nursing work, and reproducible by anyone holding the record and the criteria sheet.

What you cannot conclude: anything about the physician's level. It is scored on medical decision making by a national rulebook (Ch. 15's grid) and may legitimately be 99283 or 99285. Neither number is evidence about the other. Note also that 18 sits at the top of its band — one more scored intervention moves this encounter to 99285, which is exactly why the scored record must be retained.

Exercise 35 — F.25 (odd)

"The two levels measure different things: our facility level reports the department's resource intensity — nursing interventions, monitoring, medications, time — while the physician's level reports medical decision making. CMS has never published national facility leveling criteria, so the physician's rulebook is national and ours is our own written criteria, applied consistently. The two are expected to correlate, not to match; a patient can consume substantial departmental resources with modest decision making, and the reverse. A better question than the mismatch rate is whether our criteria are written, resource-based, consistently applied, and reproducible — and we can answer that. We can produce the criteria document, its revision history, and the scored record behind any encounter you select."

(Ch. 16 §16.9 adds the sharper point the hospital may fairly make: a facility level that matched the physician's on every claim would be the actual finding.)

Exercise 35 — F.26 † (daggered)

(a) A genuinely high-acuity case mix, or criteria that are wrong or wrongly applied. The distribution alone cannot distinguish them — the same two-explanation problem Ch. 33 §33.6 found in the case mix index, which cannot distinguish sicker patients from better documentation.

(b) The written criteria, plus a sample of scored records, decide which. A distribution is a question; the criteria and the scoring are the answer.

(c) Lowering the levels is not appropriate, and it is worse than doing nothing for a precise reason: it replaces one number the hospital cannot defend with another number the hospital cannot defend, destroys the relationship between the levels and the resources actually consumed, and misdescribes the department's work in the data everyone downstream reads. It is Ch. 5 §5.8's downcoding — inaccurate, not conservative, and not a defense.

(d) Ch. 33 §33.6's case mix index. Same structure, different setting.

Exercise 35 — G.27 (odd)

The source document is the anesthesia record. Four facts that live on it and nowhere else: (1) the anesthesia start and end times, from which every time unit is computed; (2) the physical status assignment; (3) the anesthesia professional's presence and its transitions — who was there at induction and emergence; (4) the agents administered and the monitoring performed. (The operative report will contain a time, and it is not the time you need.)

Exercise 35 — G.28 † (daggered)

   (a) ANESTHESIA TIME   13:26 → 15:09  =  103 minutes
       time units        103 ÷ 15 = 6.87  →  truncated  →  6

       Base units ................................  9
       Time units ................................  6
       Modifying units (P3, recognized) ..........  1
                                                  ───
       Total units ............................... 16

   (b) 16  ×  $22.00  =  $352.00

   (c) ROOM TIME        13:20 → 15:14  =  114 minutes
       114 ÷ 15 = 7.6  →  truncated  →  7 time units
       9 + 7 + 1 = 17 units  ×  $22.00  =  $374.00
       Difference:  374.00 − 352.00  =  $22.00

   (d) ANESTHESIA TIME under ROUND-TO-NEAREST
       6.87  →  7 time units
       9 + 7 + 1 = 17 units  ×  $22.00  =  $374.00
       Difference from (b):  $22.00

Checks: 9 + 6 + 1 = 16 ✓ · 16 × 22.00 = 352.00 ✓ · 9 + 7 + 1 = 17 ✓ · 17 × 22.00 = 374.00 ✓ · 374.00 − 352.00 = 22.00 ✓

(e) (c) is an error: room time is not anesthesia time, the record says so, and the claim would report time the record does not support — a false statement about a service (Ch. 5 §5.1). (d) is policy: the payer publishes a rounding rule, the rule produces 7 units from the same documented 103 minutes, and the claim is correct. The two produce the identical \$374.00 and are not the same kind of thing at all — which is why an anesthesia biller keeps every payer's increment and rounding rule in writing rather than reasoning from the total.

Exercise 35 — G.29 (odd)

One anesthesia code — the one carrying the highest base unit value among the procedures performed. One anesthetic, one anesthesia service, regardless of how many procedures the surgeon performed under it. (The time is the anesthetic's total time, not a per-procedure allocation.)

Exercise 35 — G.30 † (daggered)

The schedule-level fact: the anesthesiologist was directing no more than the permitted number of concurrent procedures — the arrangement's defining condition, which is a fact about the day's assignment board and cannot be established from the anesthesia record alone.

The documented steps (Ch. 18 §18.11): the preanesthetic examination and evaluation, prescribing the anesthesia plan, personal participation in the demanding portions including induction and emergence, ensuring that any procedures not performed personally are performed by a qualified individual, monitoring the course at frequent intervals, remaining physically available for immediate diagnosis and treatment of emergencies, and providing indicated postanesthesia care.

What an auditor asks for on one case: the anesthesia record showing each step and its timing, the signature and attestation, and the concurrency documentation for that time window — because without it the arrangement cannot be shown to have been permissible.

Physical status is assigned by the anesthesia professional who examined the patient and is documented on the record. A coder may never adjust it — not upward because the problem list looks severe, not downward for caution. It is a clinical judgment with a payment consequence attached, which is exactly Ch. 4 §4.7's line.

Exercise 35 — H.31 † (odd)

Convention Owner Documentation required
E/M total time on the date Ch. 15 §15.8 total qualifying time on the date and what was done in it
Timed therapy units (8-minute rule) Ch. 19 §19.11 minutes per timed service, and the date's total; total first, then convert
Psychotherapy time §35.8 start and stop times or total duration, plus content
Anesthesia time Ch. 18 §18.11, §35.7 the clock times on the anesthesia record

The four cases: an anesthesia case → [4]. 22 minutes of therapeutic exercise plus 9 minutes of manual therapy → [2] (total 31 minutes → the 23–37 band → 2 units, allocated between the codes). A 38-minute psychotherapy session → [3]. An office visit selected on total time → [1].

Exercise 35 — H.33 † (odd)

(a) Each note asserts that the session lasted 50 minutes, and the assertion is made by the clinician whose signature is on the note — not by the template that supplied the number.

(b) It is worse than the equivalent error on a claim for three reasons, all from Ch. 29's Case Study 2: the assertion sits in the clinical and legal record rather than on a claim form; the clinician's signature is on it; and a note can be amended but never un-asserted — the original entry remains part of the record forever.

(c) Three remedies: remove the default; require start and stop times rather than a duration; and reconcile documented session time against the appointment schedule quarterly — a report the practice can run against two systems it already owns, which is the only kind of control that finds a problem no claim will ever surface. (A fourth: sample a handful of notes for content that matches the stated duration.)

(d) The thread: a configuration making an assertion nobody chose (Ch. 14 §14.1). Earlier instances include the prefilled E/M time (Ch. 15), the fracture-care macro (Ch. 17 §17.7), the modifier-59 macro behind Account 31-2245 (Ch. 21 §21.9), the automatic KX attestation (Ch. 19 §19.11), and the auto-inserted modifier 25 attestation (Ch. 29's Case Study 2).

Exercise 35 — I.35 † (odd)

(a) Three things that could be wrong. (1) The payer may require place of service 02 or 10 rather than the in-person code — in which case the field is misreporting where the service occurred. (2) The payer may not want modifier 95 at all when the telehealth place of service is used, making the claim internally inconsistent. (3) Some of those encounters may have been audio-only, in which case modifier 95 — which asserts synchronous real-time audio and video — is a false statement regardless of the encounter's quality. (And a fourth, quietly: two years of "the same way for every payer" means nobody has checked a policy in two years, in the fastest-changing area of the book.)

(b) Place of service drives facility versus non-facility pricing (Ch. 23 §23.5), so the field is not merely descriptive — it moves the allowed amount, in either direction, and a wrong value pays wrongly without denying. Ch. 23's ⚠️ called it one of the purest silent errors in the book.

(c) The artifact: a telehealth matrix, one row per payer — covered services list and where it lives; the required place of service; whether modifier 95 is required, permitted, or prohibited; audio-only treatment; consent and documentation requirements; and the field most practices omit: the date the row was verified and the date it should be re-verified. In this area a matrix without dates is a matrix that will be wrong and will look authoritative while it is.

Exercise 35 — J.36 † (daggered)

Before day 1 (four things obtained). The current CPT book, read at the Surgery section guidelines and the female genital / maternity subsection guidelines and parentheticals — deliverable: your own notes on what the maternity package includes and excludes. The NCCI Policy Manual chapter for the Surgery section — deliverable: a list of the family rules that apply. The MAC's LCDs and billing-and-coding articles for obstetric ultrasound and the practice's top gynecologic procedures, plus the two largest commercial plans' maternity and preventive-services policies — deliverable: a one-page summary of what each plan treats as inside the package. The American College of Obstetricians and Gynecologists' coding resources — deliverable: a reading list, held as Tier 2.

Week 1. Days 1–2: the top-twenty lists from the practice's own twelve-month claims history, by volume and by dollars — deliverable: two lists. Day 2 (second half): the six-column grid for each code — descriptor in your own words, what is bundled, global period, whether it splits into components, edit and MUE notes, governing policy — deliverable: the grid. Day 3: the source documents — prenatal flow sheets, delivery summaries, operative reports — deliverable: a map of where the visit count, the gestational age, the delivery route, and the signature live. Days 4–5: four half-days shadowing — a clinician, the current coder, the front desk (authorization and eligibility burden), the biller who works maternity denials — deliverable: four written answers to "what do you wish the coder knew?"

Week 2. Days 6–8: code in parallel on real charts, compare after rather than during — deliverable: a written disagreement list. Day 9: ninety days of the specialty's denials by CARC and root cause — deliverable: a ranked list of the practice's characteristic failures. Day 10: open the error log — deliverable: the log itself, kept for a month and reviewed weekly.

And build the practice's obstetric episode log if it does not have one (§35.4).

What two weeks will not buy: the tail (unusual cases, where the correct behavior is to look it up and ask); the clinical fluency that makes reading a delivery summary fast, which arrives around month three; and the authority to guess — in the first month you should be checking your unusual answers with somebody and saying so out loud.

Exercise 35 — J.37 (odd)

What governs the claim: the payer's published medical policy. A specialty society's guidance is an authoritative reading of the code set and it is also advocacy for its members; it does not adjudicate (Ch. 22 §22.10).

What the society's guidance is genuinely for: understanding the convention and its rationale, and citing it in an appeal — where a well-reasoned society position is real evidence about how the code set is meant to work (Ch. 30 §30.4's evidence categories).

What to do next, in order: (1) confirm you are reading the current version of both documents, and note the date of each; (2) submit consistent with the payer's policy, because that is the rule that decides this claim; (3) put the society's position in the practice's appeal-paragraph library so it is available if the claim is later worth appealing; (4) tell the physician-owner what you did and why, in writing, in three sentences — and (5) if the disagreement is material and recurring, take it to the payer through the policy's own reconsideration or provider-relations channel (Ch. 22 §22.4), which is the only mechanism that changes a rule rather than complying with one. (If you are instructed to bill against the payer's policy anyway, Ch. 5 §5.9 owns that conversation.)

Exercise 35 — J.39 (odd)

(B) Modifier 24. The rash evaluation falls inside the 090-day global period of the fracture care code but is unrelated to the fracture; modifier 24 asserts exactly that — an unrelated evaluation and management service during a postoperative period — and it is what allows the visit to be separately payable.

Why the others fail: (A) is wrong because the global period covers the related care, not the patient; an unrelated problem is separately reportable. (C) 58 identifies a planned or staged procedure and restarts the global — neither applies, and there is no procedure here. (D) 79 identifies an unrelated procedure, not an unrelated E/M service.

Exercise 35 — J.40 † (daggered)

The E/M category. She has never been seen by the orthopedic group, so she is a new patient — the 99202–99205 range under Ch. 15 §15.2's three-year rule — rather than the established-patient 99214 on the real file.

The modifier 25 argument. On the real claim it rests on four documented elements (Ch. 4's Figure 4.2), three of which have nothing to do with the knee: three chronic conditions separately assessed with plans, prescription drug management across three medications, and two laboratory tests ordered with stated reasons. The orthopedist addresses none of those — Ch. 15 §15.5's "addressed" rule, the same finding Ch. 16 §16.10 made for the ED. So the argument must be built from the knee alone: a new-patient evaluation, a differential, imaging ordered and interpreted, a management decision. Same modifier, weaker and more contestable argument, because every element is arguably the evaluation that precedes the procedure.

The procedure code and the clause that decides it. 20610 without imaging guidance; 20611 with ultrasound guidance and a permanent recording and report. The real note's frozen clause "no imaging guidance used" settles it there (Ch. 17 §17.7). In the counterfactual, the note must document the opposite with the recording and the report behind it, or 20610 remains correct.

The diagnosis. With films obtained at the visit and a report describing degenerative change, M17.11 would be supportable on that date. On the real March 14 encounter it is not: Figure 4.2 states that no definitive diagnosis was established and no prior imaging of the knee was available, so M25.561 was correct for March 14 — the reasoning on which Ch. 22 §22.11 closed Q5. The counterfactual changes the imaging, not the history.

The line that disappears. 36415, the venipuncture — the orthopedist orders neither the hemoglobin A1c nor the lipid panel, so the draw does not happen and the \$3.00 Ch. 19 §19.12 traced to it does not exist.

Why the chapter prices none of it. The real file is frozen — \$367.00 charged, \$216.28 allowed, \$47.58 patient, \$168.70 plan — and constructing a competing set of allowed amounts would put a second set of numbers on the same patient with nothing to reconcile them. And it could not be derived anyway: Ch. 23 §23.6 showed Northfield's contract is priced per line, at four different percentages of Medicare, so no formula extends it to a code the contract has not priced. Classification is the coder's; price is the contract's.


Chapter 36 — Answer Key (daggered † and odd-numbered exercises)

The quiz's own answer key lives in quiz.md's collapsed block. Every coefficient, benchmark, score, and dollar figure below is one of this book's constructed teaching figures. Risk models, their category definitions, their code mappings, and every coefficient are revised annually and the model version in force differs by contract year and by program — verify with the plan or at CMS.

Exercise 36 — A.1 (odd)

Fee-for-service: a payment is triggered by an event — a service was furnished, a code went on a line, the line has an allowed amount. Risk-adjusted capitation: a payment is triggered by enrollment — the member exists, the month passed, and the amount is a benchmark multiplied by a risk score built from last year's diagnoses. Nothing had to happen to her for the money to move.

Exercise 36 — A.2 † (odd)

Fee-for-service. The claim may reject at the clearinghouse or the payer's gateway (Ch. 27), or adjudicate and deny with a CARC — most often for a diagnosis that does not support the service (Ch. 22, Ch. 29). Either way there is an artifact: a rejection report, a remittance line, a work queue entry, a person who reads it.

Risk-adjusted. The claim pays exactly as expected. There is no denial, no variance, no exception report, and no work queue entry. Eleven months later the plan's payment for that member is smaller than it should have been, in a system the practice cannot see, attributable to no particular chart.

The reason the second answer is short is the point of §36.1: every other failure in this book announces itself. This one produces no artifact at all, which means the only control that can catch it is somebody deliberately reading charts against the record — §36.8's legitimate half.

Exercise 36 — A.3 (odd)

Job one: justify the service. Read by an adjudication system, within days, against edits and coverage policy. Job two: describe the member. Read by a risk model, the following year, in aggregate with every other diagnosis reported for that member by anyone, to set a monthly payment before any service exists. Same code, two readers, two timescales, and only the first one talks back.

Exercise 36 — B.5 † (odd)

The mechanism. A fixed payment per member per month is the same amount whether the member is healthy or has heart failure, diabetes, and kidney disease. Revenue is flat; cost is not. So the organization's margin is determined by who enrolls, and the cheapest way to improve it is not to improve anyone's health but to end up with healthier members — declining complex referrals, being slow to return calls, locating offices inconveniently for people who cannot drive.

What it pays an organization to do: avoid sick people. Stated that plainly, it is obvious why adjusting the payment for expected cost is a patient-protection mechanism and not merely an accounting refinement.

Exercise 36 — B.7 (odd)

1.0 means the member is expected to cost the same as an average member — not any particular number of dollars. 1.6 means about 60% more than average. Normalization exists so that the average stays near 1.0 as the population ages, as the model is refit, and as documentation improves; without it, a score would drift and stop being comparable across years, and the benchmark arithmetic would have to be rebuilt every time.

Exercise 36 — C.9 (odd)

A hierarchical condition category is a group of clinically related diagnoses that predict similar incremental cost, treated by the model as one unit with one coefficient. "Hierarchical" refers to the ranking within a disease family: where a member's diagnoses reach several severities of the same disease, only the most severe counts, and the rest are zeroed for the year.

Exercise 36 — C.10 † (odd)

She has not made a mistake. A risk model is a cost-prediction instrument, not an inventory of illness, and it selects only the conditions that predict spending reliably enough to be worth including. Symptom codes generally map to nothing. Most musculoskeletal conditions map to nothing. Uncomplicated hypertension maps to nothing. Encounter and status codes generally map to nothing.

A chart with fourteen accurate codes and two mapped categories is normal. The failure this exercise guards against is the opposite instinct — a coder who concludes that the codes must be wrong and starts hunting for versions that "count," which is exactly the reasoning §36.8's enforcement landscape exists to punish.

Exercise 36 — C.11 (odd)

CMS-HCC — Medicare Advantage. CMS-HCC ESRD model — beneficiaries with end stage renal disease. RxHCC — Part D drug payments. HHS-HCC — the Affordable Care Act's individual and small-group markets. (State Medicaid programs use their own, frequently a classification developed for Medicaid populations.)

Why they legitimately disagree: each is fit to predict a different kind of spending in a different population. RxHCC selects for conditions that predict drug cost, so its categories are not the Medicare medical model's. HHS-HCC covers all ages, including infants and pregnancy, which a Medicare model has no reason to include. A condition carrying weight in one and none in another is the models working correctly, not an error.

Exercise 36 — D.13 † (odd)

(a) The RAF.

   0.346 + 0.328 = 0.674
   0.674 + 0.302 = 0.976
   0.976 + 0.127 = 1.103
   1.103 + 0.331 = 1.434
   1.434 + 0.121 = 1.555      <- RAF

(b) The payment. 1.555 × \$1,000.00 = **\$1,555.00 per member per month; \$1,555.00 × 12 = **\$18,660.00 for the payment year.

Checks: the six addends sum to 1.555 ✓ · 1,555.00 × 12 = 18,660.00 ✓

(c) Interpretation, which is the part worth grading: the member is expected to cost about 55% more than an average member, and the plan is funded on that expectation before it knows anything about what will happen to her.

Exercise 36 — D.15 † (odd)

Assumption stated in the exercise's model: the heart failure interaction fires on the presence of the diabetes group regardless of severity.

   demographic                                  0.346
   COPD                                         0.328
   diabetes WITHOUT complications               0.105
   chronic kidney disease                       (not reported)
   congestive heart failure                     0.331
   interaction: heart failure + diabetes        0.121
   ------------------------------------------------
   RAF                                          1.231

Check: 0.346 + 0.328 = 0.674 · + 0.105 = 0.779 · + 0.331 = 1.110 · + 0.121 = 1.231 ✓

The difference: 1.555 − 1.231 = 0.324. Cross-check from the components: 0.302 − 0.105 = 0.197 lost on the diabetes category, plus 0.127 lost entirely on the kidney disease; 0.197 + 0.127 = 0.324 ✓

At \$1,000.00 PMPM:** 0.324 × \$1,000.00 = \$324.00 per month** = **\$3,888.00 for the year. Check: 324.00 × 12 = 3,888.00 ✓

And notice that this is the identical arithmetic §36.11 runs on Account 10-4471 — one member, one year, one unwritten sentence.

Exercise 36 — D.17 (odd)

The disease and interaction terms are common to both: 1.555 − 0.346 = 1.209.

   member A   0.223 + 1.209 = 1.432
   member B   0.512 + 1.209 = 1.721
   difference                 0.289   (= 0.512 - 0.223)

Checks: 1.432 + 0.289 = 1.721 ✓

Why a chart cannot close it: the demographic component is built from enrollment facts — age band, sex, dual/Medicaid status, institutional residence, originally-disabled status — and nothing a clinician writes changes any of them.

Exercise 36 — E.19 (odd)

The rule: within a disease family, the highest-ranked category the member's diagnoses reach is retained and every lower category in that family is set to zero for the year.

It protects against double-counting the same disease at several severities.

It deliberately does not protect against under-description. The model cannot promote a category that was never reached, so a record that reports only the least severe version earns only the least severe coefficient — with no mechanism anywhere to notice.

Exercise 36 — E.20 † (odd)

The asymmetry. Report too much within a family and the hierarchy discards the excess: no gain. Report too little and there is no corresponding mechanism to recover the difference: full loss. Accuracy is therefore not merely the ethical strategy; it is the only strategy with a positive expected value, which is a genuinely useful thing to be able to say to someone who thinks compliance and revenue are in tension here.

The one situation where a deletion moves a score the other way: when an unsupported severe category is removed, a lower category in the same family — previously zeroed by trumping — becomes live again, provided the diagnoses supporting it were also reported. A program that only ever adds can never discover this, which is one more reason the deletion count is the number that makes a review program credible.

Exercise 36 — E.21 (odd)

Nothing trumps anything. Diabetes, chronic kidney disease, and chronic obstructive pulmonary disease are three separate disease families, and hierarchies operate within a family, not across families. All three contribute their own coefficients. (Within the kidney family, a stage-4 category would trump a less severe kidney category — but there is no second kidney category on this record.)

Exercise 36 — F.23 (odd)

Every condition returns to zero at the start of each collection period. Diagnoses documented and reported during collection year N build the risk score that pays every month of payment year N+1. Nothing carries forward from an earlier year — however permanent the condition.

Exercise 36 — F.24 † (odd)

Model answer (the grading criterion is that the concession comes first):

"You're right, and I'm not going to pretend otherwise — the amputation is permanent and asking you to write it down again every year is a burden that exists for the payment system's convenience, not the patient's. Here's the reason it works that way. The risk model is a statistical instrument fit on one year of claims at a time. It has no memory; it only ever sees the year in front of it. So a condition that isn't documented and reported this year is, to that model, a condition this patient does not have — and next year's payment for her care is set on that basis. What I can do is make it cheap: you'll get a short list before the visit of what hasn't been addressed yet this year, and anything that's genuinely no longer active, say so and I'll take it off the list permanently."

What is being graded: conceding the point, explaining the mechanism rather than asserting the rule, and ending with the workflow — because a physician who is told only "you have to" complies worse than one who is told why and offered help.

Exercise 36 — F.25 (odd)

Recaptures? Why
(a) problem list entry No Nobody assessed anything — Ch. 9 §9.7's whole point
(b) eGFR of 48 on a lab report No A laboratory is not a diagnosing provider
(c) telephone refill, no encounter No No face-to-face assessment
(d) office visit, condition assessed with status and plan Yes The only one that meets the requirement
(e) last year's note copied forward No Cloned documentation (Ch. 4 §4.6); one year of MEAT and a copy operation
(f) venipuncture claim carrying the diagnosis No The service is not an encounter with a diagnosing provider

Exercise 36 — F.26 † (odd)

Why it must still be documented every year: the annual reset does not care whether a condition can resolve. If M17.11 is not documented and reported this year, this year's record does not describe a patient with osteoarthritis — and the record is the only description anybody downstream has.

Why a coder should not assume a risk weight: osteoarthritis is not among the categories the model weights. Verify against the model in force, but the general shape holds.

The principle: a risk model selects for cost prediction, not for importance. A great many serious, permanent, disabling conditions carry no weight at all. The correct inference is not "then don't bother" — it is that a practice which instructs clinicians to "document the HCCs" has told them to write a chart optimized for a payment formula, while a practice that asks them to document the patient completely gets the risk-adjustment result as a by-product and a usable medical record as well.

Exercise 36 — G.27 † (odd)

Condition M E A T Reportable
Type 2 diabetes Yes — status stated, A1c ordered to assess control, plan stated, metformin continued
Essential hypertension Yes — "at goal," BP recorded, lisinopril continued
Hyperlipidemia Yes — atorvastatin continued, lipid panel ordered
Right knee pain Yes — history, examination, injection; symptom code, because no definitive diagnosis was established (Ch. 9 §9.6, Ch. 22)
CKD, stage 3a No — zero of four

The one that fails, and on how many criteria: chronic kidney disease, stage 3a, on all four. It appears exactly once, on the reviewed problem list, with no status, no plan, and no mention anywhere in the assessment. The coder read the record correctly; the record is the problem. This is Account 10-4471's March 14 note, and §36.11 works the consequence.

Exercise 36 — G.29 † (odd)

Item 3, "History of CHF," is a trap on two grounds.

One — it is redundant and contradictory. Item 1 already documents chronic systolic heart failure with monitoring, evaluation, assessment, and treatment. Item 3 says the same patient has a history of the condition item 1 is actively managing. A note that says both is internally inconsistent, and an auditor reads inconsistency as a template artifact.

Two — "history of" is read by the classification as a PAST condition. Chapter 12 §12.9 owns the history codes. In clinical usage the phrase is ambiguous between "has, since 2019" and "had, and no longer has"; in the classification it is not ambiguous at all. A coder who reports an active condition from that phrase alone has supplied a clinical judgment — Chapter 4 §4.7.

(Item 1 is fully reportable on its own; item 2's stroke history, with no residual deficits, is correctly a history statement and the aspirin does not convert it into an active condition.)

Exercise 36 — G.31 † (odd)

Model memorandum (under 300 words; the graded elements are in bold):

What the phrase supports. That the clinician reviewed something and refilled something. Nothing more.

What it does not support. No individual condition. MEAT is applied condition by condition, and a blanket sentence names none of them, states no status for any of them, and attaches no plan to any of them. Not one chronic condition on this patient's record is reportable from that sentence.

What it does to a risk score. If this is the only assessment in the collection year that touches those conditions, they are not recaptured. The member is described for the following payment year as not having them.

What it does to the visit level. Chapter 15 §15.10 already worked this: "chronic conditions stable, medications refilled" supports arguably low at best on the problems element, because the conditions are mentioned rather than addressed. The practice is very likely under-leveling visits it is actually performing correctly.

What I propose. Change the template from one blanket line to one line per condition, each carrying a status and a plan — the format the March 14 note already uses for three conditions and which takes the physician no additional thought, only additional keystrokes the template can supply. Keep the blanket line available for conditions genuinely not addressed. This is not a request for more documentation. It is a request that the same clinical work be attributed to the conditions it was performed on.

Exercise 36 — H.33 † (odd)

The three questions, in order:

  1. "How many codes did you delete last year, across all your clients? Not the rate — the count." A vendor with a real deletion practice answers from memory, because their own compliance staff ask about it. A vendor who cannot answer has described the program.
  2. "When your reviewer finds a condition the record does not support, who decides, and does that decision reach the plan?" Tests whether the finding has anywhere to go. A program that identifies unsupported codes and has no channel to remove them has built a discovery obligation with no remedy.
  3. "You are paid a percentage of the increase. Walk me through what your incentive is when a chart is ambiguous." Not an accusation. It tests whether they have thought about it and whether they can discuss it without defensiveness.

Is a contingency arrangement per se improper? No — it is common, and paying for a service out of what it identifies is an ordinary commercial structure. But it aligns the vendor's revenue with one direction of a bidirectional task, so the buyer has to supply the counterweight: a deletion requirement in the contract, an audit right, a trace from every submitted code to a page of the record, and a compensation structure for the reviewer that does not depend on the direction of the finding.

Exercise 36 — H.35 † (odd)

  1. Stop and scope it. Nine in a sample says nothing until you know the sample. Determine whether these are isolated or a pattern — same clinician, same condition, same source, same period?
  2. Do not touch the clinical record. A coder never adds, alters, or removes a clinical statement. Any correction to documentation is an addendum by the clinician, under Chapter 4 §4.5's rules, dated when it is made.
  3. Delete the unsupported submissions through the plan's correction process, and document the deletion — the count matters, per Figure 36.2.
  4. The sixty-day clock has started. Chapter 31 §31.9 owns the overpayment rule: an identified overpayment must be reported and returned within sixty days of identification, and "identification" includes the point at which reasonable diligence would have quantified it. Involve the compliance officer immediately; this is not the coder's decision to make alone.
  5. Root-cause it and fix the process — Chapter 37 §37.10's corrective action plan. Nine unsupported codes with nine different causes is a different problem from nine with one cause.
  6. Record what you found and when. Chapter 29 §29.9's discipline: whatever is decided above you, the contemporaneous record of the finding is the thing you will want later.

Exercise 36 — I.37 † (odd)

3044F is an outcome component — it reports a value the patient's body produced, the most recent A1c below 7.0%. 0001F is a process component — it reports that a clinician did something, namely that heart failure was assessed with the specified elements.

The three sentences for the physician:

"These two codes will be adjudicated at nothing — they carry no relative value and they are not paid. What they do is tell the payer's measure engine that the thing it is measuring actually happened, using the claim we are already sending rather than a chart abstraction somebody has to come and do later. If we skip them, the measure counts us as not having done work we did — and in a contract with a quality gate, that gets settled in dollars about eleven months from now."

Exercise 36 — I.39 † (odd)

The four terms and the question for each:

Term The question to ask the plan
Attribution "Which patients are mine, by what method, and do I get the list in advance or after the fact?"
The benchmark "What is it built from — my history, the region, a national trend — and is it risk-adjusted?"
The quality gate "Which measures, whose specification, which version, what data source, and is the gate a threshold or a multiplier?"
The data feed "What will you send me, in what format, how often, and how stale will it be when it arrives?"

Why coding behaves differently in the two arrangements. In a capitated arrangement, more complete coding raises the risk score and therefore the revenue attached to the population — the incentive §36.8's enforcement landscape exists to police. In a shared-savings arrangement, the benchmark is itself risk-adjusted, so a rising score raises the standard you are measured against at the same time it raises anything else. Coding does not manufacture savings; it moves both sides of the comparison. Programs have been designed to guarantee this — the Medicare Shared Savings Program caps how much an organization's risk score may grow between periods, precisely so that a documentation change cannot be mistaken for cost performance.

And the conclusion that matters: none of that changes the code. The record either supports a condition or it does not, and that is the only position that survives a change in the contract — which will happen.

Exercise 36 — J.40 † (the Encounter)

(a) The MEAT grid. As in G.27: diabetes, hypertension, hyperlipidemia, and the knee each satisfy all four criteria and are reportable as E11.9, I10, E78.5, and M25.561. Chronic kidney disease, stage 3a satisfies none of the four — one appearance, on the reviewed problem list, no status, no plan, no mention in the assessment, no linkage documented in either direction.

(b) The two questions.

  • Chapter 9 §9.7: "Is E11.9 correct for March 14?" — YES. The "with" convention would have permitted linking diabetes and chronic kidney disease without an explicit provider statement, but a prior question governs: Section IV reports additional diagnoses addressed, affecting treatment, or requiring management at this encounter, and the assessment does not address the kidney disease.
  • Chapter 36: "Is E11.9 sufficient?" — NO. It is incomplete as a description of the patient.

Both are correct because they are different questions. "Was this condition addressed at this encounter?" and "does this patient's record support reporting this condition sometime this year?" have different answers, and risk adjustment asks the second one. A code can be exactly right for the encounter and leave the patient described incorrectly for the year.

(c) The query. Model:

"The assessment continues metformin 1000 mg BID. The reviewed problem list includes chronic kidney disease, stage 3a. Was renal function evaluated or considered in the management of the diabetes at this encounter? If so, please document. If the kidney disease was not addressed at this encounter, please indicate that as well."

Graded on four features: it quotes only the relevant excerpt (minimum necessary); it offers the negative answer with equal weight; it asks about this encounter, not the patient generally; and it names no code, suggests no diagnosis, and mentions no payment. The form of a compliant query belongs to Chapter 38 §38.3; what Chapter 36 owns is the occasion.

(d) Yes and no.

  • Yes"I reviewed her eGFR before continuing metformin at this dose." An addendum under Chapter 4 §4.5's rules (dated when made, signed, identified as an addendum) now documents evaluation, and the encounter supports E11.22 + N18.31.
  • No — the code stays E11.9, the record is correct as written, and nothing has been lost except the assumption that a query is a tool for getting a better code.

(e) Why a query cannot fix this in general: a query cannot manufacture an encounter — if the condition was not managed on March 14, no answer to any question makes it reportable for March 14. The process that can fix it is prospective: surfacing unaddressed chronic conditions before the visit, so that the condition is actually assessed. That is §36.6's worklist and §36.8's legitimate half.

(f) The lens, and why it matters anyway. The patient is 58 and covered by a commercial PPO; no risk score is being computed for her, so §36.11's arithmetic is a lens in the same way Chapter 33's hip-fracture admission and Chapter 26 §26.9's provider-based clinic are lenses. The strongest honest argument that it matters: the practice's commercial charts and its Medicare Advantage charts are written by the same clinicians using the same templates and read by the same coder. A documentation habit is not payer-specific. The March 14 note is evidence about how this practice documents — and it is evidence collected on a chart where nothing was at stake, which makes it better evidence, not worse. Secondary arguments, all legitimate: the practice's own data cannot answer how many of our diabetics have kidney disease; the nephrology conversation a stage-3a diabetic should be having is on nobody's list; and the patient will be Medicare-eligible in seven years, at which point the chart the practice has been writing is the chart she brings.


Chapter 37 — Answer Key (daggered † and odd-numbered exercises)

The quiz's own key lives in quiz.md's collapsed block. Every figure below is a constructed teaching figure; all real-world program parameters, sampling methodology, and the sixty-day rule's current text must be verified at CMS, at the OIG, and with a compliance officer. Nothing here is legal advice.

Exercise 37 — A.1 (odd)

An audit is a structured reading of finished work against a written standard, by somebody who did not do the work, that records where the two disagree. It is not a search for wrongdoing; it is how you find out what a stranger would conclude from your records before a stranger is the one concluding it.

Exercise 37 — A.2 †

The three reasons: (1) an error found early is a correction and found late is a repayment; (2) an audit is the only instrument that measures quality, and an unmeasured function is indefensible; (3) errors run in both directions and the downward ones are invisible.

  • (a) The physician owner — lead with 3. Overpayment risk feels abstract and adversarial; "we are being paid less than the contract says, on a code you bill four thousand times a year" is neither. Then 1, because Account 31-2245 makes it concrete without accusing anyone.
  • (b) The hospital compliance officer — lead with 1. This audience already believes reason 2 and is measured on reason 1's downside. Reason 3 is a pleasant surprise rather than an argument.
  • (c) The coding manager in a budget meeting — lead with 2, and it is not close. The meeting is about whether the function survives, and the department that can show twelve quarters of measured accuracy is arguing from evidence while the department that "works hard" is arguing from loyalty.

Exercise 37 — A.3 (odd)

Three non-excellence explanations: the sample is too small to contain an error at the practice's actual rate; the standard is too vague, so nothing can fail it; the auditor is not independent — usually the coder auditing her own work or a colleague who shares the templates and assumptions and so cannot see the assumptions.

Check the standard first, because it is free to check and it fails silently. Ask to see three findings from the last two years and the authority each cited. If the findings are stated as preferences rather than citations, the standard is the problem.

Exercise 37 — A.5 (odd)

"A written plan you never ran is a written statement that you knew you needed to run it." No control at all is an oversight. A documented control that was never operated establishes what the organization understood its own obligation to be, and then shows it did not meet it.

Exercise 37 — B.6 †

"All professional claims with dates of service January 1 through June 30, any payer, on which a telehealth place-of-service code or modifier 95 appears with an evaluation and management code — count: N."

Filters needed: the date range, the claim type (professional, not facility), the payer set (or explicitly "all"), the service definition — which is the hard one — and the provider set.

The filter most likely to be defined wrongly is the service definition. "Telehealth" is not a code; it is expressed through a place-of-service code, a modifier, or both, and payers differ on which they require (Chapter 25 §25.8, Chapter 35 §35.9). A universe built on the place-of-service code alone will silently omit every claim where the practice used only the modifier — and the omitted claims are disproportionately the ones that went wrong, because inconsistent expression is the error you are looking for.

Exercise 37 — B.7 (odd)

Good for: a first look. A convenience sample is a legitimate way to find out whether an obvious problem exists, and it costs almost nothing.

Never use it for: an error rate, a comparison across providers or periods, an extrapolation, or anything that will be reported upward as a measurement.

The sentence that must appear: "These twenty charts were selected by availability, not at random. No rate stated here can be projected to any population."

Exercise 37 — B.9 †

The rule: a claim is scored against the rules in force on its date of service.

The rebuttal: "The claims at issue carry 2023 dates of service. The policy cited in the finding letter was revised effective [date] in 2025 and did not govern these claims when they were submitted. We request that the findings be rescored against the policy in force on each claim's date of service."

(Teaching note: this is one of very few objections that can dispose of an entire finding set on a single sentence, and it works in both directions — it is equally a reason your own internal audit may not score last year's charts against this year's guidelines.)

Exercise 37 — B.11 (odd)

A plausible register row for a macro that appends a distinct-procedural-service modifier:

  WHAT IT IS      charge-entry rule CE-114, configured [date], vendor
                  module "charge rules"
  WHAT IT ASSERTS "This procedure was distinct from the other procedure
                  reported on the same date."
  WHERE IT LANDS  the modifier field of the service line, in the
                  PRACTICE'S voice, on a claim the practice certifies
  OWNER           [named person], billing supervisor
  EVIDENCE TEST   Pull five claims the rule touched in the last quarter,
                  as TRANSMITTED. For each, find the sentence in the
                  operative or procedure note that establishes a distinct
                  session, site, encounter, or organ system. Record the
                  date checked and the number of the five that had one.

The test is the whole row. Note what it does not do: it does not ask whether the rule is configured as intended. It asks whether the sentence exists in the record on a claim the rule already sent.

Exercise 37 — C.13 (odd)

(1) Not supported · (2) wrong code · (3) sequencing or linkage · (4) supported but the record is fragile. Category 4 does not change the claim.

The book insists on it because category 4 is the only category that is cheap to fix and expensive to leave. It is where "not wrong, just unwritten" lives — Account 10-4471's missing decision-to-inject sentence, and Chapter 33 §33.10's "hypoxic" where "acute respiratory failure with hypoxia" was true. An audit reporting only categories 1–3 reports the errors that already cost money; category 4 reports the ones that are about to.

Exercise 37 — C.14 †

   code-level accuracy   3 correct of 4 reviewed  =  75%
   chart-level accuracy  0 charts with zero findings of 1  =  0%

The external reviewer is computing the chart-level (claim-level) number, because a reviewer's finding is about the claim.

Why it matters in an extrapolation: the sampling unit is very often the claim. One unsupported line therefore makes the entire sampled unit an error, and it is the unit's overpayment — not the line's — that gets multiplied by the universe. An internal program that reports only code-level accuracy will look systematically better than the same work looks from outside, which is a comfortable place to be right up until the letter arrives.

Exercise 37 — C.15 (odd)

The four meanings: code-level accuracy (correct codes ÷ codes reviewed) · chart-level accuracy (charts with zero findings ÷ charts) · financial accuracy (net dollar variance ÷ dollars reviewed) · directional accuracy (overstatement and understatement reported separately).

What must be added: the denominator, in the standard itself — "95% code-level accuracy, measured across a minimum of 25 charts per quarter, with overstatement and understatement reported separately." Without it, two coders on the same work are held to different numbers depending on who is counting.

Exercise 37 — C.17 †

Line 1 — 99213-25: supported. Finding category: none. Authority: the CPT modifier 25 definition and the E/M guidelines. Basis: the note documents two chronic conditions each separately assessed with a plan, two medications continued, and a laboratory test ordered — an evaluation and management service that exists independently of the lesion and would have occurred if the lesion had never been mentioned. That is the same structure Chapter 14 §14.4 found on Account 10-4471, and it is what §37.3's Code It callout lacked.

Line 2 — the excision: supported, with one condition. Authority: the CPT integumentary guidelines and the lesion-excision measurement rule (Chapter 17 §17.4). Basis: a procedure note exists and an excised diameter is documented. Code selection depends on that measurement plus the anatomic site and whether the lesion is benign; verify the exact code against the current CPT book and the pathology report where behavior is at issue.

The category-4 note: does the record state that the decision to excise was made at this encounter, or does the procedure appear as an event with no documented decision? The same gap that follows Account 10-4471 through this book applies here, and it is the sentence a reviewer will look for when the modifier is challenged. Flag it; do not score it as an error; fix the template.

Exercise 37 — D.19 (odd)

Universe — the complete, countable set of claims the review is about. Sampling frame — the enumerated list of the units in the universe, from which the draw is actually made. Point estimate — the universe size multiplied by the sample's mean overpayment; the reviewer's best estimate of the total. Lower bound — the low end of a confidence interval around that estimate, which is where sampling uncertainty is resolved in the provider's favor. Demand — what is actually asked for, which under the standard Medicare methodology is the lower bound rather than the point estimate.

Exercise 37 — D.20 †

   POINT ESTIMATE   520 x $318.75  =  $165,750.00

Check: 318.75 × 500 = 159,375.00 · 318.75 × 20 = 6,375.00 · 159,375.00 + 6,375.00 = 165,750.00 ✓

Exercise 37 — D.21 (odd)

   standard error   142.00 / sqrt(40)  =  142.00 / 6.3246  =  $22.45

Check: 6.3246 × 22.45 = 141.99 ≈ 142.00 ✓

Exercise 37 — D.22 †

   margin of error       1.685 x 22.45   =  $37.83
   lower limit of mean   318.75 - 37.83  =  $280.92
   DEMAND                520 x 280.92    =  $146,078.40

Checks: 22.45 × 1.685 = 37.828 → 37.83 ✓ · 280.92 × 520 = 146,078.40 ✓ · 165,750.00 − 146,078.40 = 19,671.60, and 37.83 × 520 = 19,671.60 ✓

Why the demand is lower than the point estimate: because the reviewer read forty claims and is making a statement about five hundred and twenty. The gap between the two numbers is the price of that uncertainty, and the methodology assigns it to the payer rather than to the provider. It is a genuine concession written into the rule, and it is the single reason the number in the letter is not the number in the analysis.

Exercise 37 — D.23 (odd)

   standard error        41.00 / 6.3246   =  $6.48
   margin of error       1.685 x 6.48     =  $10.92
   lower limit of mean   318.75 - 10.92   =  $307.83
   DEMAND                520 x 307.83     =  $160,071.60

   difference from D.22  160,071.60 - 146,078.40  =  $13,993.20

Checks: 6.3246 × 6.48 = 40.98 ≈ 41.00 ✓ · 6.48 × 1.685 = 10.9188 → 10.92 ✓ · 307.83 × 520 = 160,071.60 ✓ · 520 × (37.83 − 10.92) = 520 × 26.91 = 13,993.20 ✓

What the practice did "right" to earn \$13,993.20 of extra demand: it was consistent. A low standard deviation means the overpayments barely varied — which is what a macro, a template, or a carefully taught convention produces. Sloppiness generates variance and variance widens the interval; discipline generates uniformity and uniformity narrows it. The organization most careful about doing things the same way every time is the one whose single wrong rule is worth the most.

Exercise 37 — D.24 †

It is a census, not an extrapolation. The special investigations unit reviewed every claim carrying the pattern — all forty-two — and demanded the actual overpayment computed on each. Nothing was projected from a sample onto a universe, because the sample was the universe.

The fact that made it this size: the practice was small. Forty-two claims was the entire population of claims carrying the pattern over eighteen months. The macro, the modifier, the operative notes, and the \$612.40 average would all be identical at a group ten times the size — and there the payer would not read every note. It would sample, project, and demand a six-figure number. Extrapolation's multiplier is volume, not severity.

Exercise 37 — D.25 (odd)

Correct it in three sentences: a small sample does not limit the demand, because the demand is computed from the universe, not from the sample. A larger sample produces a narrower confidence interval, which raises the lower bound and therefore increases what is demanded. What determines the size of a demand is how many claims exist that carry the pattern, and how consistent the pattern was — which is why the first question a response letter asks is how the universe was defined (§37.6, Figure 37.3).

Exercise 37 — E.27 †

Order and ownership:

  1. The UPIC letter — first, and it changes the room. Benefit integrity means fraud, waste, and abuse rather than billing error. Counsel is involved before anything is written, and counsel decides who else is. Nobody in the business office answers this one alone, and nobody calls the contractor to "clear it up."
  2. The RAC complex review — real money, a real deadline, and a records packet that must be built as a document (§37.7). Coding and compliance produce it; the practice manager or compliance contact signs the cover letter.
  3. The TPE round-one probe — a small sample with education attached, and the response determines whether there is a round two. The coder or auditor prepares it; treat it as the cheapest external audit available.
  4. The CERT request — administratively simple and often deprioritized, which is the error. It is low stakes for you and high stakes for the national number, and a non-response is still scored as an error and can still cost the claim. Clerical staff can assemble it; somebody must verify it went.

The UPIC is the one that changes who is in the room, and that is true on the day the letter arrives, not after the analysis.

Exercise 37 — E.29 (odd)

For the design: a contractor with no financial stake in finding anything will find less than one with a stake, and the improper payments are real. Funding the work out of what it recovers also makes the program self-supporting rather than a claim on appropriations.

Against the design: the fee is earned on what is identified, not on what survives review, so the incentive rewards volume of findings rather than quality of findings — and the cost of a wrong determination falls on the provider, who bears the appeal.

(Both are true, and neither is quantified here. The reform that addressed the second without abandoning the first was withholding the contingency fee until after the second level of appeal — Case Study 1.)

Exercise 37 — F.31 (odd)

Dated the 3rd, 45 calendar days: the response is due on the 17th of the following month (3rd + 45 days). The internal calendar should carry a completion date roughly a week earlier — around the 10th — plus a separate earlier date for any physician signature or attestation that must be obtained.

The control that would have prevented the twenty-one lost days: one named person opens every payer envelope and portal notification, and every request is logged the day it arrives, with its deadline, somewhere more than one person can see. Chapter 27's Case Study 1 and Chapter 24's Case Study 1 are the same failure in different clothes: the document arrived correctly and nobody owned the place it arrived.

Exercise 37 — F.32 †

Signature present but illegible: send the packet with a signature log identifying the signature, or a signature attestation statement from the author. Either is generally accepted, because the signature exists and the question is only whose it is.

Signature absent: neither works, and neither should be sent. An attestation cannot create a signature that was never applied, and a signature added now is a late entry created after a records request — the worst document a file can contain (Chapter 4 §4.5).

Why the answers differ: the illegible signature is an identification problem, and identification can be established from other evidence. The missing signature is an authentication problem: nothing in the record establishes that the author reviewed and adopted the content. Score it, concede it, and fix the workflow prospectively.

Exercise 37 — F.33 (odd)

The words, as you would actually say them:

"I can't do that, and I want to explain why rather than just refuse. Anything added to the note now is dated now, and it will be dated after their letter arrived — so whatever it says, it reads to a reviewer as a document created for the audit. That turns a documentation finding, which we can concede and fix, into a credibility question about the whole record, which we can't. Let me send what we have and concede the point if they raise it. Then let's change the template this week, so the sentence you meant is in every note from here on, written at the time, by you."

The two rules it rests on: Chapter 4 §4.5 governs amendments, addenda, and late entries and exists to keep a correction honest — identified author, date of entry, original preserved. And Chapter 4 §4.7's line: the coder does not know what the provider meant; the coder knows what the provider wrote. The physician is almost certainly right about what happened. That is not the question a reviewer is asking.

(Note the shape of the answer. It refuses, explains the mechanism, offers what you can do instead, and puts a date on it. A refusal without the third and fourth parts is the reason people stop asking the coding department and just do it.)

Exercise 37 — F.34 †

(Quoted note language below is constructed for this exercise.)

CLAIM 0142 — DISAGREED. The finding states that the documentation does not support a significant, separately identifiable evaluation and management service and that modifier 25 is not supported.

Authority. The CPT definition of modifier 25 requires a significant, separately identifiable evaluation and management service above and beyond the usual preoperative and postoperative care associated with the procedure. It does not require a different diagnosis, and it does not require that the E/M service be unrelated to the procedure.

The record. The assessment and plan at Exhibit 12, page 2, state: "1. Type 2 diabetes — hemoglobin A1c ordered today; metformin continued at current dose. 2. Essential hypertension — at goal; lisinopril continued. 3. Hyperlipidemia — atorvastatin continued." Three chronic conditions are separately assessed, each with a documented plan; two medications are addressed and one laboratory test is ordered with a stated clinical reason. None of this work relates to the procedure, and all of it is documented distinctly from the procedure note at Exhibit 12, page 3.

Conclusion. The record documents an evaluation and management service that would have been furnished and reported had the procedure not occurred. Modifier 25 is supported.

(Teaching notes: the entry restates the finding first, cites the reviewer's own authority, quotes the record rather than describing it, and stops. It contains no adjectives, no assertion about what the physician intended, and no argument the record cannot carry.)

(And on the same letter, if six of eleven findings are correct: concede all six in the first paragraph of the cover letter, with the dollar position stated plainly. The tactical reason is that a reviewer reading a blanket disagreement learns your assessments carry no information and discounts the five you contest. The ethical reason is that they are correct — the claims were not supported, the money was not earned, and retaining it once quantified starts a different clock entirely, §37.9.)

Exercise 37 — G.35 †

First, "identified." An overpayment is identified when the person has determined — or should have, exercising the diligence the rule requires — that an overpayment was received and has quantified it. A credible indication is not identification; a quantified conclusion is. But a timely, good-faith investigation is contemplated, so "we suspected and did not look" does not avoid identification. It creates a worse fact pattern, because the failure to investigate is itself what an enforcement authority will describe.

Then the routing:

  • (a) A charge-capture rule adding a unit for eleven months, quantified.Refund, through the payer's or MAC's overpayment process, per Chapter 31 §31.9. This is an ordinary quantified overpayment with no indication of intent. It is also an assertion-register entry and a corrective action plan (§37.10), and the CAP should be attached to the refund.
  • (b) A per-referral payment to a marketing company.Counsel, then likely the OIG Self-Disclosure Protocol. Remuneration tied to referrals implicates the Anti-Kickback Statute (Chapter 5 §5.4), which is a civil monetary penalty authority. This is not a billing question and it is not the coding department's to route further.
  • (c) An undocumented equipment lease with a physician's spouse's company.Counsel, then the CMS Voluntary Self-Referral Disclosure Protocol. The physician self-referral law reaches financial relationships and is strict liability — "nobody intended anything" is not a defense, and an ordinary refund does not resolve it.
  • (d) A coder instructed to bill a level she cannot support, continuing after she raised it.Counsel first. Conduct that continued after somebody objected is the fact pattern that converts an error into a question about knowledge (Chapter 5 §5.2). The coder's own obligation is Chapter 5 §5.9 plus this chapter's: document what she found and when, in writing, and escalate.

Exercise 37 — G.37 †

Rewritten with six fields:

  FINDING      Q2 audit: 4 of 25 charts carried modifier 25 on an E/M
               billed with a 000-day-global procedure where the record
               documented one problem, one evaluation, one procedure.
               Category 1, not supported. Overstatement.
  ROOT CAUSE   The charge ticket presents modifier 25 as a default
               selection whenever a procedure code is entered; no step
               requires anyone to affirm the separately identifiable
               service.
  THE CHANGE   Remove the default. The modifier requires an affirmative
               selection, and the charge ticket displays the four
               supporting elements beside it.
  OWNER        [named person], practice manager, with the PM system
               vendor.
  DATE         Change requested [date]; in production by [date].
  TEST +       Re-audit 25 charts drawn from the 60 days AFTER the
  RE-AUDIT     production date, same universe definition. Target: zero
               category 1 findings on this issue. Re-audit owner and
               date calendared now, not later.

Rung on the durability ladder: 1 — it changes what the system permits, not what anybody knows.

When rung 1 would be the wrong choice: if removing the default were to create a large volume of new manual decisions for a modifier that is correctly applied most of the time, the manual decisions bring their own error rate — and the error would simply move from omission to commission. The test is whether the intervention's cost is smaller than the error's. Here it is not close: four of twenty-five is a rate that will extrapolate, and affirming a modifier takes a keystroke.

Exercise 37 — H.38 (exam style)

C. The E/M is not supported; remove the line. A is the trap — downcoding a service the record does not separately support at any level is still billing a service that did not separately happen (Chapter 5 §5.8). B is the other trap: a query is a documentation instrument, not a scoring one, and the question asked what the auditor should do.

Exercise 37 — H.39 (odd, exam style)

B. Extrapolation is not automatic. Under Section 1893(f)(3) of the Social Security Act a contractor may use it only where there is a determination of a sustained or high level of payment error, or where documented educational intervention has failed to correct the error. A is the common misconception and it is the first thing a response letter should test: finding an error in a sample does not, by itself, authorize projecting anything. D invents a threshold that does not exist — sample size affects the interval's width, not the authority to extrapolate.

Exercise 37 — H.40 † (the Encounter extension)

Rescoring Account 10-4471 with no procedure note:

  • Line 1 — 99214-25. Now the hardest call in the exercise, and the answer is not supported as billed. Modifier 25 asserts an E/M service separately identifiable from a procedure — and if the procedure is not documented, the claim is asserting a relationship to a service the record does not contain. The E/M itself is still supported on the four elements from Figure 4.2 (Chapter 4 §4.10), three of which have nothing to do with the knee. Finding: category 3, linkage — the E/M stands, the modifier does not, because the thing it distinguishes the visit from is not in the record.
  • Line 2 — 20610-RT: category 1, not supported. Authority: the CPT descriptor and the record. A charge generated at check-out is not documentation of a procedure. Nothing in the record states that a needle entered a joint, which drug was given, which side, or by whom. The code comes off.
  • Line 3 — J1030: category 1, not supported. The drug is reported at a dose the record does not document, for an administration the record does not document.
  • Line 4 — 36415: supported. The venipuncture is independently documented and the laboratory orders establish its reason.

Financial variance: lines 2 and 3 come off entirely — \$150.00 + \$18.00 = \$168.00 in charges, against an expected allowed of \$78.60 + \$6.28 = \$84.88. Line 1's modifier finding does not change the E/M's allowed amount on this claim but does change whether the payer would have paid it at all. Check: 367.00 − 168.00 = \$199.00 in charges remaining ✓.

What a reviewer would do: deny lines 2 and 3 for insufficient documentation, and — this is the part worth sitting with — look at the practice's other injection claims. A charge that exists with no procedure note is not an isolated coding question; it is a charge-capture pathway that may be producing the same result routinely. That is how a four-line claim becomes a universe (§37.6).

The control that would have caught it before the claim left: a rung-2 intervention — a pre-bill hold or scrubber edit requiring a signed procedure note on file before any procedure code from the charge ticket may be released. It sits on the durability ladder above education and below rung 1 (making the charge un-enterable without a linked note), and rung 2 is the right choice here because the charge ticket is a legitimate capture tool that must keep working.

And the register entry it implies: "the charge ticket asserts that a documented procedure occurred" — an assertion made by a form, landing on a claim line, in the practice's voice, with an owner and an evidence test that is exactly this exercise (§37.10).


Chapter 38 — Answer Key (daggered † and odd-numbered exercises)

The quiz's own answer key lives in quiz.md's collapsed block. Every dashboard, engine output, and evaluation figure below is a constructed teaching figure. Professional query guidance is revised without a calendar — verify the current edition with the publishing organization, and never cite a query rule from a textbook.

Exercise 38 — A.1 (odd)

The definition: clinical documentation integrity is the discipline of making the medical record describe the patient accurately, completely, and in language the classification systems can read, corrected only by the clinician who owns the statement.

The three excluding clauses. "Accurately" — not favorably; it excludes the severity-capture program, because a program that only moves one direction is describing itself. "In language the classification systems can read" — it excludes the accusation that CDI is criticizing physicians' clinical communication; the translation loss is between two audiences, not a failure by either. "Corrected only by the clinician who owns the statement" — it excludes the coder, the CDI specialist, and the engine from authoring, which is Chapter 4 §4.7's line unchanged.

Exercise 38 — A.2 † (odd)

What is accurate: CDI programs do produce measurable financial effect, they are budgeted against it, and pretending otherwise is the kind of dishonesty that makes a program easy to attack. Chapter 33 §33.10's \$1,867.44 is real money attached to one documented phrase.

The operational failure it produces: if the program's stated objective is revenue, then the worklist gets built on financial materiality alone, the metrics that get published are query rate and agreement rate, and both of them are met by sending more queries and by sending only the ones that will be answered a particular way. The program becomes a leading program by selection, without a single non-compliant query. §38.4 owns the failure.

The correction to offer: keep the financial reporting, report it in both directions with adds and removals on separate lines, and state the objective as accuracy. A program that can show an auditor a query that removed a diagnosis is defending itself with evidence; one that cannot is defending itself with adjectives.

Exercise 38 — A.3 (odd)

One sentence: an audit is a reading of finished work against a written standard by someone with no stake in the interpretation; CDI is a reading of unfinished work that can still be completed by the person who made it.

The structural difference: timing, and what timing does to the remedy. An audit's output is a finding and a corrective action plan. A CDI review's output is a clarification made by the clinician inside the ordinary documentation process — a progress note rather than an addendum (Chapter 4 §4.5), with no amendment trail and no corrected claim.

Exercise 38 — B.5 † (odd)

COPY-FORWARD POLICY

  MAY NOT carry forward:
    - the assessment and the plan
    - examination findings for the problem being treated today
    - any statement of total time on the date of the encounter
    - any statement that a decision to perform a procedure was made today
  MAY carry forward:
    - medications, allergies, past surgical and family history,
      stable problem-list entries, and other reference content

  THE PRINCIPLE: the sections that record WHAT HAPPENED TODAY do not carry.

Why that principle and not "no cloning": it is enforceable, it is defensible to a clinician, and it targets exactly the fields on which a code turns. A blanket prohibition loses the argument and the relationship, and copy-forward has genuine clinical value.

Exercise 38 — B.7 † (odd)

Five steps, no chart review:

  1. Pull a sample of signed notes per provider over a defined window — the notes themselves, as text.
  2. For each note, compare it against that provider's previous note for the same patient.
  3. Compare it also against that provider's notes for different patients on the same day.
  4. Compute a similarity score per pair and look at the distribution per provider, not the mean.
  5. Report the distribution beside a peer comparison, and treat outliers as questions, not findings.

What it is called: Chapter 37 §37.10's outside-in view — the analysis that uses only what a reviewer outside the organization could compute. Step 3 is the one that matters most, because identical notes across different patients is the pattern a payer's data analysis finds first.

Exercise 38 — B.9 † (odd)

The refusal, two sentences: a default value is not documentation, because nobody decided it for this patient; and the first time ultrasound guidance is used, the note will affirmatively state that it was not, which is a false statement in the legal health record over a physician's signature.

The mechanism: a configuration making an assertion nobody chose — the mechanism this book has watched produce a dozen failures across every part, in claim fields, posting rules, a payer's software, a note over a signature, and a script handed to a person.

Where it would have to be recorded: on Chapter 37 §37.10's assertion register, with what it asserts ("no imaging guidance was used on this procedure"), where it lands (the clinical note, in the physician's voice — amendable but never un-assertable), a named owner, and an evidence test run against a real record. Note that the register would not make it acceptable; it would make it visible.

Exercise 38 — C.11 (odd)

Four, each with its source:

  1. The clinician's memory is current — Chapter 21 §21.8, which established that a query cannot ask a surgeon to remember something eighteen months later.
  2. The clarification is a progress note rather than an addendum — Chapter 4 §4.5's amendment rules, and Chapter 30 §30.11's warning about a post-denial addendum.
  3. The record is still being written, so the clarification shapes the rest of the stay's documentation rather than fixing one closed sentence.
  4. No claim exists yet, so nothing has to become a corrected claim — Chapter 29 §29.6.

Exercise 38 — C.12 † (odd)

Four criteria: (a) records whose working DRG sits in a family with a severity split and carries no documented complication or comorbidity — finds the highest-value gaps; (b) conditions with known documentation ambiguity (respiratory failure, sepsis, heart failure specificity, renal staging, malnutrition) — finds the recurring ones; (c) clinical indicators present without a corresponding diagnosis — finds what a rule set can surface; (d) a random sample.

(d) keeps the other three honest, because (a) through (c) are all built on financial or clinical expectation, and a program that reviews only where it expects to find something can never learn what it is not looking for — and, more dangerously, produces a findings distribution that runs one direction by construction.

If (d) is dropped for capacity: the program loses its only unbiased estimate of its own hit rate, its only chance of finding an over-documented diagnosis, and its only answer to an auditor asking why every finding adds severity. Drop review volume before you drop the random leg.

Exercise 38 — C.13 (odd)

Pre-visit review reads the chart before the appointment and surfaces chronic conditions the visit will probably address, so the assessment can address them in the note rather than in memory (Chapter 36 §36.6). It is a rung 2 control on Chapter 37 §37.10's ladder — it makes the gap visible before the claim leaves — and it costs clinician attention rather than throughput.

Post-visit, pre-bill review holds defined encounter types for a documentation read before submission. Also rung 2, and it costs throughput exactly as the ladder predicts.

The boundary: surfacing an unaddressed condition before the visit so the clinician can decide whether to address it is care. Surfacing it after so somebody can decide whether to report it is a different activity, and Chapter 36 §36.8 draws that line.

Exercise 38 — D.15 † (odd)

(a) The markers tripped, with the words that trip them.

  • Marker 1 — supplies the answer: "Please document severe protein-calorie malnutrition."
  • Marker 2 — names the classification: "so this admission groups correctly."
  • Marker 3 — implies the money: the same clause. "Groups correctly" is a payment statement.
  • Marker 4 — no real alternative: there is one option and no way to answer "no."
  • Marker 5 — signals the preferred response: the whole construction, and the closing "thanks!" frames compliance as the courteous answer.

Also defective on element 2 of §38.3: "albumin has been low all week" is a characterization, not the record's own values, and a dietitian consult is not by itself a clinical indicator of a severity level.

(b) A compliant rewrite [constructed]:

 Dr. -,
 Clarification is requested on the nutritional assessment for this admission.

 The record documents:
   - albumin 2.6 g/dL on admission and 2.5 g/dL on hospital day 4
   - documented weight loss of 6.4 kg over the preceding three months
   - dietitian consult on hospital day 2, note dated and signed
   - assessment on hospital day 4 reads "poor nutritional status"

 Based on your clinical judgment, can the nutritional status be further
 specified?
   ( ) Severe protein-calorie malnutrition
   ( ) Moderate protein-calorie malnutrition
   ( ) Mild protein-calorie malnutrition
   ( ) Poor nutritional status without malnutrition - assessment as
       written is intended
   ( ) Clinically undetermined
   ( ) Other: ______________________

 Please document your response in the medical record. No particular
 response is intended or preferred.

Note the fourth option: it is the record's most likely answer stated with equal weight, and its presence is what makes the option set non-leading rather than merely long.

(c) If the original has already been sent: tell the compliance officer today rather than hoping. Do not send a follow-up "clarifying" query, because a second query on the same encounter after the first is marker 5. Preserve the original query text; do not delete or edit it. Whatever the physician documented in response is theirs and stays in the record, and whether the resulting code is reportable is a question for compliance with the query in front of them.

Exercise 38 — D.17 † (odd)

The rule: a retrospective query may ask a clinician to clarify what the record shows; it may not ask them to supply what the record never captured.

(a) Operative report documents "debridement performed" with no anatomic region. A query is available only if the report contains something from which the region can be clarified — the approach, the structures named elsewhere in the report, the diagnosis. If the report is genuinely silent, the clinician is being asked to remember, which Chapter 21 §21.8 excludes. Account 31-2245 is the cautionary file: eleven of forty-two claims were probably justified and were repaid anyway.

(b) Transfusion, estimated blood loss, and an assessment reading "blood loss." A query is available and this is the textbook case (Chapter 4 §4.9's Figure 4.1). The clinical evidence is in the record; only the diagnostic statement is missing; and the question is genuinely answerable in more than one direction, including "expected post-operative blood loss without anemia."

(c) No mention of the condition anywhere; the physician recalls treating it. No query. There is nothing to clarify, and a query here manufactures documentation. The honest outcome is the code the record supports and a prospective template fix.

Exercise 38 — D.19 † (odd)

The two models: the query and its response are part of the permanent legal health record (Chapter 4 §4.8's designated record set), or they are retained as a separate business record in the CDI or coding system.

The three rules that hold under either, and what goes wrong:

  1. The response must land in the medical record itself. Violated: a diagnosis is coded from a query form, so the claim asserts something the record does not, and on a records request there is nothing to produce. This is a coding error and potentially a false claim.
  2. Every query and response must be retrievable. Violated: the organization cannot answer "show me the queries behind the shift" (Chapter 33 §33.6), and a case mix index it cannot explain becomes the auditor's subject rather than its own.
  3. Retention runs at least as long as the audit look-back. Violated: the organization destroys its own defense on a schedule it chose, and the only surviving evidence of a documentation change is the change itself, with no provenance.

Exercise 38 — E.21 (odd)

Query rate — met by sending more queries; the marginal query is by construction the weakest in the queue, and a weak clinical case is what makes a suggestive wording feel necessary.

Agreement rate — met by sending only the queries expected to be answered a particular way; every query sent is compliant, and every query not sent is invisible.

Exercise 38 — E.22 † (odd)

The paragraph: a CDI program does not need to write a single leading query to become a leading program. It needs only to choose which clinically warranted queries to send. Drop the ones where the evidence is ambiguous, the ones where "clinically undetermined" is the likely answer, and the ones where the honest result is a removal, and the agreement rate rises while every individual query remains textbook-compliant. The selection is the leading act, and no review of query text can detect it — which is why the corrective control is the worklist design and the published direction split, not a query audit.

Who predicted it: Chapter 6 §6.3, in the discussion of grouper "what-if" runs. A what-if run tells you what a documentation change would be worth and says nothing about whether it would be true.

The line: a program that lets "will this change the DRG?" drive "is this true?" has become the leading-query problem at institutional scale.

Exercise 38 — E.23 (odd)

(a) Defensible. Attention is finite and has to go somewhere; prioritizing review by materiality is triage.

(b) Not defensible. The clinical judgment that a query is warranted has already been made; letting the answer's value decide whether to ask converts a documentation question into a revenue decision.

(c) Not defensible, and this is the corruption itself. Selecting on the likely direction of the answer produces a one-directional findings distribution by construction — which is exactly what a reviewer computes from claims data without opening a chart.

Exercise 38 — E.24 † (odd)

Program A: 152 ÷ 400 = 38.0% query rate · 139 ÷ 152 = 91.4% response rate · 128 + 11 + 0 = 139 ✓ · 128 ÷ 139 = 92.1% agreement · 61 upward + 0 downward = 61 ✓.

Program B: 88 ÷ 400 = 22.0% · 79 ÷ 88 = 89.8% · 52 + 18 + 9 = 79 ✓ · 52 ÷ 79 = 65.8% · 31 + 3 = 34 ✓.

The compliance officer's paragraph (using only the table's numbers): "Program B sent 88 queries against Program A's 152 and produced 34 DRG changes against 61, so on volume alone Program A looks stronger. The relevant difference is elsewhere. Program B's responses include 9 removals or de-specifications and 18 'clinically undetermined,' against Program A's 0 and 11; Program B's DRG changes include 3 downward, against Program A's 0. On four hundred reviewed records, Program A's findings run in exactly one direction. I can defend Program B's 65.8% agreement rate to a reviewer, because the number is low for a reason I can point to on the same page. I cannot defend Program A's zero removals, because it has only two explanations and one of them is that the worklist decides the answer before the query is written."

Exercise 38 — E.25 (odd)

Per account, produced on demand: the query text as sent · the date and time · who sent it and their credential · the clinical evidence cited from the record · the response as given · where the response landed in the medical record, by note type and date · the code that changed · and the direction of the change.

What the inability to produce it says: the case mix index has no explanation the organization controls. Chapter 28's Case Study 1 supplies the phrase — a number with a story attached stops being a question — and here the organization does not even have the story. The auditor's question is not hostile; it is the obvious next question, and a program that has not built for it has left its own best evidence unrecorded.

Exercise 38 — F.27 † (odd)

Code Disposition Reason
J18.9 Accept, with the setting checked "Treat empirically for pneumonia" plus a documented radiographic finding is a diagnostic statement on an inpatient record; on an outpatient claim the same phrasing would not support it (Chapter 9 §9.5). Certainty is the qualifier at issue.
I21.9 Reject Experiencer. "Father died of an MI at 58" is family history, not this patient's condition. A family-history code from the Z80.-/Z82.- ranges may be reportable if the record supports it; the acute infarction code is not.
R06.02 Query or reject, depending on sequencing Shortness of breath is a symptom integral to the documented COPD exacerbation and is not separately reported when it is (Chapter 9's integral-symptom rule). The engine matched a phrase, not a relationship.
J44.1 Accept Documented by name with acuity.
A41.9 Reject Negation. "Sepsis ruled out; blood cultures negative x2" asserts the absence of the condition. The confidence of 0.55 is a hint, not the reason — the reason is that the sentence says no.
E11.9 Accept if addressed The concept is present, but Section IV reports conditions addressed at the encounter. If the record shows the diabetes managed during the stay, report it; if it appears only on a list, it is not reportable on that basis (Chapter 9 §9.7).

The two that would produce an internally inconsistent claim: A41.9 and J18.9 together with J44.1's context — but the sharper answer the exercise is looking for is A41.9 accepted alongside a record that documents sepsis ruled out, which asserts on a claim the opposite of what the record says. A claim carrying both a ruled-out condition and the workup that ruled it out is the single easiest finding an auditor makes.

Exercise 38 — F.29 † (odd)

The correct pointers (Chapter 25 §25.5, frozen canon):

  99214-25  ->  A B C D
  20610-RT  ->  A
  J1030     ->  A
  36415     ->  B

with A = M25.561 · B = E11.9 · C = I10 · D = E78.5.

What a first-listed default produces: every line pointed at A, including 36415.

The assertion that error makes: that a venipuncture treats knee pain. The blood was drawn for the hemoglobin A1c, which is why line 4 points at the diabetes code.

Why it matters and why it is invisible: diagnosis linkage is exactly what a medical-necessity reviewer checks, and no edit rejects a wrongly pointed line that happens to pay. This is a defect that surfaces only in review — the same shape as Chapter 37 §37.11's category-4 findings.

Exercise 38 — F.31 (odd)

The one question: "Do any of these rules fire in the direction that removes or de-specifies a diagnosis?"

A good answer names specific rules, shows the queries they produced in the last quarter, and shows the responses — including the ones that removed a code. A bad answer explains why removals are rare.

Two rules that fire the other way: (1) a documented diagnosis whose usual clinical indicators are absent from the record — a documented acute respiratory failure with no oxygen requirement, no saturation values, and no supporting orders; (2) a diagnosis carried forward from a prior encounter's assessment with no current evaluation, treatment, or plan, which is Chapter 36 §36.7's MEAT question asked by a rule set instead of by a person.

Exercise 38 — G.32 † (odd)

Structure Code space Variability Feedback Verdict
(a) Screening mammography Yes — templated report, standardized assessment categories Yes — a small family Yes Yes — frequency and coverage edits deny quickly Autonomous is plausible
(b) Established-patient office visit leveling No — the level turns on prose No — the level plus every diagnosis No No Fails on all four
(c) Shoulder arthroscopy from an operative report No — a person describing what they did No — plus edits, modifiers, and the package No Partial — edits deny some errors Fails; assisted at best
(d) Venipuncture and routine panels Yes — the order is the document Yes Yes Yes Autonomous is plausible

The one that fails on property 4 differently: (b). An E/M level that is too low produces no signal at all — no denial, no edit, no exception report (Chapter 28 §28.8). A system optimized on denial feedback therefore learns to avoid the errors that get caught, which in E/M means learning to code low. Over time the system does not become accurate; it becomes quiet, and quiet is the direction nothing measures.

Exercise 38 — G.33 (odd)

(a) Chapter 29's Case Study 2 — a template that auto-inserted a modifier 25 attestation into signed notes. The difference in this version: the assertion lands on the claim, not in the clinical record, so it is correctable going forward and it does not sit over a physician's signature. That makes this version less serious, and it is the only respect in which it is.

(b) Can fix: turn the rule off; identify the affected claim population from the rule's own history; quantify; and route through Chapter 31 §31.9's overpayment workflow if the review establishes one. Cannot fix: the eighteen months of claims already submitted, and the notes that were never written to support the modifier. The defense is contemporaneous documentation and it cannot be built retroactively (Chapter 21 §21.8).

(c) The register field: "what it asserts," written in plain language — "the provider performed a significant, separately identifiable evaluation and management service." Written that way, the rule is obviously indefensible, which is the field's whole purpose. The evidence test: pull a claim the rule touched, as transmitted, read the note behind it, and ask whether that sentence is true on that claim.

Exercise 38 — G.34 † (odd)

Population: accepted engine suggestions, stratified by confidence band, drawn from a defined universe (date range, document type, coder) that ends in a count — Chapter 37 §37.2.

Standard: the record, the code set, the guidelines, the edits, and the coverage policy as they stood on the date of service.

Reporting: accuracy with its denominator, by confidence band, with direction (overstated versus understated) reported separately, plus the four finding categories from Chapter 37 §37.3 — including supported but fragile.

What you must not score against: the engine. An "agreement with the engine" metric measures conformity, not accuracy, and it will be highest exactly where the engine is most confidently wrong.

Why sampling rejections measures the wrong thing: a rejection is a place the coder already looked and already decided. The exposure lives in the agreements, where nobody looked twice — and §38.9's cost asymmetry says the accepted false positive is the error with the legal exposure attached.

Exercise 38 — G.35 (odd)

  1. What the reviewer sees first — usually a vendor's default screen layout, chosen by an implementation team.
  2. Whether disagreement is cheap — the workflow configuration, usually set by an information systems analyst.
  3. Whether the productivity standard was reset for review work — a manager or a director.

Number 3 is the staffing decision wearing a technology decision's clothes. If assisted charts-per-hour becomes the standard with the quality standard unchanged and no allowance for review time, the organization has budgeted for a rubber stamp and will get one.

Exercise 38 — H.36 † (odd)

Precision = 1,712 ÷ 1,905 = 89.9%. Recall = 1,712 ÷ 1,840 = 93.0%.

Sums: 1,712 + 193 = 1,905 ✓ · 1,712 + 128 = 1,840 ✓.

After the loop: unsupported accepted 22; supported found by the reviewer 96. Claims carry 1,712 + 96 = 1,808 supported and 22 unsupported = 1,830 codes. Sums: 171 + 22 = 193 ✓ · 96 + 32 = 128 ✓. Post-review accuracy = 1,808 ÷ 1,830 = 98.8%. Post-review recall = 1,808 ÷ 1,840 = 98.3%.

Which number carries the exposure, and why it is the smallest: the 22. The 32 still-missing codes cost the facility money and distort its data, and no statute is interested in them. The 22 unsupported codes are twenty-two statements to a payer that the record does not support. It is the smallest number precisely because the loop worked — and the loop's success is what makes the residue concentrated rather than diffuse: if those 22 share a cause, they are a pattern, and a pattern extrapolates.

Exercise 38 — H.37 (odd)

Paragraph one — what a missed code costs. It costs money, and then it costs truth. The claim understates what was done; the severity understates who the patient was; the risk score understates the population (Chapter 36); the quality data computed from claims describes patients as healthier than they were. And the loss is silent: an underpayment does not deny, does not reject, appears on no exception report, arrives as a payment, and raises the net collection rate (Chapter 28 §28.8). Chapter 5 §5.8 settled it for this book: upcoding and downcoding are both errors, and coding low is not the conservative option or a defense.

Paragraph two — what an unsupported code costs. Everything above, plus a category the first error does not have. A code on a submitted claim is a statement to the payer, and to a federal health program the claim is a certification (Chapter 5 §5.1). The False Claims Act supplies a developed theory for billing for what the record does not support and none for failing to bill for what it did. The two errors cost different currencies, and the second one compounds: Chapter 37 §37.6 showed that consistency narrows the interval, satisfies the precondition for extrapolation, and removes the argument that any sampled claim was different. The disciplined organization is the one whose single wrong rule extrapolates most cleanly.

Exercise 38 — H.39 (odd)

B is compliant.

A trips markers 1, 2, and 3: it supplies the diagnosis, names the grouping, and states the payment consequence in one clause ("so the admission groups correctly").

C trips markers 1, 4, and 5: it supplies the answer, offers no alternative, and "please confirm" signals the preferred response. It is also a yes/no query used to introduce a diagnosis rather than to confirm one already in the record, which is the line Case Study 2's reversal draws.

D trips marker 5 most clearly, and it introduces a form of leading the markers barely have a name for: it cites other patients' records as the reason to document this one. Nothing about two other admissions is evidence about this patient.

Why B passes: it quotes the record's own indicators, asks an open clinical question, offers an option set that includes both a lower-acuity answer and "assessment as written is intended," names no code and no dollar, and leaves the clinical judgment where it belongs.

Exercise 38 — H.40 † (odd)

Dispositions (engine output at §38.5's Encounter panel):

Suggestion Disposition One-line reason
99214 Verify, do not accept A level is a judgment about medical decision making; confirm against §15.13's frozen leveling — two of three elements at moderate
20610 Accept Major joint, no imaging guidance documented; the descriptor matches the note
J1030 Accept 40 mg descriptor, 40 mg documented, one unit
36415 Accept Venipuncture performed in office and documented
M25.561 Accept Correct for this date of service; no definitive diagnosis established (Chapter 22 closed Q5)
I10 Accept Assessed with a plan
E78.5 Accept Assessed with a plan and a lab order
E11.9 Accept — and re-derive the reason Right code; the engine did not perform Section IV's "addressed" test, so confirm it yourself

The four findings the engine could not produce:

  1. The modifier 25 argumentstructural. An engine can observe a co-occurrence; the support is four elements, three of which have nothing to do with the knee (Chapter 14 §14.4).
  2. The diagnosis pointersconfiguration failure. Line 4 points at B, not A (Chapter 25 §25.5). This one is fixable and most implementations get it wrong because nobody specified it.
  3. The diabetes and kidney-disease questionstructural. Whether an encounter addressed a condition is a property of the clinician's work, not of the text (Chapter 36 §36.11) — and a query cannot manufacture an encounter.
  4. The unwritten decision-to-inject sentencestructural. There is no text to process (Chapter 37 §37.11).

The two sentences for the manager: "On this chart the engine would have produced seven of eight codes correctly and saved us real time, and I would use it. The four things it could not produce are the modifier that gets audited, the pointer that would have asserted a venipuncture treats knee pain, the query we should have sent, and the missing sentence that made our appeal harder to write — and three of those four are things no text-reading tool can find."


Chapter 39 — Answer Key (daggered † and odd-numbered exercises)

The quiz's own key lives in quiz.md's collapsed block. Nothing below states any credentialing organization's current requirements. Every answer that touches an exam parameter, an eligibility rule, an experience requirement, a continuing-education requirement, a fee, or a code-book annotation rule is answered at the level of structure or where to verify, because that is the only honest answer a book can give. Several exercises have no single correct answer by design — they ask the reader to go and read a current source, and the answer below says what a good response looks like.

Exercise 39 — A.1 (odd)

Certifies: that on one proctored day the candidate applied the code sets and their guidelines correctly to a set of constructed scenarios. Does not certify: anything about performance at the desk.

Three things that are most of the job and are on no coding exam — any three of: working a denial and classifying its root cause (Ch. 29 §29.4–§29.5); reading a remittance advice line by line, including that a line can carry two contractual adjustments (Ch. 28); writing an appeal and assembling its evidence (Ch. 30); following a claim through a clearinghouse and reading its acknowledgments (Ch. 27 §27.6); working an aging bucket (Ch. 31); explaining a bill to a frightened person (Ch. 32 §32.10).

Exercise 39 — A.2 †

The chain of three claims.

  1. A hiring manager has more applicants than she can evaluate and no cheap way to distinguish them, because a coder's output is numbers on a claim and a paid claim proves nothing (Ch. 4 CS2).
  2. The consequence of hiring wrong is not merely a denial — it is that the organization's own federal attestations are being made by someone whose competence it has not verified (Ch. 5; Ch. 37 §37.9).
  3. So she uses a proxy that sorts sixty applications into fourteen in one pass.

The feature that makes the chain work: there is no license and no protected title. In nursing or pharmacy the state has already performed the verification and the employer inherits it. Here nobody has, so the private credential is doing the state's job — which is Case Study 1's whole argument.

Exercise 39 — A.3 (odd)

Something close to: "You're right, and the letters are how you get to the people who can. You can only interview a handful, and the credential is the only signal that arrives before the interview — it tells you somebody sat a hard open-book exam and passed. Then test what you actually care about in the room." The reply must agree without being sarcastic, and must locate the credential's value at the screening stage rather than as a measure of skill.

Exercise 39 — A.4 (even, answered because the list is load-bearing)

Local chapters and component associations · student and low-income rates · association scholarships · employer reimbursement · workforce-development funding · community college programs. The one most people never attempt: employer reimbursement. Funding an existing employee is cheaper than recruiting, most employers do not advertise it, and almost nobody asks.

Exercise 39 — B.5 (odd)

Credential Full name Code sets centered on The claim
CPC Certified Professional Coder ICD-10-CM, CPT, HCPCS II professional
COC Certified Outpatient Coder ICD-10-CM, CPT/HCPCS II, APC logic facility, outpatient
CIC Certified Inpatient Coder ICD-10-CM, ICD-10-PCS facility, inpatient
CPB Certified Professional Biller (not a coding credential) the claim after the codes
CRC Certified Risk Adjustment Coder ICD-10-CM, risk models population, not one claim
CPMA Certified Professional Medical Auditor all, applied as a standard somebody else's claim
CCA Certified Coding Associate ICD-10-CM, CPT, HCPCS II entry level, across settings
CCS Certified Coding Specialist ICD-10-CM, ICD-10-PCS, CPT facility, inpatient and outpatient
CCS-P Certified Coding Specialist — Physician-based ICD-10-CM, CPT, HCPCS II professional
RHIT Registered Health Information Technician (broader than coding) the record
RHIA Registered Health Information Administrator (broader than coding) the department

Exercise 39 — B.6 †

The rooms: AAPC came out of the physician practice; AHIMA out of the hospital medical record department, with roots to 1928.

Why the origin still predicts the shape. The two rooms have different units of work and different units of payment. In the practice the unit of work is the encounter and the unit of payment is the service line — so the credential must certify CPT fluency, modifiers, edits, and medical necessity. In the hospital the unit of work is the record and (after 1983) the unit of payment is the classified stay — so the credential must certify principal-diagnosis selection, present on admission, and the grouper. Those are not two difficulty levels; they are two jobs, and because no regulator ever consolidated them, both traditions persisted with their original shapes.

Exercise 39 — B.7 (odd)

CPB — billing: the claim after the codes are right (Chs. 25–32). CPMA — audit: scoring somebody else's coding against a cited standard and defending the finding (Ch. 37, especially §37.3). CRC — risk adjustment: the documentation a risk model requires and what it is worth to a population's score (Ch. 36).

Exercise 39 — B.8 (even, answered because the consequence is expensive)

CAHIIM is the Commission on Accreditation for Health Informatics and Information Management Education — an independent accrediting body. Its accreditation of a degree program is a prerequisite for the RHIT and RHIA pathways.

The mistake it prevents: enrolling in, paying for, and completing a health information degree at a program that is not CAHIIM-accredited, and discovering afterward that it does not open the door you enrolled to open. The check takes two minutes in CAHIIM's program directory and must happen before enrollment.

Exercise 39 — B.9 †

The framing is wrong because it implies one continuum with two points on it. The CCA is designed as an entry point and is understood that way by employers; the CCS is a mastery credential with a hospital center of gravity, and it is respected precisely because it is difficult. They are not two rungs of one ladder — they are a starting credential and a demonstration of depth.

What an employer hiring for hospital inpatient coding infers: from CCS, that this person has been tested against inpatient facility material at a mastery level; from CCA, that this person has been tested and is at the beginning. Taking the CCA first is a perfectly reasonable strategy. Presenting it as sufficient for that specific job generally is not.

Exercise 39 — C.10 †

No single correct answer — the exercise is the survey. A good response contains: thirty real postings from the reader's own commuting radius; the four columns filled for each (setting · credentials named · required or preferred · "or equivalent experience" present); a stated mode by setting rather than a range; a count of postings that would consider an uncredentialed candidate; and two named employers to call with §39.5's single question.

What to look for when grading: did the reader report the mode or a list? A list is not an answer. Did they separate required from preferred? That column is the filter and the other is the wish. Did they read the outliers? Those are the employers who will talk to them, and a survey that only reports the pattern has discarded its most actionable finding.

Exercise 39 — C.11 (odd)

The distinction: AAPC's credentials are oriented toward physician and outpatient professional coding and the practice setting; AHIMA's toward the hospital, health information management, and inpatient work.

Four exceptions: AAPC issues facility credentials (COC, CIC); AHIMA issues a physician-based coding credential (CCS-P); hospitals hire CPCs for professional-fee coding; large physician groups hire RHITs to run the record function. (Also acceptable: many professionals hold both.)

Why both halves. A center of gravity is a hypothesis generator, and a boundary is a rule. Given only the rule, a reader in a market that contradicts it concludes the book is wrong and stops trusting it. Given both, they use the distinction to form an expectation and then test it against the only evidence that governs — their own market.

Exercise 39 — C.13 †

The same procedure; possibly a different credential. Both readers run §39.5's survey. What differs is what it returns.

  • Rural, one critical access hospital and eleven practices. The postings will be dominated by small-practice professional work, and the hospital's own coding may be outsourced or performed by a small generalist team. The evidence to collect: what the hospital itself requires (one phone call reaches the person who knows), whether remote positions are realistically available to them, and whether any local program feeds either organization.
  • Metropolitan, three large health systems. The postings will separate cleanly into facility and professional, and the systems will have standardized. The evidence to collect: the mode within each setting separately, because a single combined mode across a mixed market is an artifact.

The point the exercise is making: the procedure is universal and its output is local. That is why §39.5 refuses to answer the question in the abstract.

Exercise 39 — C.14 (even, answered because the discipline matters)

Why no figure: compensation varies enormously by credential, setting, geography, experience, production basis, and remote status, and a number without a date and a geography is not information.

The three sources: the organizations' own member salary surveys; the Bureau of Labor Statistics occupational profile (current category name; state and metro tables); the reader's own thirty postings, where pay-transparency rules apply.

The limitation on the first: it is self-reported and member-only — a survey of a self-selected population, not an estimate of the workforce.

Exercise 39 — D.15 (odd)

An exam content outline (or blueprint) lists the domains an exam covers and their approximate weights. It comes from the credentialing organization, free, for the specific credential. Build the study plan against it.

The question it answers that a table of contents cannot: what is weighted. A textbook's chapter lengths reflect what is hard to explain; an outline reflects what is scored. They are not the same document and only one of them is about your exam.

Exercise 39 — D.16 †

Two additional constructed distractors for §39.6's item, each with its mistake named. Accept any two that are (a) plausible, (b) reachable by one specific error, and (c) genuinely wrong. Examples:

  • 99213-25, 20610-RT, J1030, 36415the mistake: leveling the evaluation and management service on the knee alone, or on a count of chronic conditions without the two-of-three analysis, and missing that three stable chronic conditions plus prescription drug management plus a new problem with uncertain prognosis support 99214 (Ch. 15 §15.13).
  • 99214-25, 20610-50, J1030, 36415the mistake: reaching for the bilateral modifier when the note documents one knee and explicitly records the left knee as normal (Ch. 14 §14.8).
  • 99214-25, 20610-RT, J1030 × 2, 36415the mistake: reporting units by milligrams rather than by the descriptor's increment; J1030's descriptor is written in 40 mg (Ch. 20 §20.3).
  • 99214-25, 20610-RT, J1030, 36415, plus a line for the lidocainethe mistake: billing a supply that is inside the procedure's package and is a usual supply besides (Ch. 17 §17.2, Ch. 20 §20.10, Ch. 21 §21.6 — three independent reasons).

Exercise 39 — D.17 (odd)

Three rules that change between the office and the admission, any three of:

  1. First-listed versus principal diagnosis — Ch. 9 §9.3 (outpatient) and §9.4 (inpatient), with Ch. 33 §33.2 building the inpatient hard cases.
  2. The uncertain-diagnosis rule, which reverses — Ch. 9 §9.5. "Probable" is coded as established on the inpatient record and not coded at all in the office.
  3. Which additional diagnoses are reportable — Guidelines Section IV in the office versus Section III on the inpatient record (Ch. 9 §9.2, applied at Ch. 33's Encounter).
  4. The unit of payment, and therefore what the codes are doing: service lines (Ch. 23) versus the classified stay (Ch. 33 §33.5).

Exercise 39 — D.18 (even, answered because the technique is the section's payoff)

Name the difference between the two remaining choices out loud, then find the rule that governs that difference. It is faster than re-reading the stem because the distractor was constructed from one specific mistake — so the difference between the finalists is not incidental, it is the tested point. Re-reading the narrative searches the whole item for a clue; naming the difference searches one rule.

Exercise 39 — D.19 †

Parameters to verify, and the authority on each. All of the following live in the current candidate handbook or examination policy for the specific exam, published by the organization administering it: question count · time limit · item formats · delivery mode (testing center or remote proctor) · fee · retake policy · reschedule policy and fee · eligibility requirements · identification requirements · permitted materials, including the code-book annotation rules and the edition rule · whether a wrong answer is penalized · scratch material and calculator policy · score reporting.

Two that live elsewhere on the same organization's site: the testing-accommodations process (published alongside the handbook) and the exam content outline (the authority on weighting, not on parameters). One that lives outside both organizations: program accreditation, in CAHIIM's directory.

Exercise 39 — E.20 †

No single correct answer — the artifact is the point. A complete response has all five elements: (a) honestly counted weekly hours and the total they produce; (b) a week-by-week focus naming the code book and the chapters; (c) two dated simulation days; (d) two named nights off; (e) the domain to drop first, chosen from the content outline's weights rather than by preference.

What to look for when grading. Are the hours real, or aspirational? A plan built on fourteen hours a week from someone working full time is a plan that fails in week four and takes the reader's confidence with it. Are the simulations dated? Undated, they do not happen. Is the drop-first domain the lowest-weighted one, or merely the one the reader dislikes?

Exercise 39 — E.21 (odd)

A path in Chapter 8 §8.1's sense is the route to an answer: main term → subterm → verify in the Tabular → read the conventions → check the guideline. It is a procedure, not a fact.

Why the open-book design makes path knowledge worth more. In a closed-book exam, having the fact in your head is the whole advantage. In an open-book exam everyone has the facts — they are on the desk — so the only thing that varies between candidates is how fast and how reliably they can get to them. The design converts the test from a memory test into a routing test, which is also exactly what the desk requires.

Exercise 39 — E.22 †

No single correct answer. A complete response has ten items with all four columns filled, each miss classified into one of §39.7's six reasons, and — the part that matters — a fix matched to the dominant reason, not "study more."

The mapping to look for:

Dominant reason The fix
Misread the stem read the last sentence first; slow down on the first ten seconds
Missed a guideline tab the guidelines; read the section guideline before the codes
Wrong main term index practice, specifically; Ch. 8 §8.2–§8.3
Did not verify in the Tabular process, not knowledge — enforce the two-step rule on every item
Guessed under time pressure the clock, not the content; §39.9
Genuinely did not know the only one where more content review is the answer

One of six. That is the exercise's whole argument: five of the six reasons are not fixed by studying more.

Exercise 39 — E.23 (odd)

Chapter 6 §6.10's file is a question list — every question you had to look up, the answer, and the source. §39.7 turns it into a study instrument because it is already made of the things you personally got wrong, which no commercial study guide can be. The column the exam version adds: why you got it wrong. It changes behavior because the fix depends on the reason, and without the column every miss receives the same treatment.

Exercise 39 — E.25 †

The failure mode of training speed before accuracy: you train yourself to guess. Guessing is fast, it is rewarded on a timed practice set roughly a quarter of the time on a four-option item, and it produces a rising practice score while the underlying skill is not improving — because a guess that happens to be right teaches nothing and, worse, hides the gap it came from.

That is the same shape as Chapter 21 CS1's clean edit report produced by not billing and Chapter 29 CS2's denials that genuinely fell: a number improving for a reason nobody examined. Accuracy first makes every miss informative; speed first makes some misses invisible.

Exercise 39 — F.26 †

Generally permitted: handwritten notes in margins and blank areas · highlighting and underlining · tabs, including publisher-supplied tabs · the book's own errata. Generally not permitted: taped, glued, stapled, or otherwise affixed material · inserted printed or photocopied pages · supplementary content of any kind · a rebound or assembled book. The edition rule: the book must generally be a current, unaltered edition from an approved publisher — and which edition depends on the exam date relative to the code sets' effective dates.

The sentence that must follow: verify the current rules directly with the organization administering your exam, in its own current candidate handbook or examination policy, before making a mark.

Why this book will not print the rule: the rules differ between organizations, differ between exams offered by the same organization, differ by delivery method, and change. A candidate turned away at a testing center because a textbook told them something that was true three years ago has been failed by the textbook.

Exercise 39 — F.27 (odd)

The four reasons. (1) The exam is testing navigation and application, and imported content converts it into a different test. (2) The rule must be checkable at a door in about ten seconds by a proctor who cannot adjudicate marginalia — so it is written as a bright line and is over-inclusive by design. (3) Fairness and exam security. (4) An annotation that answers the question for you teaches you nothing.

The fourth is about you. Its implication: the note that helps on exam day is the one that took twenty minutes to work out and three seconds to write. The chart you downloaded is worth nothing on the exam and nothing on the desk, because you never did the reasoning that would make it yours.

Exercise 39 — F.28 †

No single correct answer — the exercise is the lookup. A complete response records: the document's name and where it was found (the organization's own site), what it says about handwritten notes, highlighting, tabs, affixed material, the edition, and the delivery mode, the date it was read, and one thing it contains that this chapter's general shape did not supply.

What to look for. Did the reader find the handbook for their specific exam, or a general page? Did they record the date? A policy read without a date cannot be re-checked meaningfully before the exam.

Exercise 39 — F.29 (odd)

What applies: the reasoning in §39.8 — that the exam is testing navigation, and that imported content defeats it — and the update-cycle fact, since the software's code set has an effective date too. What does not apply: every rule about marks in a physical book, because there is no physical book.

The first question they should be asking instead: for my exam, in my delivery mode, what governs my workspace? — scratch material, what may be on the desk, what may be visible on camera, whether the seat may be left, and what happens if a connection drops. It is a different rule set answering a different question, and it is in the same candidate handbook.

Exercise 39 — G.30 †

Why the sequence fails, in order. The accommodations process requires (1) preparing a request, (2) obtaining documentation from a qualified professional, and (3) review by the organization. Each takes calendar time the candidate does not control. A candidate who registers and schedules first has started a clock against a process whose duration they cannot compress — and the likely outcome is either sitting without the accommodation or paying to reschedule.

Three things to do this week: find the organization's published accommodations process for the specific exam and read what documentation it requires; request that documentation from the qualified professional, since that step has the longest and least controllable lead time; and do not schedule a date until the request is submitted and its expected handling is understood.

Exercise 39 — G.31 (odd)

No single correct answer — the numbers must be the reader's own. A complete response shows: the question count and time limit with the source named (the current candidate handbook for their exam), the gross budget per item, a stated reserve with a reason, the working budget per item, and four checkpoint clock times.

What to look for. Is the reserve justified rather than arbitrary — instructions at the start and a sweep for unanswered items at the end? Are the checkpoints expressed as times, not as item numbers? The technique only works if it can be read off a clock in one glance.

Exercise 39 — G.32 †

Pass 1 (fast, no books): answer everything known cold; mark the rest. Pass 2 (books): work the marked items, hardest last. Pass 3 (commit): resolve or commit and move. Final sweep: the reserved minutes, for unanswered items only.

Why pass 1 forbids opening a book. Opening a book converts a forty-second item into a three-minute item, and doing it early spends the surplus that pass 2 exists to use. The prohibition is a budgeting rule, not a knowledge rule.

What pass 1 gives you besides answers: (a) the count of items that actually need a book, which is the number pass 2 is budgeted against — you now know whether you have three minutes each or ninety seconds each; and (b) the knowledge that the exam is survivable, which sounds soft and is not: candidates who begin with a hard item and stay on it lose time to anxiety as well as to the item.

Exercise 39 — G.33 (odd)

The rule: ninety seconds without converging, mark it and move.

Why it is arithmetic. Every item is worth the same. A fourth minute on one item is spent at the expense of some other item — and, late in the exam, at the expense of an item you will never reach and therefore certainly lose. Trading a possible point for a certain zero is a bad trade regardless of how close you feel. Willpower is not what is being tested; allocation is.

Exercise 39 — H.34 †

It signifies: that the holder has passed the exam but has not yet documented the required coding experience.

It does not signify: a lower passing score · a different or shortened exam · a provisional pass subject to review · anything about the holder's ability. The exam and the standard are identical.

The circularity: experience removes the designation, and the designation makes experience harder to get, because employers use it as a filter.

Four kinds of route: documented employment for a defined duration, verified by an employer · qualifying education recognized as replacing a portion of the requirement · the organization's own structured practical-experience program · supervised practice or an externship, to the extent the organization recognizes it — confirm before doing it.

What every route must ultimately produce: documentation the organization will accept, signed by somebody with standing. Current requirements are the organization's and are revised; verify them before asking anyone to write anything.

Exercise 39 — H.35 (odd)

The six things to record from day one: exact start and end dates · job title as it appears in payroll and what the work actually was · code sets used, settings, and document types · approximate volume · whether you assigned codes or reviewed codes assigned by others · the name, title, and current contact information of the person with standing to verify it.

A scenario. A coder spends eighteen months doing coding review at a practice that is acquired in year two. The practice's name changes, its records migrate, and the coding supervisor leaves for another state. In year three the coder needs verification: the entity that employed them no longer exists under that name, nobody remaining witnessed the work, and payroll can confirm a title but not what the person did. The work happened and is now unprovable — which is the chart rule applied to a career.

Exercise 39 — H.36 †

The four places it surfaces: a payer or client contract requiring credentialed staff · an audit response letter describing the qualifications of the staff who did the work (Ch. 37 §37.8) · the compliance program's training and qualification documentation (Ch. 5 §5.6) · a job application.

Why it belongs with the silent underpayment. Both are failures with no signal: nothing denies, nothing rejects, no exception report fires, and the operational numbers look exactly as they did the week before. Chapter 28 §28.8 made the point that an underpayment arrives as a payment; a lapsed credential arrives as an ordinary Monday. In both cases the organization only learns of it from outside, and by then the exposure has a duration.

Exercise 39 — I.37 (odd)

B — COC. A (CPC): the professional claim's lens; it does not carry APC logic, status indicators, or the facility's packaging rules. C (CIC): inpatient facility — the right building, the wrong payment system entirely (Ch. 33 versus Ch. 34). D (CPB): billing, not coding — the claim after the codes.

Exercise 39 — I.39 †

The answer: 99214-25, 20610-RT, J1030, 36415.

The path: established patient, office, professional claim → evaluation and management leveled on medical decision making because the note states time was not used → three stable chronic conditions with prescription drug management, two tests ordered, and a new problem with uncertain prognosis → 99214 (Ch. 15 §15.13). Major joint, no ultrasound guidance, no permanent recording → 20610 with RT (Ch. 14 §14.8, Ch. 17 §17.7). J1030 at one unit, because the descriptor is written in 40 mg (Ch. 20 §20.3). Venipuncture 36415. 20610 carries a 000-day global, so a significant, separately identifiable evaluation and management service on the same day takes modifier 25 — and the four supporting elements are in the note, three of which have nothing to do with the knee (Ch. 14 §14.4).

The four rejections:

  • (a) Modifier 57. The mistake: remembering that a modifier is required and grabbing the wrong one. 57 is the decision for major surgery — a 090-day global. 20610's global is 000. Wrong global period, wrong modifier.
  • (b) 20611. The mistake: selecting on joint and drug while ignoring the guidance clause. 20611 requires ultrasound guidance with permanent recording and report; the note documents that no imaging guidance was used. This is why Ch. 17 §17.7 argues for documented negatives — the sentence saying what was not done is what makes the correct code provable.
  • (c) No modifier on the evaluation and management line. The mistake: treating the visit and the procedure as one service. Without modifier 25 the line is bundled by edit and the practice is not paid for work that was separately performed and separately documented.
  • (d) Pointing 36415 at the knee. The mistake: pointing every line at the presenting complaint. The blood was drawn for the hemoglobin A1c; pointing the venipuncture at the knee asserts that a venipuncture treats knee pain (Ch. 25 §25.5, §25.10). Diagnosis pointers are assertions.

Exercise 39 — I.40 †

No single correct answer — the workbook entry is the deliverable. A complete response has the three-column ownership map, the chapter for each piece, and the three written answers.

(a) Why the CCS's version is necessarily a counterfactual. Northgate is an independent practice, so this encounter generated one claim — a professional claim. There is no facility claim on this account for a facility credential to own. The book therefore supplies two constructed alternatives: the same encounter in a provider-based department (Ch. 26 §26.9) and the same patient admitted (Ch. 33's Encounter).

(b) What the three columns produced.

Line Charge Allowed Contractual adj. Patient Plan
99214-25 185.00 128.40 56.60 30.00 98.40
20610-RT 150.00 78.60 71.40 15.72 62.88
J1030 18.00 6.28 11.72 1.26 5.02
36415 14.00 3.00 11.00 0.60 2.40
Total 367.00 216.28 150.72 47.58 168.70

Checks: 367.00 − 216.28 = 150.72 ✓ · 216.28 − 47.58 = 168.70 ✓

(c) What none of them could finish alone, and what that says. The coding was correct on day 1 and the claim was still denied on day 17 — a payer edit, not a coding error (Ch. 14 closed that question). Getting the account to a zero balance required the codes, the claim, the remittance read correctly, the classification, the appeal, and the follow-up: three columns of work by three different disciplines. A credential certifies that you can do your column. It does not certify that the file gets to zero, and the file getting to zero is the job.


Chapter 40 — Answer Key (daggered † and odd-numbered exercises)

The quiz's own key lives in quiz.md's collapsed block. Every dollar figure below is constructed and belongs to Northgate Family Medicine, a teaching example. Several exercises have no single correct answer by design — they ask the reader to compute from their own inputs or to go and read a current source, and the answer below says what a good response looks like and what its checks must be. No answer here states a salary, a job-growth figure, or a survey result, because the chapter publishes none.

Exercise 40 — A.1 (odd)

The file, in build order: the eligibility response (Ch. 24 §24.3–§24.4) · the benefit design read forward to a prediction (Ch. 2 §2.7) · the March 14 office note in full (Ch. 4 §4.10, Figure 4.2) · four diagnosis codes with their lookup paths (Chs. 7–12) · four service lines with their governing guidelines (Chs. 13, 15, 17, 19, 20) · the modifier analysis (Ch. 14 §14.4, §14.8) · the edit run (Ch. 21 §21.9) · the coverage policy and diagnosis linkage (Ch. 22 §22.6) · the pricing derivation and the charge that cannot be derived (Ch. 23 §23.1, §23.7) · the completed CMS-1500 (Ch. 25 §25.10) · the 837P with its 999 and 277CA (Ch. 27 §27.10) · the first remittance posted line by line (Ch. 28 §28.11) · the denial classified to a root cause (Ch. 29 §29.10) · the appeal letter and its calendar (Ch. 30 §30.11) · the decision letter and second remittance (Ch. 30 §30.11) · the aging history (Ch. 31 §31.12) · the patient statement (Ch. 32 §32.11) · the audit worksheet and score (Ch. 37 §37.11).

The instruction matters more than the list. Whatever you left out is the part of the cycle you have learned least well, and it is almost never the coding — most readers omit the transmission trail, the aging history, or the audit.

Exercise 40 — A.2 (odd, †)

  THE PATIENT COLUMN, ACROSS BOTH REMITTANCES

  Day 0    copay collected at check-in ............... $30.00
  Day 17   first 835 -- coinsurance on the three
           paid lines: 15.72 + 1.26 + 0.60 .......... $17.58
           (the E/M line paid nothing and produced no
            PR-3, so the copay does not move here)
  Day 66   second 835 -- 99214 allowed $128.40,
           plan $98.40, copay assigned .............. $30.00
                                                      ───────
  TOTAL PATIENT RESPONSIBILITY ....................... $47.58

  WHAT SHE ACTUALLY PAID
    Day 0 .... $30.00      Day 100 .... $17.58        $47.58

  Checks: 15.72 + 1.26 + 0.60 = 17.58 ✓
          17.58 + 30.00 = 47.58 ✓
          30.00 + 17.58 = 47.58 ✓
          216.28 allowed - 47.58 patient = 168.70 plan ✓

The prediction was the \$30.00 collected on day 0. Point-of-service collection happens before adjudication, on the benefit design read forward (Ch. 2 §2.7, Ch. 24 §24.8) — it is a forecast that the copay would apply, and it happened to be right. The \$17.58 on day 17 and the \$30.00 assigned on day 66 were both facts at the time: adjudicated amounts on a remittance. This is also why the day-70 statement must show the credit — a statement demanding \$47.58 would ask for money already handed over (Ch. 28 §28.11).

Exercise 40 — A.3 (odd)

Three things the finished file does not prove:

  1. That good coding prevents denials. It does not. This claim was clean and denied anyway on day 17, and Ch. 14 §14.4 settled why: the payer's edit is policy, not a coding correction.
  2. That the practice is well run. The audit produced one finding (Ch. 37 §37.11), category 4 — supported but fragile. Nothing came off the claim, and Ch. 30's appeal still had to construct the argument rather than quote a sentence.
  3. Anything about the files this book did not follow. Account 10-4471 was the easy one — in network, deductible met, eligibility verified, documentation better than most, coding right, denial wrong, appeal won — and it still took a hundred days.

Exercise 40 — A.5 (odd, †)

Paragraph one, agreeing with what is correct. She is right that a file where everything went right teaches nothing about failure, and this book agrees with her: five of its case studies exist precisely because it needed files that went wrong, and Chapter 29's log entry reads preventable: YES on a claim nobody got wrong. A textbook built only on clean files would be a textbook about a profession that does not exist.

Paragraph two, the reply. But the question this chapter asks is not what goes wrong — it is what does it cost to put right, and that question can only be answered on a file where nothing else is confounding it. On a file with a coding error, the labor is partly the cost of the error. On a file with a documentation gap, it is partly the cost of the gap. On this file the coding was right, the modifier was right, the documentation supported it, and the appeal won on the merits — so the 58 minutes are purely and only the cost of the denial itself. That is what makes it the right file for the measurement, and it is why the conclusion is uncomfortable rather than reassuring: if the best case costs \$34.80 to recover \$128.40, the ordinary case is worse.

Exercise 40 — B.1 (odd)

  • 58 minutes, three touches (14 + 31 + 13) — Ch. 29 §29.10; touch 2's 31 minutes itemized as 6 + 5 + 3 + 10 + 7 in Ch. 30 §30.11.
  • \$36.00 per hour fully loaded = \$0.60 per minuteCh. 31 §31.7.
  • \$128.40 allowed on the denied line — Chs. 2, 23, 28; Ch. 28 §28.11 is the one that matters, because line 1 carried two CO adjustments and the appealable amount is the allowed amount, not the \$185.00 charge.
  • 68% overturn rate, 57 of 84 appeals decided — Ch. 29 §29.7.

Checks: 14 + 31 + 13 = 58 ✓ · 6 + 5 + 3 + 10 + 7 = 31 ✓ · 57 ÷ 84 = 67.9%, reported as 68% ✓ · 56.60 + 128.40 = 185.00 ✓

Exercise 40 — B.2 (†)

  Touch 1   14 min x $0.60 = $ 8.40
  Touch 2   31 min x $0.60 = $18.60   <- most expensive
  Touch 3   13 min x $0.60 = $ 7.80
                             ───────
                              $34.80        Check: 8.40+18.60+7.80 = 34.80 ✓

Touch 2 is the most expensive and it is the only touch that produces the recovery. Touches 1 and 3 are the overhead around it: reading and classifying, then tracking and posting. Eliminating touch 2 eliminates the appeal.

And Ch. 30 §30.11's itemization shows there is very little to cut inside it: 6 re-reading the note against the four elements, 5 pulling the payer's policy, 3 pulling the Policy Manual language and edit indicator from the appeal-paragraph library, 10 drafting the demonstration — the only genuinely new work — and 7 assembling, submitting, filing proof, and calendaring. Cutting the 5 removes the policy; cutting the 7 removes the proof of timely filing, which Ch. 27 §27.7 ranks as the evidence that decides a filing dispute. The compressible minute is the one that was already compressed by the library.

Exercise 40 — B.3 (odd)

Not the cost of the claim. The coder's review, the claim build, the scrubber pass, and the posting of the first remittance happen on every claim. To capture the marginal cost you have to measure denial touches separately from production — which means a log with a minutes field, and almost no practice has one.

Not the whole cost of the delay. \$128.40 arrived 49 days after denial (66 − 17 = 49). Capturing that requires pricing the float — the practice's own cost of money — and, where a contract or state prompt-pay rule provides one, any interest remedy. Here none attached, so the delay was an invisible transfer of float from practice to payer (Ch. 31 §31.1).

Not a cost the practice noticed. Nothing in a general ledger is called "fifty-eight minutes." The labor was paid whether or not the denial existed — it is a fixed salary consumed by a variable activity — which is precisely why an unmeasured business office cannot say what its denials cost, and why Ch. 24 CS2's sentence an unmeasured function is indefensible lands here.

Exercise 40 — B.5 (†)

A method with stated assumptions; your numbers will differ and that is the point.

  ASSUMPTION (state it): without a paragraph library, the 3 minutes
  spent pulling settled language becomes ~25 minutes of finding the
  Policy Manual passage and drafting the argument from scratch.

  Touch 2 with a library ......  31 min
  Touch 2 without ....... 31 - 3 + 25 = 53 min
  DIFFERENCE ..................  22 min  x $0.60 = $13.20 per appeal

  ASSUMPTION: building this paragraph family once takes 90 minutes.
  90 x $0.60 = $54.00 to build.

  BREAK-EVEN:  $54.00 / $13.20 = 4.09  ->  it pays for itself on the
                                           FIFTH identical appeal

The input to trust least is the 25 minutes. It is a guess about work nobody timed, and the whole result scales with it: at 15 minutes the library pays back in about eight appeals, at 40 minutes in about three. The honest move is to time the next appeal you write without a library and replace the guess with a measurement — which is the same instruction §40.3 gives about the break-even itself.

Exercise 40 — B.6

Ranked by how long each keeps producing value:

  1. The log entry that names a category — longest-lived. The \$93.60 is one-time; the classification is what §40.3 spends, and it can change next year's process.
  2. The reusable paragraph — durable but bounded. It lowers the cost of every future appeal of this type until the payer's policy or the underlying guidance changes.
  3. The audit's convergent finding — valuable and one-time in itself, but it is the thing that makes the prevention argument credible, because two independent controls pointed at the same sentence.

Exercise 40 — C.1 (odd)

(a) Because the labor is certain and the recovery is probabilistic. You spend the minutes on every appeal you write; you collect on the share that succeed. Break-even is where allowed × overturn rate = labor, so allowed = labor ÷ overturn rate.

(b) "Appeal anything worth more than \$34.80" prices only the winners. It assumes every appeal is paid, which is false 32% of the time at this practice — and it therefore sets the bar about a third too low, so a band of lines between \$34.80 and \$51.18 would be appealed at an expected loss.

Exercise 40 — C.2 (†)

  $34.80 / 0.68 = 51.1764...  ->  BREAK-EVEN $51.18

  PROOF, RUN FORWARD
    A denied line allowed at $51.18, appealed:
      you spend ........................... $34.80  (every time)
      you expect  51.18 x 0.68 = .......... $34.80
      EXPECTED NET ........................ $ 0.00

  Checks: 51.18 x 0.68 = 34.8024, which is $34.80 to the cent ✓
          128.40 x 0.68 = $87.31 expected against $34.80 spent, and
          128.40 / 51.18 = 2.51 -- Account 10-4471's line was worth
          two and a half times the break-even ✓

Exercise 40 — C.3 (odd)

  BASELINE     58 min · $0.60/min · 68%  ->  $51.18

  (a) overturn 45%   34.80 / 0.45 = $77.33   check 77.33 x .45 = 34.80 ✓
  (b) overturn 90%   34.80 / 0.90 = $38.67   check 38.67 x .90 = 34.80 ✓
  (c) 20 minutes     20 x .60 = 12.00
                     12.00 / 0.68 = $17.65   check 17.65 x .68 = 12.00 ✓
  (d) $45.00/hr      $0.75/min · 58 x .75 = 43.50
                     43.50 / 0.68 = $63.97   check 63.97 x .68 = 43.50 ✓
  (e) (c) and (d)    20 x .75 = 15.00
                     15.00 / 0.68 = $22.06   check 22.06 x .68 = 15.00 ✓

Operationally: (a) a category you lose more often has to be worth more before it is worth chasing — and a very low rate is a signal to fix the triage, not the letter. (b) a category you nearly always win is worth chasing far further down. (c) minutes are the dominant lever — cutting the time by roughly two-thirds cuts the break-even by roughly two-thirds. (d) a higher labor cost raises the bar proportionally. (e) both together land at \$22.06, well under half the baseline.

The comparison that matters is (a) against (c): \$77.33 versus \$17.65. Twenty-three points of overturn rate move the break-even less than thirty-eight minutes do. If you want to appeal more denials profitably, get faster before you get better at winning.

Exercise 40 — C.4 (†)

No single correct answer — this is the exercise that makes the chapter yours. A good response has all six of these:

  1. A loaded hourly rate with its build shown, or a stated assumption clearly labeled as one. Wage alone is the common error and it understates the rate substantially.
  2. Median minutes, by category, not the mean. One monstrous denial drags a mean; the median describes the denial you will actually see next.
  3. An overturn rate from your own decided appeals, by category. Appeals decided, not appeals filed — an appeal still pending is not evidence yet.
  4. The arithmetic, with both checks: minutes × rate ÷ overturn rate, then multiply back.
  5. A named least-confident input. For most readers this is the overturn rate by category, because most practices track it in aggregate or not at all.
  6. One concrete action this month. Time the next ten denials. Pull the last two quarters of decided appeals and split them by category. Book the hour with the bookkeeper.

If the answer is "we don't have a denial log," that is the finding — and it is a better finding than any break-even, because it is the one that explains every other number the practice cannot produce.

Exercise 40 — C.5 (odd)

The sort is mechanical; the value is in the second question. A good answer reports the count below the line, the dollars below the line, and the largest root-cause category underneath it — and observes what Figure 40.2 observes: a large share of the count is usually a small share of the dollars. The category is what decides what to do instead, and it will typically be registration, eligibility, authorization, or a single payer's edit — none of which is fixable by anybody in the coding department, which is Ch. 29 §29.7's point restated with your own data.

Exercise 40 — C.6 (†)

The four limits, and the direction each one moves the estimate:

  1. 58 minutes is Account 10-4471's figure and it is a high one — a correct claim denied on a payer edit, requiring an argument to be constructed rather than quoted. → overstates the cost; break-even moves DOWN.
  2. A missing-modifier denial with an obvious fix takes a fraction of that, and many sub-break-even denials are of that kind. → overstates; DOWN.
  3. Twelve identical denials are one investigation and one letter reused — per-line minutes on a batch are nothing like per-line minutes on a singleton. → overstates; DOWN.
  4. It is an illustration of a direction, not a budget. The break-even is a tool for the one line in front of you; the aggregate is a tool for one category. → not a direction so much as a scope limit.

All three substantive limits push the same way, which is worth noticing: the \$1,866.88 expected loss is an upper bound on the harm, not an estimate of it.

What the calculation is legitimately good for: establishing the direction — that a large share of a denial queue cannot pay for its own individual recovery — and thereby forcing attention from the instance to the category. It is an argument for where to look, not a line in a budget.

Exercise 40 — C.7 (odd)

Objection about the number. \$51.18 is Northgate's, built from Northgate's loaded rate, Northgate's minutes, and Northgate's overturn rate. It must be computed from the practice's own inputs, by category, and revisited when wages or the overturn rate move.

Objection about the unit. It is applied per line, and a batch of identical denials is one investigation and one reusable letter — the per-line economics of a batch are entirely different. It also ignores root cause: a sub-threshold line whose fix is a corrected claim rather than an appeal is not an appeal decision at all (Ch. 29 §29.6).

Objection about what it must still require. Silence is not permitted. Every denial is still classified; the balance is adjusted with a preventable administrative write-off code, never as contractual; a CO balance is never billed to the patient; and an identified overpayment is outside the policy's authority entirely.

The corrected policy:

Every denied line is triaged and classified regardless of value. Where a corrected claim or resubmission is the route, take it. Where an appeal is the route, file it if the allowed amount exceeds that category's break-even — recomputed annually from our loaded rate, median minutes, and overturn rate by category — or if the line belongs to a batch of identical denials. Otherwise adjust with the preventable write-off code. Never bill a CO balance to a patient. Identified overpayments are outside this policy.

Exercise 40 — D.1 (odd)

Q4 — could Account 10-4471's denial have been prevented? Yes.

Three levels, cheapest first: the note (a template prompt asking the physician to state that the decision to perform the procedure was made at this encounter); the claim (a scrubber edit that stops the pairing and asks whether separately identifiable work is documented); the payer (the pattern, the count, the overturn rate, and the labor cost, taken to the provider representative and to contract renewal).

Cheapest per claim after it is built: levels one and two — about \$102.00 of staff time once, then nothing per claim. The only one that removes the category: level three, and it is the one nobody does, because it requires a conversation rather than a keystroke.

Exercise 40 — D.2 (†)

  BUILDING THE FIX, ONCE
    conversation with the physicians ........  30 min
    build and test the prompt ...............  60 min
    verify on five real notes ...............  20 min
    write and test the scrubber edit ........  45 min
    write it down: finding, cause, change,
      OWNER, date, test, re-audit
      (Ch. 37 37.10's six fields) ...........  15 min
                                              ────────
                                               170 min  x $0.60 = $102.00

  PAYBACK:  $102.00 / $34.80 = 2.93  ->  the THIRD occurrence
  Checks: 30+60+20+45+15 = 170 ✓ · 170 x 0.60 = 102.00 ✓
          3 x 34.80 = 104.40 > 102.00 ✓

Your own version should differ mainly in the middle two lines — a template change in a large health system's record platform is a governance process, not a sixty-minute build, and the payback moves accordingly. Report the occurrence count, not the dollars, because the occurrence count is what a manager can check against the denial log.

Exercise 40 — D.3 (odd)

Prevention. If a claim carries 99214 with modifier 25 alongside 20610 for this payer, hold the claim and present the coder with one question: does the note document work that is significant and separately identifiable from the procedure? Require an answer before release. The edit stops the claim and asks a question. A person answers it, from the record.

An assertion nobody chose. A rule that resolves the question itself — appending the modifier because the pairing is present, or inserting an attestation sentence into the note — makes a claim about a record that no human read.

Why the second is dangerous, in compliance terms. Modifier 25 is an assertion that separately identifiable work occurred and is documented; a rule that appends it is asserting that on encounters where it may not be true. The exposure is not one claim but a pattern, applied uniformly, discoverable in a single query, and extrapolable (Ch. 37 §37.6) — and when the mechanism lives in the clinical record over a physician's signature it is worse still, because a note can only be amended, never un-asserted (Ch. 29 CS2). This book has followed that mechanism roughly a dozen times, from a modifier-59 macro to a payer's own posting configuration to a script handed to a human being, and it is caught the same way every time: somebody reads a sample of records against the claims.

Exercise 40 — E.1 (odd)

Performance exercise; no key. What a good result looks like: under ninety seconds, no unexplained initialism, the causal chain intact (the payer asserted the visit was incidental → that is a bundling decision, not a coding correction → the edit's modifier indicator permits an override if documentation supports it → here is the documentation → it paid), and a non-specialist listener able to repeat the gist back. The most common failure is starting with the codes instead of with what the payer claimed.

Exercise 40 — E.3 (odd)

A good twelve-month plan is sequenced and marks what costs money:

Months 1–2 — apply to adjacent roles (charge entry, denial follow-up, posting, patient financial services, registration, authorization coordination); attend one local chapter meeting; finish the Appendix C file. Time only. Months 1–12, continuous — start the experience file on day one of any role: exact dates, payroll title, what the work actually was, code sets and settings, volume, assigned versus reviewed, and the name and current contact of the person with standing to verify it (Ch. 39 §39.10). Time only. Months 2–6 — keep the volume of records up: practice charts, a study group, second-reading whatever your employer allows. Time, occasionally materials. Months 3–9 — pursue whichever route to removing the designation your organization actually recognizes — documented employment, qualifying education, the organization's own practical-experience product, or a supervised externship. Confirm which ones count BEFORE doing one. Some cost money. Months 6–12 — say the plan out loud to your manager, ask what a coding seat would require, and get the verification letter written while the supervisor is still there. Time only.

Exercise 40 — E.5 (odd, †)

The structure is here is a thing I get wrong · here is how I detect it · here is what I changed. A worked example:

"I move too fast on charts that look familiar. I caught it when I started an error log with a 'why' column — four of my first twelve entries were the same cause, and it was always a chart that resembled one I'd done that morning. So now anything that feels familiar gets the main term looked up anyway, even when I'm sure. It costs me a few seconds a chart and it has caught three real ones."

What it demonstrates: that you notice, that you built an instrument to notice with, and that you changed behavior on evidence. The profession selects for people who detect their own errors, because the alternative — a coder who is confident and unmonitored — is exactly the exposure Ch. 5 §5.3 describes. An answer with no detection mechanism in it is not an answer to this question.

Exercise 40 — F.1 (odd)

The four, with an ask for each:

  1. The compliance channel"If I see something that looks wrong and I don't know whether it's a coding, billing, clinical, or contract question, where does it go?"
  2. The escalation path for a coding disagreement"If I'm asked to code something I can't defend, what's the sequence here?" (Ch. 5 §5.9.)
  3. Who owns the scrubber"If I find an edit that's firing wrong, who can actually change it?"
  4. Whether anyone reads the acknowledgment reports"Who looks at the clearinghouse acknowledgments, and how would we know if a batch never arrived?" (Ch. 27 CS1.)

All four are asked as how does this work here, not as do you have a problem.

Exercise 40 — F.2 (†)

  STANDARD 14 charts/hour  ->  60 / 14 = 4.29 minutes per chart

  AGAINST 40.6's QUEUE (61 charts, 298 minutes of chart time)
    budgeted at the standard:  61 x 4.29 = 261.4 minutes
    actually required: ....................  298   minutes
    DEFICIT ...............................   36.6 minutes
    ...and the standard prices NONE of the 110 minutes of
    scrubber flags, biller questions, self-audit, and update
    reading.

  THE HONEST WHOLE-DAY RATE
    61 charts / (408 min / 60) = 61 / 6.8 = 9.0 charts per hour
    to hit 14 across the same day: 14 x 6.8 = 95 charts,
    which is 56% more work in the same time.

  Checks: 60/14 = 4.286 ✓ · 61 x 4.286 = 261.4 ✓ · 298 - 261.4 = 36.6 ✓
          298 + 110 = 408 ✓ · 61 / 6.8 = 8.97 ✓

What the standard implies about a chart needing a guideline checked: it allots 4.29 minutes on average, so a 20-minute lookup has to be funded from fifteen other charts. What gets compressed is the lookups and the queries, because the routine four-minute charts cannot be compressed further. Why that is the worst possible thing to compress: those are precisely the charts where accuracy is made — the ones the coder was right to slow down on. The production standard does not fail gracefully.

Exercise 40 — F.3 (odd)

The six, with the sound of a bad answer:

  1. Which denominator — codes or charts? Bad: "Ninety-five percent accuracy." (That is the question, restated as the answer.)
  2. What counts as an error? Bad: "Anything the auditor marks."
  3. Is direction reported? Bad: "An error's an error." (It is not — one direction is a revenue problem, the other has a sixty-day clock attached.)
  4. What is the sample, and how often? Bad: "We pull a few charts when we can."
  5. Who audits, against what authority, and what happens when you disagree with a finding? Bad: "Our lead coder — she's been here fifteen years." (Experience is not an authority; a guideline, a descriptor, or a policy is.) Bad, on the second half: "Nobody's ever disputed one." — which describes a program with no rebuttal path rather than a program with no errors.
  6. What happens when the two standards conflict? Bad: "That doesn't really come up."

The common thread in every bad answer is an inherited number nobody has re-derived.

Exercise 40 — F.4 (†)

(Constructed teaching figures.) Twenty charts, four codes each — 80 codes. Two coders do identical work: 4 wrong codes each.

  CODER A -- the 4 errors fall on 4 DIFFERENT charts
    code-level ....  76 / 80 = 95.0%
    chart-level ...  16 / 20 = 80.0%

  CODER B -- all 4 errors fall on ONE chart
    code-level ....  76 / 80 = 95.0%
    chart-level ...  19 / 20 = 95.0%

  Checks: 20 x 4 = 80 ✓ · 80 - 4 = 76 ✓ · 76/80 = 95% ✓
          16/20 = 80% ✓ · 19/20 = 95% ✓

Two results at once. Against a "95%" standard, Coder A passes on one measure and fails badly on the other — identical work, a fifteen-point spread, and no error in the arithmetic. And A and B made the same number of errors and are reported fifteen points apart at chart level, because one wrong code fails a whole chart and clustering therefore flatters. The gap widens with codes per chart.

Chapter 6 §6.9 made this demonstration first — the same coder, the same audit, nothing about their performance changed, passing on one denominator and failing on another — and Chapter 37 §37.3 built the audit-scoring version on top of it. This exercise asks the reader to apply it rather than re-derive it; the clustering variant above is the one addition, and it is why two coders with identical error counts can be reported fifteen points apart. §40.6's instruction is unchanged: find out which denominator you are held to before you accept the number, and note that neither this chapter nor Chapter 6 will tell you what the number should be, because it varies by setting, specialty, document type, and employer.

Exercise 40 — F.5 (odd)

The four: your audit results with the measure named; your production against the standard; the findings you raised and what happened to them; your continuing education.

The policy paragraph, cross-checked against §40.8: When I leave, I take de-identified metrics, my error log with all identifiers stripped, and my continuing-education certificates. I take no charts, no claim images, no screenshots, and no "samples of my work." My work product and the patient information I touched stay with the employer. A portfolio built from real patient records is a privacy incident with my name on it. The artifact you show an interviewer is Appendix C — a constructed file — for exactly this reason.

Exercise 40 — G.1 (odd)

What changes: you stop being measured on your own accuracy and start being measured on other people's. The three instruments you suddenly own and must defend: a productivity standard and a quality standard (§40.6 — including which denominator, which you now have to answer rather than ask), the audit sample (its size, frequency, and selection), and the corrective action plans that follow from findings (Ch. 37 §37.10's six fields, including a named owner). The queue's priorities are the fourth, and the one nobody warns you about.

Exercise 40 — G.2 (†)

No key — the exercise is the asking. A good response names capabilities rather than credentials in part (a) ("write a finding that survives a disagreement with a colleague I'll see tomorrow," not "have a CPMA"); proposes evidence in part (b) that somebody else could verify; and asks in part (c) a question about criteria rather than about a job — "if this role opened next year, what would you need to be able to say about a candidate, including to your own director?" That second question is the whole technique, because "time in the seat" is what a manager says when nobody has asked them to specify.

Exercise 40 — G.3 (odd)

Travels easily — high-volume, structured, low-variability production: routine established-patient office visits with clean notes; charge entry; payment posting of clean remittances; front-end claim scrubbing against fixed rules; high-volume repetitive facility coding.

Travels poorly — the work that is an argument: an appeal turning on a payer's policy read against a specific record (Ch. 30); a query conversation with a clinician (Ch. 38 §38.3); an audit finding somebody has to defend (Ch. 37 §37.3); knowing which of your five payers does what; and the seam-level judgment about whether a denial is worth working at all — this chapter's own subject.

What it implies: the roles that grow are the oversight roles — the auditor sampling the vendor's output, the educator fixing what the sample finds, the denial specialist handling escalations, the manager who owns the contract. The move is toward the seam, not away from it.

Exercise 40 — G.5 (†)

Example, orthopedics; yours will differ by specialty.

  PORTABLE (a body of knowledge)        EXPIRES (a configuration)
  ------------------------------        -------------------------
  the anatomy and the procedures        your system's favorites list
  the surgical package and global       a fracture-care billing macro
    periods (Ch. 17)
  the subsection guidelines and the     one manager's preference on
    parentheticals                        modifier sequencing
  the NCCI edits and WHY a pair         a specific payer's current
    bundles                               policy document
  reading an operative report           a template's field layout
  the documented-negative habit         the current fee schedule

The professionals in Case Study 2 had built careers on the right-hand column's federal cousin — the 1995 and 1997 scoring conventions for evaluation and management, counted in bullets. The ones who were fine were the ones whose expertise was the classification and the reasoning, because the 2021 revision made medical decision making more central rather than less.

Exercise 40 — H.1 (odd)

B. Adjust it off with a code identifying it as a preventable administrative write-off (Ch. 28 §28.6). A is prohibited — the line carried group code CO, a contractual obligation, and the patient may not be billed. C hides a preventable loss inside a contractual one and blinds the practice's own denial report. D is a decision made by neglect.

Exercise 40 — H.3 (odd, †)

B — whether the denominator is codes or charts. Chapter 37 §37.3 established it and §40.6 carries it: the same audit of the same charts can honestly report code-level, chart-level, financial accuracy, or direction, and a coder held to chart-level accuracy is held to a materially harder number on identical work. A, C, and D are all real and secondary — frequency and sample size affect how reliably the number is measured, and who audits affects whether findings cite an authority, but neither changes what the standard requires of her.

Exercise 40 — H.5 (odd)

Almost nothing in §40.3 would appear on a coding certification exam because the exams test the application of the code sets and their guidelines under proctored conditions — which is what Chapter 39 §39.1 says a credential does and does not certify. The break-even is not a coding question; it is a management question built from a practice's own labor cost and its own measured outcomes, and there is no right answer that a proctor could key.

That is not an argument that it matters less. Chapter 39 is explicit that the credential certifies one difficult morning and not the job: not working a denial, not reading a remit, not writing an appeal, not holding a query conversation, not knowing local coverage policy. The material an exam cannot test is most of the work — and the chapter that assembles it is the last one for the same reason it is the one nobody is examined on.

Exercise 40 — J.1 (odd, †)

The counterfactual: the denied line is 36415, allowed \$3.00.

  AT ACCOUNT 10-4471's OWN 58 MINUTES
    cost ..................... 58 x $0.60 = $34.80
    expected recovery ........ 3.00 x 0.68 = $ 2.04
    EXPECTED NET ............. 2.04 - 34.80 = -$32.76

  EVEN WORKED FAST, AT 10 MINUTES
    cost ..................... 10 x $0.60 = $ 6.00
    expected ................. $2.04
    EXPECTED NET ............. -$3.96          still negative

  THE MINUTES AT WHICH IT BREAKS EVEN
    2.04 / 0.60 = 3.4 MINUTES
    -- less time than it takes to open the remittance and find
       the line.

  Checks: 3.00 x 0.68 = 2.04 ✓ · 2.04 / 0.60 = 3.4 ✓
          58 x 0.60 = 34.80 ✓ · 2.04 - 34.80 = -32.76 ✓

The decision. Do not appeal the instance — and do not go quiet. Touch 1 happens anyway, so classify it and adjust it with a preventable write-off code. Then work the category: Ch. 31 §31.7 already ran the model, where the same \$2.40 variance across 1,150 occurrences a year is \$2,760.00, pursued once at the pattern level.

The sentence this counterfactual teaches that Account 10-4471 cannot: whether a claim was right and whether the appeal is worth writing are independent facts. The 36415 denial could be exactly as wrong as the E/M denial, exactly as winnable, and still not worth a letter. Being right is not the same as being worth pursuing — and the whole reason the break-even exists is that the profession has no other way to say that sentence out loud without it sounding like giving up.

Exercise 40 — J.3 (odd)

No key — the exercise is writing it before reading §40.3's version. What to look for in a strong answer: it names the five cases (the observation stay, the maternity package, the standing order, the drifted authorization, the returned envelope); it resists the temptation to blame anyone, because in every one of the five the harmed person did everything correctly and so, mostly, did the staff; and it lands on asymmetry of information and leverage rather than on malice. The strongest answers add something §40.3 only implies: that the patient in each case had no denial log, no overturn rate, no paragraph library, no provider representative — and no idea the apparatus existed at all.

Where a reader disagrees with §40.3 is worth keeping. The most common productive disagreement is that prevention is not in fact the only intervention that operates before harm — the good faith estimate (Ch. 32 §32.3) and the pre-service financial conversation (Ch. 24 §24.9) also do, and a reader who argues that has read Chapter 32 properly.