- What developer APIs does Fonteum offer?
- Fonteum provides three developer access paths: an HL7 FHIR R4 provider directory API (Practitioner, Organization, Location, PractitionerRole, HealthcareService resources), bulk dataset downloads in NDJSON and CSV formats for all ingested federal source families, and HMAC-SHA256-signed provider event webhooks that fire when LEIE or PECOS state changes for a tracked provider.
- Is authentication required to use the Fonteum FHIR API?
- Anonymous GET requests are permitted for individual resource reads. SMART Backend Services authentication (client credentials flow with a signed JWT) is required for the Bulk Data $export operation, which streams the full provider dataset as NDJSON. Registration is free.
- What federal data sources power the Fonteum API?
- The Fonteum API draws from 12+ federal source families including NPPES, CMS PECOS PPEF, OIG LEIE, CMS Care Compare (Nursing Home, Home Health, Hospice, Dialysis, ASC), HCRIS Hospital Cost Reports, CMS QPP MIPS, HRSA HPSA, and HRSA UDS. Every field carries 14-tuple chain-of-custody provenance tracing back to the originating federal record.
- How does Fonteum's 14-tuple provenance chain work?
- Each data field is tagged with 14 provenance fields: dataset ID, source agency, source URL, archive URL, snapshot date, reporting period, methodology version, entity type, entity ID, field name, field value, confidence tier, chain link hash, and attested-at timestamp. This chain links every rendered fact to the specific federal record row it originated from and the ingestion run that imported it.
- Where can I find the FHIR CapabilityStatement?
- The FHIR CapabilityStatement is published at /api/fhir/metadata. It enumerates 5 USCDI v3 Provider resources: Practitioner, Organization, Location, PractitionerRole, and HealthcareService. The statement conforms to US Core 6.1.0 and includes SMART Backend Services security extensions.