This is the distinct count of snapshot source IDs with at least one positive record count.

We normalize NPPES records for provider identity, specialty-supply research, and public provider-record surfaces. Source, observation-date, and limitation metadata varies by field and response.

We cross-reference NPPES-matched healthcare practices against PECOS to surface a Medicare-billing-active indicator on the profile, alongside the CMS provider type and enrollment state. The display module is gated to medical archetypes only.

Exclusion-source context on provider profiles when an OIG row publishes the same NPI, with exclusion type, date, and reinstatement date where available. Most LEIE rows do not publish an NPI, so absence of a match is not clearance. Powers the brand-hub /sanctions surface.

Powers the /research/hospital-price-transparency-compliance-2026 flagship study and the /data/price-transparency dataset page. Enables per-state enforcement density analysis, CMP recipient identification, and compliance trend mapping.

Per-NPI Medicare order/refer eligibility, available via the read API and the dataset page. The NPI -> entity-graph link is a separate, gated follow-up — this source writes no entity rows — so eligibility does not yet render on individual provider profiles.

Per-practitioner Medicare opt-out status, available via the read API and the dataset page. The NPI -> entity-graph link is a separate, gated follow-up — this source stamps no entity_id — so opt-out status does not yet render on individual provider profiles.

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.

Per-NPI procedure-level Medicare utilization and payment, available via the read API and the dataset page. The NPI -> entity-graph link is a separate, gated follow-up — this source writes no entity rows — so utilization does not yet render on individual provider profiles.

Aggregate program-integrity research and the 'excluded-anywhere' exclusion ring. The /data and /sources pages report classification and excluding-agency breakdowns only; the per-record SAM lookup is part of the brand-hub exclusion surface, not these catalog pages.

Aggregate facility program-integrity research and the 'compromised-anywhere' enforcement signal. The /data and /sources pages report penalty-type, fine-total, and facility-count breakdowns only — no facility is named.

Aggregate compliance-monitoring research and the 'compromised-anywhere' enforcement signal. The /data and /sources pages report status and agreement-type breakdowns only — no entity is named.

Aggregate state-credentialing research and a future 'licensed/sanctioned-anywhere' screen that complements the federal exclusion ring — a provider sanctioned by a state board can look clean on the federal LEIE. The /data and /sources pages report record counts and per-state coverage only; no licensee is named on these catalog surfaces.

CCN identity backbone for supported joins where each participating dataset supplies a compatible CCN. Surface usage: brand-hub Care Compare modules + audit-pack export.

Identity backbone for Home Health Agencies (POS QIES does not cover HH). Drives the brand-hub `/care-compare/home-health` module. State-level rollups and per-agency pages ship in a follow-on wave.

Enrichment for hospice identity (POS QIES already covers hospices as PRVDR_CTGRY_CD=12; Care Compare adds ownership_type and cms_region). Drives the brand-hub `/care-compare/hospice` module. The May 2026 Training-Family-to-Care measure removal is documented in the methodology; quality-measure ingestion is a follow-on wave.

