Skip to content
FonteumPublic-records evidence
Fonteum · Compare

Komodo Health Competitors & Alternatives (2026)

Fonteum publishes healthcare provider data built on federal primary-source records — not claims aggregation. The

active production registrySource: Fonteum methodology · As of 2026-07-12
does not establish loaded, complete, or fresh coverage. This page names a documented federal healthcare subset including CMS NPPES ( NPI records), PECOS, Care Compare, OIG LEIE ( serving rows from the May 8, 2026 source release when checked July 12), and HRSA. Returned fields expose source, date, and limitation metadata where populated — citable back to the originating federal dataset when available, not a proprietary claims-derived model.

Side-by-side comparison

Fonteum vs Komodo Health

Komodo HealthFonteum
Data sourcing modelClaims data aggregation: medical, pharmacy, and lab claims from payers and PBMs — opaque sourcing, not field-level disclosedThe active production registry includes a documented healthcare federal-source subset named on this page: CMS NPPES, PECOS, Care Compare, OIG LEIE, HRSA, BLS, and Census. Active registry status is not a load, freshness, or completeness claim.
Provenance transparencyPatient-encounter claims data; source lineage proprietary and not externally citableAvailable source, date, and limitation fields from provider_field_provenance; fields may be null
Pricing modelEnterprise license; typical six-figure annual contracts for claims dataset accessPublic research and dataset downloads where linked; pilot tier from $2,500/mo for custom exports and API access
Federal source citationFederal and claims data consumed internally; not surfaced as external citationsCMS dataset IDs and federal catalog links where the source response supplies them
Post-acute facility coverageClaims-based utilization patterns for post-acute settingsDirect CMS facility records: Care Compare NH/HH/Hospice, PBJ Daily Nurse Staffing, PECOS SNF All Owners — facility identity from the source, not inferred from claims
FHIR R4 APIProprietary API; FHIR conformance not publishedFHIR R4 US Core 6.1.0 — 5 USCDI v3 resources: Practitioner, Organization, Location, PractitionerRole, HealthcareService
Primary sources vs claims aggregation

Federal records, not inferred signals

Claims data tells you what happened; federal records tell you who is enrolled

Claims data infers provider attributes from billing patterns — specialty from claim codes, affiliation from claim groupings. Loaded federal records supply a different layer: CMS NPPES supplies taxonomy at enumeration for 6.8M+ NPI records; PECOS supplies Medicare-participation fields; the OIG LEIE serving table held 68,055 rows from the May 8, 2026 source release when checked July 12; and Care Compare supplies facility-certification fields. Returned fields expose loaded-date metadata where the response supplies it; dates may be absent or lag the publisher.

Post-acute facility data from the source

Fonteum's loaded post-acute records include CMS Care Compare for nursing homes, home health, and hospice; CMS PBJ Daily Nurse Staffing for facility-level RN/LPN/CNA hours (1.3M+ daily records across 14,537 facilities, CY2025Q2); PECOS SNF All Owners for ownership disclosure (280,207 ownership rows across 14,425 facilities); and CMS NH Health Deficiency Citations (418,148 records across 14,635 facilities). Available records expose CMS dataset, snapshot-date, and limitation metadata where populated; fields may be null. These named records are loaded from the cited CMS publications.

Open-core model: public access + pilot tier

Research snapshots and dataset files linked from /research are accessible without an account when the page exposes a download. For teams that need custom exports scoped to specific geographies, specialties, or facility types, the pilot tier starts at $2,500/mo with a 30-day no-penalty exit. A custom export describes its available source and provenance fields; coverage varies by contracted source.

How it works

Ingest → provenance → deliver

STEP 1 / INGEST

Pull directly from federal data portals

The active production registry does not establish loaded, complete, or fresh coverage. This comparison names a loaded federal-source subset from CMS, OIG HHS, HRSA, BLS, and Census. The July 12 audit found NPPES at June 10, OIG LEIE at May 8, checked Care Compare modules at May 7, and PBJ work dates through June 30, 2025. Loaded dates are reported separately from publisher cadence.

STEP 2 / PROVENANCE

Expose available source, date, and limitation metadata

Parsed responses expose source, date, and limitation fields from provider_field_provenance where populated; fields may be null. PECOS enrollment, OIG LEIE, and PBJ responses retain their named federal source metadata where supplied. Missing source values — like the 82.4% SNF ownership-percentage gap — are flagged, not imputed.

STEP 3 / DELIVER

Free research, FHIR R4 API, and scoped exports

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 $export, and scoped pilot exports from $2,500/mo for custom geography, specialty, or facility-type cuts. Public and API responses expose available source metadata; coverage varies by route and source.

