Data & Storage · Integration
FHIR
Add FHIR to your product for your customers, and give your AI agents governed access to it.
Embed a FHIR integration so your customers can connect their own FHIR server or FHIR-enabled system and work resources such as patients, encounters, observations, conditions, and medications from inside your product. Implementations differ in which resources and profiles they expose, 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 endpoint 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 FHIR endpoint so clinical records are available in your product without a bespoke build.
Read patient, encounter, and observation resources per tenant so your product works from the source of truth.
Write resources back where the connected system allows it, so a change in your product is not re-keyed.
Read the capability statement at runtime so your product adapts to what each implementation actually supports.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a patient's resources in context before answering a clinician's question, within scoped permissions.
An agent summarises recent observations for review, with every read logged and attributable.
An agent pulls newly available resources on a schedule and flags what needs attention.
Example prompt
Read this patient's observations from the last month and list the results outside the reference range.
Set up FHIR in 4 steps
- 01Open the FHIR connector from your fastn dashboard.
- 02Have each customer authorise access to their own FHIR endpoint with least-privilege scopes.
- 03Map the resources, profiles, 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 FHIR integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an FHIR integration without building it. Your customers point it at their own endpoint and credentials and work their records, datasets and fields through it, 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 FHIR update is not your on-call problem.
- One integration serves your product and your agents. The same governed FHIR 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
Epic
Oracle Health
SnowflakeOften used alongside
Tools the same teams tend to run next to FHIR, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceFHIR integration FAQ
How do I add an FHIR integration to my product?
Enable the FHIR connector in your fastn dashboard, then let each customer authenticate their own FHIR account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no FHIR client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
How is an FHIR connection configured per customer?
FHIR is a specification rather than a service you sign up for, so there is no FHIR account. Each customer supplies their own endpoint and credentials, and that connection is scoped to them, so they only ever reach their own records, datasets and fields. The per-tenant isolation works the same way it does for a vendor product.
Can AI agents use this FHIR 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 a patient's resources in context before answering a clinician's question, within scoped permissions.
Who maintains the FHIR integration?
fastn does. When FHIR 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 FHIR 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 FHIR 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 FHIR integration?
A common starting point: let each customer connect their own FHIR endpoint so clinical records are available 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 FHIR integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding FHIR does not change your per-connector cost. You can start free with 3 connected accounts.
Add FHIR to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.