← All sources Healthcare graph
CMS RevalidationCMS Medicare Revalidation Due Date List
Centers for Medicare & Medicaid Services (CMS) · Tier-2 · profile-enrichment (renders on matched profiles)
The CMS Revalidation Due Date List publishes when each Medicare-enrolled provider must revalidate enrollment under 42 CFR 424.515 (ACA §6401(a)). The natural key is the pair (enrollment id, NPI): an enrollment id can carry several NPIs for organization enrollments. Each row carries name, organization, state, enrollment type, specialty, and the revalidation due date.
How this source shows up on Fonteum.
Per-enrollment Medicare revalidation due dates, available via the read API and the dataset page. The NPI -> entity-graph link is a separate, gated follow-up — this source stores revalidation records, not resolved provider-graph entities — so it does not yet render on individual provider profiles.
What this source does NOT mean
A revalidation due date is a Medicare enrollment-administration deadline — it does not indicate quality, outcomes, or any disciplinary status. A 'TBD' or absent date means CMS has not set a due date, not that the provider is non-compliant; it is not a Fonteum assessment.
Research and data questions this source supports.
- Look up when a Medicare-enrolled provider or organization must revalidate enrollment, by enrollment id and NPI.
- Build an enrollment-operations dashboard that surfaces upcoming revalidation deadlines for a provider network.
- Research revalidation due-date distribution by enrollment type and state.
- Power a provider-data API that returns the revalidation due date per enrollment.
Dataset size: 2,900,588 enrollment records (2026-06-14 snapshot)
Per-field display contract.
Fields listed below show their configured `display_allowed` flag from the §94 provenance schema. Fields marked write-locked are captured for audit and are not rendered on profile pages.
Research-only — never on profiles
7 fieldsWhat we can’t infer from this source.
- A revalidation due date is an enrollment-administration deadline, not a quality or compliance signal.
- Upstream 'TBD' / blank values are stored as null — an absent date means no due date is set, not non-compliance.
- NPI-keyed where present, but the entity-graph cross-link is deferred — due dates do not render on individual provider profiles yet.
- Snapshot-based: rows republished after the selected artifact's observation date may be absent; no future pull is promised.
Authority, license, publisher cadence.
Authority
Centers for Medicare & Medicaid Services (CMS)
Tier
Tier-2 · profile-enrichment (renders on matched profiles)
Publisher / configured cadence
Declared or configured cadence: Monthly — CMS republishes the Revalidation Due Date List under a fresh release-dated path. Not evidence of the latest loaded source date.
License
U.S. government public-domain works. Free to use with attribution; explicit redistribution rights. License ↗
Official URL
Attribution requirement
Source: Centers for Medicare & Medicaid Services (CMS) — Revalidation Due Date List · Snapshot {YYYY-MM-DD}
What the source allows.
U.S. government public-domain works. CMS publishes the Revalidation Due Date List as a no-auth bulk CSV at data.cms.gov with explicit redistribution rights. Snapshot and attestation fields must be read from the specific artifact; no provenance fact currently links deterministically to a signature.
What a single field looks like in the graph.
This worked example shows the provenance shape used when a surfaced field has populated source, last-checked, display-rule, and confidence metadata. Individual fields may omit unavailable values.
Field
Revalidation due date (research-only)
Sample value
Enrollment I00000000 · NPI 1234567890 · Due 2026-09-30
Provenance line
Source: CMS Revalidation Due Date List · Snapshot 2026-06-14 · Methodology cms-revalidation/v1 · Display rule: per-enrollment due date — read API + dataset page; profile rendering deferred with the entity-graph link
Official API, bulk download, and Fonteum endpoints.
Official API / download
Fonteum surface
Common questions about CMS Revalidation.
- What is the CMS Revalidation Due Date List?
- It publishes when each Medicare-enrolled provider must revalidate enrollment under 42 CFR 424.515 (ACA §6401(a)). The natural key is the pair (enrollment id, NPI) — an enrollment id can carry several NPIs for organization enrollments. Each row carries name, organization, state, enrollment type, specialty, and the revalidation due date.
- What does a 'TBD' or blank due date mean?
- It means CMS has not set a revalidation due date for that enrollment yet. Fonteum stores upstream 'TBD' / blank values as null — an absent date is not a sign of non-compliance.
- How often is the list published?
- CMS republishes the list monthly at data.cms.gov as a no-auth bulk CSV under a release-dated path. Fonteum resolves the live CSV by the stable dataset UUID and attests each snapshot. As of the 2026-06-14 snapshot, Fonteum holds 2,900,588 enrollment records.
- Is a revalidation due date a compliance or quality signal?
- No. It is an enrollment-administration deadline. It does not indicate quality, outcomes, or any disciplinary status, and it is not a Fonteum assessment of the provider.
- Does this render on provider profiles?
- Not yet. Due dates are available via the read API and the dataset page, but the NPI → entity-graph link is deferred, so they do not yet render on individual provider profiles.
Where this source already shows up.
Related sources in the graph
- /sources → The generated source-catalog subset — documented datasets Fonteum cites.
- /data-provenance → The provider graph — pipeline diagram, source-family clusters, field-level provenance examples, display rules.
- /methodology → Documented sourcing, publisher cadence, observed freshness, and corrections policy.
- /editorial-policy → Independence, sourcing, conflicts, corrections, retractions.