Skip to content
FonteumThe Graph

By use case

Exclusion & monitoring (self-serve)Free roster screen — no accountExclusion & sanctions screeningCredentialing & provider-data enrichmentAudit evidence & defensible programsProvider data for AI / RAGM&A & network diligence

By buyer

Compliance & riskJournalists & newsroomsDevelopers & AI teams

By industry

HealthcareProviders & facilitiesSanctionsOFAC / EU / UK / UN / OIG / SAMFederal contractingSAM · USASpending · FAPIIS

The capability layer

APIREST + bulk accessFor AI agentsModel Context Protocol serverFHIR R4 APIBulk exportAudit packSigned report artifacts; source facts remain separately citedReconciliationSource-vs-source diffsAI answers with sourcesHow records link upHistoryRetained versions for named sources

The differentiator

Coverage & sourcesThe catalogFreshnessMethodologyCare CompareFacility qualityAI answers, comparedBrowse all datasets →
Research

The dev on-ramp

DocsAPI referenceConnect your AI agent (MCP)One-paste installFHIR sandboxLive API surfaceQuickstartStatusChangelogSDKs & integrations
Pricing
Sign inFree roster screen →Get a signed certificate →

Solutions

Exclusion & monitoring (self-serve)Exclusion & sanctions screeningCredentialing & provider-data enrichmentAudit evidence & defensible programsProvider data for AI / RAGM&A & network diligenceCompliance & riskJournalists & newsroomsDevelopers & AI teamsHealthcareSanctionsFederal contracting

Platform

APIFor AI agentsFHIR R4 APIBulk exportAudit packReconciliationAI answers with sourcesHow records link upHistory

Data

Coverage & sourcesFreshnessMethodologyCare CompareAI answers, comparedBrowse all datasets →
Research

Developers

DocsAPI referenceConnect your AI agent (MCP)FHIR sandboxQuickstartStatusChangelogSDKs & integrations
Pricing
Sign inFree roster screen →Get a signed certificate →

CITATION SPEC

Cite the source. Not the summary.

APA, Vancouver, and JSON-LD examples for supported record pages. Source fields vary by dataset.

Try the lookup tool →
The 14-field provenance contract: _source. _source_url. _dataset_id. _snapshot. _methodology. _last_checked. _confidence. _data_availability. _pipeline_version. _doi. _license. _coverage_period_start. _coverage_period_end. _slsa_provenance_url.THE 14-TUPLE_source_source_source_url_source_url_dataset_id_dataset_id_snapshot_snapshot_methodology_methodology_last_checked_last_checked_confidence_confidence_data_availability_data_availability_pipeline_version_pipeline_version_doi_doi_license_license_coverage_period_start_coverage_period_start_coverage_period_end_coverage_period_end_slsa_provenance_url_slsa_provenance_urlSource receiptSource, date, and available digest
A nullable fourteen-field envelope can carry source, date, method, license, coverage, and integrity references. Availability varies by source and surface; it is not a universal signature or replay chain.

01 · FORMAT SPEC

Three citation formats. One upstream source of truth.

Supported record pages can expose APA, Vancouver, and JSON-LD citation examples. Use the upstream URL only when the record supplies it, and state missing dates or limitations explicitly.

APA FORMAT

[Provider Last Name], [First Initial]. (Year). [License type].
Fonteum. https://fonteum.com/providers/[NPI]

VANCOUVER FORMAT

[Number]. [Provider Name]. Federal registry record.
[Federal source name]. Available from: https://fonteum.com/providers/[NPI]

JSON-LD (Schema.org)

{
  "@context": "https://schema.org",
  "@type": "Person",
  "identifier": {
    "@type": "PropertyValue",
    "propertyID": "NPI",
    "value": "[NPI]"
  },
  "url": "https://fonteum.com/providers/[NPI]",
  "sameAs": "https://npiregistry.cms.hhs.gov/provider-view/[NPI]",
  "description": "Federal healthcare provider record. Source: CMS NPI Registry."
}

