Looking for a Health Catalyst Alternative?
Fonteum is the federal public-record data layer — not an analytics platform. If your team needs the raw provider and facility identity data with explicit source citations, Fonteum publishes 17+ federal source families — 6.8M+ active providers from CMS NPPES, 418,148 nursing-home deficiency citations, 1.3M+ PBJ staffing records — with source name, last-checked date, and limitation on every field. No health system dependency. No analytics stack required to access the underlying records.
Fonteum vs Health Catalyst
| Health Catalyst | Fonteum | |
|---|---|---|
| Product category | Healthcare data and analytics platform — data warehousing, analytics applications, and outcome measurement on top of health system data | Federal public-record data layer — primary-source provider and facility records from CMS, OIG, HRSA, BLS, and Census, with field-level provenance |
| Data sourcing model | Health system EHR and claims data integrated into a proprietary data platform; ingested from health system clients | 17+ federal source families ingested directly from government data portals: CMS, OIG HHS, HRSA, BLS, Census — no health system dependency |
| Provenance transparency | Analytics outputs derived from health system operational data; source lineage internal to the platform | Source name + last-checked date + limitation on every rendered field via provider_field_provenance. Every displayed fact traces to a named federal dataset |
| Pricing model | Multi-year enterprise contracts; implementation and license fees typical of large health system deployments | Free public access to all research + datasets; pilot tier from $2,500/mo for custom exports and API access |
| Federal data coverage | Health system operational data; federal datasets may be one input among many | 17+ federal source families as the primary layer: CMS NPPES, PECOS, Care Compare (8 modules), OIG LEIE, PBJ Nurse Staffing, SNF All Owners, HRSA HPSA, UDS, CMS QPP MIPS, HCRIS Hospital Cost Reports, BLS OEWS, Census |
| FHIR R4 API | FHIR support varies by product module; not a primary public API surface | FHIR R4 US Core 6.1.0 — 5 USCDI v3 resources: Practitioner, Organization, Location, PractitionerRole, HealthcareService |
Federal primary sources, no analytics stack required
17+ federal source families, no health system dependency
Fonteum ingests directly from federal government data portals: CMS NPPES (6.8M+ active providers), PECOS, Care Compare (8 modules), OIG LEIE (68,055+ exclusions), PBJ Nurse Staffing (1.3M+ daily records, 14,537 facilities), SNF All Owners (280,207 ownership rows), NH Deficiency Citations (418,148 records), HRSA HPSA and UDS, CMS QPP MIPS, HCRIS Hospital Cost Reports, BLS OEWS, and Census. These are the enrollment, licensing, quality, and geographic records — national in coverage. No health system client relationship required to access them.
Field-level provenance on every displayed fact
When Fonteum surfaces a provider's PECOS enrollment status or a nursing home's CMS staffing rating, the underlying record carries the federal source name, the date the pipeline last reconciled the field, and any known limitations. A compliance audit can trace any displayed fact to the originating federal dataset — not just to 'the platform'.
Open-core: data access without a platform contract
All research snapshots, study CSVs, and JSON datasets are freely accessible at /research. The FHIR R4 API at /api/fhir is publicly documented. For teams needing custom exports, API access, or methodology versioning commitments, the pilot tier starts at $2,500/mo. No multi-year enterprise contract required to access the federal data.
Ingest → provenance → deliver
STEP 1 / INGEST
Pull 17+ federal source families directly from government portals
Fonteum ingests directly from federal data portals — CMS (NPPES, PECOS, Care Compare, PBJ, SNF All Owners, HCRIS), OIG HHS, HRSA, BLS, BEA, and Census — on each source's native cadence, with no health-system client relationship required. NPPES refreshes weekly (6.8M+ active providers), OIG LEIE monthly, Care Compare and PBJ quarterly. The coverage is national and consistent, not limited to one system's operational footprint.
STEP 2 / PROVENANCE
Attach source, date, and limitation to every field
Each parsed fact is written to the provider_field_provenance layer with the source name, last-checked date, and any known limitation. Documented gaps — like the 82.4% missing ownership-percentage values in CMS SNF All Owners — are flagged with a data-availability state rather than imputed, and CMS suppression sentinels are preserved as nulls. A 14-tuple provenance tag travels on every FHIR resource's meta.tag.
STEP 3 / DELIVER
Free datasets, FHIR R4 API, and pipeline-ready bulk export
The structured data ships three ways: free public research datasets at /research (CSV + JSON, no account), a FHIR R4 US Core 6.1.0 API with SMART Backend Services auth and HL7 bulk NDJSON $export (Spark/Pandas/DuckDB/BigQuery-loadable, manifest at /api/v1/bulk/manifest.json), and scoped pilot exports from $2,500/mo. No multi-year platform contract gates the underlying federal data.
Common questions
- How does Fonteum differ from Health Catalyst?
- Health Catalyst is an analytics and data-warehousing platform built on top of a health system's own EHR and claims data — it helps health systems measure outcomes, cost, and performance using their internal operational data, with the analytics layer as the product. Fonteum is a federal public-record data layer: it ingests 17+ federal source families — CMS NPPES (6.8M+ active providers), PECOS, Care Compare, OIG LEIE (68,055+ exclusions), HRSA, BLS, and Census — and publishes them with field-level provenance for teams that need the underlying provider and facility identity records, not analytics built on a single health system's operations. The two are complementary rather than substitutes: Health Catalyst answers 'how is my system performing?' from internal data, while Fonteum answers 'what does the federal record say about any provider or facility in the country, and can I cite it?' Fonteum requires no health-system client relationship to access, and every field traces to a named federal dataset.
- What use cases does Fonteum support that Health Catalyst doesn't?
- Fonteum covers provider and facility identity intelligence from federal primary sources across the whole country, independent of any one health system's data: NPI and taxonomy from CMS NPPES (6.8M+ providers), Medicare enrollment from PECOS, OIG LEIE exclusion flags (68,055+ records, monthly refresh), Care Compare nursing home and home health quality ratings, PBJ nurse staffing (1.3M+ daily records across 14,537 facilities), SNF ownership disclosure (280,207 rows across 14,425 facilities), NH deficiency citations (418,148 records across 14,635 facilities), and HRSA provider-shortage-area designations. These are the compliance, credentialing, M&A diligence, and regulatory-research layers — work that needs the external federal record rather than internal operational analytics. Health Catalyst's strength is the opposite end: measuring and improving a health system's own outcomes from its own data. A team could legitimately run both — Fonteum as the federally sourced external reference spine, Health Catalyst as the internal performance-analytics engine.
- Can Fonteum integrate with an existing health system analytics stack?
- Yes — Fonteum is designed to be the upstream federal data layer feeding an analytics stack, not a competing warehouse. It exposes a FHIR R4 US Core 6.1.0 API with 5 USCDI v3 Provider resources (Practitioner, Organization, Location, PractitionerRole, HealthcareService) and bulk dataset downloads for each of the 17+ federal source families. Federal provider identity records — NPI, PECOS enrollment, taxonomy, OIG exclusion status, Care Compare quality, PBJ staffing — can be ingested as reference data into any warehouse or analytics platform. For pipeline-scale loads, the HL7 FHIR R4 Bulk Data Access ($export) endpoint returns NDJSON, one file per resource type, directly loadable by Spark, Pandas, DuckDB, and BigQuery; the bulk manifest is at /api/v1/bulk/manifest.json and the FHIR CapabilityStatement at /api/fhir/metadata. Every resource carries a 14-tuple provenance tag on meta.tag, so the federal citation travels with the record into your stack rather than being lost at the integration boundary.
- Is Fonteum's data free to use for analytics research?
- All published research snapshots and datasets at /research are free to access and cite with attribution, under a federal public-domain (17 U.S.C. § 105) data model — CMS, OIG HHS, HRSA, BLS, and Census records are not copyrightable, so the structured, provenance-tagged versions are redistributed openly with no account and no API key for static files. This is a structurally different model from a multi-year enterprise data-platform contract: there is no implementation fee and no license gate on the underlying federal data. The paid pilot tier ($2,500–$5,000/mo) adds custom export scoping, FHIR R4 API access for production workloads, methodology-versioning commitments that pin your pipeline to a stable schema, and a 30-day no-penalty exit. Academic and government teams can additionally use the free researcher API tier (citation-required) for programmatic access, and Fonteum datasets are mirrored on HuggingFace Hub for load_dataset() access with pinned methodology versions.
- How broad is Fonteum's federal source coverage?
- Fonteum ingests 17+ federal source families, each documented at /sources with its tier rating, refresh cadence, jurisdiction coverage, and redistribution posture. The identity backbone is CMS NPPES — 6.8M+ active providers across 120+ NUCC taxonomy codes, parsed from the weekly full-replacement file. Layered on top are CMS PECOS Medicare enrollment; CMS Care Compare across eight facility modules (nursing home, home health, hospice, dialysis, ASC, and more); CMS PBJ Daily Nurse Staffing (1.3M+ daily records, 14,537 facilities, CY2025Q2); CMS SNF All Owners (280,207 ownership rows, 14,425 facilities); CMS NH Health Deficiency Citations (418,148 records, 14,635 facilities); OIG LEIE (68,055+ exclusions); HRSA HPSA and UDS; CMS QPP MIPS; CMS HCRIS hospital cost reports; CMS Medicare Provider Utilization; BLS OEWS; BEA Regional; and Census population data. Because Fonteum ingests these directly from government portals rather than receiving them through a health-system client, the coverage is national and consistent, not limited to the operational footprint of a particular system.
- Does Fonteum publish the limitations of its datasets?
- Yes — surfacing limitations is part of the provenance contract, not an afterthought. Every research dataset at /research ships with a documented methodology and an explicit limitations section, and every rendered field carries a limitation note where one applies. The clearest example is the CMS SNF All Owners dataset, where 82.4% of the top-10 nursing home chains have missing ownership_percentage values in the source file — a gap first documented in a Health Affairs 2024 analysis and reproducible from the public CMS file. Rather than impute a value to make the dataset look complete, Fonteum flags the field with a data-availability state so an analyst knows the source itself is silent. CMS suppression sentinels in small-cell counts are preserved as nulls, not coerced to zero. For analytics teams, this matters because silently imputed or smoothed values can corrupt a model without warning; Fonteum's posture is to expose the federal record exactly as it is, with its gaps marked, so you decide how to handle them.
- /sources → Full source library — 17+ federal source families with tier, refresh cadence, and limitations.
- /data-provenance → Field-level provenance pipeline — how every fact ties to a federal record.
- /docs/fhir → FHIR R4 US Core 6.1.0 endpoint reference and CapabilityStatement.
- /data → Dataset catalog, B2B export concepts, and pilot pricing.
- /trust → Security, compliance, and SOC 2 posture.