Skip to content
FonteumPublic-records evidence

USE CASE · PROVIDER DATA FOR AI & RAG

Ground your AI agent in provider data it can cite back to the source.

A chunk-ready federal provider corpus with stable IDs and source metadata where available. Provenance fields are nullable and vary by endpoint, so governance reviews must inspect the fields actually returned.

9M+Source: CMS NPPES · As of 2026-06-10
providers within the active production registry (registry status is not completeness, load status, or freshness)Source-specific provenanceREST + MCP

No PHI Citation-stable chunk IDs 14-field provenance Deterministic re-pull

The AI-governance exposure

An ungrounded provider fact is a liability.

When a model answers with a provider's enrollment status, a sanction, or an NPI and cannot point to a source, that answer cannot be defended. In healthcare, an invented or stale provider fact is not a typo — it is a claim no one can stand behind. The fix is not a bigger model; it is retrieval where each chunk already carries its source and date.

Fonteum exposes source, snapshot, and methodology fields where the chunk builder has them. A grounded answer should cite only those returned fields; historical re-derivation also depends on whether the named source retains the relevant version.

The developer pain

Reference-heavy FHIR and index churn.

Raw FHIR JSON is reference-heavy — a Practitioner points to a PractitionerRole that points to an Organization that points to a Location — so building one chunk of context takes several round trips, and the coding-system URIs and extension blocks bloat every token budget. Worse, the raw files carry no chunk identity, so each re-pull re-embeds everything and churns your vector store.

One paginated GET returns pre-resolved, pre-chunked text with a stable chunk_id and the provenance block inline. The flattening, the chunking, and the citation are the response — not something you reconstruct downstream.

How it works

The corpus shape, and how a chunk stays citable.

Flat

Pre-resolved

Nested FHIR references are resolved server-side into a flat, fully-populated chunk — no client-side round trips to assemble context.

Stable

Chunk IDs

A deterministic chunk_id per record. Use it as the vector primary key; a re-pull upserts in place instead of duplicating vectors.

Nullable

Provenance fields

Source, source URL, snapshot date, last-checked date, methodology, and confidence appear where available; callers must preserve nulls and gaps.

MCP

Live agent path

The same graph is exposed as Model Context Protocol tools, so an agent can query live with the same provenance the static index carries.

Integration & workflow

One corpus. Two ways in.

Developers page the chunks endpoint into a vector store. Governance owners stand up a corpus where every retrieved fact carries a re-derivable citation. Same data, same provenance, same source snapshot.

GET /api/v1/rag/chunks

curl "https://fonteum.com/api/v1/rag/chunks?limit=50&cursor=0" \
  -H "Accept: application/json"

Response

{
  "total": 124817,
  "next_cursor": 50,
  "chunks": [
    {
      "chunk_id": "source:nppes#overview",
      "text": "The CMS NPPES registry enumerates US healthcare providers ...",
      "cite": "CMS NPPES, snapshot 2026-05-01",
      "source_url": "https://npiregistry.cms.hhs.gov/",
      "dataset_id": "nppes/v1",
      "provenance": {
        "_source": "CMS NPPES",
        "_source_url": "https://npiregistry.cms.hhs.gov/",
        "_snapshot": "2026-05-01",
        "_last_checked": "2026-06-17",
        "_methodology": "rag-chunks/v1",
        "_confidence": 1.0
      }
    }
  ]
}

Public endpoint, rate limited per source IP. Map each chunk to a LangChain Document or LlamaIndex TextNode — chunk_id as the id, text as the embed body, the provenance block as metadata. Full LangChain / LlamaIndex / MCP walkthroughs live in /docs/integrations.

Proof — not logos

Chunks expose the public-source metadata available to the endpoint.

9M+Source: CMS NPPES · As of 2026-06-10

Providers

Unique NPIs enumerated from the CMS NPI Registry — the identity backbone the corpus is chunked from.

CatalogSource: Fonteum methodology · As of 2026-08-11

Federal-source documentation

A documented catalog within the active production registry; registry status is not completeness, load status, or freshness. A retrieved chunk identifies its originating source and available snapshot metadata; coverage is bounded by the datasets exposed through this endpoint.

rag-chunks/v1

Methodology

Chunks can identify the chunking methodology version; reproducing a corpus also requires the same retained inputs and source release.

Source-cited

Evidence

Chunks carry their source and snapshot metadata when available. The 26.2M fact ledger currently has no deterministic claim-to-signature link.

“A retrieved fact is only as good as the source it carries. The chunk ID, the source, and the snapshot are the product.”

PROVIDER DATA FOR AI & RAG

Index a citation-stable provider corpus over REST or MCP.

Questions

Before the security questionnaire.

Why not just embed the raw NPPES and CMS files myself?

You can. The raw FHIR and CSV files are reference-heavy and carry no chunk identity, so a re-pull can churn your vector index. Fonteum returns pre-resolved, pre-chunked text with a stable chunk_id and the provenance fields available for that chunk; callers must handle null or absent source fields.

How does a chunk keep its citation?

A chunk can include source name, source URL, snapshot date, last-checked date, methodology version, and a cite string. Availability varies by source and endpoint, so carry only the metadata actually returned and do not infer missing fields.

Will the chunk IDs stay stable across pulls?

Yes. Chunk IDs are deterministic — the same record produces the same chunk_id on every pull, so an incremental re-pull upserts cleanly instead of duplicating vectors. Re-embedding only touches chunks whose underlying federal record actually changed.

Can my agent call this over MCP instead of REST?

Yes. The same provider graph is exposed as Model Context Protocol tools — search, resolve-by-NPI, exclusion check, dataset info, source list. MCP and REST responses expose route-specific provenance fields rather than a guaranteed tuple on every fact.

Is any patient data in the corpus?

No. The corpus is built only from public federal and state provider records keyed by NPI, CCN, and PECOS-ID. There is no PHI in the pipeline and none is required to index, retrieve, or cite a provider fact.

FONTEUM · PROVIDER DATA FOR AI

Ground your agent on public data only. No PHI.

What’s on file, by the numbers

Platform snapshot · 2026-08-29

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
19fresh 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