> 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/specific-chronic-conditions.md).

# Specific Chronic Conditions

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.SPECIFIC_CHRONIC_CONDITIONS` on Snowflake and Databricks — 12 annual reporting periods (2007–2018) 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.SPECIFIC_CHRONIC_CONDITIONS`                       |
| **Databricks**     | `cms_dwv.specific_chronic_conditions`                   |
| **Coverage**       | Jan 2007 – Dec 2018 (12 of 12 annual reporting periods) |
| **Rows**           | 2,833,488 (total across all reporting periods)          |
| **Cadence**        | Annual                                                  |
| **Update pattern** | Time-partitioned — each file adds one reporting year    |
| **CMS published**  | 2022-01-10                                              |
| **Loaded**         | 2023-08-29                                              |
| **Columns**        | 12 data + 6 lineage                                     |
| **File versions**  | 12                                                      |
| **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 2022-01-10** — awaiting the next release. New files load automatically when CMS publishes.
{% endhint %}

{% hint style="info" %}
**Time-partitioned feed** — each file version covers one reporting year, so history is additive. Query the full table for all years; filter on the reporting period columns for a single period. Do **not** filter to the latest file only — that would return just the 2018 reporting year.
{% endhint %}

## Sample queries

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

```sql
-- Each file version covers one reporting period — history is additive
SELECT *
FROM DWV.SPECIFIC_CHRONIC_CONDITIONS
LIMIT 100;
```

{% endtab %}

{% tab title="Databricks" %}

```sql
-- Each file version covers one reporting period — history is additive
SELECT *
FROM cms_dwv.specific_chronic_conditions
LIMIT 100;
```

{% endtab %}
{% endtabs %}

## About this feed

> The Select Chronic Conditions dataset provides information on 21 selected chronic conditions among Original Medicare beneficiaries. The dataset contains prevalence, use and spending organized by geography and distinct chronic conditions listed below.
>
> • Alcohol Abuse Drug Abuse/ Substance Abuse • Alzheimer’s Disease and Related Dementia • Arthritis (Osteoarthritis and Rheumatoid) • Asthma • Atrial Fibrillation • Autism Spectrum Disorders • Cancer (Breast, Colorectal, Lung, and Prostate) • Chronic Kidney Disease • Chronic Obstructive Pulmonary Disease • Depression • Diabetes • Drug Abuse/ Substance Abuse • Heart Failure • Hepatitis (Chronic Viral B & C) • HIV/AIDS • Hyperlipidemia (High cholesterol) • Hypertension (High blood pressure) • Ischemic Heart Disease • Osteoporosis • Schizophrenia and Other Psychotic Disorders • Stroke
>
> — *Source: CMS feed metadata*

**Keywords:** National, States & Territories, Counties, Medicare, Original Medicare, Chronic Conditions, Health Care Use & Payments, Health Equity **Theme:** Medicare

## Coverage timeline

2007–2018 🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩 (🟩 covered · ⬜ no data)

12 of 12 annual reporting periods present — no gaps.

## Release history

| Reporting period        | CMS published | Loaded     | Latest file |
| ----------------------- | ------------- | ---------- | ----------- |
| 2018-01-01 – 2018-12-31 | 2022-01-10    | 2023-08-29 | ✓           |
| 2017-01-01 – 2017-12-31 | 2022-01-04    | 2023-08-29 |             |
| 2016-01-01 – 2016-12-31 | 2020-11-06    | 2023-08-29 |             |
| 2015-01-01 – 2015-12-31 | 2020-11-06    | 2023-08-29 |             |
| 2014-01-01 – 2014-12-31 | 2020-11-06    | 2023-08-29 |             |
| 2013-01-01 – 2013-12-31 | 2020-11-06    | 2023-08-29 |             |
| 2012-01-01 – 2012-12-31 | 2020-11-06    | 2023-08-29 |             |
| 2011-01-01 – 2011-12-31 | 2020-11-06    | 2023-08-29 |             |
| 2010-01-01 – 2010-12-31 | 2020-11-06    | 2023-08-29 |             |
| 2009-01-01 – 2009-12-31 | 2020-11-06    | 2023-08-29 |             |

<details>

<summary>Show 2 earlier file versions</summary>

