> 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/cdc-open-data-product/cdc-chronic-disease-indicators.md).

# Chronic Disease Indicators

Chronic Disease Indicators datasets in the CDC Open Data Catalog

This page contains all datasets in the **Chronic Disease Indicators** category of the CDC Open Data Catalog.

**Total Datasets in Category**: 2 **Last Updated**: 11/21/2026

#### U.S. Chronic Disease Indicators

* **Description**: CDC's Division of Population Health provides a cross-cutting set of 115 indicators developed by consensus among CDC, the Council of State and Territorial Epidemiologists, and the National Association of Chronic Disease Directors. These indicators allow states and territories to uniformly define, collect, and report chronic disease data that are important to public health practice in their area. In addition to providing access to state-specific indicator data, the CDI web site serves as a gateway to additional information and data resources.
* **Snowflake Schema**: dwv\_cdc\_chronic\_disease
* **Databricks Schema**: cdc\_dwv\_cdc\_chronic\_disease
* **Table Name**: us\_chronic\_disease\_indicators\_\_hksd\_2xuw
* **Dataset ID**: hksd-2xuw
* **Category**: Chronic Disease Indicators
* **Total Rows**: 1,505,594
* **Last Refresh**: 9/26/2026
* **Total Batches**: 4
* **Tags**: asthma, cancer, tobacco, copd, alcohol, arthritis, diabetes
* **Source Data**: <https://data.cdc.gov/d/hksd-2xuw>

#### U.S. Chronic Disease Indicators (CDI), 2023 Release

* **Description**: This dataset is based on indicators described in MMWR "Indicators for Chronic Disease Surveillance — United States, 2013" (<https://www.cdc.gov/mmwr/preview/mmwrhtml/rr6401a1.htm>) before 2024 CDI refresh. It provided cross-cutting set of 124 indicators that were developed by consensus and that allows states and territories to uniformly define, collect, and report chronic disease data that are important to public health practice and available for states, and territories. In addition to providing access to state-specific indicator data, the CDI web site ([www.cdc.gov/cdi](http://www.cdc.gov/cdi)) provides current release and additional information and data resources.
* **Snowflake Schema**: dwv\_cdc\_chronic\_disease
* **Databricks Schema**: cdc\_dwv\_cdc\_chronic\_disease
* **Table Name**: us\_cdi\_indicators\_2023\_his\_identifier\_i\_\_g4ie\_h725
* **Dataset ID**: g4ie-h725
* **Category**: Chronic Disease Indicators
* **Total Rows**: 2,371,352
* **Last Refresh**: 7/12/2025
* **Total Batches**: 2
* **Tags**: cdi, chronic disease indicators, alcohol, arthritis, asthma
* **Source Data**: <https://data.cdc.gov/Chronic-Disease-Indicators/U-S-Chronic-Disease-Indicators-CDI-2023-Release/g4ie-h725>


---

# 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/cdc-open-data-product/cdc-chronic-disease-indicators.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.
