Skip to content
FonteumThe Graph

The capability layer

APIREST + bulk accessMCP serverCallable by AI agentsFHIR R4 APIBulk exportAttestation & audit packReconciliationSource-vs-source diffsEntity graphSnapshotsPoint-in-time, bitemporal

By use case

Exclusion & sanctions screeningCredentialing & provider-data enrichmentAudit evidence & defensible programsProvider data for AI / RAGM&A & network diligence

By buyer

Compliance & riskDevelopers & AI teams

The differentiator

Coverage & sourcesThe catalogFreshnessMethodologyCare CompareFacility qualityBrowse all datasets →
Research

The dev on-ramp

DocsAPI referenceMCPQuickstartStatusChangelogSDKs & integrations
Pricing
Sign inTry the FHIR sandbox →Request access →

Platform

APIMCP serverFHIR R4 APIBulk exportAttestation & audit packReconciliationEntity graphSnapshots

Solutions

Exclusion & sanctions screeningCredentialing & provider-data enrichmentAudit evidence & defensible programsProvider data for AI / RAGM&A & network diligenceCompliance & riskDevelopers & AI teams

Data

Coverage & sourcesFreshnessMethodologyCare CompareBrowse all datasets →
Research

Developers

DocsAPI referenceMCPQuickstartStatusChangelogSDKs & integrations
Pricing
Sign inTry the FHIR sandbox →Request access →

FOR · DIGITAL HEALTH ENGINEERING

PBJ rows

FHIR R4 in an afternoon.

US Core 6.1.0 conformant. SMART on FHIR auth. BAA on request.

Read the API docs →
11.9M

Indexed records

Practitioners, facilities, and roles across 5 FHIR resource types.

<24 h

Refresh lag

Federal CMS source files pulled on a daily schedule.

FHIR resources

Practitioner · Organization · Location · PractitionerRole · HealthcareService

Sandbox · instant access

Get a read-only sandbox token in seconds. The sandbox serves 200 real provider records drawn from CMS data. Production keys require a pilot agreement and optionally a BAA.

Get sandbox access


Quickstart · 60 seconds

One request to look up a provider.

Pass an NPI in the identifier parameter. The response is a valid FHIR R4 Practitioner bundle with row-level provenance on meta.tag.

curl https://fonteum.com/api/fhir/r4/Practitioner?identifier=1234567890 \
  -H "Authorization: Bearer $FONTEUM_API_KEY" \
  -H "Accept: application/fhir+json"

Capability statement

US Core 6.1.0. Five resources. One endpoint.

The CapabilityStatement at /api/fhir/r4/metadata declares all supported interactions, search parameters, and conformance profiles. Every resource is tagged with a 14-tuple provenance block on meta.tag.

Practitioner

/api/fhir/r4/Practitioner

Individual clinician identity from the CMS federal practitioner registry — NPI, taxonomy, address, qualifications.

Organization

/api/fhir/r4/Organization

Practice groups and facility entities keyed by NPI-2 and CMS CCN.

Location

/api/fhir/r4/Location

Physical practice addresses linked to Practitioner and Organization resources.

PractitionerRole

/api/fhir/r4/PractitionerRole

Role binding — connects a Practitioner to an Organization at a Location.

HealthcareService

/api/fhir/r4/HealthcareService

Services offered by a facility or practitioner, with specialty coding.


FONTEUM API

Stable URIs. SLSA attestations. Versioned methodology.

Read the API docs→ View OpenAPI

Auth flow

SMART on FHIR backend services. No redirect required.

Server-to-server apps use the SMART Backend Services profile. No user login, no OAuth redirect flow. Generate a JWT signed with your RS384 private key and post it to the token endpoint.

# 1. Build the client assertion JWT (RS384)
{
  "iss": "<client_id>",
  "sub": "<client_id>",
  "aud": "https://fonteum.com/api/fhir/r4/token",
  "exp": <unix_timestamp + 300>,
  "jti": "<unique_id>"
}

# 2. Exchange for an access token
curl -X POST https://fonteum.com/api/fhir/r4/token \
  -d "grant_type=client_credentials" \
  -d "client_assertion_type=urn:ietf:params:oauth:client-assertion-type:jwt-bearer" \
  -d "client_assertion=<signed_jwt>" \
  -d "scope=system/Practitioner.read"

Webhook subscriptions

Get notified when a provider record changes.

FHIR R4 Subscription resources let you register a channel and receive a ping whenever a Practitioner or Organization resource changes. The notification payload carries the updated resource and the provenance delta. Available to pilot customers — ask at press@fonteum.com.


Status & SLA

p99 under 300 ms. Daily source refresh.

38 ms

p50 latency

142 ms

p95 latency

290 ms

p99 latency

99.9 %

Uptime target

SLA applies to pilot and production tiers. Latency is measured at the API gateway. Source data refresh lag is separately tracked at /freshness.

Build toward a use case

The same REST and provenance contract powers three jobs compliance and risk teams buy on:

  • Exclusion & sanctions screening + roster monitoring →
  • Credentialing & provider-data enrichment →
  • Audit evidence & defensible programs →

FONTEUM · PILOT

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

Request access→ Read the methodology

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

Every figure traces to its federal source.

14-tuple provenance

Every rendered fact ties to a source URL, dataset ID, snapshot date, row key, and SHA-256 — the full chain-of-custody record.

Reproducible SQL

Each study ships the exact query behind its figures, run against the cited federal snapshot. Re-run it yourself.

Daily reconciliation

Published counts are reconciled against the upstream federal datasets on a daily cadence, with drift logged.

Named medical review

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

Read the full provenance and attestation methodology →

Two doors

Use the free API and open data

Query providers, facilities, sanctions, and quality scores — each field carrying its federal source. Self-serve, no call to start.

Explore the API →Browse the data catalog →

Talk to us

Managed pilots, enterprise terms, and audit-ready, signed attestation packages for compliance, risk, and research teams.

Talk to us →
Fonteum
Platform
Platform overviewAPIMCP serverFHIR R4 APIBulk exportAttestation & audit packReconciliationEntity graphSnapshots
Solutions
All solutionsExclusion & sanctions screeningCredentialing & enrichmentAudit evidenceProvider data for AI / RAGM&A & network diligenceCompliance & riskDevelopers & AI teams
Data & sources
Coverage & sourcesBrowse all datasetsFreshnessMethodologyCare CompareSanctionsOwnershipStaffingDeficienciesSpecial Focus Facilities
Developers
Developer hubDocsAPI referenceQuickstartStatusChangelogSDKs & integrationsWebhooks
Research
Research hubGlossaryComparisonsCitationsWhy Fonteum
Company
AboutPressCustomersPricingContactEditorial policyCorrections
Trust & legal
TrustQualitySecurityPrivacy policyTerms of serviceMedical disclaimer

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

© 2026 Fonteum LLC. All rights reserved.

The U.S. healthcare graph AI can cite — every fact carries its source.

Request access→

The substrate, by the numbers

9.2Mgraph entitiesProviders, organizations, owners, and facilities
15.7Mlinked identifiersNPIs, CCNs, LEIs and more, resolved to entities
5Mgraph edgesSource-attested relationships between entities
44federal source familiesDistinct CMS, OIG, HRSA, FDA and peer datasets
35dataset pagesCitable, downloadable /data catalog pages
65reproducible studiesEach shipping the SQL behind its figures