The multi-year transitional period from Epic Hyperspace to Epic Hyperdrive is underway, and Epic customers that we speak with are in varying states of readiness for the upgrade.
With a looming 2023 deadline, our guide below answers some common questions about the migration from Hyperspace to Hyperdrive.
What is Epic Hyperspace?
Hyperspace is Epic’s primary end-user interface, hosted on Citrix, that serves as the central point of access to all other Epic applications. Epic users are probably familiar with Hyperspace as their login screen. After login, Hyperspace users see different menus, tasks, and options depending on their specific roles.
What is Epic Hyperdrive?
Hyperdrive is Epic’s new web-based application intended to replace Hyperspace. This Epic-specific web browser will improve security and make it easier to access Epic applications.
Epic Hyperdrive vs Epic Hyperspace: what’s the difference?
Epic Hyperspace is a client/server application that runs on the client side and calls a remote server to access information. Hyperdrive is a browser-based application that only requires a compatible web browser. Users may not initially notice a significant functional difference between the two, but Hyperdrive should be easier to deploy and update, and offer greater performance and security than Hyperspace.
When will customers need to upgrade from Hyperspace to Hyperdrive?
Some organizations have already begun the migration to Hyperdrive. During this transition, some end users may still be on Hyperspace and others on Hyperdrive, and both applications may be installed on the same workstation. All Epic customers must officially migrate to Hyperdrive by the November 2023 release.
How should Epic customers prepare for the migration to Hyperdrive?
Many Epic workflows enabled through Hyperspace rely on integrations to third-party web-based or desktop-based applications, like voice recognition or payment solutions. Significant code and interface changes will be required to ensure that these integrations work properly in Hyperdrive.
Migration to Hyperdrive will require a detailed conversion plan to ensure that the requisite code and interface changes are implemented and properly tested. You may need to coordinate with third-party solution providers impacted by the transition, for example, Imaging/PACS and transcription vendors.
To understand the technical requirements for the Hyperdrive transition, your team will reply on specs and code published to the Epic User Web and notes in NOVA, the Epic release management system.
What technical resources are required for the upgrade from Hyperspace to Hyperdrive?
From a resource perspective, customers will work with their Epic client manager (aka, your Epic BFF) and the Epic client services team. Consider an experienced Project Manager, Epic-skilled technical and clinical architects, and integration/application analysts for your internal team. During the transition from Hyperspace to Hyperdrive, training resources will be needed to assist end users, and to update legacy training materials.
How can Healthcare IT Leaders assist our Hyperdrive transition planning?
If your org is struggling to develop or implement a Hyperdrive transition plan, our Epic team can help. Utilizing Healthcare IT Leaders consultants ensures that you have unbiased, expert advice for developing and executing your plan before the official sunsetting of Hyperspace.