← All sources Healthcare graph
CMS Price TransparencyCMS Hospital Price Transparency Enforcement
Centers for Medicare & Medicaid Services (CMS) · Tier-2 · profile-enrichment (renders on matched profiles)
The committed CMS Hospital Price Transparency Enforcement snapshot contains 11,440 action rows across 4,988 review cases through March 31, 2026. It records warning, corrective-action, civil monetary penalty, and resolution actions published in that snapshot; it does not establish a newer load from CMS's monthly cadence.
How this source shows up on Fonteum.
Powers the /research/hospital-price-transparency-compliance-2026 flagship study and the /data/price-transparency dataset page. Enables per-state enforcement density analysis, CMP recipient identification, and compliance trend mapping.
What this source does NOT mean
This dataset records CMS enforcement actions — it does not contain the hospitals' actual machine-readable files (MRFs) or the price data itself. An action does not represent a finding of ongoing non-compliance; hospitals that completed corrective actions appear as 'Met Requirements'. Fonteum does not editorially rank hospitals based on enforcement history.
Research and data questions this source supports.
- Map per-state hospital price-transparency enforcement density to see where CMS has concentrated its 45 CFR § 180 actions.
- Identify hospitals that received a civil monetary penalty (CMP) under the Hospital Price Transparency rule, and which later reached 'Met Requirements'.
- Track the compliance trend across the full enforcement arc — warning, corrective action plan, CMP, resolution — since the rule took effect January 1, 2021.
- Reproduce the /research/hospital-price-transparency-compliance-2026 study with the underlying enforcement records and source provenance.
- Support hospital M&A or compliance diligence with a hospital's documented CMS enforcement history.
Dataset size: 11,440 enforcement actions across 4,988 hospital cases (2026 snapshot)
Per-field display contract.
Fields listed below show their configured `display_allowed` flag from the §94 provenance schema. Fields marked write-locked are captured for audit and are not rendered on profile pages.
Research-only — never on profiles
7 fieldsWhat we can’t infer from this source.
- Snapshot-based: this committed study runs through March 31, 2026. Later actions are absent unless and until a newer artifact is published.
- Hospital identity is name + address string — no NPI or CCN in the raw CMS export. Cross-referencing to NPPES or Care Compare requires fuzzy matching.
- A hospital with multiple review cycles appears multiple times with distinct Case_IDs; the same hospital may show both 'Warning Notice' and 'Met Requirements' actions in the same snapshot.
- Enforcement actions are CMS determinations of regulatory compliance under 45 CFR § 180; they do not reflect clinical quality, financial health, or patient outcomes.
Authority, license, publisher cadence.
Authority
Centers for Medicare & Medicaid Services (CMS)
Tier
Tier-2 · profile-enrichment (renders on matched profiles)
Publisher / configured cadence
Declared or configured cadence: Monthly — CMS publishes updated enforcement data each month. Not evidence of the latest loaded source date.
License
U.S. government public-domain works (17 U.S.C. § 105). Federal enforcement records. Attribution required: 'Source: CMS Hospital Price Transparency Enforcement · Snapshot {YYYY-MM-DD}'. License ↗
Official URL
Attribution requirement
Source: CMS Hospital Price Transparency Enforcement · Snapshot {YYYY-MM-DD}
What the source allows.
U.S. government public-domain works (17 U.S.C. § 105). CMS publishes the enforcement dataset at data.cms.gov under U.S. government open data terms. No API key required. This page uses a committed March 31, 2026 snapshot; hash coverage is artifact-specific and no provenance fact currently links deterministically to a signature.
What a single field looks like in the graph.
This worked example shows the provenance shape used when a surfaced field has populated source, last-checked, display-rule, and confidence metadata. Individual fields may omit unavailable values.
Field
Enforcement action (research)
Sample value
CMP Notice · Case 555 · 2022-07-14 · TX
Provenance line
Source: CMS Hospital Price Transparency Enforcement · Snapshot 2026-06-06 · Methodology price-transparency/v1 · Display rule: enforcement action renders in research study and dataset page only
Official API, bulk download, and Fonteum endpoints.
Official API / download
Common questions about CMS Price Transparency.
- What is the CMS Hospital Price Transparency Enforcement dataset?
- It is the federal record of every enforcement action CMS has taken under 45 CFR § 180, the Hospital Price Transparency rule effective January 1, 2021. It covers general acute care, critical access, and specialty hospitals subject to the rule and tracks the full arc from initial warning through corrective action plans, civil monetary penalties, and final resolution.
- How many enforcement actions are in the dataset?
- As of the 2026 snapshot, the dataset spans 11,440 enforcement actions across 4,988 unique hospital review cases. A single hospital with multiple review cycles appears multiple times with distinct CMS case IDs.
- Does this dataset contain hospital prices?
- No. The dataset records CMS enforcement actions — not the hospitals' machine-readable files (MRFs) or the price data itself. An enforcement action is a CMS determination of regulatory compliance; it does not reflect clinical quality, financial health, or patient outcomes.
- Does an enforcement action mean a hospital is non-compliant today?
- Not necessarily. Hospitals that completed corrective actions appear with a 'Met Requirements' action, and the same hospital may show both a 'Warning Notice' and a 'Met Requirements' record in the same snapshot. Fonteum does not editorially rank hospitals based on enforcement history.
- Where does the data come from and how often is it updated?
- CMS publishes the enforcement dataset at data.cms.gov as U.S. government public-domain data (17 U.S.C. § 105); no API key is required. Loaded dates must be read from the specific response; publisher cadence is not proof of a completed load.
Where this source already shows up.
Research studies citing this source
Related sources in the graph
- /sources → The generated source-catalog subset — documented datasets Fonteum cites.
- /data-provenance → The provider graph — pipeline diagram, source-family clusters, field-level provenance examples, display rules.
- /methodology → Documented sourcing, publisher cadence, observed freshness, and corrections policy.
- /editorial-policy → Independence, sourcing, conflicts, corrections, retractions.