> For the complete documentation index, see [llms.txt](https://docs.dataplex-consulting.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dataplex-consulting.com/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/hospital-price-transparency-enforcement-activities-and-outcomes.md). # Hospital Price Transparency Enforcement Activities and Outcomes Part of the [CMS Data Feeds Dataset](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog.md) › Medicare Dataplex delivers this CMS feed as the analysis-ready table `DWV.HOSPITAL_PRICE_TRANSPARENCY_ENFORCEMENT_ACTIVITIES_AND_OUTCOMES` on Snowflake and Databricks — coverage from 2023 to 2026 in a single aligned schema, refreshed automatically whenever CMS publishes a new file. Every row carries lineage back to the exact CMS source file that produced it. ## Key facts | | | | ------------------ | ------------------------------------------------------------------------- | | **Snowflake** | `DWV.HOSPITAL_PRICE_TRANSPARENCY_ENFORCEMENT_ACTIVITIES_AND_OUTCOMES` | | **Databricks** | `cms_dwv.hospital_price_transparency_enforcement_activities_and_outcomes` | | **Coverage** | Oct 2023 – Jun 2026 | | **Rows** | 133,171 (total across all reporting periods) | | **Cadence** | Monthly | | **Update pattern** | Time-partitioned — each file adds one reporting period | | **CMS published** | 2026-07-14 | | **Loaded** | 2026-07-15 | | **Columns** | 11 data + 6 lineage | | **File versions** | 18 | | **License** | CMS public data — U.S. Government work | | **Platforms** | Snowflake Marketplace · Databricks Delta Sharing | Included in the CMS Data Feeds Dataset — [start a free trial on Snowflake Marketplace](https://app.snowflake.com/marketplace/listing/GZT1Z125KDH/dataplex-consulting-data-products-cms-data-feeds-dataset). {% hint style="success" %} **Current** — CMS last published this feed on 2026-07-14. Coverage runs through 2026-06-30. Next CMS release expected \~Aug 2026. {% endhint %} {% hint style="info" %} **Time-partitioned feed** — each file version covers one reporting period, so history is additive. Query the full table for all periods; filter on the reporting period columns for a single period. Do **not** filter to the latest file only — that would return just the 2026 reporting period. {% endhint %} ## Sample queries {% tabs %} {% tab title="Snowflake" %} ```sql -- Each file version covers one reporting period (2023, 2024, 2025, 2026) — history is additive SELECT * FROM DWV.HOSPITAL_PRICE_TRANSPARENCY_ENFORCEMENT_ACTIVITIES_AND_OUTCOMES LIMIT 100; ``` {% endtab %} {% tab title="Databricks" %} ```sql -- Each file version covers one reporting period (2023, 2024, 2025, 2026) — history is additive SELECT * FROM cms_dwv.hospital_price_transparency_enforcement_activities_and_outcomes LIMIT 100; ``` {% endtab %} {% endtabs %} ## About this feed > The Hospital Price Transparency Enforcement Activities and Outcomes dataset contains information related to enforcement actions taken by CMS following a compliance review of a hospital's obligation to establish, update and make public a list of the hospital’s standard charges for items and services provided by the hospital, in accordance with regulation (45 CFR 180). This data set includes the name of each hospital or hospital location, the hospital or hospital location address, the outcome or action following a CMS compliance review and the date of the outcome or action taken. > > — *Source: CMS feed metadata* **Keywords:** Medicare, Hospitals & Facilities, Health Care Use & Payments **Theme:** Medicare ## Coverage timeline 2023 🟩 · 2024 🟩 · 2025 🟩 · 2026 🟩 4 of 4 years covered — no gaps. ## Release history | Reporting period | CMS published | Loaded | Latest file | | ----------------------- | ------------- | ---------- | ----------- | | 2026-06-01 – 2026-06-30 | 2026-07-14 | 2026-07-15 | ✓ | | 2026-05-01 – 2026-05-31 | 2026-06-09 | 2026-06-11 | | | 2026-01-01 – 2026-01-31 | 2026-04-30 | 2026-06-03 | | | 2025-12-01 – 2025-12-31 | 2026-02-17 | 2026-06-03 | | | 2025-04-01 – 2025-04-30 | 2025-07-25 | 2026-06-03 | | | 2025-01-01 – 2025-01-31 | 2025-05-12 | 2026-06-03 | | | 2024-12-01 – 2024-12-31 | 2025-02-06 | 2026-06-03 | | | 2024-09-01 – 2024-09-30 | 2024-10-17 | 2026-06-03 | | | 2024-06-01 – 2024-06-30 | 2024-08-14 | 2026-06-03 | | | 2023-12-01 – 2023-12-31 | 2024-08-06 | 2026-06-03 | |
Show 8 earlier file versions | Reporting period | CMS published | Loaded | Latest file | | ----------------------- | ------------- | ---------- | ----------- | | 2026-01-01 – 2026-03-31 | 2026-04-30 | 2026-04-30 | | | 2025-10-01 – 2025-12-31 | 2026-02-17 | 2026-02-17 | | | 2025-04-01 – 2025-06-30 | 2025-07-25 | 2025-07-25 | | | 2025-01-01 – 2025-03-31 | 2025-05-12 | 2025-05-12 | | | 2024-10-01 – 2024-12-31 | 2025-02-06 | 2025-02-06 | | | 2024-07-01 – 2024-09-30 | 2024-10-17 | 2024-10-17 | | | 2024-04-01 – 2024-06-30 | 2024-08-14 | 2024-08-14 | | | 2023-10-01 – 2023-12-31 | 2024-03-04 | 2024-03-06 | |
## Data dictionary
📋 11 data columns + 6 lineage columns Column-level definitions are maintained by CMS in the official [Hospital Price Transparency Enforcement Activities and Outcomes data dictionary](https://data.cms.gov/resources/hospital-price-transparency-enforcement-activities-and-outcomes-data-dictionary-current). **Data columns** | Column | Type | | ---------------- | ------ | | `CASE_ID` | NUMBER | | `HOSP_NAME` | TEXT | | `HOSP_ADDRESS` | TEXT | | `CITY` | TEXT | | `STATE` | TEXT | | `ACTION` | TEXT | | `DATE_OF_ACTION` | DATE | | `__CASE_ID` | NUMBER | | `__HOSP_NAME` | TEXT | | `HOSP_ID` | NUMBER | | `DT_ACTION` | DATE | **Lineage columns** (present on every feed table) | Column | Type | Description | | -------------- | -------------- | -------------------------------------------- | | `ROW_ID` | TEXT | Unique row ID for this table (PK) | | `FILE_ID` | TEXT | Source file — joins to `FEEDS_FILES.ID` (FK) | | `FILE_FEED_ID` | TEXT | Parent feed — joins to `FEEDS.ID` (FK) | | `FILE_NAME` | TEXT | Source file name as published by CMS | | `ROWNUM` | NUMBER | Row number within the source file | | `CREATED_AT` | TIMESTAMP\_NTZ | Timestamp when the record was loaded |
## Row-level lineage Every row in this table traces to the exact CMS source file that produced it. The `FILE_ID` column joins to the `FEEDS_FILES` catalog table, and `FILE_FEED_ID` joins to the `FEEDS` master table: ```mermaid erDiagram FEEDS ||--o{ FEEDS_FILES : "ID = FEED_ID" FEEDS ||--o{ HOSPITAL_PRICE_TRANSPARENCY_ENFORCEMENT_ACTIVITIES_AND_OUTCOMES : "ID = FILE_FEED_ID" FEEDS_FILES ||--o{ HOSPITAL_PRICE_TRANSPARENCY_ENFORCEMENT_ACTIVITIES_AND_OUTCOMES : "ID = FILE_ID" FEEDS { text ID PK text TITLE text VIEW_NAME text ACCURAL_PERIODICITY } FEEDS_FILES { text ID PK text FEED_ID FK date TEMPORAL_START date TEMPORAL_END date CMS_FEED_MODIFIED number IS_LATEST } HOSPITAL_PRICE_TRANSPARENCY_ENFORCEMENT_ACTIVITIES_AND_OUTCOMES { text ROW_ID PK text FILE_ID FK text FILE_FEED_ID FK number CASE_ID text HOSP_NAME text HOSP_ADDRESS text CITY number remaining_7_data_columns } ``` Trace any row back to its source file and reporting period: ```sql SELECT d.CASE_ID, d.HOSP_NAME, d.HOSP_ADDRESS, ff.TEMPORAL_START, ff.TEMPORAL_END, ff.CMS_FEED_MODIFIED FROM DWV.HOSPITAL_PRICE_TRANSPARENCY_ENFORCEMENT_ACTIVITIES_AND_OUTCOMES d JOIN DWV.FEEDS_FILES ff ON d.FILE_ID = ff.ID; ``` ## Source & provenance Published by the **Centers for Medicare & Medicaid Services** (bureau 009:38). * [Official CMS data dictionary](https://data.cms.gov/resources/hospital-price-transparency-enforcement-activities-and-outcomes-data-dictionary-current) * [Hospital Price Transparency Enforcement Activities and Outcomes Methodology](https://data.cms.gov/resources/hospital-price-transparency-enforcement-activities-and-outcomes-methodology) ## Frequently asked questions ### How often is Hospital Price Transparency Enforcement Activities and Outcomes updated? Monthly. CMS last published this feed on 2026-07-14, and Dataplex loaded it to the warehouse on 2026-07-15. New releases are added automatically when CMS publishes them. ### What years does Hospital Price Transparency Enforcement Activities and Outcomes cover? 2023 through 2026. ### How many records are in Hospital Price Transparency Enforcement Activities and Outcomes? 133,171 rows across all 18 reporting periods. Because this feed is time-partitioned, the full table total is the meaningful count — no deduplication needed. ### How do I get Hospital Price Transparency Enforcement Activities and Outcomes data? It's included in the CMS Data Feeds Dataset on the [Snowflake Marketplace](https://app.snowflake.com/marketplace/listing/GZT1Z125KDH/dataplex-consulting-data-products-cms-data-feeds-dataset) (free trial available) and via [Databricks Delta Sharing](https://checkout.dataplex-consulting.com/b/3cIdR2e1J59Sh2w7pWbQY00). Once mounted, query `DWV.HOSPITAL_PRICE_TRANSPARENCY_ENFORCEMENT_ACTIVITIES_AND_OUTCOMES` directly — no pipeline setup required. ## Related feeds {% content-ref url="/pages/GunW3MkiWCFfZuAmepRm" %} [Medicare Post-Acute Care Utilization - Inpatient Rehabilitation Facility by Geography/Provider and Case-Mix Grouping](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/medicare-post-acute-care-utilization-inpatient-rehabilitation-facility-by-geographyprovider-and-case.md) {% endcontent-ref %} {% content-ref url="/pages/ml83e2e6mZ6ku9Bwuf1W" %} [Hospital Service Area](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/hospital-service-area.md) {% endcontent-ref %} {% content-ref url="/pages/Sn2725n4tKoU6XkZLqcw" %} [Medicare Outpatient Hospitals - by Provider and Service](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/medicare-outpatient-hospitals-by-provider-and-service.md) {% endcontent-ref %} {% content-ref url="/pages/MrXKeZnI8w3SkNJ0SBme" %} [Medicare Post-Acute Care Utilization - Inpatient Rehabilitation Facility](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/medicare-post-acute-care-utilization-inpatient-rehabilitation-facility.md) {% endcontent-ref %} {% content-ref url="/pages/w9EmSkF4fT7S7SRm8U4Q" %} [Payroll Based Journal Daily Nurse Staffing](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/payroll-based-journal-daily-nurse-staffing.md) {% endcontent-ref %} ## Get this feed 1. [Start a free trial on Snowflake Marketplace](https://app.snowflake.com/marketplace/listing/GZT1Z125KDH/dataplex-consulting-data-products-cms-data-feeds-dataset) or purchase via [Databricks](https://checkout.dataplex-consulting.com/b/3cIdR2e1J59Sh2w7pWbQY00) 2. Mount the share — the database and `DWV` schema appear in your account immediately 3. Run the [sample query](#sample-queries) above — no ETL, no pipeline maintenance Questions about this feed? Contact us at . *** Part of the [CMS Data Feeds Dataset](/data-catalog/cms-data-feeds-dataset.md) — 280+ feeds · 245B+ records · updated daily. [Back to the full catalog →](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog.md#hospital-price-transparency-enforcement-activities-and-outcomes) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.dataplex-consulting.com/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/hospital-price-transparency-enforcement-activities-and-outcomes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.