metriport

Complete real-time patient context from every source that matters, transformed into relevant intelligence for your care teams and their AI agents.

Learn more »




Docs
·
Website
·
Dashboard
·
NPM

Overview

Metriport provides real-time access to medical data for 340+ million individuals across the US. Its open-source platform turns scattered patient records across all major healthcare IT systems into structured information that gives clinicians what they need, exactly when they need it, to provide the best possible care.

Metriport manages dozens of connections across all national HIEs and QHINs, state and regional HIEs, ADT networks, pharmacies, labs, and EHRs. It then matches, extracts, standardizes, deduplicates, and enriches records, and converts them into a unified data model, accessible through a single API, data warehouse, or apps directly within an EHR.

In addition to providing longitudinal patient clinical data at the point of care, Metriport offers ambient monitoring, alerting providers in real time as patients are moved through the healthcare system to assist with transitions of care. Metriport also delivers insights on top of the data, like AI medical record summarization, condition suspecting, and surfacing care gaps.

Founded in 2022 and headquartered in San Francisco, Metriport processes 4.2 billion network requests a month and returns the first structured record in under 15 seconds. Teams across care delivery, value-based programs, and health tech platforms build on Metriport, including Amazon One Medical, Strive Health, Color, Sollis Health, and Canvas Medical.

Security and Privacy

Metriport is HITRUST r2 certified, SOC 2 Type 2 certified, and HIPAA compliant. Visit our trust center to learn more about our security practices.

Platform

Metriport connects to every major source of patient data, harmonizes it into a single record, and delivers it wherever your team works - through an API, a data warehouse, apps inside your EHR, or as ready-made clinical insights.

Integrations

HIE Networks

A single Network Query reaches all four national networks - TEFCA/QHINs, Carequality, CommonWell, and eHealth Exchange.

ADT Networks

Enroll a patient once and their admissions, transfers, and discharges are pushed as they happen, from the national ADT networks (Bamboo Health, PointClickCare) and from state and regional HIEs.

Pharmacies & Labs

Medication fill history & notifications from Surescripts and PBM networks, reconciled onto the record you already query. Lab history & notifications from Quest.

EHRs

Turnkey bi-directional connections to most major EHRs that reconcile internal chart data with everything retrieved from outside it into one interactive longitudinal record.

Unified Data Platform

Harmonization Engine

Work with structured data that’s clean, standardized, and actionable - no matter the format at its source.

API

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

Data Warehouse

Run analytical queries via a single unified flattened schema applied across all of your data.

Applications

Ambient Monitoring & TCM

Real-time admission, transfer, and discharge events for enrolled patients, with the discharge summary retrieved automatically. The webhook lands in your care-management system with the encounter record already attached, so transition-of-care follow-up starts from context instead of from a search.

EHR Apps

External patient history rendered inside the chart your clinicians already have open, in EHRs like Epic, athenaOne, Practice Fusion, and Canvas.

Dashboard & iFrame

Use our apps standalone, or bake them into your homegrown EHR.

Messaging

Send and receive referrals to other providers, and send electronic case reports to public health agencies.

Insights and Analytics

Medical Record Summaries

Get an AI summary of the patient information most pertinent to you - thousands of records in a single customizable paragraph.

Condition Suspecting & Recapture

Discover conditions that should be presently diagnosed, but are not, based on a patient’s longitudinal medical record.

Care Gap Identification

Find proof of open and closed care gaps with an NCQA certified HEDIS engine.

Getting Started

Check out the links below to get started with Metriport:

**Book a Demo **

**Quickstart Guide **

**Developer Dashboard **

npm package

Repo Rundown

API

Backend for the Metriport platform.

• Dir: /packages/api
• URL: https://api.metriport.com/
• Sandbox URL: https://api.sandbox.metriport.com/

Infrastructure as Code

We use AWS CDK as IaC.

• Dir: /packages/infra

Docs

Our beautiful developer documentation, powered by mintlify ❤️.

