> 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/hospice-zip-data.md).

# Hospice - Zip Data

ZIP codes where each hospice provides services.

Part of the [CMS Data Feeds Dataset](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog.md) › Hospice care

Dataplex delivers this CMS feed as the analysis-ready table `DWV.HOSPICE_ZIP_DATA` on Snowflake and Databricks: two snapshot releases spanning 2026–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.HOSPICE_ZIP_DATA`                              |
| **Databricks**     | `cms_dwv.hospice_zip_data`                          |
| **Cadence**        | Monthly                                             |
| **Update pattern** | Full-refresh; each file replaces the prior snapshot |
| **CMS published**  | 2026-08-01                                          |
| **Loaded**         | 2026-09-28                                          |
| **Columns**        | 4 data + 6 lineage                                  |
| **Identifiers**    | CCN · ZIP codes                                     |
| **File versions**  | 2                                                   |
| **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 2026-08-01**: awaiting the next release. New files load automatically when CMS publishes.
{% 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.HOSPICE_ZIP_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.hospice_zip_data
WHERE file_id IN (
  SELECT id FROM cms_dwv.feeds_files WHERE is_latest = 1
)
LIMIT 100;
```

{% endtab %}
{% endtabs %}

## About this feed

> ZIP codes where each hospice provides services.
>
> *Source: CMS feed metadata*

**Keywords:** hospice, zip codes, service area, location, quality reporting program **Theme:** Hospice care

## Coverage timeline

2026 🟩

1 of 1 years with snapshot releases, no gaps.

## Release history

| Reporting period          | CMS published | Loaded     | Latest file |
| ------------------------- | ------------- | ---------- | ----------- |
| Snapshot as of 2026-08-01 | 2026-08-01    | 2026-09-28 | ✓           |
| Snapshot as of 2026-08-01 | 2026-08-01    | 2026-09-22 |             |

## Data dictionary

<details>

<summary>📋 <strong>4 data columns + 6 lineage columns</strong></summary>

**Data columns**

| Column                         | Type | Description                                                                                |
| ------------------------------ | ---- | ------------------------------------------------------------------------------------------ |
| `DATA_PERIOD`                  | TEXT | Data snapshot period from BATCH\_LOG (for this feed, derived from the CMS source filename) |
| `STATE`                        | TEXT | Two-letter state abbreviation associated with the hospice provider                         |
| `CMS_CERTIFICATION_NUMBER_CCN` | TEXT | CMS Certification Number (CCN) for the hospice provider                                    |
| `ZIP_CODE`                     | TEXT | ZIP code where the hospice provides services                                               |

**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        |

</details>

## 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{ HOSPICE_ZIP_DATA : "ID = FILE_FEED_ID"
    FEEDS_FILES ||--o{ HOSPICE_ZIP_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
    }
    HOSPICE_ZIP_DATA {
        text ROW_ID PK
        text FILE_ID FK
        text FILE_FEED_ID FK
        text DATA_PERIOD
        text STATE
        text CMS_CERTIFICATION_NUMBER_CCN
        text ZIP_CODE
    }
```

Trace any row back to its source file and reporting period:

{% tabs %}
{% tab title="Snowflake" %}

```sql
SELECT d.DATA_PERIOD, d.STATE, d.CMS_CERTIFICATION_NUMBER_CCN,
       ff.TEMPORAL_START, ff.TEMPORAL_END, ff.CMS_FEED_MODIFIED
FROM DWV.HOSPICE_ZIP_DATA d
JOIN DWV.FEEDS_FILES ff ON d.FILE_ID = ff.ID;
```

{% endtab %}

{% tab title="Databricks" %}

```sql
SELECT d.data_period, d.state, d.cms_certification_number_ccn,
       ff.temporal_start, ff.temporal_end, ff.cms_feed_modified
FROM cms_dwv.hospice_zip_data d
JOIN cms_dwv.feeds_files ff ON d.file_id = ff.id;
```

{% endtab %}
{% endtabs %}

## Source & provenance

Published by the **Centers for Medicare & Medicaid Services** (bureau 009:38).

* [Official CMS documentation](https://data.cms.gov/provider-data/topics/hospice-care)
* [95rg 2usp](https://data.cms.gov/provider-data/dataset/95rg-2usp)

## Frequently asked questions

### How often is Hospice - Zip Data updated?

Monthly. CMS last published this feed on 2026-08-01, and Dataplex loaded it to the warehouse on 2026-09-28. New releases are added automatically when CMS publishes them.

### What years does Hospice - Zip Data cover?

2026 through 2026.

### How many records are in Hospice - Zip Data?

Count the current snapshot yourself once the share is mounted:

{% tabs %}
{% tab title="Snowflake" %}

```sql
SELECT COUNT(*)
FROM DWV.HOSPICE_ZIP_DATA d
JOIN DWV.FEEDS_FILES ff ON d.FILE_ID = ff.ID
WHERE ff.IS_LATEST = 1;
```

{% endtab %}

{% tab title="Databricks" %}

```sql
SELECT COUNT(*)
FROM cms_dwv.hospice_zip_data d
JOIN cms_dwv.feeds_files ff ON d.file_id = ff.id
WHERE ff.is_latest = 1;
```

{% endtab %}
{% endtabs %}

### How do I get Hospice - Zip 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.HOSPICE_ZIP_DATA` directly; no pipeline setup required.

## Related feeds

{% content-ref url="/pages/3mQaYtsNjEf56QH9Uj0M" %}
[Home Health Care - Zip Codes](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/home-health-care-zip-codes.md)
{% endcontent-ref %}

{% content-ref url="/pages/tU6uuheRUajExC8lzQbp" %}
[Hospice - Provider Data](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/hospice-provider-data.md)
{% endcontent-ref %}

{% content-ref url="/pages/mH5nUMTkoDqU6pNDObMf" %}
[Hospice care - Provider CAHPS Hospice Survey Data](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/hospice-care-provider-cahps-hospice-survey-data.md)
{% endcontent-ref %}

{% content-ref url="/pages/lyly4dcGlvcIiSnnA3HN" %}
[Hospice - General Information](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/hospice-general-information.md)
{% endcontent-ref %}

{% content-ref url="/pages/0mIYEFdRCLFUa4U60LNc" %}
[ESRD QIP - Facility Commitment to Health Equity - Payment Year 2026](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/esrd-qip-facility-commitment-to-health-equity-payment-year-2026.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 <notifications@dataplex-consulting.com>.

***

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#hospice-zip-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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dataplex-consulting.com/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/hospice-zip-data.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
