TL;DR
- Epic moved its main end-user application from Hyperspace to Hyperdrive, and most Epic customers switched their users in 2022 and 2023.
- Hyperdrive is Epic’s own secure browser with a Windows plugin layer. It is not a general web browser, and many hospitals still deliver it through Citrix.
- HL7, FHIR, SMART on FHIR, DICOM and web-service integrations don’t change. Integrations that talk to the desktop client through COM, and some web apps embedded in Hyperspace, do.
- Epic publishes test harnesses for both kinds of client integration, so a product team can check its integration before a customer’s go-live.
If your product shows up inside Epic, as an embedded web app, a scanning or signature tool, a speech engine or a single sign-on device, the move from Hyperspace to Hyperdrive is an Epic change that could reach your code even when your interfaces stayed the same. Most writing on the switch covers screens and speed. This guide covers what it does to integrations, from Epic’s own documentation.
I. What Is Epic Hyperspace?
Epic Hyperspace is the classic Epic client: the application clinicians, schedulers, coders and analysts open to work in Epic’s modules, from ambulatory charting to registration and billing. It is a thick client, and most hospitals delivered it through application virtualization such as Citrix or other remote desktop servers, so the software ran on shared servers rather than on each workstation [Login VSI, November 2024].
The Hyperspace name hasn’t disappeared. During a cutover, some organizations kept the old client available as “Classic” next to the new one; Providence renamed its Hyperspace icon to “Classic” and phased it out after its Hyperdrive go-live Providence, January 2024. And Epic offers a Hyperspace for Mac download, which developers use to test launches against Epic’s sandbox open.epic, Hyperdrive.
II. What Is Epic Hyperdrive?
Epic describes the change in one line: “Epic has moved its primary end user application, Hyperspace, to a web-based framework called Hyperdrive. Hyperdrive is a secure, Epic-specific web browser” [open.epic, Hyperdrive]. Epic adds that Hyperdrive matters to almost every user because it carries “a Windows-native plugin infrastructure” that lets other products plug into Epic workflows.
Three things follow from that definition, and each one corrects a common reading:
- Same EHR, new client: Providence put it plainly to its clinicians: Hyperdrive “is a new way to access the Epic activities you use every day”, with the same activities behind it Providence, January 2024.
- A separate application: Hyperdrive is Epic’s own secure browser, opened from its own icon. Epic’s developer site also documents Hyperspace Web (HSWeb) running in enterprise browsers, with separate APIs for recognizing trusted workstations and for printing to label, wristband and document printers [open.epic, so which client a user group runs is a local setup decision.
- It doesn’t have to run on the workstation: Hospitals can install it locally or publish it through Citrix. For the published case, Epic says a component called Slingshot “can make some integrations available on the endpoint device” [open.epic].
As of October 2026, Epic’s guidance reads: “Most organizations transitioned their users to Hyperdrive in 2022 and 2023, though a few may not have completed this transition until later.” So for most readers the question is no longer whether to move. It is whether everything that plugs into Epic moved with them.
III. Epic Hyperspace vs Epic Hyperdrive: Core Differences
| Epic Hyperspace | Epic Hyperdrive | |
|---|---|---|
| What it is | Epic’s classic thick-client application | “A secure, Epic-specific web browser” with a Windows plugin layer |
| How hospitals deliver it | Mostly through Citrix or other app virtualization | Installed on the workstation, or published through Citrix (Slingshot extends some integrations to the endpoint) |
| Status (October 2026) | Replaced for most users; kept as “Classic” during cutovers; Hyperspace for Mac used for developer testing | Primary client for most Epic customers since 2022-2023 |
| Desktop integrations | COM-based APIs | Hyperdrive’s own APIs (Subspace and others); COM integrations must be updated |
| Web apps shown inside Epic | Hosted in Hyperspace | Hosted in Hyperdrive as an iframe or an embedded window; some need changes |
| HL7, FHIR, SMART on FHIR, DICOM, web services | Work | Work the same, no changes |
Sources: [open.epic, Hyperdrive], fetched October 2026; Login VSI and Providence as cited above.
Is Hyperdrive faster? The most-cited public measurement comes from one health system’s test by Login VSI, published November 2024. Logging into Epic took 17.48 seconds on Hyperdrive against 18.88 on Hyperspace, and opening a patient chart took 2.25 seconds against 6.78. The setup matters as much as the number: Hyperspace ran on shared remote desktop servers and Hyperdrive was installed on a single older workstation, and the authors attribute the gap mainly to less resource sharing on the endpoint [Login VSI. So the honest reading is that how you deliver Hyperdrive affects speed more than the client itself does.
IV. Which Integrations Change in Hyperdrive (and Which Don’t)
This part decides whether a product team has work to do. Epic’s answer is specific: “Existing products integrating with Epic Hyperspace via COM-based APIs will need to be updated to work with Hyperdrive. Web applications hosted within, or launched from, Hyperspace may require changes to work with Hyperdrive. HL7, Web Services, DICOM, XML file drop, SMART on FHIR, and outgoing command line integrations will not require changes” [open.epic].
| No change needed | Must be updated | May need changes |
|---|---|---|
| HL7 v2 interfaces (the message standard most hospital systems use) | Integrations that call Hyperspace through COM-based APIs | Web apps hosted inside Hyperspace or launched from it |
| Web services and FHIR APIs | ||
| SMART on FHIR app launches (FHIR apps that open inside the EHR with the user’s context) | ||
| DICOM imaging links | ||
| XML file drop, outgoing command line |
If your product reads and writes Epic data through FHIR APIs or HL7 interfaces, or launches as a SMART on FHIR app, the client change left it alone. If it sits on the desktop next to Epic and drives Epic’s window, session or controls, it needed new work.
For that second group, Epic’s page lists the APIs for each kind of desktop and web integration. The main ones, grouped by the job they do:
| If your product… | Epic’s API for Hyperdrive |
|---|---|
| Launches Epic activities, follows login, logout and secure events, or moves the Epic window | Subspace Communication Framework, Subspace User Session Management, Other Subspace APIs |
| Signs users in, re-authenticates them, or identifies a patient with a badge or biometric device | Desktop Generic Authentication |
| Scans documents into Epic or shows scanned documents | Scan Acquisition, Scan Viewing |
| Captures or verifies signatures | E-Signature |
| Drives Epic fields and commands by voice | Speech Recognition, plus Speech Recognition for Embedded Applications for web apps iframed in Hyperdrive |
| Works in an external coding encoder and files results to Epic | Subspace Encoder, Web Services Encoder |
| Identifies patients at self-arrival kiosks | Kiosk Generic Authentication |
| Takes card or bank payments inside Epic | Credit Card and Bank Account Integration |
| Keeps patient or study context in step with Epic, as PACS viewers do | XML Context Synchronization, FHIRcast, FHIRcast Content Sharing in Subspace |
| Links documents in a separate document system to claims or coverages | Tapestry Document Linker |
Not every row means new work. Epic expects XML Context Synchronization and the card and bank payment interface to work “identically” in Hyperdrive; the Subspace-based rows are where updated desktop integrations land. Epic also notes that Hyperspace supports OpenID Connect sign-in for users.
One rule from Epic catches teams out: “integrations developed for Hyperdrive may not work with the current Hyperspace client”. Your product should support both clients, or run a Hyperdrive version side by side with the old one on the same workstation, until all your customers have moved. Vendors document the failure modes too; Hyland, for example, publishes a troubleshooting page for its OnBase integration titled “Cannot Connect to Epic Hyperdrive” Hyland documentation.
Need Help with Epic Hyperdrive Integration?
V. How to Test an Integration for Hyperdrive
Epic gives integration teams two harnesses and a Mac client, all listed on open.epic:
- Hyperdrive Client Test Harness: Checks that a desktop integration works with Hyperdrive. Supported workflows include e-signature, login, voice recognition, scan acquisition, scan viewing, scan signature deficiencies, FHIRcast, XML and web content integration. If a hospital publishes Hyperdrive through Citrix, the harness documentation covers how Slingshot handles the endpoint side.
- Hyperdrive Web Developer Test Harness: Shows how your website renders and behaves inside Hyperdrive, either in an iframe or in a Hyperdrive embedded window, before it reaches production. Epic’s “Prepare Web Content for Hyperdrive” document lists the changes a site may need.
- Hyperspace for Mac: Useful for testing URL launches (SMART on FHIR, HTTP GET and SAML) against the fhir.epic sandbox. Most client integrations only work on Windows, so test those on a Windows workstation or VM.
Before a customer’s go-live, six questions settle where your product stands:
- Which integration type do we use: FHIR or HL7 only, a web app inside Epic, or a desktop integration?
- If desktop, which Hyperdrive API replaces the COM calls we make today?
- Have we run it in the right harness, and on Windows where the integration needs it?
- Do we support Hyperspace and Hyperdrive at the same time for customers mid-cutover?
- Does it still work when the hospital publishes Hyperdrive through Citrix?
- Is the sign-on device or SSO product our users depend on ready for Hyperdrive?
For the wider testing picture, from sandbox access to production approval, see our walkthrough of an Epic sandbox proof of concept and the SMART Health IT sandbox for FHIR app testing.
VI. What Changes for Clinicians and IT Teams
For clinicians, the activities stay the same: the same charts, orders and In Basket, opened from a new icon. Training at Providence was organized by service line our Epic training guide covers how Epic training works), with new hires moved onto a Hyperdrive curriculum from January 2024 Providence.
For IT teams, the cutover is mostly a delivery and integration project:
- Both clients on one workstation for a while: Epic expects most organizations to have some users on Hyperspace and others on Hyperdrive during the transition, “and both clients will be installed on the same workstations.”
- A delivery decision: Install locally, publish through Citrix, or mix the two by role. The Login VSI results above suggest this choice drives the speed users feel.
- An integration inventory: List every product that plugs into the client, sort it into the three columns in section IV, and ask each vendor for its Hyperdrive version and test results.
VII. Building an Integration That Works in Hyperdrive
The simplest way to avoid client changes is to integrate where Epic doesn’t change them: FHIR APIs, HL7 interfaces and SMART on FHIR launches. Mindbowser builds those Epic integrations for digital health and device companies, and Mindbowser is an Epic Vendor Services member. Where a product has to plug into the desktop client, Mindbowser updates the integration for Hyperdrive, moving COM-based calls to Epic’s Hyperdrive APIs, and tests it in Epic’s Hyperdrive harnesses. ConnectHealth gives your product one Epic connection, with read and write access, running in your own cloud, and its SDK embeds your app in the EHR with launch, sign-in and patient context handled.
For the decision before any of this (which Epic route fits your product, and what Epic asks of you on each), start with our guide to Epic integration strategies.
Hyperdrive Moved the Work to the Desktop Edge
Hyperdrive changed the window clinicians work in, and left the interfaces between systems as they were. That makes the switch easy to underestimate in both directions: teams that only use FHIR and HL7 had nothing to fix, and teams with a desktop plugin had real work, often discovered at a customer’s go-live. Map your integrations to Epic’s three columns, test the ones that touch the client in Epic’s harnesses, and support both clients until your last customer has moved.
Where to go next
- Epic routes and decisions: Epic integration strategies, Epic FHIR API guide
- Apps inside Epic: SMART on FHIR launch for Epic, Epic sandbox proof of concept
- Building your product on Epic: Epic integration services, ConnectHealth
- Talk to us








BLOGS
NEWSROOM
CASE STUDIES
WEBINARS
PODCASTS
ASSET HUB
EVENT CALENDAR 


















