Price transparency files: mandated, massive and hard to read
The Transparency in Coverage rule mandated publication of negotiated rates, not their usability. Whether the files were worth anything depended on volume, meaning and accountability, three engineering and governance problems the rule left to plans, employers and intermediaries.
Looking Back revisits one week at a time, from January 2020 to today, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.
The week
On October 29, 2020, the Departments of Health and Human Services, Labor and the Treasury issued the Transparency in Coverage final rule. It required most group health plans and health insurance issuers to publish machine-readable files of negotiated in-network rates and historical out-of-network allowed amounts, and to give members an online tool showing estimated cost-sharing before care. The files were originally due from January 2022; the departments later announced enforcement from July 1, 2022. The member tool was phased in, with an initial list of 500 items and services for plan years beginning in 2023 and all covered items and services from 2024. The rule followed the separate hospital price transparency rule, which took effect on January 1, 2021.
The policy debate around Transparency in Coverage concerned consumers and competition. For health plans, health systems, employers and analysts, the operational reality was a data engineering problem of unusual size. The rule required publication; it did not and could not require that the files be usable. Their value depended on three things the regulation specified only partly: the volume of data, the meaning of each rate, and accountability for its accuracy. Each needs a different kind of investment, from a different owner.
Volume: publishing is not delivering
A negotiated rate file has to express every combination of plan, provider, billing code and rate arrangement. For a large insurer with broad networks that is an enormous number of rows, refreshed monthly. When the files began appearing in July 2022, observers widely reported individual payers publishing many terabytes, with some single files too large to open on an ordinary workstation.
Volume decided who could use the data. Individual consumers could not. Employers, researchers, brokers, data companies and providers with engineering capacity could, after building pipelines to download, parse, deduplicate and index the files. In effect the rule created a market for intermediaries. That may have been unavoidable, but it was not the outcome most public commentary imagined in 2020.
For health systems the volume posed a quieter question: whether to ingest payer and competitor rate data for contract negotiation. Doing so meant storage and pipeline costs that sat in no existing budget line. It also meant deciding who would maintain the pipeline when file formats changed, as they did several times through schema updates.
Meaning: rates are not prices
The deeper problem was semantic. Health care contracts do not always state a dollar amount per service. Rates can be a percentage of billed charges, a case rate for a bundle, a per diem, or a reference to a fee schedule. Translating these into a common schema loses context, and different payers made different translation choices.
The same procedure at the same hospital could appear with several rates, each technically correct and practically confusing. Some files listed rates for provider and code combinations that would rarely or never be billed, because contracts covered whole fee schedules. Without knowing which arrangements actually drove payment, an analyst could not tell a meaningful rate from an artifact of contract structure.
This is a familiar trap in data and AI work. A schema can guarantee structure without guaranteeing meaning. Any model or comparison built on the files inherited their ambiguity. Teams that extracted value spent most of their effort on interpretation: matching provider identifiers to real practice locations, filtering implausible combinations, converting percentage-based rates using assumed charge levels, and checking results against actual claims.
That interpretation work is where the competitive value sat. Two organizations with the same raw files could reach different conclusions about the same market, depending on how they filtered and validated. For a health system’s managed care team, the quality of that interpretation mattered more in negotiations than access to the files themselves.
Accountability: who answers for the number
Plans could use third parties, such as administrators or vendors, to produce files, but the obligation stayed with the plan. For self-funded employer plans, that meant an employer was legally responsible for a file it had probably never opened, generated from network contracts it did not negotiate.
That arrangement put a premium on documentation. An employer needed to know which vendor produced which file, how it was validated, where it was posted, and how errors would be found and corrected. Many service agreements with administrators were silent on these points in 2020. Renewals were the natural moment to add them, with clear allocation of responsibility and costs. Organizations should check with counsel on how responsibility is allocated in their own plan and vendor agreements.
Providers had a stake without control. A health system whose rates appeared in a payer’s file had an interest in whether they were represented correctly, since errors could surface in negotiations, research and the press. It had no direct way to correct the publication. Comparing payer files with its own contract terms lets a system spot misrepresentation before others do.
A mandated public dataset is also a public statement. Errors in it can appear in a reporter’s story, a competitor’s pitch or an enforcement action. Quality checks that would be optional for internal reporting become necessary when the data is published under legal obligation.
Read together, the three problems explain the uneven results. The rule assumed that once data was public, markets would use it. Use required engineering capacity for volume, domain expertise for meaning and clear ownership for quality. Those were spread very unevenly across plans, employers and providers.
Organizations planning to use any mandated disclosure in analytics or AI should ask three questions first. What does the publisher actually guarantee? How often does the format change? How are errors corrected, and how would you know? Price transparency files were an early, large-scale example of the gap between compliance data and analytical data.
With hindsight
By 2026 the machine-readable files are an established if imperfect resource. Researchers, employer coalitions and commercial data firms built products on them, and providers increasingly use them in contract talks. The criticism that the files were too large and inconsistent for direct use held up. Much of their value reached decision-makers only after heavy processing by intermediaries.
Federal attention did not fade. Hospital price transparency enforcement was tightened over time. A February 2025 executive order directed the departments to improve the accuracy and comparability of disclosed prices and to strengthen enforcement. The consumer cost-estimate tools also arrived on schedule but did not become the main way most patients make decisions about care. The 2020 rule is best understood as the point when health care pricing turned into a public data asset, with all the engineering and governance that implies.