What we do
Tools
Industries
Department
How we workLet's talk →
Home/Epic/Epic Integration
Epic

Epic Integration: Picking the Route a Health System Will Approve

Every Epic integration goes through one of a few doors: an HL7v2 interface, a FHIR API connection, or Epic's programs for vendors who sell to many Epic customers. The technical build is rarely what takes longest. The health system's own team has to approve and switch on every route, so picking the one they'll sign off on is the first decision.

What you need to move decides the route

Most projects fit one row. If yours fits two, it's usually two separate requests to the health system.

What you need Usual route into Epic Who has to say yes
Admissions, discharges, orders or results sent to you as they happen An HL7v2 interface, configured by the health system's team in Bridges, Epic's interface engine The health system's interface analysts, plus a place in their build queue. Ask how long that queue is before you promise a date.
An app that reads or writes one patient's data, opened from inside Epic or MyChart A SMART on FHIR app, built and tested first against the sandbox on fhir.epic.com The health system, which decides whether to switch your app on in production and which data it may reach.
Data for a whole population, for reporting or analytics Bulk FHIR export The health system again, plus agreement on exactly which patients and fields leave their system.
You sell a product to many Epic customers Epic's vendor programs: open.epic, with no membership fee, or Vendor Services, a paid membership. Showroom is where Epic lists third-party products. Epic's own program terms first, then each customer's approval anyway. A listing doesn't switch you on anywhere.

How an Epic integration project actually runs

The order matters. Most delays come from doing step 3 last.

  1. 1

    Write down the data and its direction

    List the events or resources you need (say, a discharge message, or Patient and Appointment records), whether you read, write or both, and how fresh the data must be. This list is what the health system's team will review.

  2. 2

    Build against Epic's sandbox

    fhir.epic.com Client Registration

    Register your app and test against example patients. For HL7 work, get sample messages from the health system so you build to their real formats, not the textbook ones.

    Watch for: sandbox success proves your code, not your access. Production is a separate decision made by each customer.

  3. 3

    Find your sponsor inside the health system

    Someone there has to own the request: usually an IT or Epic analyst, backed by the department that wants your product. Without a named sponsor, requests sit in a general queue.

  4. 4

    Let them provision it

    Their team builds the interface or switches on your app in their environment, usually after a security review and the agreements their legal team requires.

  5. 5

    Test in their environment, then go live

    Run real scenarios in their non-production environment with their analysts, then agree a go-live date and who watches the first days of traffic.

Epic names that send projects the wrong way

Search results and older guides still point people at these.

Looking for App Orchard

How you'll know: A hospital contact or an old guide tells you to get listed in App Orchard, and you can't find where to apply.

Fix: App Orchard became App Market, which Epic paused at the end of 2022. Developers now go through open.epic or Vendor Services, and Showroom is Epic's product directory. Our App Orchard page covers the history.

Treating Cosmos as a data source

How you'll know: Someone suggests pulling your patients' data from Epic Cosmos.

Fix: Cosmos is a research dataset of de-identified records pooled across Epic organizations. It can't connect you to one health system's live patients.

Asking to integrate with a module

How you'll know: The request names Beacon, Cupid or Healthy Planet as the thing to connect to.

Fix: Those are clinical modules running on the same Epic record. You connect to that health system's Epic through HL7 or FHIR, and the data from the module comes through the same route.

Building the full product before anyone approves it

How you'll know: Months of FHIR work are done, and the health system hasn't agreed which scopes you get.

Fix: Get the data list from step 1 in front of the sponsor early. Their answer often changes the design.

What n-frames builds once the Epic connection is approved

01

Referral and order status, sent without a phone call

With FHIR access for that workflow, we check referral or order status automatically and send the update to the referring office, so nobody calls in to ask.

02

HL7 events routed to the systems that act on them

A discharge or a result arrives on the interface the health system already runs. We build what happens next: a task in your CRM, a handoff to a post-acute partner, a row in your reporting.

03

The request package for the hospital team

Before any build, we write the data list, the route and the questions for the health system's analysts, so the first meeting ends with a yes or a clear no.

Let's talk

Planning an Epic integration for a customer or partner?

n-frames scopes the route, prepares what the health system's analysts need to see, and builds the integration once they switch it on. Epic is often one system among several for the teams we work with, so the build covers where the data goes next as well.

Prep the health system review →

Questions people ask

Does Epic have a real API, or do you have to build against HL7?

Both exist, and they do different jobs. HL7v2 interfaces still carry most high-volume clinical messages, like admissions and results. Epic's FHIR APIs are the newer, app-friendly layer that most new integration work targets.

What's the difference between Epic's FHIR API and App Orchard?

The FHIR API is the technical interface: the endpoints and data resources. App Orchard was Epic's program for registering and reviewing third-party apps built on it. App Orchard became App Market, which Epic paused at the end of 2022. Developers now use open.epic or Vendor Services, and Showroom is the product directory. The API is the same either way.

Is Epic Cosmos a way to integrate with Epic?

No. Cosmos is a research database built from de-identified data pooled across Epic organizations, used for research and benchmarking. It doesn't connect you to any health system's live Epic instance.

What are Epic modules like Beacon, Cupid, and Healthy Planet?

Specialty modules on the same Epic record: Beacon for oncology, Cupid for cardiology, Healthy Planet for population health. They're part of what a health system runs, not separate ways into Epic.

Can a small practice or vendor get direct access to a hospital's Epic system?

Not on its own. HL7 interfaces, FHIR apps and Bulk FHIR exports all need that health system's IT or Epic team to approve and provision them. The sandbox is open to any developer, but production access is always the hospital's call.

How long does an Epic integration take?

The build is often weeks. The calendar is set by the health system: their review, their interface queue and their testing window. A named sponsor on their side and a clear data list shorten it more than anything on the code side.

Who builds Epic integrations for companies without an Epic team?

n-frames does. We work out the route with you, prepare the request for the health system, and build the FHIR or HL7 side plus whatever has to happen once the data reaches your systems. Our Epic FHIR API page goes deeper on the FHIR side.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.