Official Epic Hyperdrive Discussion Post

[Julia_Tabaj]

Hello Everyone. 

We want to thank you for your valuable participation in this thread as well as everywhere else that you engage on Community. We were recently able to have a new topic added to Community for Forum posts, which is simply titled "Hyperdrive". This will enable us to build a collection of Forum posts, both Q&A and Discussion types, specifically for Hyperdrive. Example: 

In addition, using separate Forum posts with the Hyperdrive topic will better support answering specific questions or discussing issues/concerns/best practices in their own threads instead of here in this long thread, where information is more likely to get lost.

For current/ongoing discussions that are already taking place in this thread, please feel free to continue to use it or start a new Integration for Epic Forum post with the Hyperdrive topic (when applicable).

In the future, we will add a final post to this thread notifying you that it's locked to new replies and asking that we create new Forum posts with the Hyperdrive topic instead.

To create a new Forum post with the Hyperdrive topic:

1. Navigate to the Integration for Epic Forum. 

2. Click 

3. In the Topic field, choose "Hyperdrive" from the dropdown menu.

If you have any questions, please feel free to reach out. If you have any issues using this functionality, please reach out to Community Support. 

[CurtisFox]

Hello @David, 

I wanted to answer your question here to bring visibility to it, as this is a more current thread. Your question was: 

"Can we also implement Hyland IdP with HyperSpace, or will we continue to use Shared System User Tokens between HyperSpace and the Healthcare Web Viewer and move to the Hyland IdP when we are ready to go with HyperDrive?"

You will not be able to utilize the Hyland IdP with Hyperspace for authentication. That functionality was added with our support for Hyperdrive using SMART on FHIR (SoF). The Hyperspace and Hyperdrive COM integration will continue to authenticate via the Epic Authentication method used in previous versions of OnBase. However, you can have the Hyland IdP setup and ready to go for use with the Hyperdrive SoF integration once your organization is ready to move to that functionality.

(Re-posting to tag the correct user.)

[CurtisFox]

Hi @Ryan,

How Web Server licenses are used can vary based on what licensing structure a customer has. Unfortunately, because of that, we cannot give you a general answer for this here. The best option would be to speak with your Account Executive to discuss how addressing the potential load on the Web Server will affect your licensing. 

[Ryan_Wakefield]

Hi @Ryan , How Web Server licenses are used can vary based on what licensing structure a customer has. Unfortunately, because of that, we cannot give you a general answer for this here. The best option would be to speak with your Account Executive to discuss how addressing the potential load on the Web Server will affect your licensing.

Thanks for the update here Curtis. I will reach out to my AM if need be.

[CurtisFox]

The Minimum-Recommended OnBase Builds for Epic Hyperdrive page has been updated again with additional known issues and software changes, many of which have been fixed 21.1.12.1000. This release is available now and you can find it here. 

Please note that a defect has been added to the list that is not Hyperdrive-specific, but could affect any customers who are using the Image Retrieval API (IRA). The scope of the impact depends on how many image documents are stored as a separate file per page, versus being stored as multi-page TIFs. Please review Software Change ID HC-165501 on the above-linked page for more information. If you have additional questions about this defect or others noted on that page, please reach out to your first line of support.

Apologies for the delay in getting the page updated after the release of 21.1.12.1000 on March 9th.

[Ashleigh_Yingli]

Are there timelines for when Epic Hyperdrive will be available for previous EP versions (EP3 specifically)?