API | Metriport

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

Integrate once. Read every record.

Integrate Metriport into any workflow with a universal FHIR-native API.

YOUR APP

METRIPORT

CONSOLIDATED FHIR

AI brief · Binary resource

{
  "resourceType": "Binary",
  "id": "1234",
  "contentType": "text/plain",
  "data": "VGhlIHBhdGllbnQgaXMgYSA0Mi15ZWFyLW9sZCBtYWxl..."
}

WEBHOOK EVENTS

Webhook message types

network-query.hie
network-query.pharmacy
network-query.lab
network-query.hie.first-data-ready

ADT FEED

patient.discharge

{
  "meta": { "type": "patient.discharge" },
  "payload": {
    "patientId": "metriport-patient-uuid",
    "url": "<presigned-download-url>"
  }
}

Join the teams running production record retrieval through one integration.

Medical API

One endpoint in, every source class out.

POST /medical/v1/patient/{id}/consolidated/query

Consolidated FHIR, not a folder of documents

One query returns the patient's reconciled record as standard FHIR R4 resources: conditions, medications, labs, encounters. C-CDA and PDF come back too 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.

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.

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.

How it works

Four calls. The whole record.

  1. Create a facility - Where your patients receive care. Everything below hangs off it.
  2. Add a patient - The more demographics you provide, the better the match rate. Nicknames, old addresses, and prior names all help.
  3. Start a network query - Asynchronous by design: sources finish on their own clock, and each one calls your webhook as its data lands.
  4. 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.

Metriport's API is very well-documented and user-friendly. We went from evaluation to deployment in a few days.

FAQs

  1. What do I need to access the Medical API in production? 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.
  2. What formats does patient data come back in? FHIR R4 is primary. C-CDA is available for clinical documents, and PDF for medical record summaries.
  3. Do I have to poll for query results? No. Network queries are asynchronous, and Metriport emits network-query.* webhook events as each source class (HIE, pharmacy, lab) finishes processing.