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 a — including active NPPES provider records and OIG exclusions among them — with source metadata shown where available.
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~ | the documented federal-source catalog — 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✗ | Available source, date, and limitation fields from provider_field_provenance; fields may be null✓ |
| 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 and federal catalog links where the source response supplies them✓ |
| 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✗ | Loaded May 8, 2026 OIG LEIE release; NPI + PECOS cross-reference where identifiers support it✓ |
| 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 exposes source, date, and limitation metadata where populated; fields may be null. An excluded provider's OIG LEIE flag (one of 68,055+ records from the loaded May 8, 2026 release) carries the oig.hhs.gov download date. A nursing home's staffing rating can carry 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
Load named public files and report their observed dates
Fonteum loads named public files from CMS, OIG HHS, HRSA, BLS, Census, and other publishers. Publisher cadence and loaded-source date are separate fields; the July 12, 2026 production observations show that several serving tables lag their publishers.
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. Documented gaps, like the 82.4% missing ownership-percentage values in CMS SNF All Owners, are flagged rather than imputed. FHIR resources expose provenance tags where populated, and coverage varies by resource.
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 →
Documented federal-source catalog 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 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. Fonteum's includes CMS NPPES, PECOS, Care Compare, OIG LEIE, PBJ staffing, SNF All Owners, NH deficiency citations, HRSA, BLS, and Census. Returned fields expose source, date, and limitation metadata where supplied; fields may be null. Active production registry status does not establish loaded, complete, or fresh coverage.
- 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 ( daily records across facilities, CY2025Q2); PECOS SNF All Owners for ACA § 6101 ownership disclosure ( ownership rows across facilities); and CMS NH Health Deficiency Citations for per-survey inspection findings ( records across facilities, with 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 teams use NPPES for NPI administrative fields, PECOS for Medicare enrollment, and OIG LEIE for exclusions. The NPPES and LEIE source volumes are active NPI records and exclusion records, but those rows are not joined wholesale: an exact NPI cross-reference is possible only where LEIE or PECOS publishes the same identifier. Name-based screening is a separate process with its own limitations. Fonteum is the source-data tier; Verisys is a credentialing workflow platform.
- 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?
- Each publisher has its own cadence, but configured cadence is not proof of a completed Fonteum refresh. In production on July 12, 2026, the loaded NPPES table's newest system timestamp was June 10; PECOS carried a June 18 source date; OIG LEIE carried May 8; the loaded Care Compare facility modules carried May 7; and PBJ's newest source date was June 30, 2025. Public copy reports source release or observation dates where available rather than promising a 48-hour or daily ingest.
- /sources → Documented source catalog with publisher cadence and limitations where recorded; catalog presence is not loaded coverage.
- /data-provenance → Available source and date metadata across public responses.
- /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.