Particle Health
Particle Health is a healthcare data interoperability platform that aggregates patient medical records from across the US healthcare system into a single RESTful API. Particle is connected to all three nationwide health information exchange networks (Carequality, CommonWell, eHealth Exchange), TEFCA / QHIN partners, state HIEs (Healthix in New York, Manifest MedEx in California), and Surescripts for pharmacy data. The platform exposes patient demographics, clinical resources, and document retrieval via FHIR R4, C-CDA, Flat, and Deltas formats, layered with deduplication, normalization, AI summarization (Particle Snapshot), real-time encounter and transition alerts (Particle Signal), and longitudinal patient journey tracking (Particle Navigator). Customer segments include value-based care organizations, payers, health systems, primary and specialty providers, and digital health developers.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Particle Health the way a machine reads it — 72 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Particle Health scores 61.3/100 (strong), with a separate agent-readiness read of 34/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Particle Health's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/particle-health/"
title="Particle Health on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/particle-health.svg"
alt="Particle Health Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/particle-health/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/particle-health/"
title="Particle Health on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/particle-health/card.svg"
alt="Particle Health Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Particle Health
Each block below is one kind of artifact we hold for Particle Health. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 17
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Particle Health Authentication API
OAuth 2 client-credentials JWT issuance.
Particle Health Batches API
Batch query orchestration over patient cohorts.
Particle Health CCDA API
C-CDA clinical document retrieval.
Particle Health Deltas API
Incremental change retrieval since a previous query.
Particle Health Documents API
Document upload, retrieval, and deletion.
Particle Health FHIR API
FHIR R4 resource search and read.
Particle Health Files API
Query result file download.
Particle Health Flat API
Flat (normalized columnar) clinical data domains.
Particle Health HL7v2 API
HL7v2 ADT messages.
Particle Health NetworkParticipants API
Directory search over connected network organizations.
Particle Health Notifications API
Project-level webhook notification configuration.
Particle Health Patients API
Patient demographic registration and lookup.
Particle Health Projects API
Project and service-account management.
Particle Health ProviderMap API
Patient provider mapping across the network.
Particle Health Queries API
One-time network query orchestration.
Particle Health Signal API
Real-time encounter, transition, and ADT alerts.
Particle Health Subscriptions API
Patient subscription management for Signal.
Scroll within the panel for all 17 ·
Postman Collections 17
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Scroll within the panel for all 17 ·
Open Collections 19
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONParticle Health Authentication API
OPEN COLLECTIONParticle Health Authentication Batches API
OPEN COLLECTIONParticle Health Authentication CCDA API
OPEN COLLECTIONParticle Health Authentication Deltas API
OPEN COLLECTIONParticle Health Authentication Documents API
OPEN COLLECTIONParticle Health Authentication FHIR API
OPEN COLLECTIONParticle Health Authentication Files API
OPEN COLLECTIONParticle Health Authentication Flat API
OPEN COLLECTIONParticle Health Authentication HL7v2 API
OPEN COLLECTIONParticle Health Authentication NetworkParticipants API
OPEN COLLECTIONParticle Health Authentication Notifications API
OPEN COLLECTIONParticle Health Authentication Patients API
OPEN COLLECTIONParticle Health Authentication Projects API
OPEN COLLECTIONParticle Health Authentication ProviderMap API
OPEN COLLECTIONParticle Health Authentication Queries API
OPEN COLLECTIONParticle Health Authentication Signal API
OPEN COLLECTIONParticle Health Authentication Subscriptions API
OPEN COLLECTIONParticle Health API
OPEN COLLECTIONScroll within the panel for all 19 ·
Arazzo Workflows 5
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Particle Health ADT Event Subscription
Register a patient, subscribe to encounter (ADT) notifications, trigger a sandbox event, and retrieve the resulting HL7 v2 messages.
ARAZZOParticle Health Clinical Document Exchange
Submit a clinical document to the network, then retrieve it and list all documents on file for the patient.
ARAZZOParticle Health FHIR R4 Resource Query
Create a FHIR Patient, run a FHIR-native network query, poll for completion, then search and read individual US Core resources.
ARAZZOParticle Health Network Provider Discovery
Register a patient, run a network query, then discover which providers and organizations hold records for that patient.
ARAZZOParticle Health National Patient Record Retrieval
Authenticate, register a patient demographic, run a national query across the health information networks, poll until the query completes, then collect the aggregated clinical r...
ARAZZOMCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Particle Health MCP Server
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Particle Health Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Particle Health Finops
FINOPSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Particle Health Webhooks
ASYNCAPISemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Particle Health Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Particle Health API Rules
SPECTRALJSON Schema 2
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Particle Health Patient
JSON SCHEMAParticle Health Query
JSON SCHEMASecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Particle Health — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 4
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 9
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 9 ·
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 7
Authentication, authorization, and security posture
Scroll within the panel for all 7 ·
Learn 1
Tutorials, courses, talks, and written guidance
Operate 8
Status, limits, changes, and where to get help
Scroll within the panel for all 8 ·
Commercial 4
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 4
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/particle-health · machine-readable index on apis.io
This is an independent, third-party profile of Particle Health, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.