Healthcare Provider Data Platforms Compared
Side-by-side comparison of five healthcare provider data platforms — Definitive Healthcare, Verisys, Komodo Health, Trella Health, and Fonteum — across eight criteria: sourcing model, provenance transparency, federal citation, pricing, post-acute coverage, OIG exclusion monitoring, FHIR R4 API, and free public access. The dividing line is provenance: Fonteum is built on 17+ federal source families — 6.8M+ active providers and 68,055+ OIG exclusions among them — with a citable source on every field.
Platform comparison matrix
✓ = strong coverage~ = partial✗ = gap or not a product surface
| Criterion | Definitive HC | Verisys | Komodo Health | Trella Health | Fonteum |
|---|---|---|---|---|---|
| Data sourcing model | IQVIA claims + proprietary aggregation~ | OIG LEIE + credentialing data, proprietary matching~ | Medical, pharmacy, lab claims from payers~ | Medicare claims — PAC market intelligence~ | 17+ federal source families — CMS, OIG, HRSA, BLS, Census✓ |
| Field-level provenance | Methodology proprietary; not field-level cited✗ | Federal source, not field-level disclosed✗ | Claims sourcing; source lineage not externally citable✗ | Claims-derived; field provenance not published✗ | Source name + date + limitation on every field via provider_field_provenance✓ |
| Federal source citation | Federal data consumed internally; not in exports✗ | OIG LEIE sourced; citation format not exported~ | Claims-based; federal citation not surfaced✗ | CMS claims data; facility-level citation not published~ | CMS dataset IDs + federal data catalog links on every record✓ |
| Pricing model | $30K–$185K+/yr enterprise license✗ | Per-seat/entity enterprise pricing; 5-figure+ annual✗ | Six-figure enterprise license for claims access✗ | Five–six figure enterprise contracts for PAC intelligence✗ | Free public access; pilot tier from $2,500/mo✓ |
| Post-acute facility coverage | Facility counts + contact data; not direct CMS records~ | OIG exclusion focus; PAC not a core product✗ | Claims-based PAC utilization; not direct CMS facility records~ | Medicare claims PAC market intelligence~ | CMS Care Compare NH/HH/Hospice, PBJ Staffing, PECOS SNF All Owners, NH Deficiency Citations✓ |
| OIG LEIE exclusion monitoring | Not a primary product surface✗ | Core product — monthly LEIE + automated matching✓ | Not a primary product surface✗ | Not a primary product surface✗ | Monthly OIG LEIE ingest — 68,055+ excluded providers, NPI + PECOS cross-reference✓ |
| FHIR R4 API | Proprietary REST API; not FHIR-conformant✗ | Proprietary API; not FHIR-conformant✗ | FHIR conformance not published✗ | Not a primary product surface✗ | FHIR R4 US Core 6.1.0 — 5 USCDI v3 resources✓ |
| Free public data access | No public access tier✗ | No public access tier✗ | No public access tier✗ | No public access tier✗ | All research datasets free at /research — no account required✓ |
Source: Fonteum research based on publicly available product documentation as of 2026. Platform descriptions reflect the primary product positioning, not the full product surface. Accuracy of competitor descriptions may lag product updates — confirm with each vendor.
The dimension that separates compliance-grade data from market intelligence
Claims data vs primary-source records
Claims-based platforms infer provider attributes from billing patterns. That model works for utilization analytics and referral intelligence, but the source lineage is proprietary — the underlying federal record is not surfaced field-by-field. Primary-source platforms start from the enrollment and licensing record itself: CMS NPPES (6.8M+ active providers), PECOS, Care Compare, OIG LEIE (68,055+ exclusions), PBJ staffing (1.3M+ daily records), and SNF ownership (280,207 rows). The distinction matters the moment a compliance audit asks which federal record backs a specific field, and on what date it was last checked.
Field-level provenance as an audit trail
Fonteum's provider_field_provenance layer attaches source name, last-checked date, and known limitations to every rendered field. An excluded provider's OIG LEIE flag (one of 68,055+ records refreshed monthly) carries the oig.hhs.gov download date. A nursing home's staffing rating carries the CMS PBJ snapshot date; a deficiency citation (one of 418,148) keeps its B–L scope/severity code. Documented gaps — like the 82.4% missing ownership-percentage values in SNF All Owners — are flagged, not imputed. This is the audit trail that claims-derived platforms cannot provide: the federal record, not a derived score.
Open-core pricing vs enterprise license
Four of the five platforms in this comparison require enterprise contracts in the five-to-six-figure range for data access. Fonteum's public access tier — all research datasets at /research, FHIR R4 API at /api/fhir, bulk manifest at /api/v1/bulk/manifest.json — is free with no account required. The paid pilot tier adds custom scoping and methodology versioning commitments starting at $2,500/mo.
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), OIG HHS, HRSA, BLS, and Census — on each source's native cadence. NPPES refreshes weekly (6.8M+ active providers), OIG LEIE monthly (68,055+ exclusions), Care Compare and PBJ quarterly. There is no licensed claims feed and no intermediary aggregator between the federal file and the parse — the same files regulators publish are the files Fonteum reads.
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 — the field-level audit trail that separates a citable record from a derived score. Documented gaps, like the 82.4% missing ownership-percentage values in CMS SNF All Owners, are flagged rather than imputed. A 14-tuple provenance tag travels on every FHIR resource's meta.tag.
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 (manifest at /api/v1/bulk/manifest.json), and scoped pilot exports from $2,500/mo. The federal data is open; the paid tier covers only scoping, throughput, and integration support.
Platform-specific comparison pages
Fonteum vs Definitive Healthcare →
17+ federal source families vs proprietary aggregation
Fonteum vs Verisys →
OIG LEIE + NPPES + PECOS cross-reference with provenance
Fonteum vs Komodo Health →
Federal primary records vs claims aggregation
Fonteum vs Trella Health →
Direct CMS records vs claims-derived PAC intelligence
Common questions
- What is a healthcare provider data platform?
- A healthcare provider data platform aggregates and structures records about physicians, facilities, and other health-system entities — NPI and taxonomy, Medicare enrollment status, facility quality ratings, ownership, staffing, and compliance flags. The platforms in this comparison differ sharply along three axes. The first is sourcing model: federal primary sources (the enrollment, licensing, and inspection records themselves) versus claims aggregation (attributes inferred from billing) versus proprietary matching (a vendor's assembled and reconciled dataset). The second is provenance transparency: can you cite the underlying federal record for a specific field, with a source name and date, or only the platform's derived output? The third is pricing: a five- or six-figure annual enterprise license versus open access to federally sourced public data. These axes determine fit. Market-intelligence and sales teams weigh coverage and contact data; compliance, credentialing, and diligence teams weigh citability and audit trail, because in those contexts the basis of a data point can carry legal and regulatory consequences.
- How does Fonteum differ from Definitive Healthcare, Komodo Health, and Trella Health?
- Definitive Healthcare, Komodo Health, and Trella Health are built on claims data or proprietary aggregation — strong for market intelligence, utilization patterns, and referral analytics, but their source lineage is internal to the model and not citable field-by-field. Fonteum is built on 17+ federal source families: CMS NPPES (6.8M+ active providers), PECOS Medicare enrollment, Care Compare, OIG LEIE (68,055+ exclusions, monthly refresh), PBJ staffing (1.3M+ daily records across 14,537 facilities), SNF All Owners (280,207 ownership rows), NH deficiency citations (418,148 records across 14,635 facilities), HRSA, BLS, and Census. Every field surfaces the source name, last-checked date, and any limitation, written to the provider_field_provenance layer. The distinction is decisive for compliance, credentialing, and M&A diligence, where the underlying federal record must be citable in an audit trail. Many teams run both kinds of platform — a claims or market-intelligence tool for go-to-market, and Fonteum for the provenance-grade compliance and diligence record.
- Which platform has the strongest post-acute facility coverage?
- For post-acute facility identity and quality records sourced from federal primary data, Fonteum is the only platform in this comparison that ingests the direct CMS records rather than inferring from claims: 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 ACA § 6101 ownership disclosure (280,207 ownership rows across 14,425 facilities); and CMS NH Health Deficiency Citations for per-survey inspection findings (418,148 records across 14,635 facilities, with 5.59% at the actual-harm G+ threshold). Trella Health offers PAC market intelligence derived from Medicare claims — useful for referral and utilization analysis. Fonteum offers the federal facility-identity, ownership, staffing, and quality layer, joined on the CMS Certification Number so a single facility view is reproducible against the public files. The two answer different questions: claims-derived flow versus source-of-truth facility record.
- Which platform is appropriate for compliance and credentialing use cases?
- Compliance and credentialing teams typically need OIG LEIE exclusion monitoring, NPPES NPI and taxonomy checks, PECOS Medicare enrollment status, and field-level federal citations for audit trails. Both Fonteum and Verisys cover OIG LEIE, but they sit at different layers: Verisys is a credentialing workflow platform (task queues, re-credentialing schedules, CAQH integration, continuous monitoring orchestration), while Fonteum is the federal data tier those workflows consume. Fonteum provides the NPI + PECOS + LEIE cross-reference in one source-provenance graph — 6.8M+ providers joined to 68,055+ exclusion records — with explicit federal citations, last-checked dates, and the match basis on every field. That citability is the audit-trail requirement claims-based or proprietary-matching platforms typically cannot satisfy: when an auditor asks 'against which version of the federal list, on what date, and show me the record,' Fonteum answers with the OIG file and its date stamp rather than a derived verdict. A team would pair Fonteum's data with a workflow platform, not choose one instead of the other.
- How is pricing structured across these platforms?
- Four of the five platforms in this comparison — Definitive Healthcare, Verisys, Komodo Health, and Trella Health — operate on enterprise licensing, where access to the dataset generally requires an annual contract in the five- or six-figure range, often with implementation fees. That model reflects their sourcing: claims feeds and proprietary aggregation are licensed assets with real acquisition costs. Fonteum inverts the model. The underlying records are federal public works under 17 U.S.C. § 105 — NPPES, PECOS, Care Compare, OIG LEIE, and the rest are not copyrightable — so Fonteum publishes the structured, provenance-tagged versions openly at /research with no account and no API key for static CSV and JSON files. The paid pilot tier ($2,500–$5,000/mo) covers only what genuinely costs money to provide: custom export scoping, FHIR R4 API throughput for production workloads, methodology-versioning commitments, and integration support, with a 30-day no-penalty exit. You pay for scoping and throughput, not for access to the federal data itself.
- How current is the data, and how is freshness tracked?
- Fonteum ingests each of its 17+ federal source families on that source's native publication cadence and records the freshness explicitly. CMS publishes the NPPES full-replacement file weekly (6.8M+ active providers); Fonteum ingests it within roughly 48 hours and tags each snapshot with a retrieved date, a SHA-256 hash of the source file, and a methodology version. The OIG LEIE refreshes monthly (68,055+ exclusions); Care Compare and PBJ staffing publish quarterly (PBJ at 1.3M+ daily records across 14,537 facilities for the current quarter); SNF All Owners and HCRIS publish quarterly or annually. Because freshness is written to the provenance layer field-by-field, every rendered fact shows when it was last reconciled rather than presenting an undated aggregate. This is observable on the FHIR API via each resource's meta.lastUpdated field and on the /sources reference pages. Claims-derived platforms, by contrast, generally surface a model-refresh date rather than a per-field, per-source last-checked timestamp tied to the originating federal file.
- /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.