Integrate once. Read every record.
Integrate Metriport into any workflow with a universal FHIR-native API.
Join the teams running production record retrieval through one integration.
Read customer stories
Medical API
One endpoint in, every source class out.
Consolidated FHIR, not a folder of documents
One query returns the patient's reconciled record as standard FHIR R4 resources — conditions, medications, labs, encounters — with C-CDA and PDF when you want them.
SDKs in your language
Typed TypeScript and Python SDKs, an OpenAPI spec, and public docs that hold up under evaluation.
Webhooks push as each source finishes
Network queries are asynchronous: your app gets called back as HIE, pharmacy, and lab data lands, instead of polling for it.
A sandbox seeded with test patients
Example clinical data behind a sandbox key, on its own host — so evaluation runs on realistic records and nothing real can break.
Benefits
Ship your product, not healthcare plumbing.The networks, the formats, and the retries are ours to run.
One key where there were a dozen integrations.
HIEs, pharmacies, laboratories, and ADT feeds arrive through the same authenticated API, in the same shape — so connecting a new source class is a parameter, not a project.
Tono Health called Metriport an immediate solution to patient data across health systems with varying EHRs.
Evaluation to production in days, not quarters.
The sandbox runs the whole surface on test patients the moment you have a key. When production opens, the code you evaluated is the code you ship.
Color Health went from dashboard pilot to full API production in 2 weeks.
Complete enough to change the decision.
A full longitudinal history reads differently from a referral face sheet. What the record carries — and the summary on top of it — is what your clinicians decide with.
ArcHouse found a previously missed cardiac condition in a full-history review — not mentioned by the family, and not on the referral face sheet.
How it works
Create a facility, add a patient, query, read the record.A sandbox key runs all four this afternoon.
Create a facility
Where your patients receive care. Everything below hangs off it.
Add a patient
The more demographics you provide, the better the match rate — nicknames, old addresses, and prior names all help.
Start a network query
Asynchronous by design: sources finish on their own clock, and each one calls your webhook as its data lands.
Read the consolidated record
Production access needs a covered entity, an NPI, and a Treatment purpose of use. The sandbox needs none of them.
Customers
Integrated in days, load-bearing for years.Hospice, cancer care, and consumer scale — one API under all three.
Support
FAQs
Access to the Medical API requires you to make requests on behalf of a covered entity with an NPI number, for a valid Treatment purpose of use. The sandbox has no such requirement.
FHIR R4 is primary. C-CDA is available for clinical documents, and PDF for medical record summaries.
No. Network queries are asynchronous and Metriport emits network-query.* webhook events as each source class — HIE, pharmacy, lab — finishes processing.
Explore our platform
All our products
Where does the data come from?
What shape is it in once we have it?
Where does my team actually use it?