> 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/historical-hospital-patient-safety-indicators-psi-dataset.md). # Historical Hospital Patient Safety Indicators (PSI) Dataset 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_PATIENT_SAFETY_INDICATORS_PSI_DATASET` on Snowflake and Databricks — coverage from 2017 to 2019 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_PATIENT_SAFETY_INDICATORS_PSI_DATASET` | | **Databricks** | `cms_dwv.hospital_patient_safety_indicators_psi_dataset` | | **Coverage** | Oct 2017 – Sep 2019 | | **Rows** | 8,174 (total across all reporting periods) | | **Update pattern** | Time-partitioned — each file adds one reporting period | | **CMS published** | 2019-09-23 | | **Loaded** | 2025-05-18 | | **Columns** | 21 data + 6 lineage | | **Identifiers** | ZIP codes | | **File versions** | 5 | | **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="info" %} **Last CMS publication 2019-09-23** — awaiting the next release. New files load automatically when CMS publishes. {% 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 2019 reporting period. {% endhint %} ## Sample queries {% tabs %} {% tab title="Snowflake" %} ```sql -- Each file version covers one reporting period (2017, 2018, 2019) — history is additive SELECT * FROM DWV.HOSPITAL_PATIENT_SAFETY_INDICATORS_PSI_DATASET LIMIT 100; ``` {% endtab %} {% tab title="Databricks" %} ```sql -- Each file version covers one reporting period (2017, 2018, 2019) — history is additive SELECT * FROM cms_dwv.hospital_patient_safety_indicators_psi_dataset LIMIT 100; ``` {% endtab %} {% endtabs %} ## About this feed > The CMS Historical Hospital Patient Safety Indicators (PSI) Dataset contains hospital-level data on Patient Safety Indicators. > > — *Source: CMS feed metadata* **Keywords:** Medicare, Historical Hospital Patient Safety Indicators (PSI) Dataset **Theme:** Medicare ## Coverage timeline 2017 🟩 · 2018 🟩 · 2019 🟩 3 of 3 years covered — no gaps. ## Release history | Reporting period | CMS published | Loaded | Latest file | | ----------------------- | ------------- | ---------- | ----------- | | 2019-09-23 – 2019-09-23 | 2019-09-23 | 2025-05-18 | ✓ | | 2018-09-21 – 2018-09-21 | 2018-09-21 | 2025-05-18 | | | 2018-07-10 – 2018-07-10 | 2018-07-10 | 2025-05-18 | | | 2018-02-06 – 2018-02-06 | 2018-02-06 | 2025-05-18 | | | 2017-10-16 – 2017-10-16 | 2017-10-16 | 2025-05-18 | | ## Data dictionary
📋 21 data columns + 6 lineage columns Column-level definitions are maintained by CMS in the official [Historical Hospital Patient Safety Indicators (PSI) Dataset data dictionary](https://data.cms.gov/provider-data/dataset/muwa-iene). **Data columns** | Column | Type | | ------------------------- | ------ | | `FACILITY_ID` | TEXT | | `FACILITY_NAME` | TEXT | | `ADDRESS` | TEXT | | `CITY` | TEXT | | `STATE` | TEXT | | `ZIP_CODE` | NUMBER | | `COUNTY_NAME` | TEXT | | `MEASURE_ID` | TEXT | | `MEASURE_NAME` | TEXT | | `DENOMINATOR` | TEXT | | `OBSERVED_RATE_PER_1_000` | TEXT | | `FOOTNOTE` | TEXT | | `START_DATE` | DATE | | `END_DATE` | DATE | | `PHONE_NUMBER` | TEXT | | `PROVIDER_ID` | TEXT | | `HOSPITAL_NAME` | TEXT | | `NUMERATOR` | TEXT | | `FOOTNOTES` | TEXT | | `MEASURE_START_DATE` | DATE | | `MEASURE_END_DATE` | 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_PATIENT_SAFETY_INDICATORS_PSI_DATASET : "ID = FILE_FEED_ID" FEEDS_FILES ||--o{ HOSPITAL_PATIENT_SAFETY_INDICATORS_PSI_DATASET : "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_PATIENT_SAFETY_INDICATORS_PSI_DATASET { text ROW_ID PK text FILE_ID FK text FILE_FEED_ID FK text FACILITY_ID text FACILITY_NAME text ADDRESS text CITY number remaining_17_data_columns } ``` Trace any row back to its source file and reporting period: ```sql SELECT d.FACILITY_ID, d.FACILITY_NAME, d.ADDRESS, ff.TEMPORAL_START, ff.TEMPORAL_END, ff.CMS_FEED_MODIFIED FROM DWV.HOSPITAL_PATIENT_SAFETY_INDICATORS_PSI_DATASET d JOIN DWV.FEEDS_FILES ff ON d.FILE_ID = ff.ID; ``` ## Source & provenance Published by the **Centers for Medicare & Medicaid Services**. * [Official CMS documentation](https://data.cms.gov/provider-data/dataset/muwa-iene) ## Frequently asked questions ### How often is Historical Hospital Patient Safety Indicators (PSI) Dataset updated? CMS last published this feed on 2019-09-23. New releases are added automatically when CMS publishes them. ### What years does Historical Hospital Patient Safety Indicators (PSI) Dataset cover? 2017 through 2019. ### How many records are in Historical Hospital Patient Safety Indicators (PSI) Dataset? 8,174 rows across all five reporting periods. Because this feed is time-partitioned, the full table total is the meaningful count — no deduplication needed. ### How do I get Historical Hospital Patient Safety Indicators (PSI) Dataset 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_PATIENT_SAFETY_INDICATORS_PSI_DATASET` directly — no pipeline setup required. ## Related feeds {% content-ref url="/pages/Fqi17V590OnuhVu78h3s" %} [Footnote Crosswalk](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/footnote-crosswalk.md) {% endcontent-ref %} {% content-ref url="/pages/nNLU9KV057ffzs4qUMzQ" %} [Managing Clinician Aggregation Group Performance](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/managing-clinician-aggregation-group-performance.md) {% endcontent-ref %} {% content-ref url="/pages/FhR8aogG6dJfeEgYz4G7" %} [Innovation Center Innovation Advisors](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/innovation-center-innovation-advisors.md) {% endcontent-ref %} {% content-ref url="/pages/1heDaPDcdcUpXgdsKYXJ" %} [Timely and Effective Care - Hospital](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/timely-and-effective-care-hospital.md) {% endcontent-ref %} {% content-ref url="/pages/QalzllRReOcJ5hwmltA2" %} [Healthcare Associated Infections - State](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/healthcare-associated-infections-state.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#historical-hospital-patient-safety-indicators-psi-dataset) --- # 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/historical-hospital-patient-safety-indicators-psi-dataset.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.