What is the anchor identifier in the Fonteum identity graph?

CCN — the 6-character CMS Certification Number — is the primary join identifier in the named CMS POS, Care Compare, and nursing-home datasets that publish it. It is stored as TEXT with leading zeros preserved; sources that do not publish CCN require a different match path.

Does Fonteum have NPI coverage?

Partially. In the OIG LEIE intersection, 8,551 of 68,055 exclusion records carry an NPI. Broader NPI-to-CCN matching remains limited to source records that publish compatible identifiers.

Are TIN, DEA, and state Medicaid IDs available yet?

Not yet — each is a dated roadmap commitment. TIN arrives with PECOS Ordering & Referring (Sprint 2, Q3 2026), DEA with DEA Active Registrants (Sprint 3, Q4 2026, subject to data-distribution licensing review), and state Medicaid IDs phase in from Sprint 4 (Q1 2027), starting with California, New York, and Texas.

Does Fonteum use proprietary identifiers like IQVIA HCP-OneKey?

No. Fonteum is anchored on public-record sources only and does not ingest licensed reference identifiers such as IQVIA's HCP-OneKey.

How can I consume the identity-graph crosswalk?

Today via the REST API: GET /api/v1/audit-pack/export?ccn={ccn} returns the full record with every available identifier plus per-field provenance (API key via /pilot-intake). Delta Sharing and Snowflake Secure Data Share are on the Sprint 2 (Q3 2026) roadmap.

SOURCES · IDENTITY GRAPH

How Fonteum reconciles provider records across sources.

CCN is the primary join identifier in the named snapshot-manifest datasets that publish it. NPI is partial in the OIG LEIE intersection, and broader matching remains limited to source records that publish compatible identifiers. TIN, DEA, and state Medicaid IDs are dated commitments on the roadmap below.

We publish identifier coverage honestly — including where it's missing — because acquirer data teams will diligence it anyway. Same brand discipline as /trust/data-provenance and the data-availability flags on /sanctions.

Current-state coverage matrix

Per-identifier coverage across the Fonteum corpus, with explicit Sprint roadmap commitments where coverage is partial or pending.

Identifier	Definition	Coverage	Source families	Notes
CCN	CMS Certification Number — 6-character TEXT, leading zeros preserved	Dataset-scoped	POS + named Care Compare and NH-depth datasets	Primary join identifier where the source publishes a CCN; other source families do not necessarily carry it.
NPI	National Provider Identifier — 10-digit TEXT	~10% (LEIE intersection only)	OIG LEIE	LEIE provides NPI for 8,551 of 68,055 exclusion records (~10%); the rest carry name + state. Broader matching remains limited to sources that publish compatible identifiers.
TIN	Taxpayer ID — 9-digit TEXT, masked in most public sources	Not currently ingested	(Sprint 2: PECOS Ordering & Referring)	Available via CMS PECOS Ordering & Referring file (Sprint 2 priority Q3 2026). Public PECOS exposes TIN for ordering/referring providers; full TIN coverage requires the §108B PECOS ingestion to land.
DEA	Drug Enforcement Administration registration — 9-character TEXT	Not currently ingested	(Sprint 3: DEA Active Registrants)	DEA Active Registrants Q4 2026 target. Subject to DEA data-distribution licensing review; not all DEA distributions are redistributable.
Medicaid Provider ID	Per-state Medicaid program ID — format varies by state	Not currently ingested	(Sprint 4: state-specific)	State-by-state ingestion. CA, NY, TX prioritized for Sprint 4 (Q1 2027). Each state has its own Medicaid Management Information System (MMIS) with distinct data formats and access policies.
HCP-OneKey ID	IQVIA proprietary individual-physician identifier	Not applicable	—	Proprietary identifier requiring IQVIA license. Fonteum does not ingest licensed reference data; Fonteum is anchored on public-record sources only.

Sample crosswalk — CCN 015009

One worked example showing what a single facility looks like when joined across the CCN-keyed datasets in the snapshot manifest. Verifiable via the audit-pack export endpoint at /api/v1/audit-pack/export?ccn=015009 (requires API key — see /pilot-intake).

CCN	015009· Anchor identifier
Facility name	BURNS NURSING HOME, INC.· As reported in CMS POS
State	AL
Facility type	skilled-nursing-facility
POS record	1 (release 2026-05-07)
Care Compare NH	1 (release 2026-05-07)
PBJ daily staffing	4 reporting quarters
NH deficiencies	N citations (per snapshot)
NH penalties	M records (per snapshot)
SNF Owners (Phase-1)	1 record · ownership_pct missing per Health Affairs 2024 baseline
SFF status	flagged 85/441 active/candidate corpus
NPI	not currently mapped (LEIE intersection N/A)
TIN	not ingested (Sprint 2 PECOS)
DEA	not ingested (Sprint 3)