• Dir: /docs
• URL: https://docs.metriport.com/

Contributing

Got ideas for how you can make Metriport better? We welcome community contributions!

Contribution guidelines

By making a contribution to this project, you are deemed to have accepted the Developer Certificate of Origin (DCO), agree to GitHub's Community Guidelines, and agree to the Acceptable Use Policies.

Requesting a feature, or reporting a bug

Click here to open a new issue - follow the chosen template and you're good to go.

Local Development

Monorepo

This monorepo uses npm workspaces to manage the packages and execute commands globally.

But not all folders under /packages are part of the workspace. To see the ones that are, check the root folder's package.json under the workspaces section.

To setup this repository for local development, issue this command on the root folder:

$ npm run init # only needs to be run once
$ npm run build # packages depend on each other, so its best to build/compile them all

Useful commands:

• npm run test: it executes the test script on all workspaces;
• npm run typecheck: it will run typecheck on all workspaces, which checks for typescript compilation/syntax issues;
• npm run lint-fix: it will run lint-fix on all workspaces, which checks for linting issues and automatically fixes the issues it can;
• npm run prettier-fix: it will run prettier-fix on all workspaces, which checks for formatting issues and automatically fixes the issues it can;

Semantic version

This repo uses Semantic Version, and we automate the versioning by using Conventional Commits.

This means all commit messages must be created following a certain standard:

[optional scope]: 
[optional body]
[optional footer(s)]

To enforce commits follow this pattern, we have a Git hook (using Husky) that verifies commit messages according to the Conventional Commits - it uses commitlint under the hood (config).

Accepted types:

• build
• chore
• ci
• docs
• feat
• fix
• perf
• refactor
• revert
• style
• test

Scope is optional, and we can use one of these, or empty (no scope):

• api
• sdk
• infra
• core
• shared
• utils
• scripts
• docs
• ... (usually subdirectories of ./packages)

The footer should have the issue number supporting the commit:

...
Ref: #

Commitizen

One can enter the commit message manually and have commitlint check its content, or use Commitizen's CLI to guide through building the commit message:

$ npm run commit

In case something goes wrong after you prepare the commit message and you want to retry it after fixing the issue, you can issue this command:

$ npm run commit -- --retry

Commitizen will retry the last commit message you prepared previously. More about this here.

Security

To avoid pushing secrets to the remote git repository we use Gitleaks - triggered by Husky.

From their repository:

Gitleaks is a SAST tool for detecting and preventing hardcoded secrets like passwords, api keys, and tokens in git repos.

It automaticaly scans new commits and interrupts the execution if it finds content that match the configured rules.

Example of report while trying to commit changes:

…

If you're absolutely sure there's no secret on the reported file/line, add the fingerprint to .gitleaksignore file - that will be ignored and you'll be able to commit.

API Server

First, create a local environment file to define your developer keys, and local dev URLs:

$ touch packages/api/.env
$ echo "LOCAL_ACCOUNT_CXID=" >> packages/api/.env
$ echo "API_URL=http://localhost:8080" >> packages/api/.env
$ echo "FHIR_SERVER_URL=" >> packages/api/.env # optional

Additionally, define your System Root OID. This will be the base identifier to represent your system in any medical data you create - such as organizations, facilities, patients, and etc.

Your OID must be registered and assigned by HL7. You can do this here.

By default, OIDs in Metriport are managed according to the recommended standards outlined by HL7.

$ echo "SYSTEM_ROOT_OID=" >> packages/api/.env

These envs are specific to CommonWell and are necessary in sending requests to their platform.

…

Optional analytics reporting

The API server reports analytics to PostHog. This is optional.

If you want to set it up, add this to the .env file:

$ echo "POST_HOG_API_KEY_SECRET=" >> packages/api/.env

Optional usage report

The API server reports endpoint usage to an external service. This is optional.

A reachable service that accepts a POST request to the informed URL with the payload below is required:

{
  "cxId": "",
  "cxUserId": ""
}

If you want to set it up, add this to the .env file:

$