Drug Price History Check · method and verification

How was the Drug Price History Check checked, and what did the independent check find?

A separate reader recomputed the figures from the raw files and matched them with no mismatches. The method was written and hashed on 12 November 2026 before any figure was published.

What was fixed before any figure was published?

The method was frozen on 12 November 2026. The file's SHA-256 hash begins 3ebe8ab65a13. The tool refuses to build if the method file no longer matches its hash.

What does the independent check do?

  1. Every snapshot row lands in exactly one product at one year end, or is counted as unpriced (the builder stops otherwise).
  2. A test recomputes the median, lowest, highest and count for a random sample of 300 product-year points straight from the stored snapshot rows; the page data must equal them.
  3. A name search that matches a drug returns the same record the page shows.
  4. A mutation control: removing one year from a product's series must change its reported change (the control must be able to fail).

What did it find?

MeasureResult
Points sampled400
Seed99
Mismatches0

A separate Python reader recomputes the median, lowest, highest and NDC count for sampled product-year points straight from the stored snapshot rows.

The checking has so far led to no amendments to the method.

What is still not covered?

Year-end snapshots are one week of 52; a price move inside a year is not shown. Descriptions can be renamed by CMS; a renamed product appears as two products. NDC mix differs between snapshots. Brand and generic status is CMS's classification at each snapshot and can differ by year. Biologics and some products are not priced by NADAC.

How can you check it yourself?

The source data is public: see the CMS pharmacy pricing page. The dataset, the method and the code that rebuilds it are published at doi:10.5281/zenodo.24182320. Open the Drug Price History Check to see the result.

Questions about how the check works

What does "frozen before the first publication" mean?

The method was written, hashed and saved before any figure from the data was published. A change after that is an amendment with a date, and the original hash is kept, so anyone can see what was decided and when.

Why does an independent reader matter?

A tool can agree with itself and still be wrong. A separate reader, written without the builder's code, recomputes the figures from the raw files; where the two disagree, one of them has a defect.

Does a clean check mean the tool is always right?

No. It means the numbers match an independent recomputation under the stated method. The limits section lists what the method does not cover.

Further reading: Zenodo, where the datasets are deposited; the FAIR data principles; the National Academies on reproducibility; the author's ORCID record; the CMS pharmacy pricing page.

Compiled by Vincent Wesley Couey (ORCID 0009-0005-6869-308X).