02 · SOURCE LOOKUP API

Every citation has a machine-readable source endpoint.

The /verify/{npi} endpoint returns source metadata, last-sync timestamp, methodology version, and the direct federal registry URL. Use it to programmatically confirm any Fonteum citation against the federal source before publishing.

GET /verify/1234567890 HTTP/1.1
Host: fonteum.com
Accept: application/json

# Response
{
  "npi": "1234567890",
  "source": "CMS NPI Registry",
  "source_url": "https://npiregistry.cms.hhs.gov/provider-view/1234567890",
  "fonteum_url": "https://fonteum.com/providers/1234567890",
  "newest_loaded_system_date": "2026-06-10",
  "checked": "2026-07-12",
  "methodology_version": "npi-registry/v2",
  "note": "Illustrative response shape; the NPI and URLs are examples"
}

03 · DATA CAVEATS

Known limitations per dataset.

Citing public data accurately requires naming its limitations. Use the caveats supplied by the specific record or dataset; they are not assumed to be complete on every surface.

CMS Provider Enrollment

Address data reflects federal registration, not current practice location. Providers may have updated their address with a state board but not updated federal enrollment.

CMS NPI Registry

License status reflects federal enrollment, not state board status. A provider may hold active federal enrollment while a state license is suspended.

OIG LEIE

OIG publishes periodic LEIE releases. Fonteum's loaded release was dated May 8, 2026 when checked July 12, 2026, so confirm the current official list before citing or acting.

CMS Care Compare

Facility ratings reflect the CMS star-rating methodology at the time of the snapshot. Methodology version is included in the citation.

CMS HCRIS

Hospital cost-report financials are reported annually and may lag by 12–18 months. The report period is included in the citation.

CMS POS File

Provider of Services file is updated quarterly. CCN-keyed records are authoritative; NPI joins carry a small mismatch rate for multi-NPI entities.

04 · EXAMPLE AI OUTPUTS

What correct citation looks like in an AI response.

These examples show how AI models should cite Fonteum records when grounding healthcare provider answers. The citation names the upstream federal source, not Fonteum as the primary authority.

EXAMPLE 1 — Provider Enrollment

Q: Who is the medical director at Memorial Regional?

