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. Then select PRDHyperspace Proceed to log into Epic. The allowability is described in policy section 5100.12: When accessing an application or system owned or managed by the Yale-New Haven Health. Most organizations will transition their users to Hyperdrive in 20, though a few may not complete this transition until later. Access to EPIC from a personal computer is allowed. TimelinesOrganizations expect to begin testing their integrations in Hyperdrive by Q4 of 2021, with the first end users switching to use Hyperdrive to access Epic in early 2022. It allows you to see how a site will present either in an iframe or in a Hyperdrive embedded window. 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.Further detail can be found in the test harness documentation. When Hyperdrive is used as a published application, Slingshot can make some integrations available on the endpoint device.Functionality of this harness will be updated as we release additional features and enhancements.Supported workflows currently include: E-Signature, Login, Voice Recognition, Scan Acquisition, Scan Viewing, Scan Signature Deficiencies, FHIRcast, XML, and web content integration workflows.The Hyperdrive Client Test Harness allows you to ensure your development is compatible with Hyperdrive.
Testing Integrations in HyperdriveWe have developed testing harnesses to help you validate that your integration is successful with Hyperdrive: 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.
As you evaluate these APIs keep in mind that integrations developed for Hyperdrive may not work with the current Hyperspace client. The details of our new API specifications can be found in the sections below.
Epic hyperspace code#
This reference can help you evaluate if changes are needed for your application.Īs of the May 2021 release, we have released the majority of our integration code in Hyperdrive. 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. HL7, Web Services, DICOM, XML file drop, SMART on FHIR, and outgoing command line integrations will not require changes. Web applications currently hosted within, or launched from, Hyperspace may require changes. Changes for IntegrationsExisting products integrating with Epic via COM-based APIs will need to be updated to work with Hyperdrive. Hyperdrive is essential for almost all end users largely because it includes a Windows-native plugin infrastructure that enables integrations with other products. Many Epic workflows rely on integrations with other products for users to complete a task. Hyperdrive, our new client application, is a secure, Epic-specific web browser and code-level changes are required for current web- and desktop-based Hyperspace integrations.
Epic is moving the current primary end user application, Hyperspace, to a web-based framework.