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 | 1942209770 | cms_part_d_prescribers | exact_prescriber_npi | 1.000 | 2026-06-14 | evidencerecorded: 2026-06-14 methodology: entity-graph/v1 evidence: {"note":"fill-gap: prescriber in CMS Part D but absent from NPPES active extract","rule":"D-PART-D","source":"cms_part_d_prescribers","prescriber_npi":"1942209770","prescriber_specialty":"Dentist"} |
Graph edges
One-hop relationships — ownership, chain membership, operation — each backed by a federal source row.
Current record
Every current claim asserted about this entity, grouped by provenance subject. Each cell carries its upstream federal source.
provider · 1942209770 JSON
| Metric | Value | Asserted | Source |
|---|---|---|---|
| credential | DMD | 2026-06-10 | Centers for Medicare & Medicaid Services |
Provider screening signals
NPI-keyed source families read directly for 1942209770: federal and state integrity lists, CMS Open Payments, Order and Referring eligibility, Medicare opt-out, and enrollment revalidation. Each cell carries its own source and 14-tuple provenance. 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
On fileA hard exclusion is in force on 1 list. Screening aid — re-confirm against the primary source before acting.
- Excluded by: WA Medicaid
- Screened 14 integrity lists.
14-tuple provenance (14)
Point-in-time
Reconstruct this record as of any date, or diff it between two dates — both axes of the bitemporal store (bitemporal-read/v1): valid time (when a fact was true per the source) and recorded time (what the store knew when).
Pick a date to reconstruct, or two dates to diff. Equivalent JSON: /api/v1/history/{subject_type}/{subject_id}?at=… and …/diff?from=…&to=…