Skip to content
FonteumThe Graph

The capability layer

APIREST + bulk accessMCP serverCallable by AI agentsFHIR R4 APIBulk exportAttestation & audit packReconciliationSource-vs-source diffsEntity graphSnapshotsPoint-in-time, bitemporal

By use case

Exclusion & sanctions screeningCredentialing & provider-data enrichmentAudit evidence & defensible programsProvider data for AI / RAGM&A & network diligence

By buyer

Compliance & riskDevelopers & AI teams

The differentiator

Coverage & sourcesThe catalogFreshnessMethodologyCare CompareFacility qualityBrowse all datasets →
Research

The dev on-ramp

DocsAPI referenceMCPQuickstartStatusChangelogSDKs & integrations
Pricing
Sign inTry the FHIR sandbox →Request access →

Platform

APIMCP serverFHIR R4 APIBulk exportAttestation & audit packReconciliationEntity graphSnapshots

Solutions

Exclusion & sanctions screeningCredentialing & provider-data enrichmentAudit evidence & defensible programsProvider data for AI / RAGM&A & network diligenceCompliance & riskDevelopers & AI teams

Data

Coverage & sourcesFreshnessMethodologyCare CompareBrowse all datasets →
Research

Developers

DocsAPI referenceMCPQuickstartStatusChangelogSDKs & integrations
Pricing
Sign inTry the FHIR sandbox →Request access →

← All sources · Healthcare graph

CMS Price Transparency

CMS Hospital Price Transparency Enforcement

Centers for Medicare & Medicaid Services (CMS) · Tier-2 · profile-enrichment (renders on matched profiles)

Live
Source:CMS Price Transparency·Checked May 2026Open official source ↗

The CMS Hospital Price Transparency Enforcement dataset records every enforcement action taken under 45 CFR § 180 (the Hospital Price Transparency rule, effective January 1, 2021). It covers all hospitals subject to the rule — general acute care, critical access, and specialty hospitals — and tracks the full enforcement arc from initial warning through corrective action plans, civil monetary penalties (CMPs), and final resolution. As of 2026, the dataset spans 11,440 enforcement actions across 4,988 unique hospital review cases.

What Fonteum uses it for

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.

What this dataset answers

Research and data questions this source supports.

  • 01Map per-state hospital price-transparency enforcement density to see where CMS has concentrated its 45 CFR § 180 actions.
  • 02Identify hospitals that received a civil monetary penalty (CMP) under the Hospital Price Transparency rule, and which later reached 'Met Requirements'.
  • 03Track the compliance trend across the full enforcement arc — warning, corrective action plan, CMP, resolution — since the rule took effect January 1, 2021.
  • 04Reproduce the /research/hospital-price-transparency-compliance-2026 study with the underlying enforcement records and source provenance.
  • 05Support 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)

Fields used

Per-field display contract.

Every field below has a `display_allowed` flag in the §94 provenance schema. Write-locked fields are captured to provenance for audit but never rendered on profile pages.

Research-only — never on profiles

7 fields
case_idCMS case ID
hosp_nameHospital name
hosp_addressHospital address
stateState
actionEnforcement action type
action_dateAction date
closure_reasonClosure reason
Limitations

What we can’t infer from this source.

  • Snapshot-based: the dataset reflects enforcement actions as published at each monthly CMS release; actions finalized after the snapshot date do not appear until the next pull.
  • 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.
Source metadata

Authority, license, refresh cadence.

Authority

Centers for Medicare & Medicaid Services (CMS)

Tier

Tier-2 · profile-enrichment (renders on matched profiles)

Refresh cadence

Monthly — CMS publishes updated enforcement data each month. Fonteum re-pulls on the 1st of each month.

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

https://data.cms.gov/provider-characteristics/hospitals-and-other-facilities/hospital-price-transparency-enforcement-activities-and-outcomes

Attribution requirement

Source: CMS Hospital Price Transparency Enforcement · Snapshot {YYYY-MM-DD}

ToS & usage notes

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. Fonteum snapshots the data via the data-api/v1 endpoint (dataset ID 6a3aa708-3c9d-411a-a1a4-e046d3ade7ef) and attest each pull with SHA-256.

