Data & Storage · Integration
Metriport
Add Metriport to your product for your customers, and give your AI agents governed access to it.
Embed a Metriport integration so your product can reach patient medical records through one API instead of integrating with health information networks yourself. Metriport retrieves records from the major United States networks and normalises them into FHIR resources, so your product maps a consistent shape once rather than per source. Each customer connects their own account, so every request and every document read is scoped to that tenant and logged, which is the minimum bar when the data is health data. Pagination and throttling are handled for you, and the same governed connection gives your AI agents scoped, audited read access.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own Metriport account so your product can query patient medical records without integrating each network yourself.
Request a patient's consolidated record and read it back as FHIR resources your product maps once.
Pull retrieved documents per tenant so a clinician can see the source behind a summary.
Keep every read scoped and logged per tenant, which is what handling health data requires.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent summarises a patient's history from the customer's own Metriport data within scoped permissions.
An agent finds the document behind a diagnosis or medication so a human can verify it, with each read audited.
An agent checks whether a requested record has arrived and reports what is still outstanding.
Example prompt
Summarise this patient's medication history from Metriport and cite the documents it came from.
Set up Metriport in 4 steps
- 01Enable the Metriport connector in your fastn dashboard.
- 02Have each customer authorise their own Metriport account so calls run under their credentials.
- 03Map the patient, document and FHIR resource fields your product uses.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Metriport integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Metriport integration without building it. Your customers connect their own Metriport account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Metriport update is not your on-call problem.
- One integration serves your product and your agents. The same governed Metriport connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Compare with
FHIR
Epic
Oracle HealthOften used alongside
Tools the same teams tend to run next to Metriport, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceMetriport integration FAQ
How do I add a Metriport integration to my product?
Enable the Metriport connector in your fastn dashboard, then let each customer authenticate their own Metriport account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Metriport client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Metriport account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Metriport account and only ever sees their own records, datasets and fields. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Metriport integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent summarises a patient's history from the customer's own Metriport data within scoped permissions.
Who maintains the Metriport integration?
fastn does. When Metriport changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the Metriport integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large Metriport reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the Metriport integration?
A common starting point: connect their own Metriport account so your product can query patient medical records without integrating each network yourself. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Metriport integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Metriport does not change your per-connector cost. You can start free with 3 connected accounts.
Add Metriport to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.