| Reporting period        | CMS published | Loaded     | Latest file |
| ----------------------- | ------------- | ---------- | ----------- |
| 2008-01-01 – 2008-12-31 | 2020-11-06    | 2023-08-29 |             |
| 2007-01-01 – 2007-12-31 | 2020-11-06    | 2023-08-29 |             |

</details>

## Data dictionary

<details>

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

Column-level definitions are maintained by CMS in the official [Specific Chronic Conditions data dictionary](https://data.cms.gov/resources/specific-chronic-conditions-data-dictionary).

**Data columns**

| Column                     | Type   |
| -------------------------- | ------ |
| `BENE_GEO_LVL`             | TEXT   |
| `BENE_GEO_DESC`            | TEXT   |
| `BENE_GEO_CD`              | NUMBER |
| `BENE_AGE_LVL`             | TEXT   |
| `BENE_DEMO_LVL`            | TEXT   |
| `BENE_DEMO_DESC`           | TEXT   |
| `BENE_COND`                | TEXT   |
| `PRVLNC`                   | NUMBER |
| `TOT_MDCR_STDZD_PYMT_PC`   | NUMBER |
| `TOT_MDCR_PYMT_PC`         | NUMBER |
| `HOSP_READMSN_RATE`        | NUMBER |
| `ER_VISITS_PER_1000_BENES` | NUMBER |

**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{ SPECIFIC_CHRONIC_CONDITIONS : "ID = FILE_FEED_ID"
    FEEDS_FILES ||--o{ SPECIFIC_CHRONIC_CONDITIONS : "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
    }
    SPECIFIC_CHRONIC_CONDITIONS {
        text ROW_ID PK
        text FILE_ID FK
        text FILE_FEED_ID FK
        text BENE_GEO_LVL
        text BENE_GEO_DESC
        number BENE_GEO_CD
        text BENE_AGE_LVL
        number remaining_8_data_columns
    }
```

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

```sql
SELECT d.BENE_GEO_LVL, d.BENE_GEO_DESC, d.BENE_GEO_CD,
       ff.TEMPORAL_START, ff.TEMPORAL_END, ff.CMS_FEED_MODIFIED
FROM DWV.SPECIFIC_CHRONIC_CONDITIONS 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/specific-chronic-conditions-data-dictionary)
* [Medicare Chronic Conditions Methodology](https://data.cms.gov/resources/medicare-chronic-conditions-methodology)

## Frequently asked questions

### How often is Specific Chronic Conditions updated?

Annually. CMS last published this feed on 2022-01-10, and Dataplex loaded it to the warehouse on 2023-08-29. New releases are added automatically when CMS publishes them.

### What years does Specific Chronic Conditions cover?

2007 through 2018 — 12 annual reporting periods with no gaps. Each reporting year arrives as its own file version, and all years remain queryable side by side.

### How many records are in Specific Chronic Conditions?

2,833,488 rows across all 12 reporting periods. Because this feed is time-partitioned, the full table total is the meaningful count — no deduplication needed.

### How do I get Specific Chronic Conditions 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.SPECIFIC_CHRONIC_CONDITIONS` directly — no pipeline setup required.

## Related feeds

{% content-ref url="/pages/Uyp5dZjGoIrc5ypyJYQ9" %}
[Multiple Chronic Conditions](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/multiple-chronic-conditions.md)
{% endcontent-ref %}

{% content-ref url="/pages/5H1w0p0jmbbBcj2z19zh" %}
[Medicare Geographic Variation - by National, State & County](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/medicare-geographic-variation-by-national-state-county.md)
{% endcontent-ref %}

{% content-ref url="/pages/dZ5a1Et93c7pLvaH9tnH" %}
[Medicare Post-Acute Care & Hospice - by Geography and Provider](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/medicare-post-acute-care-hospice-by-geography-and-provider.md)
{% endcontent-ref %}

{% content-ref url="/pages/vSHuyZ1yd8hv11QUlJFL" %}
[Medicare Post-Acute Care and Hospice - by Geography & Provider](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/medicare-post-acute-care-and-hospice-by-geography-provider.md)
{% endcontent-ref %}

{% content-ref url="/pages/uxn7MKni7n1pinf1CT6a" %}
[Medicare Monthly Enrollment](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/medicare-monthly-enrollment.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#specific-chronic-conditions)


---

# 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/specific-chronic-conditions.md?ask=<question>&goal=<endgoal>
```

`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.