Sample provenance

What a single field looks like in the graph.

A worked example. Every field surfaced from this source carries this shape of provenance line — source · last checked · display rule · confidence (when applicable).

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

How to access

Official API, bulk download, and Fonteum endpoints.

Official API / download

https://data.cms.gov/provider-characteristics/hospitals-and-other-facilities/hospital-price-transparency-enforcement-activities-and-outcomes ↗

Frequently asked

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. Fonteum re-pulls on the 1st of each month and attests each snapshot with a SHA-256 hash.
Related

Where this source already shows up.

Research studies citing this source

  • Hospital Price Transparency Enforcement: 11,440 CMS Actions Since 2021 →

Related sources in the graph

  • /sources/cms-hcris-hospital-2552-10 →
  • /sources/cms-care-compare-hospitals →
  • /sources/cms-pos →

Per-source methodology: /methodology/cms-price-transparency →

See also
  • /sources → The full source library — every dataset Fonteum cites.
  • /data-provenance → The provider graph — pipeline diagram, source-family clusters, field-level provenance examples, display rules.
  • /methodology → Network-wide sourcing, refresh cadence, and corrections policy.
  • /editorial-policy → Independence, sourcing, conflicts, corrections, retractions.

The substrate, by the numbers

9.2Mgraph entitiesProviders, organizations, owners, and facilities
15.7Mlinked identifiersNPIs, CCNs, LEIs and more, resolved to entities
5Mgraph edgesSource-attested relationships between entities
44federal source familiesDistinct CMS, OIG, HRSA, FDA and peer datasets
35dataset pagesCitable, downloadable /data catalog pages
65reproducible studiesEach shipping the SQL behind its figures

Built on the authoritative federal record

The primary sources, named on every page.

These are the federal agencies whose public datasets Fonteum ingests and attributes — the issuing authorities, not customers or partners. Every figure on the site links back to one of them.

  • CMS
  • HHS-OIG
  • HRSA
  • FDA
  • NLM
  • NUCC
  • Census
  • BLS
  • BEA

See the full source registry, with license and refresh cadence for each →

Reproducible by design

Every figure traces to its federal source.

14-tuple provenance

Every rendered fact ties to a source URL, dataset ID, snapshot date, row key, and SHA-256 — the full chain-of-custody record.

Reproducible SQL

Each study ships the exact query behind its figures, run against the cited federal snapshot. Re-run it yourself.

Daily reconciliation

Published counts are reconciled against the upstream federal datasets on a daily cadence, with drift logged.

Named medical review

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

Read the full provenance and attestation methodology →

Two doors

Use the free API and open data

Query providers, facilities, sanctions, and quality scores — each field carrying its federal source. Self-serve, no call to start.

Explore the API →Browse the data catalog →

Talk to us

Managed pilots, enterprise terms, and audit-ready, signed attestation packages for compliance, risk, and research teams.

Talk to us →
Fonteum
Platform
Platform overviewAPIMCP serverFHIR R4 APIBulk exportAttestation & audit packReconciliationEntity graphSnapshots
Solutions
All solutionsExclusion & sanctions screeningCredentialing & enrichmentAudit evidenceProvider data for AI / RAGM&A & network diligenceCompliance & riskDevelopers & AI teams
Data & sources
Coverage & sourcesBrowse all datasetsState Medicaid exclusionsFreshnessMethodologyCare CompareSanctionsOwnershipStaffingDeficienciesSpecial Focus Facilities
Developers
Developer hubDocsAPI referenceQuickstartStatusChangelogSDKs & integrationsWebhooks
Research
Research hubHospital margin gapProvider access gapsGlossaryComparisonsCitationsWhy Fonteum
Company
AboutPressCustomersPricingContactEditorial policyCorrections
Trust & legal
TrustQualitySecurityPrivacy policyTerms of serviceMedical disclaimer

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

© 2026 Fonteum LLC. All rights reserved.

·hello@fonteum.com

The U.S. healthcare graph AI can cite — every fact carries its source.

Request access→