HL7

Enable the HL7 connector in your fastn dashboard, then let each customer authenticate their own HL7 account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no HL7 client code in your app and no per-customer branch in your codebase. Setup is 4 steps.

Yes. Every connection is scoped to the individual customer, so each authorises their own HL7 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.

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 recent messages to ground an answer in the customer's own data, within scoped permissions.

fastn does. When HL7 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.

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.

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.

A common starting point: send messages from their own interface into your product, mapped to the fields you need. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.

It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding HL7 does not change your per-connector cost. You can start free with 3 connected accounts.