Case Study 2 — The 340B Drug Payment Cut: A Rate That Was Reversed, and the Bill for Reversing It

DataField.Dev

Case Study 2 — The 340B Drug Payment Cut: A Rate That Was Reversed, and the Bill for Reversing It

A real, public case — the litigation over Medicare's payment rate for drugs acquired under the 340B Drug Pricing Program, decided by the Supreme Court of the United States in 2022 — told from the documented record: statute, notice-and-comment rulemaking, and published opinions. This case study asserts no dollar total, no hospital count, and no current payment rate. Every rate named below has already changed at least once; the current one is in this year's OPPS final rule.

Background

Case Study 1 was a policy the government defended and won. This is one it defended and lost — under the same statute, in the same annual rule, decided by a unanimous Supreme Court — and the interesting part is not the loss. It is what unwinding a payment rule costs inside a budget-neutral system.

Two systems meet here.

The 340B Drug Pricing Program (established by statute in 1992) requires drug manufacturers, as a condition of Medicaid participation, to sell covered outpatient drugs at substantially discounted prices to defined categories of safety-net providers — disproportionate-share hospitals, certain rural and children's hospitals, cancer hospitals, and a list of federally supported clinics. A qualifying hospital buys the drug cheaply. Nothing in the program dictates what any payer then pays the hospital for administering it; the spread between the discounted acquisition price and the payment is, by design, money the safety-net provider keeps.

OPPS pays separately for drugs above an annual per-day cost threshold — the status indicator K lines of §34.4, the ones that did not get packaged under §34.5. The statute gives the Secretary two routes for setting that rate. The first is the drug's average acquisition cost, determined using hospital acquisition-cost survey data — and on that route, the statute permits the rate to vary by hospital group. The second, available when survey data are not, is the drug's average price, calculated and adjusted by the Secretary — and on that route, one rate applies to everybody. In practice the second route has meant a rate built on the drug's average sales price: for years, average sales price plus a defined percentage.

The issue

In the CY 2018 OPPS final rule, CMS reduced the payment rate for 340B-acquired drugs — well below the rate paid to every other hospital for the identical drug — while exempting several categories of hospital from the reduction. The stated rationale was straightforward and, as policy, widely understood: 340B hospitals acquire these drugs at deep discounts, Medicare was paying them a rate built on a national average price they did not pay, and beneficiaries were paying coinsurance computed on that same higher amount.

Two features of the design matter for this chapter.

First, it arrived at the claim as a modifier. Hospitals had to identify, line by line, whether the drug on that line was 340B-acquired — modifiers JG and TB carried the distinction, one affecting payment and one informational, with the assignments revised as the policy changed. The same pattern as Case Study 1's PO and PN, and as the PT of §34.11: a national payment argument compressed into two characters that somebody at a desk has to get right. Chapter 25 §25.2 named the underlying form: a data element that stands in for a fact about the world.

Second, it was budget-neutral. The money taken out of 340B drug lines did not leave OPPS. It was redistributed across the system as an increase to the conversion factor, raising payment for every other non-drug outpatient service at every hospital — including the hospitals that had just lost the drug payment, and including hospitals with no 340B involvement whatsoever. This is §34.2's sentence in its purest documented form: inside a budget-neutral system, every winner is funded by everyone else. Hold on to it; it is the whole reason the ending is complicated.

What happened

Hospital plaintiffs and the American Hospital Association sued. The district court ruled for the hospitals; the D.C. Circuit reversed and upheld the agency; the Supreme Court granted review.

On June 15, 2022, in American Hospital Association v. Becerra, the Court ruled for the hospitals — unanimously.

The holding is narrow, and the narrowness is the lesson. The Court did not hold that the policy was bad policy, or that a lower rate for 340B drugs would be unlawful. It held that HHS had not done the survey. The statute permits rates that vary by hospital group only on the acquisition-cost route, and that route is conditioned on hospital acquisition cost survey data. Having not collected the data, the Secretary was on the average-price route — and on that route the statute does not permit varying the rate for one group of hospitals. The agency had lost on the predicate, not on the merits of the idea.

The outcome — and the part nobody expected to be hard

CMS restored the standard rate for 340B drugs going forward. That was the easy half.

The hard half is arithmetic that §34.2 predicted. The reduction had been budget-neutral for five rate years. That means two separate things were true at once by 2022:

