Skip to content
FonteumPublic-records evidence

DILIGENCE KIT

Diligence bundle. One PDF.

SOC 2 not held (stated plainly), BAA template, scoped data-provenance map, source-specific license and freshness notes, and incident policy in one downloadable PDF.

v2026.05 · Active production source registry · Delaware LLC

Included · Not yet included

SOC 2 not held, stated plainly, beats SOC 2 implied. This table is honest. Procurement teams respect transparency.

StatusItemNote
Delaware LLC registrationFonteum LLC — formed December 2024.
Active production source registry documentedRegistry status does not establish loaded, complete, or fresh coverage. 11.9M NPPES and PECOS rows are counted separately rather than as historical versions.
Source-specific cadence disclosureThe count-observation date is separate from each upstream source release and ingestion date.
🟡Provenance fields on supported exportsFields vary by source and export. Fourteen of 26,211,234 directly counted provenance rows lacked a source-file SHA-256 on July 12.
BAA template availableTemplate in this pack. Fonteum processes no PHI; BAA is a procurement formality.
FHIR R4 API (Practitioner, Organization, Location, PractitionerRole, HealthcareService)US Core 6.1.0. SMART on FHIR auth. p99 under 300ms on single-record lookups.
SOC 2 Type 1 — not heldFonteum does not currently hold a SOC 2 Type 1 attestation, and displays no badge it does not hold.
SOC 2 Type 2 — not heldFonteum does not currently hold a SOC 2 Type 2 attestation. The hosting and data tiers run on SOC 2 Type 2 attested infrastructure (Vercel, Supabase).
HITRUST certificationNot held. Federal-data-only scope, with no PHI processed, covers procurement requirements.
FedRAMP authorizationOut of scope for current procurement tier.

Dataset documentation

Audit evidence by dataset.

Each dataset pack names its source families, documented fields, limitations, and snapshot scope. The paired methodology page records the reproducibility rules and version history.

Inside the pack

01

Corporate

  • Delaware limited liability company — formed December 2024.
  • Legal name: Fonteum LLC
  • Registered agent: on file with Delaware Division of Corporations.
  • EIN: available to contracted customers under NDA.
02

Security

  • SOC 2 — not held. Fonteum does not currently hold a SOC 2 attestation; the hosting and data tiers run on SOC 2 Type 2 attested infrastructure (Vercel, Supabase).
  • Infrastructure: Vercel (US-East) + Supabase managed Postgres.
  • Encryption in transit: TLS 1.2+. At rest: AES-256.
  • Access controls: row-level security on all public tables. Service-role keys never exposed to browser.
  • Vulnerability disclosure: security@fonteum.com · /.well-known/security.txt (RFC 9116).
03

Data

  • 15 cataloged ingest datasets within the active production registry; registry status does not establish loaded, complete, or fresh coverage. 11.9M NPPES and PECOS rows counted separately.
  • License grant: CMS data is U.S. Government Works (public domain). HHS-OIG LEIE is publicly distributed federal data.
  • No claims data, no EHR data, no commercial data, no consumer PII.
  • Available provenance fields: source, snapshot date, methodology version, and confidence tier where supplied; fields may be null.
  • Provenance schema documented at /methodology.
04

Operations

  • Freshness reporting: source and loaded-observation dates are stated per dataset where available; this pack does not claim a platform-wide refresh SLA.
  • Incident notification: 72h from confirmed breach, plus public corrections-log entry.
  • Corrections log: /corrections-log — public entries for published data corrections.
  • Response-time commitment: P0 (service-down) within 2h. P1 (data-quality) within 24h.
05

Legal

  • BAA template: included in this pack. Fonteum processes no PHI.
  • AI training license: federal public-record data is public domain. No restriction on downstream model training.
  • Terms of use: /terms. Data use for research, analytics, and commercial applications is permitted with attribution.
  • GDPR position: DSAR requests honored within 30 days. We do not sell personal data.
NPPESPECOSOIG LEIEOPEN PAYMENTS
Fonteum Audit Pack
v2026.05 · 2026-05-25
Active production source registry; status is not loaded, complete, or fresh coverage
11.9M NPPES and PECOS rows, counted separately
SOC 2: not held
BAA template: included
License: US Government Works

Pilot and contracted customers

Customer-scoped packs on request.

Pilot, standard, and enterprise customers receive audit packs scoped to their contracted dataset list and delivery cadence. Methodology version is pinned to the snapshot they received. Rollback to a prior version is documented in the change history. This pack is the downloadable artifact behind the audit evidence & defensible programs use case, where the same provenance drives a dual-buyer screening and query workflow.

API export endpoint

Bulk export for contracted customers.

Contracted pilots get programmatic access via /api/v1/audit-pack/export. The endpoint returns NDJSON, JSON, or CSV. Source inventory is drawn from the SPRINT1_EXPORT_SOURCES registry (a scoped healthcare export catalog; provenance availability varies by source).

# Sample request

curl -H "Authorization: Bearer fnt_<your_key>" \

"https://fonteum.com/api/v1/audit-pack/export?format=ndjson"

Supported exports document the provenance columns they include; do not assume every source emits the same source, snapshot, method, and confidence fields. Export keys are issued at pilot onboarding. Contact pilot@fonteum.com to request a key.

What’s on file, by the numbers

Platform snapshot · 2026-08-08

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