Cross-source identifiers
Every current identifier attachment, with the link method and confidence carried verbatim — deterministic links are 1.000; probabilistic links surface their real matcher confidence, never rounded up.
| Scheme | Value | Source table | Link method | Confidence | Since | Provenance |
|---|---|---|---|---|---|---|
| npi | 1417271909 | nppes_providers | deterministic_pk | 1.000 | 2026-06-11 | evidencerecorded: 2026-06-11 methodology: entity-graph/v1 evidence: {"rule":"D-NPI","source_pk":"1417271909","entity_type_code":"1"} |
Graph edges
One-hop relationships — ownership, chain membership, operation — each backed by a federal source row.
Current record
Current claims returned for this entity, grouped by provenance subject. The table exposes the source identifier recorded for each claim.
provider · 1417271909 JSON
| Metric | Value | Asserted | Source |
|---|---|---|---|
| credential | D.C. | 2026-06-11 | Centers for Medicare & Medicaid Services |
Provider screening signals
NPI-keyed source families read directly for 1417271909: federal and state integrity lists, CMS Open Payments, Order and Referring eligibility, Medicare opt-out, and enrollment revalidation. Cells expose the source and provenance fields supplied by the selected record. A screening aid — re-confirm any match against the primary source before acting; absence means nothing on file in the data Fonteum currently holds, never a guarantee none exists.
Sanctions & integrity
Coverage staleExclusion coverage is stale or cannot be reconciled to an attested source artifact. This result is indeterminate and must not be treated as a clearance; check the current issuing-agency lists.
- Coverage status: indeterminate
- Screened 26 integrity lists; no negative determination was made.
14-tuple provenance (26)
Point-in-time
Query retained claim coordinates under bitemporal-read/v1. Most facts have no superseded row; dates outside retained coverage may return no prior version, and diffs require both coordinates.
Pick a date to reconstruct, or two dates to diff. Equivalent JSON: /api/v1/history/{subject_type}/{subject_id}?at=… and …/diff?from=…&to=…