Case Study 1 — Hospital Price Transparency: What Happens When You Publish the Second Number

A real, public regulatory action. Tier 1 facts. No figures are invented; where a specific number would be required to make a point, the point is made qualitatively instead.

Background

For most of the history of American hospital billing, exactly one of the four numbers in §1.2 was public: the charge. Hospitals maintained a chargemaster, a list of every billable item and its price, and in most states that document was at least nominally available. What was not available — anywhere, to anyone outside the negotiation — was the allowed amount: the payer-specific rate that each insurer had contracted to pay.

That asymmetry had a straightforward consequence. A patient could learn that a procedure was "charged" at \$18,000 and could learn nothing at all about what it would actually cost them, because the charge is not a price and the price was confidential. Providers and insurers both treated negotiated rates as trade secrets, and both had structural reasons to prefer it that way: a hospital that discovered a competitor was getting a better rate from the same insurer would demand parity, and an insurer that discovered it was paying above market would demand a reduction.

The Hospital Price Transparency rule changed the legal position. Adopted by the Centers for Medicare & Medicaid Services under authority in the Affordable Care Act and codified at 45 C.F.R. Part 180, it took effect January 1, 2021 and required each hospital operating in the United States to publish, publicly and without registration or a paywall:

1. A machine-readable file containing standard charges for all items and services, including gross charges, discounted cash prices, payer-specific negotiated charges, and de-identified minimum and maximum negotiated charges.
2. A consumer-friendly display of at least 300 "shoppable" services, either as a list or through a price estimator tool.

The rule was challenged by the American Hospital Association and others, and the challenge failed: the D.C. Circuit upheld the rule in 2020. Publication of payer-specific negotiated rates — the number this book calls the allowed amount — became a federal requirement for every hospital in the country.

The issue

The rule assumed that the reason nobody knew the second number was that nobody had published it. That assumption turned out to be only partly right, and the gap between the assumption and the reality is what makes this case worth studying in Chapter 1.

Compliance was slow and uneven. In the years following the effective date, successive reviews by CMS, by advocacy organizations, and by health services researchers reported substantial rates of non-compliance and partial compliance — files that were missing, incomplete, formatted in ways that frustrated use, or technically posted but effectively unfindable. CMS responded by raising civil monetary penalties, issuing corrective action notices, publishing the names of non-compliant hospitals, and — in subsequent rulemaking — imposing a required template and schema so that the files would be comparable across institutions rather than each hospital inventing its own layout.

The published files were harder to use than anyone expected. This is the part that matters to a revenue cycle professional, because it is a direct consequence of the structure this chapter taught. A "price" in healthcare is not a single number attached to a service. It is a number attached to a code, under a contract, with a payer, for a plan, at a site of service, subject to modifiers, potentially packaged into another service, and adjusted by the patient's benefit design. A machine-readable file that faithfully represents all of that is enormous and difficult to interpret. A file simple enough for a consumer to read has necessarily thrown away the qualifications that make it accurate.

And the number a patient actually wants was never in the file. A patient does not want to know the negotiated rate. They want to know what they will owe, which is a function of the allowed amount and their remaining deductible, their coinsurance percentage, their out-of-pocket maximum, their accumulator balances, whether the provider is in network for their specific plan rather than for the insurer generally, and which additional claims the encounter will generate. The price transparency rule published the second number. The patient needed the fourth.

What it shows

First, it confirms the chapter's central structural claim from the outside. A federal rulemaking, a trade-association lawsuit, and a circuit court opinion were all required to make public the fact that a charge is not a price. If the distinction between the charge and the allowed amount were obvious, none of that would have been necessary.

Second, it demonstrates why the four numbers must be understood as a system rather than a list. Publishing one of them, in isolation, produced far less benefit than expected, because the four are sequentially dependent: the charge is nearly meaningless without the allowed amount, the allowed amount is meaningless to a patient without the benefit design, and the benefit design is meaningless without knowing how much of the deductible is already spent.

Third, it explains a change in the reader's own job. A hospital's price transparency file is generated from the chargemaster and the contract management system — which means, in practice, that somebody in the revenue cycle department maintains it. Chargemaster accuracy stopped being an internal billing concern and became a public disclosure with a penalty attached. Chapter 23 §23.8 covers chargemaster maintenance, and this rule is a large part of why that section exists.

Fourth, and most usefully for a new professional: the industry's own data was worse than it thought. Multiple hospitals discovered, in the course of building the required file, that they did not have a single authoritative machine-readable source for their own negotiated rates — the rates lived in contracts, in spreadsheets, in a contract management module that had drifted from the signed agreements, and in the institutional memory of two people in the finance department. The exercise of publishing forced reconciliation. Underpayment identification (Chapter 28 §28.8) depends on knowing what the contract says, and a surprising number of organizations did not.

Outcome

The rule remains in effect and has been progressively tightened: CMS increased penalties, mandated a standardized template and required data elements, and required hospitals to affirm the accuracy and completeness of their files. Reported compliance improved over successive review cycles, though assessments differ substantially depending on what the reviewer counts as compliant — a "file exists" standard and a "file is complete, accurate, and usable" standard produce very different numbers, and readers evaluating any published compliance statistic should first ask which standard it used.

Parallel requirements were extended to insurers under separate transparency-in-coverage rulemaking, requiring plans to publish in-network rates and out-of-network allowed amounts, and to provide members with cost-sharing estimates. The combined effect is that far more of the second number is now public than at any previous point.

Whether it has changed what patients pay is a genuinely contested empirical question, and this book does not have an answer to it. What it has unambiguously changed is what a revenue cycle department is responsible for.

The lesson

A charge is not a price, and the fact that it took a federal rule and a court case to establish that publicly is the strongest possible argument for learning §1.2 properly.

Two further lessons for the working professional:

Transparency exposes internal data quality. Any requirement to publish forces an organization to discover what it actually knows. If your chargemaster and your contract management system disagree about what a payer allows for a code, that disagreement was always costing you money through unidentified underpayments — the rule simply made it visible.

The number that matters to the patient is the one closest to the end of the chain. A patient facing a procedure does not need the charge and does not really need the allowed amount. They need an estimate of their own responsibility, which requires the allowed amount plus real-time benefit information. Chapter 24 §24.9 and Chapter 32 §32.2 cover how to build one, and why the organizations that do it well collect more at lower cost than the ones that send a statement and hope.

Discussion questions

1. The rule required publication of the allowed amount but not of the patient's expected responsibility. Given the four-number structure in §1.2, was that the right choice? What would a rule requiring the fourth number have to specify that this one did not?

2. Hospitals argued that publishing payer-specific negotiated rates would raise prices, because below-market providers would demand parity. Insurers argued the opposite. Using only the structure in this chapter, construct the strongest version of each argument. Which depends on assumptions the chapter does not supply?

3. A hospital discovers, while building its machine-readable file, that its contract management system has a different allowed amount for a code than the signed contract does. Name three downstream processes that were affected by that discrepancy before anyone noticed.

4. The chapter says a charge is "an opening figure, not a price." After this case study, is there any audience for whom the charge is the operative number? Name them, and say what protects them.

5. Suppose you are the coder or biller asked to help validate the accuracy of your organization's transparency file. What are the three questions you would ask before signing off on it?