> 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/medicare-alternative-payment-model-adoption.md).

# Medicare Alternative Payment Model Adoption

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.MEDICARE_ALTERNATIVE_PAYMENT_MODEL_ADOPTION` on Snowflake and Databricks — coverage from 2024 to 2024 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.MEDICARE_ALTERNATIVE_PAYMENT_MODEL_ADOPTION`     |
| **Databricks**    | `cms_dwv.medicare_alternative_payment_model_adoption` |
| **Coverage**      | Jan 2024 – Dec 2024                                   |
| **Cadence**       | Annual                                                |
| **CMS published** | 2026-03-16                                            |
| **Loaded**        | 2026-03-16                                            |
| **Columns**       | 3 data + 6 lineage                                    |
| **File versions** | 1                                                     |
| **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="success" %}
**Current** — CMS last published this feed on 2026-03-16. Coverage runs through 2024-12-31. Next CMS release expected \~Mar 2027.
{% endhint %}

## Sample queries

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

```sql
SELECT *
FROM DWV.MEDICARE_ALTERNATIVE_PAYMENT_MODEL_ADOPTION
LIMIT 100;
```

{% endtab %}

{% tab title="Databricks" %}

```sql
SELECT *
FROM cms_dwv.medicare_alternative_payment_model_adoption
LIMIT 100;
```

{% endtab %}
{% endtabs %}

## About this feed

> The Medicare Alternative Payment Model (APM) Adoption data set provides information on the amount and percent of Medicare payments flowing through APMs, including downside risk models. The data is segmented according to the categories of the HCP-LAN APM framework, which provides a common, industry framework for classifying payment models. The Framework classifies APMs in four categories and eight subcategories, specifying decision rules to standardize classification efforts.
>
> — *Source: CMS feed metadata*

**Keywords:** Medicare, Original Medicare, Chronic Conditions, Value-Based Care, Coordinated Care **Theme:** Medicare

## Coverage timeline

2024 🟩

1 of 1 years covered — no gaps.

## Release history

| Reporting period        | CMS published | Loaded     | Latest file |
| ----------------------- | ------------- | ---------- | ----------- |
| 2024-01-01 – 2024-12-31 | 2026-03-16    | 2026-03-16 | ✓           |

## Data dictionary

<details>

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

**Data columns**

| Column                                                                  | Type   | Description                                                           |
| ----------------------------------------------------------------------- | ------ | --------------------------------------------------------------------- |
| `APM_CATEGORY`                                                          | TEXT   |                                                                       |
| `TOTAL_FEE_FOR_SERVICE_MEDICARE_DOLLARS_PAID_THROUGH_APM_CATEGORY`      | NUMBER | TOTAL FEE-FOR-SERVICE MEDICARE DOLLARS PAID THROUGH APM CATEGORY      |
| `PERCENT_OF_FEE_FOR_SERVICE_MEDICARE_DOLLARS_PAID_THROUGH_APM_CATEGORY` | NUMBER | PERCENT OF FEE-FOR-SERVICE MEDICARE DOLLARS PAID THROUGH APM CATEGORY |

**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{ MEDICARE_ALTERNATIVE_PAYMENT_MODEL_ADOPTION : "ID = FILE_FEED_ID"
    FEEDS_FILES ||--o{ MEDICARE_ALTERNATIVE_PAYMENT_MODEL_ADOPTION : "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
    }
    MEDICARE_ALTERNATIVE_PAYMENT_MODEL_ADOPTION {
        text ROW_ID PK
        text FILE_ID FK
        text FILE_FEED_ID FK
        text APM_CATEGORY
        number TOTAL_FEE_FOR_SERVICE_MEDICARE_DOLLARS_PAID_THROUGH_APM_CATEGORY
        number PERCENT_OF_FEE_FOR_SERVICE_MEDICARE_DOLLARS_PAID_THROUGH_APM_CATEGORY
    }
```

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

```sql
SELECT d.APM_CATEGORY, d.TOTAL_FEE_FOR_SERVICE_MEDICARE_DOLLARS_PAID_THROUGH_APM_CATEGORY, d.PERCENT_OF_FEE_FOR_SERVICE_MEDICARE_DOLLARS_PAID_THROUGH_APM_CATEGORY,
       ff.TEMPORAL_START, ff.TEMPORAL_END, ff.CMS_FEED_MODIFIED
FROM DWV.MEDICARE_ALTERNATIVE_PAYMENT_MODEL_ADOPTION 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/medicare-alternative-payment-model-adoption-data-dictionary)
* [Medicare Alternative Payment Model Adoption Methodology](https://data.cms.gov/resources/medicare-alternative-payment-model-adoption-methodology)

## Frequently asked questions

### How often is Medicare Alternative Payment Model Adoption updated?

Annually. CMS last published this feed on 2026-03-16, and Dataplex loaded it to the warehouse the same day. New releases are added automatically when CMS publishes them.

### What years does Medicare Alternative Payment Model Adoption cover?

2024 through 2024.

### How many records are in Medicare Alternative Payment Model Adoption?

Count the current snapshot yourself once the share is mounted:

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

### How do I get Medicare Alternative Payment Model Adoption 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.MEDICARE_ALTERNATIVE_PAYMENT_MODEL_ADOPTION` directly — no pipeline setup required.

## Related feeds

{% content-ref url="/pages/uVH3qjISV5hQe3xhzVKS" %}
[Comprehensive End-Stage Renal Disease Care Model Data](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/comprehensive-end-stage-renal-disease-care-model-data.md)
{% endcontent-ref %}

{% content-ref url="/pages/0zSM236Zu2Dq0fRaBCcS" %}
[ACO REACH Eligible Beneficiaries](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/aco-reach-eligible-beneficiaries.md)
{% endcontent-ref %}

{% content-ref url="/pages/LdgpCrmhC8k7STtUOc30" %}
[ACO REACH Aligned Beneficiaries](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/aco-reach-aligned-beneficiaries.md)
{% endcontent-ref %}

{% content-ref url="/pages/FJHKBvD3DL0HCyTLA98L" %}
[Pioneer ACO Model](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/pioneer-aco-model.md)
{% endcontent-ref %}

{% content-ref url="/pages/6gwCSLmAsHSaRIGHzRaC" %}
[ACO Realizing Equity, Access and Community Health Providers](/data-catalog/cms-data-feeds-dataset/cms-data-feeds-catalog/aco-realizing-equity-access-and-community-health-providers.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#medicare-alternative-payment-model-adoption)


---

# 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/medicare-alternative-payment-model-adoption.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.
