> 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/medicaid-managed-care.md). # Medicaid Managed Care Part of the [CMS Data Feeds Dataset](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog.md) › Medicaid Dataplex delivers this CMS feed as the analysis-ready table `DWV.MEDICAID_MANAGED_CARE` on Snowflake and Databricks — coverage from 2023 to 2025 in a single aligned 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.MEDICAID_MANAGED_CARE` | | **Databricks** | `cms_dwv.medicaid_managed_care` | | **Coverage** | Oct 2023 – Mar 2025 | | **Rows** | 62,027 (total across all reporting periods) | | **Cadence** | Quarterly | | **Update pattern** | Time-partitioned — each file adds one reporting period | | **CMS published** | 2025-06-13 | | **Loaded** | 2025-06-13 | | **Columns** | 13 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="info" %} **Last CMS publication 2025-06-13** — awaiting the next release. New files load automatically when CMS publishes. {% endhint %} {% hint style="info" %} **Time-partitioned feed** — each file version covers one reporting period, so history is additive. Query the full table for all periods; filter on the reporting period columns for a single period. Do **not** filter to the latest file only — that would return just the 2025 reporting period. {% endhint %} ## Sample queries {% tabs %} {% tab title="Snowflake" %} ```sql -- Each file version covers one reporting period (2023, 2024, 2025) — history is additive SELECT * FROM DWV.MEDICAID_MANAGED_CARE LIMIT 100; ``` {% endtab %} {% tab title="Databricks" %} ```sql -- Each file version covers one reporting period (2023, 2024, 2025) — history is additive SELECT * FROM cms_dwv.medicaid_managed_care LIMIT 100; ``` {% endtab %} {% endtabs %} ## About this feed > The Medicaid Managed Care dataset uses CMS' state Transformed Medicaid Statistical Information System (T-MSIS) data for Arizona, Michigan, Nevada, and New Mexico to identify various metrics for managed care plans within each state. These metrics are designed to allow users to compare plans in each state across different specialty areas (currently Pediatric Dental, Behavioral Health, and Prenatal OB/GYN). This dataset does not include all available data in T-MSIS but utilized a subset to calculate the individual metrics identified. > > — *Source: CMS feed metadata* **Keywords:** States & Territories, Counties, Medicaid, Health Care Use & Payments, Health Equity **Theme:** Medicaid ## Coverage timeline 2023 🟩 · 2024 🟩 · 2025 🟩 3 of 3 years covered — no gaps. ## Release history | Reporting period | CMS published | Loaded | Latest file | | ----------------------- | ------------- | ---------- | ----------- | | 2025-01-01 – 2025-03-31 | 2025-06-13 | 2025-06-13 | ✓ | | 2024-10-01 – 2024-12-31 | 2025-05-21 | 2025-05-21 | | | 2023-10-01 – 2023-12-31 | 2024-12-13 | 2024-12-13 | | ## Data dictionary
📋 13 data columns + 6 lineage columns Column-level definitions are maintained by CMS in the official [Medicaid Managed Care data dictionary](https://data.cms.gov/resources/medicaid-managed-care-data-dictionary). **Data columns** | Column | Type | | ------------------------------------------------- | ------ | | `__STATE` | TEXT | | `COUNTY` | TEXT | | `MCO_NAME` | TEXT | | `SERVICE_CATEGORY` | TEXT | | `NUMBER_OF_ACTIVE_PATIENTS` | TEXT | | `NUMBER_OF_ELIGIBLE_MCO_PATIENTS` | TEXT | | `NUMBER_OF_PROVIDERS` | NUMBER | | `PERCENT_OF_ELIGIBLE_PATIENTS_RECEIVING_SERVICES` | NUMBER | | `NUMBER_OF_SERVICES_PER_ACTIVE_PATIENT` | NUMBER | | `NUMBER_OF_ACTIVE_PATIENTS_PER_PROVIDER` | TEXT | | `CALENDAR_YEAR` | NUMBER | | `PLAN_CATEGORY` | TEXT | | `STATE` | 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{ MEDICAID_MANAGED_CARE : "ID = FILE_FEED_ID" FEEDS_FILES ||--o{ MEDICAID_MANAGED_CARE : "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 } MEDICAID_MANAGED_CARE { text ROW_ID PK text FILE_ID FK text FILE_FEED_ID FK text __STATE text COUNTY text MCO_NAME text SERVICE_CATEGORY number remaining_9_data_columns } ``` Trace any row back to its source file and reporting period: ```sql SELECT d.__STATE, d.COUNTY, d.MCO_NAME, ff.TEMPORAL_START, ff.TEMPORAL_END, ff.CMS_FEED_MODIFIED FROM DWV.MEDICAID_MANAGED_CARE 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/medicaid-managed-care-data-dictionary) * [Medicaid Managed Care Methodology](https://data.cms.gov/resources/medicaid-managed-care-methodology) ## Frequently asked questions ### How often is Medicaid Managed Care updated? Quarterly. CMS last published this feed on 2025-06-13, and Dataplex loaded it to the warehouse the same day. New releases are added automatically when CMS publishes them. ### What years does Medicaid Managed Care cover? 2023 through 2025. ### How many records are in Medicaid Managed Care? 62,027 rows across all three reporting periods. Because this feed is time-partitioned, the full table total is the meaningful count — no deduplication needed. ### How do I get Medicaid Managed Care 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.MEDICAID_MANAGED_CARE` directly — no pipeline setup required. ## Related feeds {% 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/Uyp5dZjGoIrc5ypyJYQ9" %} [Multiple Chronic Conditions](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/multiple-chronic-conditions.md) {% endcontent-ref %} {% content-ref url="/pages/ObHxy8Bkd9I5jjhCGzwg" %} [Specific Chronic Conditions](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/specific-chronic-conditions.md) {% endcontent-ref %} {% content-ref url="/pages/CusqjYRh7Ezm8cQ9Nbfr" %} [Medicaid Opioid Prescribing Rates - by Geography](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/medicaid-opioid-prescribing-rates-by-geography.md) {% endcontent-ref %} {% content-ref url="/pages/xWyPWPGWGD4YiJR6fzZg" %} [Market Saturation & Utilization State-County](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/market-saturation-utilization-state-county.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 . *** 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#medicaid-managed-care) --- # 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/medicaid-managed-care.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.