Skip to content
buildbay.
Metriport logo

Metriport

metriport · API tools

GitHub stars

787
—Collecting 30d data

Stats updated

786 stars on Sep 27 to 787 stars on Oct 1, up 1.5 measured star snapshots

What is Metriport?

Metriport connects healthcare applications to national, state, regional, pharmacy, laboratory, ADT, and EHR data sources. It matches patient records, converts source formats into a unified FHIR model, removes duplication, and delivers the resulting clinical context through APIs, warehouse tables, dashboards, or embedded applications.

Metriport is an open-source universal API for healthcare data. It helps organizations retrieve patient medical data from clinical networks and supports FHIR, C-CDA, and PDF formats.

Core capabilities

  • Query patient records across major healthcare data networks
  • Harmonize C-CDA, HL7v2, PDF, and FHIR data into FHIR R4
  • Deliver clinical context through APIs, warehouses, dashboards, and EHR apps

Many healthcare networks, one patient record

A single integration reaches national and regional exchange networks, ADT feeds, pharmacies, laboratories, and EHR connections. Metriport matches patient identities and consolidates the returned material so applications do not need a separate interface and record model for every source.

  • HIE
  • ADT
  • pharmacies
  • EHR

Harmonized data at the point of work

The platform converts clinical source formats into FHIR R4, standardizes and deduplicates the result, and can deliver it through the Medical API, normalized warehouse tables, dashboards, or embedded EHR applications. Teams can also subscribe to patient movement events and build summaries or analytics on the unified record.

  • FHIR R4
  • API
  • data warehouse
  • clinical insights

Where it fits

Use cases

  1. 01

    Retrieve a longitudinal patient record

    Create a patient, query available healthcare networks, and receive standardized clinical data through a webhook or API so care teams can review records gathered beyond their own organization.

  2. 02

    Normalize outside clinical documents

    Convert C-CDA, HL7v2, PDFs, and existing FHIR resources into consistent FHIR R4 data, then deduplicate and enrich medical concepts before downstream systems consume them.

  3. 03

    Embed outside context in a care workflow

    Present retrieved records, admission and discharge events, summaries, or care-gap insights through an existing EHR, a standalone dashboard, a warehouse, or a custom healthcare application.