Source transparency

Data Sources

See the official CMS datasets Medicare Plan Lookup uses for 2026 plan identity, benefits, premiums, and MOOP information.

Last updated: August 26, 2026

Official CMS data

Medicare Plan Lookup builds its 2026 plan records from public data published by the Centers for Medicare & Medicaid Services (CMS). The site normalizes those records into a faster plan-code lookup format while preserving the source meaning as closely as possible.

Primary benefits source · Contract Year 2026

CMS PBP Benefits Data

Plan identity and medical benefit fields are derived from the CMS Plan Benefit Package (PBP) Benefits 2026 JSON release. This dataset is used for items such as inpatient hospital cost sharing, ambulance, emergency room, and home health when those fields are available for the plan.

Open the CMS PBP Benefits source ↗

Cross-check source · August 10, 2026 release

CMS Medicare Landscape Data

Public Medicare Landscape data is used to cross-check plan identity and selected fields such as premium and maximum out-of-pocket information where the source provides comparable values.

Open the CMS prescription drug coverage data page ↗

How the importer handles missing information

A missing field is not automatically treated as a zero-dollar benefit. When the CMS export does not clearly report a value, the site may show wording such as “Not reported,” “Not separately reported,” or “Verify in plan documents” instead of inventing a cost.

Standalone Prescription Drug Plans are also kept distinct from medical plans. A PDP record can identify prescription drug coverage without implying hospital, ambulance, emergency room, or other medical benefits.

Normalization and validation

During the production build, the source records are normalized by contract, plan, and segment code. Automated checks are used to catch duplicate plan codes, malformed records, inconsistent source matches, and arithmetic errors in calculated inpatient copay totals before the site is deployed.

CMS datasets can be revised, and carrier documents can contain details that are not represented in a public data export. Current official plan documents control when there is a difference.

What to verify before relying on a result