The whole history,
and nothing to build
Metriport queries every available clinical network and reconciles what comes back into one patient record. It arrives in a Dashboard your team can use today, and behind an API you can build on when the workflow is ready.
Triage
The decision gets made with or without the record.Metriport gets it there in seconds.
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
Your first query to your first record
A hosted product on day one, the same data behind an API when you want it, and a record that keeps filling in without anyone re-running anything.
Query the networks on your first day, not your first sprint
Thousands of pages, read in the minutes you actually have
The same record, inside your product or your EHR
The record keeps filling in long after the first query
Scale & assurance
The same footprint from your first patient
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.
- Open source
Support
Working with Metriport
Time to first record
Start in the hosted Dashboard while the integration is still a plan, and move the same queries into your product when you are ready. Most teams are running queries in a sandbox within hours and in production within weeks — and when you do build, an implementation engineer from the team that builds Metriport works it with you.
Talk to the team
“We didn't need any integration support to get started. Going from demo to up and running for our clinicians took less than two weeks.”
Ghita SoulimaniChief of Staff of Product & Engineering, Color HealthOnboarding specialist
A specialist assigned to your account, who owns the approvals that stand between you and your patients' records.
- Kickoff call
- Network enrollment and agreements
- Go live
Shared channel
Message the people working on your integration in a Slack or Microsoft Teams channel opened for your account.
Customers
Cancer care, hospice referrals, virtual psychiatry.None of them built the integration.
Updates
Useful resources
Deep dives on interoperability and data quality, and the documentation a first integration is actually built against.
Support
FAQs
Use the Dashboard when your team needs a hosted patient-retrieval and review workflow. Use the Medical API when records and source updates need to appear inside your own product.
Requests are made on behalf of a covered entity with an NPI number, for a valid Treatment purpose of use. Production use adds network onboarding plus facility and patient setup, and exchange customers contribute clinical data back through the same API.
No. Availability varies by patient and source. Network Queries complete asynchronously and report source-specific status as data is processed.
Explore our platform
All our products
Where does the data come from?
Where does my team actually use it?