Healthcare IT & EHRs | Metriport

Metriport raises $26 million to give clinicians insight at the point of care

Metriport connects to every available clinical network, normalizes what comes back to FHIR R4, and returns one accurate, comprehensive record through your own product. Everything you ship to your customers, AI tools included, rests on that record.

Read the docs
Book a demo

ArcHouse integrated Metriport once. Every hospice on their platform got an hour back.

  1. 1 hour off the average referral, at each hospice. Their patients start care sooner.

A universal platform 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.

Networks

C-CDA XML · PDF

State & regional HIEs

C-CDA · ADT

Pharmacies & labs

HL7v2

EHRs

C-CDA · FHIR

AI summary

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.

Patient record

FHIR R4

{
  "resourceType": "Bundle",
  "entry": [
    { "resource": { "resourceType": "Condition", … } },
    { "resource": { "resourceType": "MedicationRequest", … } },
    { "resource": { "resourceType": "Observation", … } },
    …
  ]
}

One connection, and every chart

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

Reach 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.

340M+ patients reachable
750K+ providers
FHIR R4 normalized output
AICPA SOC 2
SOC 2 Type II
HITRUST r2
HIPAA Compliant

Fully Encrypted

AES-256 encryption at rest and in transit across the platform.

Audit logging

End-to-end audit trails and provenance for data access across the platform.

Access controls

Role-based access and least-privilege controls for patient data and operations.

EHRs, care platforms, and the companies building on top of them. The same record under all of it.

Clinical depth at consumer scale

46 million+ Patient records retrieved 20 seconds To skim a full history.

“Medical record reconciliation at scale was the problem, and we wanted to find the best possible offering in the market.”
— Brian Shi, Director of Product

An EHR retires its interoperability patchwork

3.5 minutes To pull a full record.

“Metriport provides a window into parts of the patient's story that providers wouldn't otherwise know or couldn't easily find out.”
— Andrew Hines, Founder and Chief Technology Officer

Data going back out, not just coming in

One record Out of many fragmented sources 72 hours To reach a discharged member.

“Having a clinical intelligence layer ahead of time truly enables us to deliver a more informed and holistic patient experience.”
— David Duel, Founder and CEO

Useful resources

Deep dives on interoperability and data quality, and the documentation a platform integration is actually built against.

FAQs

  1. Our customers are the covered entities, not us. How does that work?
    Medical API requests are made on behalf of a covered entity with an NPI number, for a valid Treatment purpose of use.

  2. Which networks does one integration actually reach?
    The national networks — TEFCA and its QHINs, Carequality, CommonWell, and eHealth Exchange.

  3. What does our platform have to contribute back?
    Network participation is bidirectional: clinically relevant FHIR R4 resources and clinical documents are contributed back after encounters.