Hyperdrive

Epic’s web-based end user client application

Epic has moved its primary end user application, Hyperspace, to a web-based framework called Hyperdrive. Hyperdrive is a secure, Epic-specific web browser and code-level changes are required for web- and desktop-based Hyperspace integrations in order to integrate wth Hyperdrive. Many Epic workflows rely on integrations with other products for users to complete a task. Hyperdrive is essential for almost all end users largely because it includes a Windows-native plugin infrastructure that enables integrations with other products.

Changes for Integrations

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.

If your integration is a website, the Prepare Web Content for Hyperdrive document summarizes changes that may be necessary to make your integration Hyperdrive-ready. This reference can help you evaluate if changes are needed for your application.

The details of our new API specifications can be found in the sections below. As you evaluate these APIs keep in mind that integrations developed for Hyperdrive may not work with the current Hyperspace client. Your application should support integration with both clients, or be side-by-side compatible with your current application, on the same workstation or server until all customers have transitioned off of Hyperspace.

Testing Integrations in Hyperdrive

We have developed testing harnesses to help you validate that your integration is successful with Hyperdrive:

The Hyperdrive Client Test Harness allows you to ensure your development is compatible with Hyperdrive.
- Supported workflows currently include: E-Signature, Login, Voice Recognition, Scan Acquisition, Scan Viewing, Scan Signature Deficiencies, FHIRcast, XML, and web content integration workflows.
- Functionality of this harness will be updated as we release additional features and enhancements.
- When Hyperdrive is used as a published application, Slingshot can make some integrations available on the endpoint device. Further detail can be found in the test harness documentation.
The Hyperdrive Web Developer Test Harness allows you to validate that your website renders and functions correctly when hosted inside of Hyperdrive before it enters production. It allows you to see how a site will present either in an iframe or in a Hyperdrive embedded window.

Timelines

Most organizations transitioned their users to Hyperdrive in 2022 and 2023, though a few may not have completed this transition until later. During the transition, most organizations will have some users using Hyperspace and others using Hyperdrive, and both clients will be installed on the same workstations.

Tapestry Document Linker DMS Integration read the spec

This web service allows third-party DMS vendors to launch activities within a pre-existing Hyperspace instance to link documents to records in Epic such as claims or coverages. Information about the document in the third-party database will be populated in the activity launched, and users can complete the linking workflow from the Hyperspace session. The web service can also launch a new Hyperspace instance if one is not open when the web service is called.

Desktop Generic Authentication read the spec

This interface allows external authentication software to implement authentication devices for use in Epic. The external authentication software can write installable devices that can be configured for use as devices to authenticate a user for login into Epic, to re-authenticate the user after login (for example, to sign off on medications), or to identify a patient (for example, to check into an appointment).

Subspace Communication Framework read the spec

The Subspace Communication Framework is a pattern for asynchronous, semi-event-driven integrations between Epic and external applications. This document outlines the steps that an external application must take to initiate and communicate with Epic via a Subspace integration.

Subspace User Session Management read the spec

This API allows other applications to receive events about and request changes to be made to a user's session in Epic. This includes information about logging in, logging out, securing, and shutting down. The API uses the Subspace Communication Framework.

E-Signature read the spec

This API provides information about two workflows where e-signing functionality is used within Epic: Document Collection and Signature Authentication/Reconstruction. During Document Collection workflows, one or more individuals can sign an electronic document and their signatures will be stored into Epic. Signature Authentication workflows allow a user to authenticate the validity of a signature, and Signature Reconstruction workflows reconstruct signature images from discreetly stored data.

Scan Acquisition read the spec

Epic has the ability to allow end users to acquire scanned documents via a Document Management System (DMS). This API specifies how to integrate an external desktop scan acquisition application with Epic to allow end users to perform the scanning work and file the documents’ metadata to Epic.

Scan Viewing read the spec

Epic provides ways for users to view scans acquired via a Document Management System (DMS). This API specifies how to integrate a web-based external scan viewing application with Epic for end users to view acquired scans.

XML Context Synchronization

This document contains APIs that can be used for single sign-on, patient context synchronization, study context synchronization, and real-time measurement exchange. These APIs are commonly used with PACS and CPACS vendors, but may have other uses as well. We additionally have an encryption utility for use with our XML integration (identical to URL encryption). We expect this functionality to work identically with Hyperdrive as it does with Hyperspace.

Speech Recognition read the spec

This API allows speech recognition systems to interact with controls and views within Epic. The speech recognition system can receive information about and make changes to the content of a control as well as execute commands on an activity.

FHIRcast read the spec

FHIRcast is a web based integration method used for context synchronization between Epic and other applications. This API is used to ensure that all applications display the same patient or study.

Credit Card and Bank Account Integration

This interface communicates with payment gateways to integrate credit card and bank account payments directly into Epic. Payment methods can be saved and used for automatic payment plans. We expect this functionality to work identically with Hyperdrive as it does with Hyperspace.

Subspace Encoder read the spec

Epic has the ability to allow users to work in an external encoder application and file the results to Epic when the user is finished. This API specifies how to integrate an external encoder application using the Subspace Communication Framework.

Web Services Encoder read the spec

Epic has the ability to allow users to work in an external encoder application and file the results to Epic when the user is finished. This API enables integration with an external encoder application using web services.

Kiosk Generic Authentication read the spec

Allows external authentication software to implement authentication devices for use in Epic’s self-arrival kiosk software. The external authentication software can write installable devices that can be configured to identify a patient or to enroll a patient for future identifications.

OpenID Connect read the spec

Epic’s Hyperspace application now supports the OpenID Connect (OIDC) authorization code flow as a means of authenticating users for logging in to Hyperspace as well as authentication within Hyperspace workflows.