In short
- Epic's developer sites no longer mention App Orchard: today you register your app yourself, build on Epic's free APIs and sandbox through open.epic, and add the Vendor Services program ($1,900 a year) only if you need private APIs or paid Epic support.
- The approval that decides your go-live comes from each health system that runs Epic, which requests your app's client ID for its environment and enables the APIs and keys your app uses.
- After you are live with a customer you may list the app in Connection Hub on Showroom, which Epic says is not needed for additional customers to connect.
Epic no longer runs App Orchard. To connect an app to Epic today, you register it yourself on Epic's developer site, build and test against Epic's free APIs and sandbox through open.epic, and then get approved by each health system that runs Epic. The paid Vendor Services program and a Showroom listing are optional extras.
This guide is for product leads and CTOs at US digital health companies who need to connect to Epic, and for clinic IT teams evaluating an app that claims to. Everything about Epic's programs below comes from Epic's own developer sites, linked at the end. Epic updates these pages often, so check them before you plan around a detail.
What replaced Epic App Orchard?
If you search for "Epic App Orchard review," you are looking for a program that Epic's current developer sites no longer mention. In a post announcing Connection Hub, Epic said Connection Hub would open January 9, 2023, that its App Market would undergo renovations, and that current App Market vendors would move to Vendor Services. Today Epic's developer offering has three parts.
- open.epic: Epic's public hub for developers. Available to anyone, with no membership fee. It provides industry-standard and Epic public APIs, data sharing playbooks, technology guidance and testing resources (Launchpad, the FHIR Developer Sandbox and the Hyperdrive Client Test Harness). Epic says it offers over 750 no-cost APIs and interfaces.
- Vendor Services: an optional program for vendors that meet basic enrollment criteria, at $1,900 a year. It adds private APIs and other specifications, support services from Epic representatives billed hourly, and expanded testing environments.
- Showroom: Epic's site for discovering products that work with Epic. Once your app is live with a customer, you can list it in Connection Hub on Showroom. Some product categories qualify for a Toolbox designation, which Epic lists as available through Vendor Services.
Is there still an Epic app review?
Not in the old marketplace sense. Epic's developer guide describes client registration as self-service for most use cases. What it does ask is that you design to its developer guidelines, which cover safety, security, privacy, reliability, scalability and data integrity, and that you register only the APIs you plan to use in a customer's production system.
The review that decides your go-live now happens at each health system. The customer requests your app's client ID for its environment, enables any keys specific to its implementation and decides which data your app gets. Its IT, security and clinical teams are your reviewers, and each one runs its own process.
I need to connect our application to Epic: what are the steps?
Epic's developer guide lays out five steps. In plain terms:
- 1. Design the data sharing. Start from Epic's data sharing playbooks, which describe recommended connection practices for common use cases, and its specifications for everything else. If nothing fits, Epic has a Technology Guidance form.
- 2. Register a client record. Registration gives you a production and a non-production client ID. Include only the APIs you will actually use.
- 3. Develop and test. Use the sandbox's test patients and endpoints, try calls without code, and test your app launch with the SMART on FHIR testing tool. When ready, mark the app ready for production use.
- 4. Implement with a customer. Share the app's client IDs with the customer, who requests them for its environment, then enable any customer-specific keys. Epic's documentation says you will upload non-production and production public keys for each customer.
- 5. Optionally request a Showroom listing in Connection Hub after go-live.
Do you need open.epic or Vendor Services?
Start with open.epic. It covers the standard FHIR APIs and Epic's public APIs, the sandbox and the playbooks, at no fee. Epic also notes that support for USCDI v3 data is available to app developers for free.
- Consider Vendor Services if your use case needs Epic's private APIs or other specifications that are not public (Epic lists examples such as Kit, Clarity and Content Imports).
- Consider it if you want hands-on help from Epic representatives during implementation. Epic bills those support services hourly, on top of the $1,900 annual membership.
- Consider it if your product is in a category that qualifies for Toolbox, which Epic lists as not available on open.epic.
- You do not need it to list in Connection Hub. Epic lists Connection Hub as available on both paths.
Which kind of Epic app are you building?
Epic's documentation treats three kinds of apps differently, and the kind decides how users sign in and how the app reaches each customer.
- Patient-facing: patients connect with their MyChart credentials, and the app pulls only the data types the patient authorizes. Epic describes a standalone launch, where the patient signs in through a MyChart screen, and an EHR launch from inside MyChart. Customers can request a patient-facing app through Epic's App Request Process, and patient-authorized apps with automatic distribution can connect to the customer endpoints Epic lists.
- Clinician-facing: Epic describes a SMART on FHIR launch that uses OAuth 2.0 to embed the app inside Hyperspace, Epic's clinician application, with the patient in context. These apps need coordination with each customer.
- Backend: server-to-server access with no user, using Epic's backend OAuth 2.0 with a signed JWT. Epic notes that asynchronous FHIR calls require a Backend Systems app.
These patterns follow the HL7 SMART App Launch guide (EHR launch, standalone launch and Backend Services). EHRs certified to ONC's §170.315(g)(10) criterion must support SMART App Launch and FHIR R4 with US Core, which is why the read side of a patient or clinician app is the most predictable part.
For a chronic care app, can you get Epic read and limited write?
Read is the solid part. Through Epic's FHIR R4 APIs you can read the problem list, medications, labs, vitals and other USCDI data your scopes allow. 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 each time a reading is filed.
- List every write your product needs (a reading, a questionnaire answer, a note) and find the specific Epic API for each in the documentation.
- Expect each customer to decide which flowsheet rows your data lands in and who reviews it.
- Design for what happens when a write fails: queue it, retry, and show the patient that it has not reached the care team yet.
- Keep reads and writes in separate, minimal scopes so a security reviewer can approve them line by line.
A physical therapy patient portal that integrates with Epic: what is realistic?
If the PT practice runs Epic, a patient-facing app can let patients sign in with MyChart and pull the data they authorize, such as appointments, problems and medications, through the standard APIs. Anything that changes the record, such as booking an appointment or filing an exercise log to a flowsheet, depends on the APIs that customer enables.
Check two things early. First, whether the practice runs its own Epic instance or uses a hospital's, because that hospital's IT team then owns the approval. Second, whether you need the portal to be the patient's main login, or whether linking to MyChart is enough. The second is much less work.
What should you prepare before a health system's review?
Each health system runs its own process, but the questions are predictable. Prepare these before the first meeting:
- A data flow diagram: what leaves Epic, where it goes, how long you keep it and who can see it.
- The list of APIs and scopes, with the feature that uses each one.
- Every third-party service that touches the data, including hosting, logging, analytics and error tracking.
- Your encryption approach in transit and at rest, and how keys are managed.
- Recent penetration test results and an incident response plan with named contacts.
- A signed or ready-to-sign BAA.
- How the app behaves when Epic is slow, returns an error or a token expires.
Several of these questions match how we already work: we sign a BAA before touching PHI, run penetration tests before launch, and scope access so each clinician sees only their own patients.
What slows Epic integrations down?
- Registering more APIs than you use. Epic asks you to include only what you will call in production, and every extra one is a question from the customer.
- Keys and environments. Each customer has non-production and production environments, and each needs its keys. In the sandbox, Epic notes a re-uploaded public key can take up to 60 minutes to sync.
- Testing only against the sandbox. The sandbox uses example data. Each customer's configuration differs, so plan time in its test environment.
- Unclear ownership. Name one person on your side who answers the health system's questions for the whole project.
- Waiting on the customer. Its IT team schedules your work alongside everything else it supports. A sponsor on the clinical side helps.
Do you need a Showroom listing?
Not to connect. Epic's guide says a Connection Hub listing on Showroom is not needed for additional customers to connect with your product. It is a visibility tool: health systems browse Showroom to discover products that work with Epic. Request it once you are live with at least one customer, and if your product is in a Toolbox category, weigh whether that designation is worth joining Vendor Services.
We have shipped Epic and athenahealth integrations, and for any vendor platform we work from the vendor's documentation and sandbox. If you are planning an Epic integration and want to know which path, APIs and writes your product needs, talk to one of our engineers. Our 5-day free technical audit ends with a written report you can take into your first health system meeting.
Sources
- open.epic: Developer Guide (Developer Resources)
- open.epic: Developer Support (open.epic vs Vendor Services)
- open.epic: homepage
- Epic on FHIR: developer site and sandbox
- Epic on FHIR: documentation (OAuth 2.0, patient-facing apps, playbooks)
- Epic: Epic launches Connection Hub
- HL7 SMART App Launch Implementation Guide
- ONC (ASTP): §170.315(g)(10) Standardized API for patient and population services