Identity backbone for represented ESRD facilities (POS QIES doesn't cover dialysis). Drives the brand-hub `/care-compare/dialysis` module and supports source-specific ownership analysis.

Identity backbone for ASC CCNs (POS QIES coverage incomplete). Deterministic NPI bridge (no NPPES fuzzy match needed) — match-confidence improvement vs other Care Compare datasets. Drives the brand-hub `/care-compare/asc` module. ASC-12 (7-day risk-standardized hospital visit rate) is the headline quality measure.

Audit-pack export coverage + cross-source resolver enrichment for represented hospital CCNs. Buyer pitch leverage rather than consumer SEO surface.

Audit-pack export coverage for represented post-acute records (acute hospitals → LTACH → IRF → SNF → HH → Hospice).

Audit-pack export coverage; IRF CCN distinction is relevant for supported cross-source joins.

The documented research subset includes nursing homes, home health, dialysis, and hospice, plus source-pack work staged for future facility pilots. CMS overall star ratings and component sub-ratings render only on surfaces with the required facility-level data; otherwise the data remains research-only.

Drives the brand-hub `/staffing` editorial surface with the facility-level staffing fields represented in the loaded PBJ data.

Drives the brand-hub `/ownership` surface. Direct backbone for the published flagship study at /research/private-equity-nursing-home-ownership-analysis. Fonteum surfaces missingness via DataAvailabilityState: OWNERSHIP_PCT_MISSING — the gap is the data product.

Drives the brand-hub `/deficiencies` surface. Per-citation transparency layer; NH Penalties sub-join surfaces in audit-pack export only.

Sub-join. Audit-pack export field for /deficiencies methodology-versioned customer exports.

Drives the brand-hub `/special-focus-facilities` surface. Per-facility SFF status flag joins to Care Compare NH Provider Information via CCN.

Loaded PY2023 MIPS composite scores can render on NPI-matched provider profiles with source and performance-year metadata. The loaded table has no populated per-clinician payment-adjustment percentage, so Fonteum does not display one. Data is surfaced as published by CMS; Fonteum does not independently score, weight, or rank clinicians.

Tier-2 profile enrichment for Medicare-certified hospitals. Headline fields can render with available source, vintage, and fiscal-year metadata; coverage varies by record.

Tier-2 research enrichment for federally qualified health centers. Awardee-level patient population (Medicaid / uninsured share), staffing FTEs, and clinical-quality-measure rates support FQHC access and quality studies, joined to HRSA HPSA shortage designations. The /data and /sources pages report aggregate counts and per-grant-year breakdowns only — no awardee is named on these catalog surfaces.

The POS file provides the CCN backbone for Care Compare facility joins. Facility fields can render with available source, quarter, and methodology metadata; coverage varies by record. No NPI is included in the iQIES POS export.

Surfaces ACO id, participant legal business name, and performance year on the dataset page and via the read API. The public CMS file carries no participant TIN or NPI (those are restricted to ResDAC), so entity-graph linkage is name-keyed and deferred — ambiguous matches are held.

Tier-1 research-only context for /research pages discussing healthcare access. HRSA HPSA designations cover Primary Care + Dental + Mental Health only; they do NOT cover dermatology, chiropractic, or specialty care.

Tier-1 research-only context for /research pages that discuss workforce supply, wage benchmarks, or per-capita density. OEWS data appears in study commentary and methodology footnotes — it does NOT attach to individual provider profiles.

Tier-1 research-only context for /research pages that discuss regional spending, healthcare-services GDP, or per-capita income. BEA data appears in study commentary — it does NOT attach to individual provider profiles.

Per-capita denominators in research studies (e.g. 'X dermatologists per 100,000 residents'). Tier-1 — appears in study tables and methodology, never on individual provider profiles.

Tier-2 area-level context for /data and /research pages on healthcare access. HPSA designations are keyed to geographies and facilities, not to individual provider NPIs; Fonteum surfaces designation type, discipline, HPSA score, status, and geography on the dataset page.

Tier-2 area-level context for /data and /research pages on primary-care access. MUA/MUP designations are keyed to service areas and populations, not to individual provider NPIs; Fonteum surfaces designation type, IMU score, status, and geography on the dataset page.

Will surface 340B covered-entity identity (340B ID, entity name, entity type, participation status, location) on the dataset page once the first OPAIS export lands. NPI / CCN cross-link into the entity graph is deferred to a gated follow-up — ambiguous matches are held, never written.

Tier-1 area-level context for /data and /research pages on provider supply and Medicare utilization by geography. Fonteum surfaces provider counts, beneficiary counts, average users per provider, and total payment per geography × service type, resolvable by FIPS.

Tier-1 reference code set for resolving a taxonomy code to its grouping, classification, specialization, and display name — used to label NPPES-sourced taxonomy across research and data surfaces, and queryable per code. There is no NPI or entity linkage; this is a code set, not a provider record.

Tier-1 research-only context for studies on research activity and key-opinion-leader networks. Fonteum surfaces study title, status, conditions, sponsor, and overall officials at the aggregate level. Records are name-keyed (PIs and sponsors by name / affiliation); there is no NPI in the source, and NPI / entity-graph linkage is deferred — ambiguous matches are held.

Tier-1 research-only context for studies on research activity and grant-funding networks. Will surface project title, fiscal year, award amount, principal investigators, and awardee organization at the aggregate level. Records are name-keyed (PIs by name; awardee org as affiliation); there is no NPI in the source, and NPI / entity-graph linkage is deferred — ambiguous matches are held.

Aggregate research context on drug and device recalls, keyed to the recalling firm. The firm name is normalized so an Open Payments manufacturer organization can be cross-referenced in a separate, gated follow-up; that entity-graph link is deferred and ambiguous matches are held, not written.

Aggregate drug-product reference, keyed to the sponsor / manufacturer (name-normalized for a deferred Open Payments cross-link). Fonteum surfaces the approved-product identity and marketing status; the entity-graph link is held for ambiguous matches, never written.

Will surface NDC-level drug-product reference (labeler name-normalized for a deferred Open Payments cross-link) once the first snapshot lands. Until then the dataset page renders an honest empty state — figures populate after the operator runs the NDC ingest.

Aggregate device-firm reference, keyed to the registered establishment (name-normalized for a deferred Open Payments cross-link). Fonteum surfaces the establishment identity and type; the entity-graph link is held for ambiguous matches, never written.

Tier-1 drug-level Medicare Part D spending reference for /data and /research pages, keyed on brand × generic × manufacturer. The read API resolves on the brand name. There is no NPI and no entity-graph linkage.

Hosting Fonteum's own research deliverables: state-level CMS Care Compare snapshots, healthcare specialty supply studies (dermatology, chiropractor, NPPES specialty factory), and provider-supply benchmarks. Renders on /research and /press; never overwrites federal source attribution on a per-field basis.