340B hospitals had been underpaid on their drug lines from 2018 forward, and
every hospital — 340B and non-340B alike — had been overpaid on every other OPPS service across the same years, through the offsetting conversion-factor increase that had recycled the savings.

You cannot undo one without confronting the other. CMS's remedy, finalized by rule in 2023 after its own notice-and-comment process, did both: a one-time lump-sum payment to affected 340B providers for the underpaid years, and a prospective reduction to the OPPS conversion factor, applied over future rate years until the offsetting amount is recovered. Hospitals that had no part in the litigation, and clinicians treating patients who were not born when the rule took effect, will be paid slightly less per service for years, to unwind a redistribution that happened in the past.

The limit this case teaches

A rule can be substantively defensible and still unlawful, because of a step nobody performed. This is the sharpest version of a lesson the book has been circling since Chapter 22: an agency, like a provider, has to be able to show its predicate. HHS's reasoning survived the case intact. Its route to the reasoning did not, and the difference cost five years of payment policy. When a coder is told "we've always done it this way and it makes sense," the transferable question is the same one the Court asked: on what authority, and what does that authority require you to have done first?

Budget neutrality makes reversal expensive in both directions. Section 34.2 stated the rule in a sentence and warned it explained half the policy fights in this chapter. Here it explains the fight after the fight. A payment reduction that had been designed as a transfer could not be reversed as a transfer — the beneficiaries of the transfer had already spent five years of it, and the recovery lands on a conversion factor that touches every outpatient claim in the country.

Nothing on any claim was wrong. Read that again. Every drug line in this five-year story carried the correct J-code, the correct units, the correct modifier, and the correct diagnosis. Chapter 28 §28.8's underpayment method — expected allowed versus actual allowed — would have found nothing, because the claims paid exactly what the rule said they should. This is the same category Chapter 23's Case Study 2 opened, where the failure was in measurement rather than in any claim, and it is the purest instance the book has: a correct claim, correctly adjudicated, under a rule later held unlawful. No revenue-cycle control detects that. The control that does is somebody reading the rulemaking.

And it is not an overpayment in the sixty-day sense — do not confuse the two. Chapter 31 §31.9's rule runs on an overpayment a provider identifies on its own claims: money received that the provider was not entitled to under the rules as they stood. What happened here is a rate change applied backward by remedy rulemaking, worked out through the conversion factor by the agency itself. Treating a retroactive rate remedy as a self-reportable overpayment — or, worse, treating a genuine identified overpayment as "probably some rate thing that will sort itself out" — is a compliance error in both directions, and the sixty-day clock does not care which way you got it wrong.

Finally, the chapter's own discipline, vindicated. §34.2 told you never to present a rate as current, and this book labels every constructed figure it prints. Consider a textbook published in 2019 that printed the 340B rate as a fact. It would have been wrong when the Supreme Court decided the case, wrong again when the rate was restored, and wrong a third time when the remedy began adjusting the conversion factor. The structure is what you learn. The number is what you look up.

Discussion questions

The Court held for the hospitals without holding that the policy was wrong. State, in two sentences, exactly what HHS would have had to do to reach the same outcome lawfully — and then say what that implies about the difference between "we have good reasons" and "we have authority."
The reduction was budget-neutral, so reversing it required recovering money from hospitals that were not parties and had done nothing wrong. Is that fair? Argue both sides in a paragraph each, then say which design you would choose if you were writing the original rule and knew it might be challenged.
Every claim in this story was coded correctly and adjudicated correctly. Name the revenue-cycle control that would have detected the problem, and if your honest answer is "none," say what function in a hospital should own reading the annual OPPS rule — and what that person should be expected to produce from it.
Modifiers JG and TB, PO and PN, PT, PD, GA: this book keeps finding national policy compressed into two characters on a claim line. Using Chapter 25 §25.2's framing — a data element that stands in for a fact — describe what each of those characters asserts and who in the organization actually knows whether the assertion is true. Then say what that pattern implies about where facility coding errors will concentrate.
This chapter told you the OPPS conversion factor, the APC weights, the packaging threshold, and the status indicators all expire annually. Using this case, write the two-sentence explanation you would give a new coder who asks why the book will not just tell them the current numbers — and then name the three sources you would tell them to check instead.