> 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/comprehensive-care-for-joint-replacement-model-provider-data.md). # Comprehensive Care For Joint Replacement Model - Provider Data 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.COMPREHENSIVE_CARE_FOR_JOINT_REPLACEMENT_MODEL__PROVIDER_DATA` on Snowflake and Databricks — three snapshot releases spanning 2024–2026, aligned to a single 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.COMPREHENSIVE_CARE_FOR_JOINT_REPLACEMENT_MODEL__PROVIDER_DATA` | | **Databricks** | `cms_dwv.comprehensive_care_for_joint_replacement_model__provider_data` | | **Update pattern** | Full-refresh — each file replaces the prior snapshot | | **CMS published** | 2026-01-26 | | **Loaded** | 2026-02-28 | | **Columns** | 18 data + 6 lineage | | **File versions** | 3 | | **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-01-26. Coverage runs through 2026-01-26. Next CMS release expected \~Feb 2027. {% endhint %} {% hint style="info" %} **Full-refresh feed** — each file version is a complete snapshot and newer files supersede older ones. Filter to the latest file (see the sample query) to avoid double-counting across versions. {% endhint %} ## Sample queries {% tabs %} {% tab title="Snowflake" %} ```sql -- Latest snapshot only (avoids double-counting across file versions) SELECT * FROM DWV.COMPREHENSIVE_CARE_FOR_JOINT_REPLACEMENT_MODEL__PROVIDER_DATA WHERE FILE_ID IN ( SELECT ID FROM DWV.FEEDS_FILES WHERE IS_LATEST = 1 ) LIMIT 100; ``` {% endtab %} {% tab title="Databricks" %} ```sql -- Latest snapshot only (avoids double-counting across file versions) SELECT * FROM cms_dwv.comprehensive_care_for_joint_replacement_model__provider_data WHERE file_id IN ( SELECT id FROM cms_dwv.feeds_files WHERE is_latest = 1 ) LIMIT 100; ``` {% endtab %} {% endtabs %} ## About this feed > Comprehensive Care for Joint Replacement Model - provider data. This data set includes provider data for two quality measures tracked during an episode of care: complication rate for hip/knee replacement patients and the Hospital Consumer Assessment of Healthcare Providers and Systems (HCAHPS) Survey. > > — *Source: CMS feed metadata* **Keywords:** Medicare, Comprehensive Care For Joint Replacement Model - Provider Data **Theme:** Medicare ## Coverage timeline 2024 🟩 · 2025 🟩 · 2026 🟩 3 of 3 years with snapshot releases — no gaps. ## Release history | Reporting period | CMS published | Loaded | Latest file | | ------------------------- | ------------- | ---------- | ----------- | | Snapshot as of 2026-01-26 | 2026-01-26 | 2026-02-28 | ✓ | | Snapshot as of 2025-01-08 | 2025-01-08 | 2025-02-27 | | | Snapshot as of 2024-01-08 | 2024-01-08 | 2024-12-14 | | ## Data dictionary
📋 18 data columns + 6 lineage columns Column-level definitions are maintained by CMS in the official [Comprehensive Care For Joint Replacement Model - Provider Data data dictionary](https://data.cms.gov/provider-data/dataset/tqkv-mgxq). **Data columns** | Column | Type | | -------------------------- | ------- | | `FACILITY_ID` | NUMBER | | `FACILITY_NAME` | TEXT | | `MSA` | NUMBER | | `MSA_TITLE` | TEXT | | `HCAHPS_HLMR` | TEXT | | `HCAHPS_HLMR_PERCENTILE` | TEXT | | `HCAHPS_START_DATE` | DATE | | `HCAHPS_END_DATE` | DATE | | `HCAHPS_FOOTNOTE` | TEXT | | `COMP_HIP_KNEE` | TEXT | | `COMP_HIP_KNEE_PERCENTILE` | TEXT | | `COMP_START_DATE` | DATE | | `COMP_END_DATE` | DATE | | `COMP_FOOTNOTE` | NUMBER | | `PRO` | BOOLEAN | | `PRO_START_DATE` | DATE | | `PRO_END_DATE` | DATE | | `RECONCILIATION_FOOTNOTE` | TEXT | **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{ COMPREHENSIVE_CARE_FOR_JOINT_REPLACEMENT_MODEL__PROVIDER_DATA : "ID = FILE_FEED_ID" FEEDS_FILES ||--o{ COMPREHENSIVE_CARE_FOR_JOINT_REPLACEMENT_MODEL__PROVIDER_DATA : "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 } COMPREHENSIVE_CARE_FOR_JOINT_REPLACEMENT_MODEL__PROVIDER_DATA { text ROW_ID PK text FILE_ID FK text FILE_FEED_ID FK number FACILITY_ID text FACILITY_NAME number MSA text MSA_TITLE number remaining_14_data_columns } ``` Trace any row back to its source file and reporting period: ```sql SELECT d.FACILITY_ID, d.FACILITY_NAME, d.MSA, ff.TEMPORAL_START, ff.TEMPORAL_END, ff.CMS_FEED_MODIFIED FROM DWV.COMPREHENSIVE_CARE_FOR_JOINT_REPLACEMENT_MODEL__PROVIDER_DATA 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/tqkv-mgxq) ## Frequently asked questions ### How often is Comprehensive Care For Joint Replacement Model - Provider Data updated? CMS last published this feed on 2026-01-26. New releases are added automatically when CMS publishes them. ### What years does Comprehensive Care For Joint Replacement Model - Provider Data cover? 2024 through 2026. ### How many records are in Comprehensive Care For Joint Replacement Model - Provider Data? Count the current snapshot yourself once the share is mounted: ```sql SELECT COUNT(*) FROM DWV.COMPREHENSIVE_CARE_FOR_JOINT_REPLACEMENT_MODEL__PROVIDER_DATA d JOIN DWV.FEEDS_FILES ff ON d.FILE_ID = ff.ID WHERE ff.IS_LATEST = 1; ``` ### How do I get Comprehensive Care For Joint Replacement Model - Provider Data 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.COMPREHENSIVE_CARE_FOR_JOINT_REPLACEMENT_MODEL__PROVIDER_DATA` directly — no pipeline setup required. ## Related feeds {% content-ref url="/pages/kLqJ5Dc19BigNA5ii0Iv" %} [Home Health Agency Cost Report](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/home-health-agency-cost-report.md) {% endcontent-ref %} {% content-ref url="/pages/J7IhjRAk8B6WfWcKv6kr" %} [CMS Program Statistics - Medicare SNF Utilization by Facility Type and Bedsize](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/cms-program-statistics-medicare-snf-utilization-by-facility-type-and-bedsize.md) {% endcontent-ref %} {% content-ref url="/pages/uVH3qjISV5hQe3xhzVKS" %} [Comprehensive End-Stage Renal Disease Care Model Data](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/comprehensive-end-stage-renal-disease-care-model-data.md) {% endcontent-ref %} {% content-ref url="/pages/r1CLuBN7OqupzdFdosia" %} [Hospital Change of Ownership](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/hospital-change-of-ownership.md) {% endcontent-ref %} {% content-ref url="" %} {% 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#comprehensive-care-for-joint-replacement-model-provider-data) --- # 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/comprehensive-care-for-joint-replacement-model-provider-data.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.