Part C&D Plan Crosswalk

Provides the list of annual plan crosswalks for all organization types.

Part of the CMS Data Research Dataset › Plan Crosswalk

Dataplex delivers this CMS research table as the analysis-ready table DWV.PLAN_CROSSWALKS on Snowflake and Databricks: coverage from 2006 to 2027 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.PLAN_CROSSWALKS
Databricks	cms_research_dwv.plan_crosswalks
Coverage	Jan 2006 – Jan 2027
Rows	130,455 (total across all reporting periods)
Cadence	Annual
Update pattern	Time-partitioned; each file adds one reporting period
Latest report period	2027-01-01
Loaded	2026-10-05
Columns	14 data + 5 lineage
Identifiers	Contract ID (H-number) · Plan ID
File versions	18
License	CMS public data (U.S. Government work)
Platforms	Snowflake Marketplace · Databricks Delta Sharing

Included in the CMS Data Research Dataset, start a free trial on Snowflake Marketplace.

Current: data runs through the Jan 2027 report period. Next CMS release expected ~Jan 2028.

Partitioned by report period: each file version covers one report period and history is additive. The sample query below returns the latest report period; drop the WHERE clause to query the full history.

Sample queries

Snowflake

-- Latest report period only (drop the WHERE clause for the full history)
SELECT *
FROM DWV.PLAN_CROSSWALKS
WHERE FILE_ID IN (
  SELECT ID FROM DWV.FEEDS_FILES WHERE IS_LATEST = 1
)
LIMIT 100;

Databricks

-- Latest report period only (drop the WHERE clause for the full history)
SELECT *
FROM cms_research_dwv.plan_crosswalks
WHERE file_id IN (
  SELECT id FROM cms_research_dwv.feeds_files WHERE is_latest = 1
)
LIMIT 100;

About this feed

Provides the list of annual plan crosswalks for all organization types.

Source: CMS feed metadata

Theme: Plan Crosswalk

Coverage timeline

2006–2027 🟩🟩🟩🟩🟩⬜⬜⬜🟩🟩⬜🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩 (🟩 covered · ⬜ no data)

18 of 22 years covered, with gaps: 2011, 2012, 2013, 2016.

Release history

Report period	Files	Loaded	Latest	CMS source
2027-01-01	1	2026-10-05	✓	source ↗
2026-01-01	1	2025-11-20		source ↗
2025-01-01	1	2025-01-12		source ↗
2024-01-01	1	2025-11-20		source ↗
2023-01-01	1	2023-12-03		source ↗
2022-01-01	1	2023-12-03		source ↗
2021-01-01	1	2023-12-03		source ↗
2020-01-01	1	2023-12-03		source ↗
2019-01-01	1	2023-12-03		source ↗
2018-01-01	1	2023-12-03		source ↗

Show 8 earlier report periods

Report period	Files	Loaded	Latest	CMS source
2017-01-01	1	2023-12-03		source ↗
2015-01-01	1	2023-12-03		source ↗
2014-01-01	1	2023-12-03		source ↗
2010-01-01	1	2023-12-03		source ↗
2009-01-01	1	2023-12-03		source ↗
2008-01-01	1	2023-12-03		source ↗
2007-01-01	1	2023-12-03		source ↗
2006-01-01	1	2023-12-03		source ↗

Data dictionary

📋 14 data columns + 5 lineage columns

Data columns

Column	Type
PREVIOUS_CONTRACT_ID	TEXT
PREVIOUS_PLAN_ID	TEXT
PREVIOUS_PLAN_NAME	TEXT
PREVIOUS_SNP_TYPE	TEXT
PREVIOUS_SNP_INSTITUTIONAL	TEXT
CURRENT_CONTRACT_ID	TEXT
CURRENT_PLAN_ID	TEXT
CURRENT_PLAN_NAME	TEXT
CURRENT_SNP_TYPE	TEXT
CURRENT_SNP_INSTITUTIONAL	TEXT
STATUS	TEXT
DESCRIPTION	TEXT
PREVIOUS_SNP_POPULATION	TEXT
CURRENT_SNP_POPULATION	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

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:

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

Snowflake

SELECT d.PREVIOUS_CONTRACT_ID, d.PREVIOUS_PLAN_ID, d.PREVIOUS_PLAN_NAME,
       ff.FILE_REPORT_PERIOD AS TEMPORAL_START, ff.FILE_REPORT_PERIOD AS TEMPORAL_END
FROM DWV.PLAN_CROSSWALKS d
JOIN DWV.FEEDS_FILES ff ON d.FILE_ID = ff.ID;

Databricks

SELECT d.previous_contract_id, d.previous_plan_id, d.previous_plan_name,
       ff.file_report_period AS temporal_start, ff.file_report_period AS temporal_end
FROM cms_research_dwv.plan_crosswalks d
JOIN cms_research_dwv.feeds_files ff ON d.file_id = ff.id;

Source & provenance

Published by the Centers for Medicare & Medicaid Services.

• Official CMS documentation (MA/Part D contract and enrollment data)

• Latest source file from CMS (zip)

Frequently asked questions

How often is Part C&D Plan Crosswalk updated?

Annually. CMS last published this feed on 2027-01-01, and Dataplex loaded it to the warehouse on 2026-10-05. New releases are added automatically when CMS publishes them.

What years does Part C&D Plan Crosswalk cover?

2006 through 2027. Coverage gaps: 2011, 2012, 2013, 2016.

How many records are in Part C&D Plan Crosswalk?

130,455 rows across all 18 report periods. Because this feed is partitioned by report period, the full table total is the meaningful count; no deduplication needed.

How do I get Part C&D Plan Crosswalk data?

It's included in the CMS Data Research Dataset on the Snowflake Marketplace (free trial available). Once mounted, query DWV.PLAN_CROSSWALKS directly; no pipeline setup required.

Get this feed

1. Start a free trial on Snowflake Marketplace

2. Mount the share; the database and DWV schema appear in your account immediately

3. Run the sample query above; no ETL, no pipeline maintenance

Questions about this feed? Contact us at [e-mail].

---

Part of the CMS Data Research Dataset; 48 research tables · 25 years of Medicare Advantage & Part D history · updated daily. Back to the full catalog →