How we read CMS's files
Every answer here comes from public CMS files, downloaded November 9, 2026. Nothing is typed in by hand and nothing comes from insurers' marketing.
| File | Last-Modified | SHA-256 |
|---|---|---|
| 2027-plan-id-crosswalk-puf.zip PY2027 Plan ID Crosswalk PUF: every 2026 plan mapped to a 2027 plan, county by county | Fri, 30 Oct 2026 13:15:12 GMT | a88a48fe22ac5273e86d9bf10393cdd40db12a8d773bb38f4f5c22ad23192bb2 |
| 2027-plan-attributes-puf.zip PY2027 Plan Attributes PUF: 2027 plan names, issuers, metal levels | Fri, 30 Oct 2026 13:15:06 GMT | c31902e4a441a3aa4515f340a351f26f6bd978043ac7fceb7d4e1c963f3af076 |
| 2026-plan-attributes-puf.zip PY2026 Plan Attributes PUF: 2026 plan names, issuers, metal levels | Mon, 10 Aug 2026 14:01:54 GMT | 954e697885efcb709aed0be1de14075afe11704bf3447372960d08c879950af2 |
| 2027-service-area-puf.zip PY2027 Service Area PUF (kept for the record; the crosswalk already lists counties) | Fri, 30 Oct 2026 13:15:27 GMT | f2fa35b71fee19b10b4d7804f0a61fd98cddbfd757e2acf5842475af839b2280 |
| national_county2020.txt US Census Bureau 2020 county FIPS codes and names (the crosswalk gives FIPS codes only) | Mon, 13 Feb 2023 20:11:55 GMT | 9f6e5f6eb6ac2f5e9a36d5fd01dec77991bddc75118f748a069441a4782970d6 |
1. The crosswalk decides the answer
CMS's Plan ID Crosswalk has one row per 2026 plan per county: the 2027 plan ID it maps to and a reason code. We group the rows by 2026 plan ID and read each county's row:
- Continuing in 2027 / Continuing, new name: every row points to the same plan ID (renamed when CMS's 2027 Plan Attributes file gives a different name).
- Same plan, new plan ID: reason code 1, the same plan under a different 2027 ID.
- Crosswalked to another plan: every row points to a different plan of the same insurer (codes 2, 3, 6, 7).
- Crosswalked to a different insurer: every row is code 8, a different insurer chosen by CMS.
- Depends on your county: the rows differ by county (for example it continues in some counties and moves members in others).
- No 2027 crosswalk: no row names a 2027 plan. Oregon: leaving HealthCare.gov: the same, for Oregon, which leaves HealthCare.gov for 2027.
Insurer names, plan names and metal levels come from CMS's Plan Attributes files (the on-exchange variant's name). County names come from the Census Bureau's 2020 FIPS list.
2. What we checked
- Every 2026 plan × county appears exactly once in the file (148,015 rows, no duplicates), and every 2026 individual health plan in the Plan Attributes file is in the crosswalk.
- Every 2027 plan a row points to exists in CMS's 2027 Plan Attributes file.
- Every plan page lists its county rows exactly as CMS's file has them (tested against the raw zip).
3. What we don't do
- We don't say which plan to choose, rank plans or show premiums: HealthCare.gov's plan comparison does that with your income and household.
- The lookup makes no requests to anyone but this site; guide and state pages count anonymous page views (no cookies).
- CMS's files cover HealthCare.gov states only. States with their own marketplace get a link to it, not a guess.
- CMS posts the next crosswalk each autumn; this site is rebuilt then. Until it is, it describes 2026 → 2027.
2027 in numbers
| What CMS's crosswalk says for 2027 | Health plans | Dental plans |
|---|---|---|
| Continuing in 2027 | 1,081 | 586 |
| Continuing, new name | 1,543 | 9 |
| Same plan, new plan ID | 89 | 10 |
| Crosswalked to another plan | 590 | 15 |
| Crosswalked to a different insurer | 459 | 0 |
| Depends on your county | 223 | 2 |
| No 2027 crosswalk | 0 | 10 |
| Oregon: leaving HealthCare.gov | 59 | 20 |
| All 2026 plans in the file | 4,044 | 652 |
Counted per 2026 plan ID (14 characters, e.g. 12345NC0010001) from plan-id-crosswalk-puf.csv (148,015 rows), 30 states. "Depends on your county" = the plan's rows give different outcomes in different counties.