Epic web services: the gaps between standards
Epic's own APIs, listed on open.epic next to the standard ones, for transactions FHIR and HL7 don't cover cleanly. Useful, but they tie your code to Epic specifically.
When a hospital says "use the Epic API", it could mean a FHIR endpoint, an HL7v2 feed, one of Epic's own web services, a CDS Hooks service or a Bulk FHIR export. They're documented side by side on open.epic and they do very different jobs. Which one applies depends mostly on who you are and what you want to happen after the data arrives.
Epic runs the clinical record, while referrals, forms and intake still move by fax and phone around it.
Stuck on Epic? Let's solve it →More than one. Epic publishes FHIR APIs (R4, plus older STU3 and DSTU2 versions), HL7v2 interfaces, its own web services for transactions the standards don't cover, CDS Hooks for decision support inside the clinician's screen, and Bulk FHIR for population exports. It also supports X12, DICOM and NCPDP exchanges.
Where to look: open.epic lists them by interface type. Developers register and test FHIR apps on fhir.epic.com against test patients.
The catch: none of them reaches a live hospital until that health system's own Epic team switches it on for you.
Pick by the job, not by which one sounds newest.
Request and response over REST: a patient, an appointment, a lab result. Most new app work starts here. Client IDs, launch types and the sandbox are on our Epic FHIR page.
Epic pushes messages as events occur: an admission, a discharge, an order, a result. Still the workhorse for high-volume clinical feeds, built by the health system's interface team. Choosing between this and FHIR is on our Epic integration page.
Epic's own APIs, listed on open.epic next to the standard ones, for transactions FHIR and HL7 don't cover cleanly. Useful, but they tie your code to Epic specifically.
Epic calls your service at a set moment, such as opening a chart or signing an order, and shows the card you send back. For decision-support products, not data syncs.
An asynchronous export of many patients to files, for reporting and analytics. Slow by design, so it's no use for questions about one patient right now.
open.epic came first and costs nothing. Vendor Services and Connection Hub arrived in early 2023, after App Market (once App Orchard) was paused, and Showroom followed later that year. What happened to App Orchard is on its own page.
Most people who search for the Epic API fit one of these four.
Multi-specialty health system · Epic across every department · referrals from community PCP offices by fax and email
A community primary care office faxed a cardiology referral. A coordinator read it, searched Epic for the patient or opened a new chart, keyed in the referral order, then phoned the office to say it had arrived.
Only after all of that could anyone book the consult.
Incoming faxes are read, structured and matched to the patient automatically, then passed through the referral interface the health system's Epic team already runs.
The coordinator opens a referral that's already filled in and books it. The confirmation back to the referring office goes out without a phone call.
n-frames builds the automation in the space around a health system's Epic: referral intake like the case above, the sync that keeps a referring-physician CRM in step with who was actually scheduled and seen, and the pipeline that puts Epic's reporting extracts next to staffing, marketing or collections numbers Epic doesn't hold.
It also works the other direction. When an event happens in Epic, such as a referral sent or a result ready, we build what turns it into the fax, email or portal update an outside partner needs. All of it runs through the interfaces the organization's Epic team already supports. We don't touch clinical build.
Epic is the electronic health record behind many large hospitals, academic medical centers and multi-specialty systems. Clinical charting, scheduling and billing run through modules such as Cadence for scheduling and Resolute for billing, and MyChart is the app patients use.
Hyperspace is the staff-facing Epic application: the screens and menus that clinicians, schedulers and billers work in all day. MyChart, the patient side, sits on the same record but is a separate experience. Many organizations now run it through Epic's newer client, Hyperdrive.
Epic doesn't publish prices and quotes each organization on its size and modules. Large health system implementations commonly reach tens of millions once hardware, staff, training and build are counted. On the developer side, open.epic and the fhir.epic.com sandbox cost nothing; Vendor Services is a paid membership.
Yes, through the interfaces on this page: FHIR, HL7v2, Epic's web services, CDS Hooks and Bulk FHIR. In practice the health system's own Epic analysts build or approve each connection, so an outside party can't simply plug in. n-frames builds through those approved channels and handles what happens to the data afterwards.
Mostly. Its pricing and implementation effort suit large, well-funded systems and big groups. Some smaller practices reach Epic through a nearby health system's shared instance, but most independent practices run a lighter EHR.
open.epic is the public catalog and program, not an API itself. It lists Epic's interfaces by type, explains its terms, and links to fhir.epic.com, where developers register FHIR apps and test them.