> 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-injury-and-violence.md).

# Injury and Violence

Injury & Violence datasets in the CDC Open Data Catalog

This page contains all datasets in the **Injury & Violence** category of the CDC Open Data Catalog.

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

#### Mapping Injury, Overdose, and Violence - Census Tract

* **Description**: This file contains death counts and death rates for drug overdose, suicide, homicide and firearm injuries by census tract of residence (additional datasets exist for other levels of geography). The data is grouped by 2 different time periods including yearly and trailing twelve months. Please see data dictionary for intents and mechanisms included in each measure.

When there are 1-9 deaths in an area, CDC uses a Bayesian model to calculate rates. A Bayesian model is a type of statistical model often used in geographic analysis. This model can improve stability of the rates in lower population areas and protects privacy by taking into account information from neighboring areas.

* **Snowflake Schema**: dwv\_unsaferesponsefilter
* **Databricks Schema**: cdc\_dwv\_unsaferesponsefilter
* **Table Name**: mapping\_injury\_overdose\_violence\_census\_\_4day\_mt2f
* **Dataset ID**: 4day-mt2f
* **Category**: Injury & Violence
* **Total Rows**: 8,511,040
* **Last Refresh**: 11/6/2026
* **Total Batches**: 20
* **Tags**: drug overdose, deaths, firearm injury, homicide, mortality, nchs, suicide
* **Source Data**: <https://data.cdc.gov/d/4day-mt2f>

#### Mapping Injury, Overdose, and Violence - County

* **Description**: This file contains death counts and death rates for drug overdose, suicide, homicide and firearm injuries by county of residence (additional datasets exist for other levels of geography). The data is grouped by 2 different time periods including yearly and trailing twelve months. Please see data dictionary for intents and mechanisms included in each measure.

When there are 1-9 deaths in an area, CDC uses a Bayesian model to calculate rates. A Bayesian model is a type of statistical model often used in geographic analysis. This model can improve stability of the rates in lower population areas and protects privacy by taking into account information from neighboring areas.

* **Snowflake Schema**: dwv\_unsaferesponsefilter
* **Databricks Schema**: cdc\_dwv\_unsaferesponsefilter
* **Table Name**: mapping\_injury\_overdose\_violence\_county\_\_psx4\_wq38
* **Dataset ID**: psx4-wq38
* **Category**: Injury & Violence
* **Total Rows**: 2,451,096
* **Last Refresh**: 11/6/2026
* **Total Batches**: 19
* **Tags**: suicide, firearm injury, homicide, mortality, deaths, nchs, drug overdose
* **Source Data**: <https://data.cdc.gov/d/psx4-wq38>

#### Mapping Injury, Overdose, and Violence - National

* **Description**: This file contains death counts and death rates for drug overdose, suicide, homicide and firearm injuries at the United States national level (additional datasets exist for other levels of geography). The data is grouped by 3 different time periods including monthly, yearly, and trailing twelve months. Please see data dictionary for intents and mechanisms included in each measure.
* **Snowflake Schema**: dwv\_unsaferesponsefilter
* **Databricks Schema**: cdc\_dwv\_unsaferesponsefilter
* **Table Name**: mapping\_injury\_overdose\_violence\_nation\_\_t6u2\_f84c
* **Dataset ID**: t6u2-f84c
* **Category**: Injury & Violence
* **Total Rows**: 11,715
* **Last Refresh**: 11/6/2026
* **Total Batches**: 22
* **Tags**: firearm injury, suicide, nchs, mortality, homicide, drug overdose, deaths
* **Source Data**: <https://data.cdc.gov/d/t6u2-f84c>

#### Mapping Injury, Overdose, and Violence - State

* **Description**: This file contains death counts and death rates for drug overdose, suicide, homicide and firearm injuries by state of residence (additional datasets exist for other levels of geography). The data is grouped by 2 different time periods including yearly and trailing twelve months. Please see data dictionary for intents and mechanisms included in each measure.
* **Snowflake Schema**: dwv\_unsaferesponsefilter
* **Databricks Schema**: cdc\_dwv\_unsaferesponsefilter
* **Table Name**: mapping\_injury\_overdose\_violence\_state\_\_fpsi\_y8tj
* **Dataset ID**: fpsi-y8tj
* **Category**: Injury & Violence
* **Total Rows**: 43,452
* **Last Refresh**: 11/6/2026
* **Total Batches**: 21
* **Tags**: mortality, suicide, nchs, deaths, drug overdose, firearm injury, homicide
* **Source Data**: <https://data.cdc.gov/d/fpsi-y8tj>


---

# 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-injury-and-violence.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.
