Data & Storage · Integration
Epic
Add Epic to your product for your customers, and give your AI agents governed access to it.
Embed an Epic integration so your customers can read their own clinical records from inside your product, including patients, encounters, appointments, observations, and results, through Epic's FHIR-based APIs. Every health system configures its deployment differently, so resource and field mapping is configuration per customer rather than code, and access is scoped per tenant with every call logged. fastn handles per-customer authorisation and API upkeep, so onboarding another health system does not become a release for you.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Epic environment so clinical data appears in your product without a bespoke build.
Read patient and encounter records per tenant so your product works from the source of truth rather than an export.
Read appointment and scheduling data so your product plans around what is already booked.
Refresh reads on a schedule or react to changes so your product is not making decisions on stale records.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads records for a patient in context before answering a clinician's question, within scoped permissions.
An agent summarises recent encounters for review, with every read logged and attributable.
An agent pulls newly available results on a schedule and flags what needs attention.
Example prompt
Summarise this patient's encounters in the last six months and list the results recorded for each.
Set up Epic in 4 steps
- 01Open the Epic connector from your fastn dashboard.
- 02Have each customer authorise access to their own Epic environment with least-privilege scopes.
- 03Map the resources and fields your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Epic integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Epic integration without building it. Your customers connect their own Epic 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 an Epic update is not your on-call problem.
- One integration serves your product and your agents. The same governed Epic 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
Oracle Health
FHIR
SnowflakeOften used alongside
Tools the same teams tend to run next to Epic, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceEpic integration FAQ
How do I add an Epic integration to my product?
Enable the Epic connector in your fastn dashboard, then let each customer authenticate their own Epic account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Epic client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Epic account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Epic 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 Epic 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 reads records for a patient in context before answering a clinician's question, within scoped permissions.
Who maintains the Epic integration?
fastn does. When Epic 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 Epic 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 Epic 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 Epic integration?
A common starting point: let each customer connect their own Epic environment so clinical data appears in your product without a bespoke build. 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 Epic integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Epic does not change your per-connector cost. You can start free with 3 connected accounts.
Add Epic to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.