FAQ

Common questions

What is the key difference between Komodo Health and Fonteum?
Komodo Health is built on claims data — medical, pharmacy, and lab claims aggregated from payers and PBMs into a longitudinal patient-encounter model. Fonteum's does not establish loaded, complete, or fresh coverage. This comparison focuses on a documented federal healthcare subset including CMS NPPES ( NPI records), CMS PECOS, CMS Care Compare, OIG LEIE ( serving rows from the May 8, 2026 source release when checked July 12), HRSA, BLS, and Census. Returned fields expose federal source, date, and limitation metadata from provider_field_provenance where populated; fields may be null. A field with populated metadata can identify a specific CMS dataset ID or OIG HHS file, while claims-derived lineage remains proprietary.
Does Fonteum have post-acute provider coverage like Komodo Health?
Fonteum holds loaded CMS Care Compare, Payroll-Based Journal, ownership, and deficiency data. In the July 12 production audit, checked Care Compare modules had a newest source date of May 7, 2026 and PBJ work dates ended June 30, 2025. Other source dates and metadata vary by response; this is not a claim of current or complete post-acute coverage.
Is Fonteum's provider data free to access?
Static research snapshots and dataset files linked from /research are available without an account when the page exposes a download. The named upstream federal records — NPPES, PECOS, Care Compare, and OIG LEIE — are U.S. government works under 17 U.S.C. § 105; licensing and download availability vary for other sources. By contrast, claims-based platforms like Komodo Health license claims feeds. The Fonteum paid pilot tier ($2,500–$5,000/mo) adds custom export scoping, FHIR R4 API access for production workloads, and methodology-versioning commitments with a 30-day no-penalty exit. Basic public-record pages remain public; custom scoping and production API throughput are paid services.
Can Fonteum support pharma or life sciences market sizing use cases?
Where supported, Fonteum exposes loaded provider and facility records: NPI records with taxonomy and practice-address fields from CMS NPPES, Medicare-enrollment fields from PECOS, shortage-area designations from HRSA HPSA, MIPS quality scores from CMS QPP, and named facility datasets from CMS. It does not cover patient-level claims utilization — encounter frequency, diagnosis prevalence, or Rx volume by provider. Market-sizing work that needs patient-journey or prescribing signals still needs a claims analytics platform for the utilization layer. The supported, dated public-record fields can serve as a reference layer to join against utilization data; coverage and source dates vary by response.
Why does claims-inferred provider data drift from the federal record?
Claims-based platforms derive provider attributes from billing behavior: specialty is inferred from procedure codes, affiliation from claim groupings, and activity from encounter volume. Those inferences can differ from enrollment records. Fonteum starts from loaded public-source records instead: NPPES supplies taxonomy at enumeration ( NPI records), PECOS supplies Medicare-participation fields, and the OIG LEIE serving table held rows from the May 8, 2026 source release when checked July 12, 2026. That serving observation is not evidence of a completed monthly refresh. Where a response supplies source-date metadata, readers can compare the federal record's observed date with a billing-derived proxy; missing dates remain explicit. For compliance and credentialing, teams should evaluate the dated source record and its limits rather than treating a billing inference as equivalent.
How does Fonteum surface data gaps instead of hiding them?
Fonteum's posture is to mark silences in the federal record rather than impute over them. The clearest case is CMS SNF All Owners: 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 Fonteum's ingestion of the public CMS file. Rather than substitute an estimated percentage to make the data look complete, Fonteum flags the field with an explicit data-availability state, so an analyst knows the source itself is silent. The same discipline applies across families: CMS suppression sentinels in small-cell counts are preserved as nulls, not coerced to zero, and returned fields expose limitation notes where the source supplies them. This is the opposite of a claims model that produces a smooth, fully populated derived score — Fonteum shows the federal record as it actually is, gaps marked, which is what regulatory and diligence work requires.
Request access

See the federal source layer for yourself.

Browse the free research datasets at /research, review source documentation at /sources, or request access to scope a custom export.

See also
  • /sources → Generated source-catalog subset — documented entries with tier, publisher cadence, observed freshness where available, and limitations.
  • /care-compare/nursing-homes → CMS Care Compare NH module — star ratings, staffing, health inspection history.
  • /staffing → PBJ Daily Nurse Staffing — facility-level RN/LPN/CNA hours from the federal payroll record.
  • /data-provenance → Available source and date metadata across public responses.
  • /data → Dataset catalog, B2B export concepts, and pilot pricing.

What’s on file, by the numbers

Platform snapshot · 2026-08-04

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