Per-field provenance ships as a fourteen-field contract on every audit-pack record: (source, source_url, dataset_id, snapshot, methodology, last_checked, confidence, availability, pipeline_version, doi, license, coverage_start, coverage_end, slsa_provenance_url).

JSON snippet — first NDJSON line of /api/v1/audit-pack/export?ccn=015009

{"schema_type":"fonteum-audit-pack-export","schema_version":"1.0","ccn":"015009","format":"ndjson","methodology_version":"v2026.05.0","emitted_at":"<iso-timestamp>"}
{"line_type":"audit_pack_record","ccn":"015009","facility_type":"skilled-nursing-facility","facility_name":"BURNS NURSING HOME, INC.","state":"AL","pos_qa_status":"ok",
  "fields":{"sff_status":{"value":"<status>","provenance":{"source":"CMS Special Focus Facility list","snapshot_date":"2026-05-07","data_availability":"available"}},
            "ownership_pct":{"value":null,"provenance":{"source":"CMS SNF All Owners","snapshot_date":"<iso>","data_availability":"missing-by-design","caveat":"Per Health Affairs March 2024: 82.40% of top-10-chain ownership_pct missing in CMS data"}}}}

Crosswalk methodology in brief

CCN-anchored joins. For the named CMS facility datasets that publish it, Fonteum joins on the 6-character CCN with leading zeros preserved as TEXT (not coerced to integer — alphanumeric CCNs would lose information on int-cast). Sources without CCN use a separately disclosed match path.

Name + state fallback. Sources without CCN (OIG LEIE individual-provider records, restricted-source name lists) join via fuzzy name + state pairing. The fuzzy match runs through the §sprint1-nh-depth-ingest-b PE/REIT entity registry pattern: substring match against a curated alias list with per-entity confidence scoring. Match results are flagged in the audit-pack with data_availability: "name-matched" so downstream consumers can opt out of fuzzy joins.

Edge cases.CCN reuse after facility closure (a CCN can be re-issued after termination) is handled by joining on (CCN, snapshot_date) tuples — every audit-pack record is anchored to a snapshot date, so two sequential occupants of a CCN appear as distinct records, not a merged history. Facility name variants (legal name vs DBA, casing differences, "Inc." vs "Incorporated") are normalized via the §sprint1-export hydration service before comparison.

Full per-field provenance contract: /methodology. Per-source license + redistribution posture: /trust/data-provenance.

Roadmap

Dated commitments. Each entry is subject to data-source availability and licensing review; we update this page on Sprint completion (or earlier if a milestone slips).

Sprint 2 · Q3 2026NPPES ingestion → evidence-backed NPI ↔ CCN crosswalk where a source publishes both identifiers

Sprint 2 · Q3 2026PECOS Ordering & Referring → TIN coverage for ordering/referring providers (where public)

Sprint 3 · Q4 2026DEA Active Registrants (subject to data-distribution licensing review)

Sprint 4 · Q1 2027State Medicaid Provider IDs — California, New York, Texas initial; remaining states phased

How acquirers and integration partners consume this

REST API today. GET /api/v1/audit-pack/export?ccn=015009 returns the full record with all available identifiers + per-field provenance. Authenticate via the API access flow at /pilot-intake.
Delta Sharing (Sprint 2 Q3 2026). Parquet-native crosswalk table with same provenance contract.
Snowflake Secure Data Share (Sprint 2 Q3 2026). Same data, exposed natively via Snowflake-native distribution.
SFTP delivery. Available on request — see /integrations.

Frequently asked questions

What is the anchor identifier in the Fonteum identity graph?: CCN — the 6-character CMS Certification Number — is the primary join identifier in the named CMS POS, Care Compare, and nursing-home datasets that publish it. It is stored as TEXT with leading zeros preserved; sources that do not publish CCN require a different match path.
Does Fonteum have NPI coverage?: Partially. In the OIG LEIE intersection, 8,551 of 68,055 exclusion records carry an NPI. Broader NPI-to-CCN matching remains limited to source records that publish compatible identifiers.
Are TIN, DEA, and state Medicaid IDs available yet?: Not yet — each is a dated roadmap commitment. TIN arrives with PECOS Ordering & Referring (Sprint 2, Q3 2026), DEA with DEA Active Registrants (Sprint 3, Q4 2026, subject to data-distribution licensing review), and state Medicaid IDs phase in from Sprint 4 (Q1 2027), starting with California, New York, and Texas.
Does Fonteum use proprietary identifiers like IQVIA HCP-OneKey?: No. Fonteum is anchored on public-record sources only and does not ingest licensed reference identifiers such as IQVIA's HCP-OneKey.
How can I consume the identity-graph crosswalk?: Today via the REST API: GET /api/v1/audit-pack/export?ccn={ccn} returns the full record with every available identifier plus per-field provenance (API key via /pilot-intake). Delta Sharing and Snowflake Secure Data Share are on the Sprint 2 (Q3 2026) roadmap.