Skip to content
FonteumPublic-records evidence
CMS monthly cadenceCMS · Tier 2

CMS Hospital Price Transparency
Enforcement Data

11,440 enforcement actions in the committed CMS-derived snapshot, spanning January 2021 through March 2026. 4,988 hospital review cases across all 50 states; this page does not claim a newer load from publisher cadence.

Source: CMS Hospital Price Transparency Enforcement·Snapshot: 2026-03-31·Method: price-transparency/v1·ID: 6a3aa708-3c9d-411a-a1a4-e046d3ade7ef
Source:CMS Hospital Price TransparencySnapshot 2026-03-31

Dataset at a glance

11,440

Total records

Enforcement actions

4,988

Hospital cases

Unique review cases

28

Civil Monetary Penalties

Most severe action

Monthly

CMS publisher cadence

Page snapshot through March 2026

2021–2026

Temporal coverage

Snapshot 2026-03-31

7

Fields

Case_ID · Hosp_Name · State · Action · Action_Date · +

Field reference

FieldTypeDescription
case_idtextCMS-assigned case identifier. One hospital may have multiple Case_IDs across separate review cycles.
hosp_nametextHospital name as published by CMS.
hosp_addresstextHospital address as published by CMS.
statetext (2-char)Two-letter state abbreviation for the hospital's location.
actiontext (enum)Enforcement action type: Warning Notice, CAP Request, CMP Notice, Met Requirements, Closure Notice, Administrative Closure, Appealed.
action_datedateDate CMS issued the enforcement action. Parsed from MM/DD/YYYY to ISO-8601.
closure_reasontext (nullable)Reason for administrative closure when applicable.

Source fields: CMS exports Case_ID, Hosp_Name, Hosp_Address, State, Action, Action_Date, Closure_Reason. No NPI or CCN field in the CMS export.

Known limitations

  • Hospital identity is name + address string — no NPI or CCN. Cross-referencing to NPPES or Care Compare requires fuzzy matching.
  • CMP dollar amounts are not published in this dataset; it records the existence of a CMP Notice, not a separately signature-linked fact.
  • A hospital may have multiple Case_IDs across separate review cycles; compliance status must be inferred from the action sequence.
  • Federal enforcement only — state-level enforcement actions are not included.
  • Does not contain the hospitals' actual charge files (MRFs) or pricing data.

Frequently asked questions

What fields are included in the CMS Hospital Price Transparency enforcement dataset?
The CMS export includes 7 fields: Case_ID, Hosp_Name, Hosp_Address, State, Action, Action_Date, and Closure_Reason. No NPI or CCN field is present in the raw CMS data.
How often is the price transparency enforcement data updated?
CMS declares a monthly publication cadence. This page's committed snapshot spans through March 2026; the publisher cadence does not establish a newer Fonteum load or universal signature coverage.
Does this dataset include the actual hospital prices or charge files?
No. This dataset records CMS enforcement actions only — it does not contain the hospitals' machine-readable files (MRFs) or the price data itself. For actual hospital charge data, see the hospitals' published MRFs under 45 CFR Part 180.
What is a Civil Monetary Penalty under the price transparency rule?
A Civil Monetary Penalty (CMP) is the most severe enforcement action available to CMS under 45 CFR § 180.90. The committed snapshot through March 2026 contains 28 CMP Notice rows; it does not publish penalty amounts.
Can I access the full price transparency enforcement dataset via API?
Yes. CMS publishes the source data on data.cms.gov as a public JSON API and bulk download; the dataset identifier is listed in the Source & provenance section below. The data is U.S. government works (17 U.S.C. § 105) and in the public domain.

Source & provenance

Primary source: CMS Hospital Price Transparency Enforcement Activities and Outcomes — Centers for Medicare & Medicaid Services. Dataset ID: 6a3aa708-3c9d-411a-a1a4-e046d3ade7ef.

License: U.S. government works (17 U.S.C. § 105) — public domain. Attribution: “Source: CMS Hospital Price Transparency Enforcement · Snapshot 2026-03-31”.

Methodology version: price-transparency/v1

Snapshot date: 2026-03-31. Consult CMS for a later release.

What’s on file, by the numbers

Platform snapshot · 2026-08-11

13.4Mproviders & companiesProviders, organizations, owners, and facilities on file
26.2Msource-linked factsSource-linked field facts in the dated platform snapshot
90sources with dataDistinct snapshot source IDs with at least one positive record count
73fresh sourcesDistinct source IDs whose latest positive-data snapshot falls within the preceding 45 days
111sources integratedActive registry rows; integration does not establish a load
13state Medicaid jurisdictionsDistinct states represented in the state-exclusions serving table

Integrated, with-data, and fresh-observation counts are separate. No platform-wide source-completeness count is published. Completeness is source-specific and must be evaluated against the named source's expected scope. State coverage is a separate jurisdiction measure.

Source authority is record-specific

Use the issuer named on the record.

Fonteum spans federal, state, and global public publishers. A source page or returned record identifies its issuer and dataset where that metadata is available. A platform registry count does not assign every page to one authority or establish loaded, fresh, or complete coverage.

Browse source records and their stated limitations →

Reproducible by design

Inspect the evidence each published figure actually supplies.

Source and date

Research pages expose the named public file and observation date where those fields are available. Source-file SHA-256 coverage is separate; facts do not currently link deterministically to signatures.

Available derivation

Studies with a retained release and committed derivation link the SQL or method used. Other studies state the evidence and reproduction limits they actually have.

Daily observations

Dated table row-count observations can detect local drift. They do not imply that an upstream publisher released or Fonteum ingested new data that day.

Named medical review

Reviewed by Jennifer Montecillo, MD, medical reviewer. Non-practicing medical reviewer.

Read the full provenance and attestation methodology →

Request access