Home › API › Data Quality

Everyone ingests the same federal files.
Almost nobody checks what's in them.

Hospital price transparency data all comes from one place: the machine-readable files hospitals are required to publish under 45 CFR Part 180. The files are free. Parsing them is not hard. What separates a usable dataset from a large one is knowing which of those numbers are real — and a meaningful share of them are not.

3,650
hospitals publishing placeholder values
144,484
rows we flag and exclude
212
files that are majority unusable
17,621
procedure codes affected

What a placeholder looks like

When a hospital's billing vendor has no price to publish for a line, it does not leave the field empty. It writes a number. These are the conventions, measured across all 6,113 facilities in our corpus:

Value publishedRowsHospitalsWhat it means
$0.0128,0951,347no price available
$0.7013,393337vendor default
$0.0013,14189no price available
$0.353,860261vendor default
$999,999,9991,40223max-integer, "not applicable"

These are syntactically valid numbers. A parser accepts them, a schema validates them, and a database stores them. Nothing about the ingest fails.

Why it breaks benchmarking specifically

Placeholders are not randomly distributed — they cluster at the extreme ends of the price distribution. That makes them maximally damaging to exactly the statistics a rate-benchmarking team depends on:

A worked example

CPT 27447, total knee replacement. Same source files, two ways of handling them:

ApproachReported figure
Ingest as published, report the mean$1,866,246
Detect placeholders, exclude, report the median$9,069

The first number is not a typo and not a rounding difference. It is what the arithmetic produces when a handful of max-integer rows are treated as prices. A knee replacement does not cost $1.8 million, and any benchmark built on that figure is unusable — but nothing in the pipeline errors.

The hard part is not detection. It's not over-detecting.

A crude filter — drop anything implausible — destroys real data. Gene and cell therapies genuinely bill in eight figures, and they are in these files:

CodeTherapyPublished chargeVerdict
J3399onasemnogene abeparvovec (Zolgensma)$20,072,246real — retained
J3394lovotibeglogene autotemcel (Lyfgenia)$16,577,889real — retained
J3392exagamglogene autotemcel (Casgevy)$11,764,953real — retained
Q2055idecabtagene vicleucel (CAR-T)$10,000,000real — retained
MS075viral meningitis w/ CC-MCC$999,999,999sentinel — excluded

A $5M cut-off looks sensible and silently deletes every one of the real therapies above. Ours sits at $99M — above every genuine charge line we have observed, below every max-integer convention. Detection is relative to the peer distribution for the same code, with an absolute ceiling as a backstop.

The question for a data vendor is not how many rows they have. It is whether they can tell you which rows are fiction — and show you the list.

What we can hand you

The exclusion list itself

Not a claim — a file. Every flagged row, by hospital, code, published value, and the peer median it was measured against. If you are already licensing this data from someone, run it against what you have and see what comes back.

A per-facility compliance grade

4,077 facilities scored on whether they meet 45 CFR Part 180 at all: 427 publish no usable file, 3,650 publish a file containing placeholders, 212 are majority unusable. Each with a phone number.

Coverage others skip

6,113 facilities across 55 states and territories — including Puerto Rico, the US Virgin Islands, Guam and American Samoa, which most corpora stop short of. Plus 59,618 clinic and surgery-center locations and 1,102,404 individual practitioners alongside the hospital data.

Test it against your current source

Send us a state and a handful of codes you already have rates for. We will return our figures beside the exclusion list for those codes, so you can see exactly which rows differ and why. No commitment, and you keep the comparison.

info@medcompare.co · API documentation and access tiers →

Figures on this page are computed from our own corpus of hospital machine-readable files and are reproducible from the exclusion list. They describe what is in the source files published by hospitals — they are not a measurement of any other vendor's product.