Skip to content
FonteumPublic-records evidence
Screen 25 NPIs free →Buy $129 certificate →
FONTEUM — USE CASES

Healthcare provider data for every team

An active production source registry whose status does not establish loaded, complete, or fresh coverage. FHIR R4 API. Free research datasets. Each surface is designed for a specific buyer workflow — learn how yours fits.

Use cases

  • Health Plans

    Federal provider-record reconciliation, exclusion screening, and source-specific NPI comparison for Medicare Advantage and commercial plans.

    Read more

  • Telehealth

    NPI lookup, specialty coverage, and HPSA shortage-area data to route patients to in-network providers across jurisdictions.

    Read more

  • Patient Portals

    Provider profiles with available source and observation metadata for embedding in patient-facing find-a-doctor surfaces.

    Read more

  • Researchers

    Free researcher API for .edu and .gov institutions. Reproducible datasets with methodology, limitations, and citation chain.

    Read more

  • Developers

    HL7 FHIR R4 US Core 6.1.0 endpoints, bulk NDJSON export, SMART Backend Services auth, and MCP server for agentic workflows.

    Read more

  • Payer Credentialing

    CMS NPPES, OIG LEIE, and CMS PECOS in one source-provenanced graph — field-level federal citation on every credentialing record.

    Read more

  • M&A Diligence

    Facility-level acquisition risk: SNF ownership chains, PBJ staffing hours, and CMS Care Compare deficiency histories, each tied to its federal source.

    Read more

  • Healthcare Analytics

    FHIR R4 bulk export, semantic search, and free research datasets for data science teams at health systems, payers, and digital health companies.

    Read more

  • Government Contractors

    FHIR R4 US Core 6.1.0, SMART Backend Services auth, and HL7 Bulk Data Access for IT vendors serving CMS, VA, and OIG.

    Read more

FONTEUM — PILOT

Run a 90-day pilot. Public data only. No PHI.

What’s on file, by the numbers

Platform snapshot · 2026-07-24

13.4Mproviders & companiesProviders, organizations, owners, and facilities on file
26.2Msource-linked factsSource-linked field facts in the dated platform snapshot
90sources with dataDistinct snapshot source IDs with at least one positive record count
79fresh sourcesDistinct source IDs whose latest positive-data snapshot falls within 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

Integrated, with-data, and fresh-observation counts are separate. No platform-wide source-completeness count is published. Completeness is source-specific and must be evaluated against the named source's expected scope. State coverage is a separate jurisdiction measure.

Source authority is record-specific

Use the issuer named on the record.

Fonteum spans federal, state, and global public publishers. A source page or returned record identifies its issuer and dataset where that metadata is available. A platform registry count does not assign every page to one authority or establish loaded, fresh, or complete coverage.

Browse source records and their stated limitations →

Reproducible by design

Inspect the evidence each published figure actually supplies.

Source and date

Research pages expose the named public file and observation date where those fields are available. Source-file SHA-256 coverage is separate; facts do not currently link deterministically to signatures.

Available derivation

Studies with a retained release and committed derivation link the SQL or method used. Other studies state the evidence and reproduction limits they actually have.

Daily observations

Dated table row-count observations can 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 →

Request access