{ "@context": "https://schema.org", "@type": "Article", "headline": "Fonteum vs Definitive Healthcare — 12-dimension procurement comparison", "datePublished": "2026-05-29", "author": { "@type": "Organization", "name": "Fonteum, Inc." }, "publisher": { "@type": "Organization", "name": "Fonteum, Inc." }, "mainEntityOfPage": "https://fonteum.com/compare", "fonteum:dimensions": [ { "name": "Provenance contract", "description": "Can every field cite its source row and snapshot?", "fonteum_evidence": "Every rendered field carries a 14-tuple provenance record tying it to a source row, a snapshot date, and a SHA-256 digest.", "fonteum_proof_url": "/data-provenance", "competitors": { "definitive_healthcare": "Aggregation methodology described at a high level; field-level source lineage is not publicly documented.", "iqvia_onekey": "Reference-data linkage across many sources; per-field source citation is not publicly documented.", "healthverity": "Identity-resolution lineage is proprietary; per-field provenance is not publicly documented.", "diy": "Provenance is whatever you build — the raw NPPES file ships with no field-level contract." } }, { "name": "Snapshot immutability", "description": "Are historical snapshots retained, addressable, and citable?", "fonteum_evidence": "Historical snapshots are retained, content-addressed by SHA-256, and carry a citable identifier so a past state is recoverable.", "fonteum_proof_url": "/snapshots", "competitors": { "definitive_healthcare": "Point-in-time snapshots are not publicly documented as a queryable, content-addressed artifact.", "iqvia_onekey": "Reference data is refreshed in place; immutable historical snapshot access is not publicly documented.", "healthverity": "Longitudinal data is retained, but a public snapshot-addressing scheme is not documented.", "diy": "CMS publishes weekly full-replacement files; retaining and addressing prior versions is on you." } }, { "name": "Methodology versioning", "description": "Is the scoring methodology pinned to a published version?", "fonteum_evidence": "Each scoring methodology is a pinned, published version string (for example nsa-compliance/v1) with its own methodology page.", "fonteum_proof_url": "/methodology", "competitors": { "definitive_healthcare": "Scoring and modeling methodology is proprietary; a public version-pinning scheme is not documented.", "iqvia_onekey": "Reference methodology is proprietary; published version identifiers are not documented.", "healthverity": "Matching methodology is proprietary; a public version-pinning scheme is not documented.", "diy": "No methodology layer — you define, document, and version your own." } }, { "name": "Federal source coverage", "description": "How many primary federal sources are cross-resolved?", "fonteum_evidence": "22 federal source families are cross-resolved on a shared identity backbone (NPI and CCN), all primary-source and explicitly cited.", "fonteum_proof_url": "/sources", "competitors": { "definitive_healthcare": "Combines federal data with commercial and claims sources; a primary-federal-source count is not the public framing.", "iqvia_onekey": "Built on IQVIA's reference universe plus licensed sources; federal-source cross-resolution is not the framing.", "healthverity": "Centered on claims and consumer data; federal provider-source coverage is not the public framing.", "diy": "You choose and join each federal source yourself; cross-resolution is your engineering cost." } }, { "name": "Update cadence", "description": "How often is the data refreshed, and is the date on the field?", "fonteum_evidence": "Each source refreshes on its native cadence — NPPES weekly, LEIE monthly, Care Compare and PBJ quarterly — and the last-checked date is on every field.", "fonteum_proof_url": "/sources", "competitors": { "definitive_healthcare": "Regular updates are cited; per-dataset cadence is not published field-by-field.", "iqvia_onekey": "Continuous reference-data maintenance; per-source cadence is not published.", "healthverity": "Claims refresh on data-partner cadence; per-source dates are not surfaced per field.", "diy": "Cadence is whatever your pipeline runs; CMS publishes each file on its own schedule." } }, { "name": "Cryptographic attestation", "description": "SLSA-style build provenance, SHA-256, signed artifacts?", "fonteum_evidence": "Snapshots carry SHA-256 digests and Ed25519 witness co-signatures; integrity headers can ship on responses.", "fonteum_proof_url": "/trust", "competitors": { "definitive_healthcare": "Cryptographic attestation of data artifacts is not publicly documented.", "iqvia_onekey": "Cryptographic attestation of data artifacts is not publicly documented.", "healthverity": "Cryptographic attestation of data artifacts is not publicly documented.", "diy": "None unless you build a signing and attestation layer yourself." } }, { "name": "License clarity", "description": "Are commercial-use rights and embargo flags stated?", "fonteum_evidence": "Underlying records are federal public works (17 U.S.C. § 105); commercial-use and embargo flags are stated per source.", "fonteum_proof_url": "/trust", "competitors": { "definitive_healthcare": "Commercial enterprise license; terms are set per contract and not publicly posted.", "iqvia_onekey": "Licensed commercial data; terms are set per contract and not publicly posted.", "healthverity": "Licensed data with privacy constraints; terms are set per contract and not publicly posted.", "diy": "Federal files are public domain, but you own license review for anything you layer on." } }, { "name": "API quality", "description": "Stripe-grade docs, OpenAPI, SDKs, sane rate limits?", "fonteum_evidence": "FHIR R4 US Core 6.1.0 API with three-column Stripe-style docs, an OpenAPI surface, and an unauthenticated sandbox key.", "fonteum_proof_url": "/api", "competitors": { "definitive_healthcare": "A REST API is available to enterprise customers; it is not FHIR-conformant and public docs are gated.", "iqvia_onekey": "API access is delivered through OneKey integrations; a public OpenAPI and open docs are not posted.", "healthverity": "API and data-delivery options exist for customers; a public OpenAPI is not openly posted.", "diy": "No API — you parse flat files and stand up your own service." } }, { "name": "Agent / MCP support", "description": "First-class MCP server and pre-built agent integrations?", "fonteum_evidence": "First-class MCP server at /.well-known/mcp.json, a published agent card, and an integration surface for AI agents.", "fonteum_proof_url": "/for/ai-agents", "competitors": { "definitive_healthcare": "An MCP server or agent-native integration is not publicly documented.", "iqvia_onekey": "An MCP server or agent-native integration is not publicly documented.", "healthverity": "An MCP server or agent-native integration is not publicly documented.", "diy": "None unless you build an MCP server over your own pipeline." } }, { "name": "Reproducibility", "description": "Can a third party recreate a published claim?", "fonteum_evidence": "Published research ships CSV and JSON downloads, a methodology, and snapshot identifiers, so a third party can recreate any claim.", "fonteum_proof_url": "/research", "competitors": { "definitive_healthcare": "Reports are derived from proprietary models; independent recreation of a published figure is not supported.", "iqvia_onekey": "Outputs are derived from proprietary reference data; independent recreation is not supported.", "healthverity": "Outputs are derived from proprietary linkage; independent recreation is not supported.", "diy": "Fully reproducible in principle — you own the whole pipeline, and its drift." } }, { "name": "Pricing transparency", "description": "Public pricing, or opaque enterprise sales?", "fonteum_evidence": "Public pricing: free research and datasets, with a pilot tier published from $2,000/mo at /pricing.", "fonteum_proof_url": "/pricing", "competitors": { "definitive_healthcare": "Opaque enterprise sales; pricing is by quote, with third-party reports citing five- to six-figure annual licenses.", "iqvia_onekey": "Enterprise sales; pricing is by quote and not publicly posted.", "healthverity": "Enterprise sales; pricing is by quote and not publicly posted.", "diy": "The data is free, but staff time and infrastructure are the real, recurring cost." } }, { "name": "Time-to-first-result", "description": "From signup to the first successful query.", "fonteum_evidence": "An unauthenticated sandbox key returns a live federal record on the first call — minutes from landing on /api.", "fonteum_proof_url": "/api", "competitors": { "definitive_healthcare": "Gated by a sales process and onboarding; the first query follows a signed contract.", "iqvia_onekey": "Gated by sales and integration; the first query follows onboarding.", "healthverity": "Gated by sales and a data-governance review; the first query follows onboarding.", "diy": "Days to weeks — download, parse, model, and host before the first query returns." } } ] }