Metriport

Give teams patient records without building a new interface.

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

Join the teams putting complete patient records in front of the people delivering care.

Read customer stories
Kivo Health
Canvas Medical
Healthie
Sollis Health
Notable
Brightside Health
Qventus
General Medicine
In every deployment
Network Queries today0123456789,012345678901234567890123456789Patients reachable012345678901234567890123456789M+Embedded views0123456789Token lifetime01234567890123456789h

Dashboard & iFrame

One less thing to build, host, staff, or secure.

The whole record, inside the chart your team already maintains

Conditions, medications, labs, and encounters, reconciled from every connected network and rendered in your own product.

Go live on day one

Create facilities and patients, run a Network Query, and review consolidated records in the hosted Dashboard.

Transitions of Care, without a second integration

Give authorized users a focused view of admissions, transfers, and discharges as they happen.

Credentials never reach the browser

Your API key mints tokens server-side. Each is scoped to one environment and expires in up to ten hours.

Benefits

Get to production fast, without the worry.Metriport handles the networks and formats, you just read the record.

2 weeksColor Health, demo to full production

We didn't need any integration support to get started.
Ghita Soulimani, Chief of Staff of Product and Engineering, Color Health

Start from the story, not the stack of documents.

The AI summary puts the history up front, so a clinician gets the picture without working through the hundreds of pages it was assembled from.

See how summaries work

Your care team can run it without an engineer.

Nothing to build and nobody to wait for. The people who need the records set them up and pull them themselves, on the same account your API build lands on later.

EDS Clinic started on the Dashboard with no engineering team, and moved visit prep from days to same-day.

Read the quickstart

Put it inside your own product when you’re ready.

Embed Patient View or Transitions of Care behind a token your own backend mints, as a redirect or an iframe. You decide where it sits, who can open it and which patient they see, with no record viewer for you to build or maintain.

Read the embed docs

How it works

The whole embed is three moves.Or skip all three and open the Dashboard.

  1. Generate an embed token from your backend

    The API key stays on your server. The token expires on its own, and a leaked URL dies with it.

  2. Build the embedded app URL

    Tokens do not cross environments. Sandbox is seeded with test patients, so nothing real can break.

  3. Render it in an iframe

    Everything inside the frame is Metriport's. Yours is one tag, or a redirect to the same URL.

Customers

Open it on its own, or open it inside your chart.Same records, same summary, either way in.

Support

FAQs

Patient View and Transitions of Care are documented for redirect or iframe use.

Generate time-limited embed tokens on your backend with the Medical API key. Never expose the API key in browser code.

Tokens and URLs are environment-specific. A token generated for one environment cannot be used in the other. An iframe avoids a native SMART-app deployment, but organizational review may still apply.

Put records in front of your team this week.