Epic Fax Integration — Sending Epic-Generated Documents via Our API
Epic sites already fax through their own systems, but when a document generated in Epic needs to go out through Send FAX Mail — a referral, a records release, an order — the connection runs through Epic's interface layer, not a plugin from us. There is no Send FAX Mail module in Epic's Connection Hub or Showroom, and we do not claim one. Epic's Bridges interfaces and Interconnect web services can hand a generated document to a service that POSTs it to our REST API.
Plan requirement
The REST API and webhooks this depends on are part of the Business ($79.99/mo) and Enterprise ($169.99/mo) plans, which include HIPAA terms. A covered entity that transmits PHI must e-sign a BAA before sending and before provisioning a number. Epic-side interface work (Bridges, Interconnect, or an integration engine) is governed by the health system's own Epic environment and change process.
How it works
Epic does not call arbitrary external APIs directly, so the bridge is the interface layer the health system already operates. A document Epic renders — through a print-to-interface route, a Bridges HL7 message carrying a document reference, or an Interconnect web service — is picked up by an integration engine or a service the IT team runs. That service holds the bearer key and POSTs the document to /v1/faxes with the recipient number, sending PHI-bearing files inline rather than over a public link. The fax id returns for reconciliation into the chart or a work queue, and a registered webhook reports delivered or failed. The send runs the same gated pipeline as the dashboard, so BAA, quota, and number rules all hold.
What you can do
- ✓Send an Epic-generated referral, order, or records release to /v1/faxes
- ✓Bridge Epic via its interface layer — Bridges, Interconnect, or an engine
- ✓Keep PHI off public links by sending document bytes inline
- ✓Reconcile the returned fax id back into the chart or a work queue
- ✓Gate sending behind a signed BAA for entities that transmit PHI
- ✓Report delivered or failed through a registered webhook
Setup steps
- 1Put the account on Business or Enterprise and e-sign the BAA if you transmit PHI
- 2Create an API key at /dashboard/developers with faxes:send
- 3Have your integration engine capture the Epic-generated document
- 4POST the document inline to /v1/faxes with the recipient number
- 5Store the returned fax id against the chart, order, or referral
- 6Register a webhook and reconcile delivered or failed onto the record
Example
POST /v1/faxes (from your Epic interface engine)
Authorization: Bearer sfm_live_xxxxxxxx
Idempotency-Key: referral-epic-88213
Content-Type: application/json
{
"to": "+15551234567",
"document": { "content": "JVBERi0xLjQK...", "content_type": "application/pdf" }
}Epic Fax — FAQ
No. Nothing from us installs into Epic, and we will not suggest a Connection Hub or Showroom listing that does not exist. The path is Epic's own interface layer — Bridges, Interconnect, or an integration engine — handing a generated document to a service that calls our REST API. Epic itself does not talk to our API.
Through the interface route the health system already runs: a print-to-interface queue, a Bridges HL7 message referencing the document, or an Interconnect web service. An integration engine picks it up and forwards it to /v1/faxes. Epic renders the document; the engine is what reaches an external endpoint.
The service sends document bytes inline rather than exposing a public link, and the account runs on a HIPAA-tier plan with a signed BAA before any PHI is transmitted. Inbound fax PDFs on those plans are never emailed — they stay in the authenticated dashboard — so the API path does not weaken Epic's or our clinical controls.
Yes. Save the fax id from the response against the order or referral, then register a webhook for fax.delivered and fax.failed. When an event arrives, match its id and update the chart or a work queue. Because your engine correlates the id to the source document, the loop closes without polling every fax.
Not necessarily. Many Epic sites keep their existing fax infrastructure and use this route only for specific document flows or destinations. Because the send goes through a service your team controls, you decide which Epic-generated documents route to Send FAX Mail and which stay on Epic's own faxing.
Build with the Epic Fax
API access and webhooks are included on the Business and Enterprise plans. Create a key at /dashboard/developers and start sending.
7-day free trial · No credit card required