Epic integration services for apps, portals, RPM and CRM

We connect patient apps, provider portals, remote monitoring tools and CRMs to Epic, and we have shipped Epic integrations. The work runs on Epic's free open.epic APIs and sandbox, with the paid Vendor Services program added only when your features need it. The approval that decides your go-live comes from each health system that runs Epic, so we plan around it from the first week.

Provider portal home screen with an inbox, open referrals, recent claims and a surgical calendar

What does integrating with Epic involve?

Integrating with Epic means your product reads or writes data in a health system's Epic instance through interfaces Epic publishes. Most new work uses Epic's FHIR R4 APIs with SMART on FHIR authorization, which follows the HL7 SMART App Launch guide. Some workflows, such as event feeds inside a hospital, still run on HL7 v2 interfaces that the health system's integration team manages.

Epic's developer offering has three parts. open.epic is open to anyone with no membership fee, and Epic says it offers more than 750 no-cost APIs and interfaces, along with data sharing playbooks and testing tools: Launchpad, the FHIR Developer Sandbox and the Hyperdrive Client Test Harness. Vendor Services is an optional program at $1,900 a year. Showroom is where health systems find products that work with Epic, through a Connection Hub listing.

Epic describes client registration as self-service for most use cases, and its developer guide says you can register and go live without needing Epic's involvement. The involvement you do need comes from each customer.

Do you need open.epic or Vendor Services?

Most projects start and stay on open.epic. It covers the industry-standard and Epic public APIs, the sandbox and the playbooks.

Vendor Services adds what open.epic does not: private APIs and other specifications (Epic lists Kit, Clarity and Content Imports as examples), access to Epic representatives invoiced at an hourly rate, and expanded testing environments with configurable test data. Some product categories qualify for Epic's Toolbox program, which is available only through Vendor Services.

A Connection Hub listing is available on both paths, and Epic says it is not needed for additional customers to connect. We decide which path you need from the list of APIs your features call, during the audit, so you do not pay for a membership you will not use.

Which kind of Epic app are you building?

Epic treats three kinds of apps differently, and the kind decides how users sign in and how the app reaches each customer.

A patient-facing app lets patients connect with their MyChart credentials and pulls only the data types the patient authorizes. A clinician-facing app uses a SMART on FHIR launch with OAuth 2.0 to open inside Hyperspace, Epic's clinician application, with the patient already in context; these need coordination with each customer. A backend app runs server to server with no user, using Epic's backend OAuth 2.0 with a signed JWT, and Epic notes that asynchronous FHIR calls require a Backend Systems app.

Many products need more than one. An RPM product, for example, may have a patient app that files readings and a backend service that syncs them. We map each feature to an app type before anyone registers a client.

What can you read from Epic, and what can you write?

Read is the predictable part. EHRs certified to ONC's §170.315(g)(10) criterion must offer a FHIR R4 API with US Core and SMART App Launch, so problems, medications, labs, vitals and other USCDI data are available within the scopes the customer grants.

Write is narrower and needs a plan per customer. For filing measurements, Epic's playbooks point to the Observation.Create API, which is often used to file data to flowsheets so clinicians see it in their workflow. In its remote patient monitoring material, Epic says Observation.Create must be added to an app with Patients as the primary user type and authenticated with OAuth 2.0, and it recommends JWT authentication so patients do not have to log in for every reading.

Every write needs the customer's sign-off: which flowsheet rows the data lands in, who reviews it, and what the care team sees when a write fails. We keep reads and writes in separate, minimal scopes so a security reviewer can approve them line by line.

What do we need from you to start?

A sponsoring health system or practice that runs Epic, with a named contact in its IT team and, ideally, a clinical sponsor who wants the workflow. You can build in the sandbox before you have one, but you cannot go live without one.

Access to your Epic developer account, or agreement that we create the client registration in your company's name. We recommend the registration stays with you, so the client IDs and keys remain yours after the project.

A signed BAA before we touch PHI, the list of features you want in the first release, and the person on your side who answers the health system's questions.

What drives the timeline and cost of an Epic integration?

We do not publish a price, because the drivers differ by project. The main ones are the number of distinct APIs and writes, the number of app types, whether Vendor Services is needed, and how many customers you are rolling out to.

Much of the timeline depends on the customer's calendar. Each health system has non-production and production environments that need their own keys, and its IT team schedules your work alongside everything else it supports. Its security review can add questions about hosting, logging, analytics and every other service that touches the data.

The audit report turns these into a dated plan for your project, with the waiting points marked.

What are the risks, and how do we reduce them?

Testing only against the sandbox. The sandbox uses example data, and each customer's configuration differs, so we plan time in the customer's test environment.

Registering more APIs than you use. Epic asks you to include only the APIs you plan to use in a customer's production system, and every extra one is a question from the customer's reviewers.

Failed writes and expired tokens. We design queues, retries and clear messages so a reading that has not reached the care team never looks as if it has.

Security gaps found late. We sign a BAA before PHI, scope access so each clinician sees only their own patients, and run a penetration test before launch, which answers many of the questions a health system's review will ask.

How we run a Epic integration

  1. 1

    5-day free technical audit

    We read your product, your data flows and the vendor's current documentation, then list every read and write your features need and the API or interface that serves each one. You get a written report, whether or not you hire us.

  2. 2

    Scope and dated plan

    From the report we agree the scope, the order of work and a plan with dates, including the points where we wait on the vendor or your customer. We sign a BAA before any PHI is in reach.

  3. 3

    Build in the vendor sandbox

    We register the client with only the APIs you need, get production and non-production client IDs, and build against Epic's sandbox test patients and endpoints. For any part of Epic's platform we work from its documentation and sandbox.

  4. 4

    Testing

    We test the app launch and each read and write, then repeat the tests in the customer's own test environment once it requests your client ID and enables its keys.

  5. 5

    Go-live with a penetration test

    Before launch we run a penetration test and fix what it finds, then go live with the customer and watch the first days of real traffic. Access is scoped so each clinician sees only their own patients.

Epic integration questions

1

Have you shipped Epic integrations?

Yes, we have shipped Epic integrations. We do not publish client names or project details. For any part of Epic's platform, including modules we have not used before, we work from Epic's documentation and sandbox, and the audit report tells you what we found for your use case before you commit.

2

Is Epic integration free?

open.epic has no membership fee and gives you the standard and public APIs, the sandbox and the playbooks. Vendor Services costs $1,900 a year, and Epic bills its representatives' support services hourly on top. Your own build cost and your customer's internal effort are separate, and we estimate the first in the audit.

3

Do we still need App Orchard?

No. Epic's current developer sites do not mention App Orchard. In announcing Connection Hub, which opened on January 9, 2023, Epic said its App Market would be renovated and existing App Market vendors would move to Vendor Services. Today you register through Epic's developer site and get approved by each customer.

4

Can we start before we have a health system customer?

Yes. Registration and sandbox development do not need a customer, so you can build and test the integration first. Going live does: the customer requests your app's client ID for its environment and enables the keys and APIs your app uses. Building first also lets your sales team demo a working connection.

5

Do we need a Showroom listing?

Not to connect. Epic says a Connection Hub listing on Showroom is not needed for additional customers to connect with your product. It helps health systems discover you, so request it once you are live with at least one customer.

6

Can our app write data back into Epic?

Often, within limits. Measurements are commonly filed to flowsheets through Observation.Create, and other writes depend on the specific API and on what each customer enables. We list every write your product needs, find the Epic API for each, and plan with the customer where the data lands and who reviews it.