One integration, every record downstream
Metriport connects once to every available clinical network, normalizes it to FHIR R4, and hands it back through your own product: everything you ship to your customers rests on a complete record.
Throughput
ArcHouse integrated Metriport once.Every hospice on their platform got an hour back.
What we do
A universal API for medical records
Patient history lives across networks, HIEs, labs, and EHRs, and the raw data is inconsistent and unusable. Metriport connects to all of them and does the tedious job for you. We convert it, standardize it, deduplicate it, and deliver one clean record into the systems your teams already run. Retrieval that took weeks now takes seconds.
The patient is a 42-year-old male who is currently on multiple medications to manage various conditions. His medication regimen includes zolpidem 10 mg for sleep…
{
"resourceType": "Bundle",
"entry": [
{ "resource": { "resourceType": "Condition", … } },
{ "resource": { "resourceType": "MedicationRequest", … } },
{ "resource": { "resourceType": "Observation", … } },
…
]
}Platform
One connection, and every panel
Retrieved once per patient and kept current, then delivered through your product into the systems each of your customers' teams already works in — one integration on your roadmap rather than one per network.
Your customers query a whole panel without leaving your product
Your product, inside the chart their clinicians already open
In your own warehouse, in a schema your analysts already query
Your records show up in charts you never integrated with
Scale & assurance
The posture your customers will ask you about
Review securityReach is the network footprint, not a plan tier: the smallest account queries exactly what the largest one does. Certifications and audit reports are published in the Trust Center rather than sent on request, so your own security reviews can point at them.
- Open source
- SSO
- SCIM
Customers
EHRs, care platforms, and the companies building on top of them.The same record under all of it.
Updates
Useful resources
Deep dives on interoperability and data quality, and the documentation a platform integration is actually built against.
Support
FAQs
Medical API requests are made on behalf of a covered entity with an NPI number, for a valid Treatment purpose of use. Production access adds network onboarding plus facility and patient setup, and any approved on-behalf-of arrangement is established during that onboarding.
The national networks — TEFCA and its QHINs, Carequality, CommonWell, and eHealth Exchange — plus state and regional HIEs, EHR-direct connections, pharmacy and laboratory sources. Everything returned is normalized to FHIR R4, so one integration handles all of it.
Network participation is bidirectional: clinically relevant FHIR R4 resources and clinical documents are contributed back after encounters, through the same Medical API used to query. Exact obligations are set per organization during production onboarding.
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?