Particle Health
Health data interoperability API with an AI enrichment layer on top. The base capability is retrieval: a single bidirectional API querying national health information networks including CommonWell, Carequality, and eHealth Exchange plus ADT feeds and prescription data, reaching a reported 320 million patient records across more than 70,000 healthcare organizations, with the company stating it locates roughly 90 percent of patients nationally. The Particle Insights Platform is where the AI sits, built on three stated pillars: enhanced data quality through parsing that surfaces critical elements, enrichment by integrating additional sources, and usability through normalization and deduplication. Snapshot applies AI powered summarization to condense retrieved records, and the company has built an AI discharge summary product. Its published engineering writing is unusually candid about the underlying problem, describing why template based CCDA parsing loses clinically important medications and why identity resolution rather than event delivery is the real failure mode in discharge alerting. Buyers are health technology companies, telehealth and remote monitoring vendors, care management organizations, and payers rather than provider organizations directly.
Capability Axes
The durable asset is the interoperability network: connections to national health information networks, identity resolution, and record retrieval at a reported 320 million record scale. That is infrastructure, not inference. The AI is a real and growing layer on top, covering summarization through Snapshot, discharge summary generation, and model based clinical document parsing that the company argues outperforms template based CCDA extraction. A customer buys the data access first and the enrichment second, which is what this grade describes. This is the same pattern as Helix, where the network is the moat and the models are the layer.
Unusually candid engineering disclosure for a data vendor. Published writing explains why template based CCDA parsing drops clinically important medications and what was built instead, and argues that discharge alerting fails on identity resolution rather than event delivery. Naming your own failure modes in public is a stronger transparency signal than a capability list. Held back from A because no model detail, benchmark, or accuracy measurement for the summarization and parsing products was retrieved.
The company operates under the interoperability and information blocking rules and handles the query attribution requirements that health information networks impose, which is a real compliance function. However the platform explicitly positions retrieved clinical data as a resource for training AI models, and no disclosure was retrieved covering consent scope for that secondary use, de identification standard, or customer controls over it. For a vendor whose product is bulk access to identified clinical records, that is the disclosure a buyer most needs and it is absent.
This is the product and the coverage is specific: a single bidirectional API spanning CommonWell, Carequality, and eHealth Exchange plus ADT feeds and prescription data, reaching a reported 70,000 healthcare organizations and locating roughly 90 percent of patients nationally, returned in structured FHIR. Particle for Platforms additionally handles the query permission and attribution burden for health IT vendors who lack a direct treatment relationship with patients, which is a genuine regulatory constraint rather than a feature.
No public pricing. Contact the vendor. Sold to health technology companies, payers, and care organizations, with a platform tier for health IT vendors serving many downstream clients. Buyers should establish whether pricing is per query, per patient record, or subscription, since retrieval volume drives cost in very different ways under each.
Pricing
Vendor-published figures are labeled as such. Figures labeled “Estimated” are derived from third-party sources and have not been confirmed by the vendor.
| Entry Price | Pricing Basis | BAA Tier | Implementation | Source |
|---|---|---|---|---|
|
Contact the vendor
|
API access agreements; separate platform tier for health IT vendors | — | — | Vendor Published |
No rate card published. Sold to health technology companies, telehealth and remote monitoring vendors, care management organizations, and payers, with a separate platform tier for health IT vendors serving many downstream clients. Establish the pricing unit before committing: per query, per patient record retrieved, and flat subscription behave very differently for a product whose value scales with retrieval volume, and a per query model can make broad panel searches prohibitively expensive.