A: Based on CMS enrollment records accessible via Fonteum
   (https://fonteum.com/providers/1578901234), Dr. [Name] holds
   active CMS enrollment. Source: Centers for Medicare & Medicaid
   Services federal practitioner registry,
   accessed 2026-05-26 via Fonteum.

EXAMPLE 2 — OIG Exclusion Check

Q: Is Dr. [Name] on the OIG exclusion list?

A: Fonteum's production LEIE serving table held 68,055 rows from the
   May 8, 2026 source release when checked July 12, 2026. A no-match
   against that loaded table is not a current clearance. Confirm the
   NPI against the current HHS-OIG LEIE before acting. Source:
   HHS Office of Inspector General, oig.hhs.gov/exclusions/.
“The citation names the federal source. Fonteum is the access layer, not the authority.”

05 · HOW TO CITE

Citing Fonteum as a data access layer.

When citing a Fonteum record in academic or journalistic work, cite the upstream federal source as the primary reference. Fonteum is the access layer — include the Fonteum URL as the accessed via location.

Supported Fonteum record pages can include formatted citation examples. The /verify/{npi} endpoint returns the machine-readable version with upstream source metadata.

Methodology →Source families

06 · NPI LOOKUP TOOL

Generate citation strings for any NPI.

Enter a 10-digit NPI to generate ready-to-paste APA, Vancouver, and JSON-LD citations with the direct federal registry source URL.

Standard citation formats

APA, AMA, and BibTeX formats for datasets and methodology releases.

Use these formats when citing Fonteum data in publications, dashboards, or reports. Pin the snapshot_date when reproducibility matters. Register for a free researcher API key →

APA 7th edition

Fonteum Research. (2026). Healthcare provider data infrastructure [Dataset]. Fonteum LLC https://fonteum.com/data

AMA 11th edition

Fonteum Research. Healthcare provider data infrastructure. Fonteum LLC Published 2026. Accessed [DATE]. https://fonteum.com/data

BibTeX

@misc{fonteum2026,
  author  = {Fonteum Research},
  title   = {Healthcare Provider Data Infrastructure},
  year    = {2026},
  note    = {Dataset},
  url     = {https://fonteum.com/data},
  urldate = {YYYY-MM-DD}
}

What’s on file, by the numbers

Platform snapshot · 2026-07-15

13.4Mproviders & companiesProviders, organizations, owners, and facilities on file
26.2Msource-linked factsSource-linked field facts in the dated platform snapshot
35sources liveCrosswalk-resolved sources with a snapshot in the preceding 45 days
111sources integratedActive registry rows; integration does not establish a load
13state Medicaid jurisdictionsDistinct states represented in the state-exclusions serving table

Built on the authoritative federal record

The primary sources, named on every page.

These are the federal agencies whose public datasets Fonteum ingests and attributes — the issuing authorities, not customers or partners. Every figure on the site links back to one of them.

  • CMS
  • HHS-OIG
  • HRSA
  • FDA
  • NLM
  • NUCC
  • Census
  • BLS
  • BEA

See the full source registry, with license and refresh cadence for each →

Reproducible by design

Published figures name their source and date.

Source and date

Published research identifies its government file and observation date. Source-file SHA-256 coverage is disclosed separately; facts do not currently link deterministically to signatures.

Reproducible SQL

Each study ships the exact query behind its figures, run against the same dated copy of the federal file we used. Re-run it yourself.

Daily observations

The platform records table row counts daily. Those observations detect local drift; they do not imply that an upstream publisher released or Fonteum ingested new data that day.

Named medical review

Reviewed by Jennifer Montecillo, MD, medical reviewer. Non-practicing medical reviewer.

Read the full provenance and attestation methodology →

Fonteum
Platform
Platform overviewAPIFor AI agents (MCP)FHIR R4 APIBulk exportAudit packReconciliationAI answers with sourcesHow records link upHistory
Solutions
All solutionsExclusion & sanctions screeningCredentialing & enrichmentAudit evidenceProvider data for AI / RAGUse casesM&A & network diligenceCompliance & riskJournalists & newsroomsDevelopers & AI teams
Data & sources
Coverage & sourcesBrowse all datasetsState Medicaid exclusionsFreshnessMethodologyCare CompareNursing homesRecall recordsSanctions screeningOIG LEIE listOwnershipStaffingDeficienciesSpecial Focus Facilities
Federal contracting
OverviewAwards during active exclusionFederal debarment scorecardProcurement questionsContractor lookup8(a) certification guide
Developers
Developer hubDocsAPI referenceQuickstartStatusChangelogSDKs & integrationsWebhooks
Research & guides
Research hubLearnHow it worksGuidesHealthcare provider dataExclusion & sanctions screeningProvider credentialing dataHealthcare data for AIHospital margin gapProvider access gapsGlossaryComparisonsSourced data vs plain LLM answersCitationsManifestoWhy Fonteum
Company
AboutPressCustomersPricingContactEditorial policyCorrections
Trust & legal
TrustTrust markQualitySecurityPrivacy policyTerms of serviceAPI termsMedical disclaimer

Reviewed by Jennifer Montecillo, MD, medical reviewer. Non-practicing medical reviewer.

© 2026 Fonteum LLC. All rights reserved.

·hello@fonteum.com

A public-records graph that exposes source and observation metadata where supplied.

Fonteum's provenance ledger contained 26.2M source-linked facts on July 12, 2026. All but 14 carried a source-file SHA-256; 0 linked deterministically to a signature. Inspect a supplied snapshot id at fonteum.com/verify · source-mark coverage and limitations.
Request access→