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]

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

Our recommendation is to upgrade to EP5 to ensure compatibility with Hyperdrive. That being said, the existing COM Integration for Epic from previous versions of OnBase (such as EP3) will work with Hyperdrive, if you enable COM compatibility mode in Epic. Please reach out to Epic or refer to the "Configuring Epic for OnBase" guide if you have questions on how to do this.

If there appears to be an issue with the OnBase software, please work with Support to troubleshoot the behavior. If the issue is caused by a defect in OnBase, we cannot guarantee a backported fix to all previous EPs and it may be necessary to upgrade to EP5 for a fixed build.

[CurtisFox]

Known issues and software changes have been added and/or updated to the Minimum-Recommended OnBase Builds for Epic Hyperdrive page.

The Minimum Supported Build and the Minimum Recommended Build have been updated to 21.1.13.1000, which is available for download here. The Minimum Supported Build was updated due to the scope of the bugs that have been identified and fixed up to this point. This only impacts the App/Web servers and client installs related to the Epic Integration. All other aspects of the OnBase solution can remain on older builds of EP5 if desired.

The most notable fix completed in this build is for the Image Retrieval API (IRA), which was not a Hyperdrive-specific issue, but would most likely impact any Epic Integration that uses IRA. 

A status update was provided on HC-165764 (formerly CSFMD-1666). It currently is the last outstanding known issue related to Hyperdrive.

[Kay_Okunoren]

We currently use the Combined Query Viewer in our OnBase 18 Epic integration.  Will it be supported by the  EP5 Hyperdrive integration?

[Steven_Thorders]

I noticed that the EP3 MRG details "Printing Documents Using Epic" on page 345-346. This section has been mostly removed from the EP5 MRG. Since upgrading from OnBase 18 to OnBase EP5, we are unable to Print from Epic Chart Review (namely, the print button in the preview pane). Does the Healthcare Web Viewer not support Epic printing functionality from Chart Review?

(Hate to do it but pinging @Curtis Fox )

[Julia_Tabaj]

We currently use the Combined Query Viewer in our OnBase 18 Epic integration. Will it be supported by the EP5 Hyperdrive integration?

Hi @Kay Okunoren , 

Combined Query Viewer will be supported in the EP5 version of Hyperdrive. It will not use the SMART on FHIR authentication, but work as it does today. Be sure to mention you use CQV to the services team and you should be good to go.