cancel
Showing results for 
Search instead for 
Did you mean: 
CurtisFox
Employee
Employee

Purpose/Overview

The purpose of this post is to provide a page to follow, in order to receive email notifications when updates related to Epic Hyperdrive are posted. Whenever a new update is posted here, we will make a comment on this page with the updated content, so anyone who follows the page will receive an email notification containing a snippet of the update, with a link to view this page and read the full update. 

 

We will post regarding topics such as:

  • Known issues that are found or resolved.
  • Best practices or common "gotchas" that are discovered.
  • Updates to documentation (such as the "Configuring Epic for OnBase" guide).
  • FAQs

To follow this page and receive email notifications for updates (which we highly recommend!), click the FOLLOW button below this post (before the Comments). If the button says UNFOLLOW, you're good to go!


Latest Update - 11/9/2023

While it's been almost two months since our last update, we've been hard at work improving the Epic integration. Some of the work has been behind the scenes and some of it is listed on our Known Issues pages. Here are some highlights:

  • Deficiencies
    • SD4E had in issue in 22.1 and 23.1 where it would only launch once - subsequent attempts to launch would result in an error. 
      • EP5/21.1 was not impacted. 
        • Resolved in 22.1.25.1000 & 23.1.4.1000.
    • DeficiencyPop Analysis has an issue that impacts solutions where documents can be scanned to child encounters in deficiency episodes.
      • DeficiencyPop only displays documents associated with the primary CSN/encounter and does not display documents associated with the child CSNs.
      • SD4E does not have this issue. 
      • Resolved in OnBase EP5 in 21.1.47.1000 (available 11/10/23) and will be resolved in upcoming 22.1 and 23.1 builds. 
        • Due to this issue, the minimum recommended build for the SMART on FHIR Hyperdrive integration for OnBase EP5/21.1 is now 21.1.47.1000 (see the Hyperdrive Wiki).
  • Healthcare Web Viewer
  • Integrated Scanning
    • SAS was not retaining the following user preferences/selections between launches:
    • Improved Application Server resource utilization when launching FOS & SAS via the SMART on FHIR integration.
      • Also resolved an issue with FOS consuming multiple concurrent client licenses when multiple documents were uploaded and linked to Epic via FHIR.
      • Resolved in 21.1.47.1000, 22.1.25.1000, and 23.1.4.1000.
24 Comments
Julia_Tabaj
Employee
Employee

July 19, 2023 Update: 

 

Hello everyone! Thank you for your patience as we work on releasing our new integration with Hyperdrive. While we have been working with our SMART on FHIR early adopters, over 130 organizations have gone live on COM Wrappers! We currently anticipate restarting SMART on FHIR Hyperdrive integrations in August after successful testing concludes by the early adopters. In the meantime, you can be upgrading to the minimum builds, ensuring your SOWs are in place, and reviewing the Hyperdrive Wiki for the latest information regarding known issues, overview of the Hyperdrive integration, FAQs and more. Your Hyperdrive SMART on FHIR project team will be reaching out to begin configuring needed components.

CurtisFox
Employee
Employee

August 22, 2023 Update:

 

• SMART on FHIR Hyperdrive Integration Printing issue update:

   - The printing issue has been fixed in EP5 with the release of 21.1.43.1000.

   - The fix for 22.1 and 23.1 is still pending but is expected to be included in the next release build of each version.

   - For more information on this issue, please reference the Healthcare Web Viewer Resolved Issues page.

• We posted a new page with guidance on how to download the Hyperdrive apps required for the SMART on FHIR integration from fhir.epic.com.

• With the availability of OnBase 23.1, the Epic Hyperdrive Integrations for Epic Tapestry and One Epic, Multiple OnBase (EMO) for Hyperdrive have been released.

   - Though not related to Hyperdrive, the highly anticipated Epic Chart Search Integration is also available with this release!

• Now that OnBase 23.1 is available on the downloads page, please note that EP5/21.1 is no longer available for direct download.

   - To obtain new release builds of EP5, please contact your first line of support.

• Please check out Epic URL Integration - Encryption Algorithms Support for information on Epic’s new encryption methodology.

   - Follow that post for additional updates from Hyland as we have them available.

• Also, note that Medical Pop integrations (LongitudinalPop, MRNPop, and ChartPop) are not supported in Chrome or Epic Hyperdrive.

   - These products are from older versions of OnBase (v11 and v12), so most customers should not be using them.

   - If you are still using these, the solutions should be migrated to OnBase Patient Window or Hyland Clinician window prior to implementing Hyperdrive.

Dewey_Green
Content Contributor
Content Contributor

September 29, 2023 Update:

 

Hello everyone, I wanted to quickly update you that Epic has resolved the two SMART on FHIR caveats previously mentioned in the SMART on FHIR with Epic Hyperdrive Update post. Please reference the QA Note for each item and take the corresponding SU if your organization uses any workflows associated with the described behavior.

 

Printing from Epic Hyperdrive

In order to allow printing from OnBase an Epic setting must be changed to allow OnBase to open the print dialog screens in Hyperdrive controlled windows. Previously this setting was only available at the global level and changing it would impact all 3rd party applications. Epic rolled out an update that gives OnBase this privilege without impacting other 3rd party applications. For information on the Epic SU, have your Epic TS reference QA Note 7243369.

 

Scanning to invalid encounter types in Prelude

In Epic Prelude, it is possible to scan to encounter types that are not valid for scanning. This is the case with Hyperspace Classic and Hyperdrive.  With Hyperspace Classic, users are not alerted to the invalid scanning.  With Hyperdrive, Epic presents an error when scanning to these encounters. However the error does not appear until the end of the scanning process. Epic rolled out an update to address this and SUs go back to Epic Feb 2023. Please have your Epic TS reference QA Note 7256083 to get more information.

CurtisFox
Employee
Employee

November 9, 2023 Update:

While it's been almost two months since our last update, we've been hard at work improving the Epic integration. Some of the work has been behind the scenes and some of it is listed on our Known Issues pages. Here are some highlights:

 

Deficiencies

   - SD4E had in issue in 22.1 and 23.1 where it would only launch once - subsequent attempts to launch would result in an error. 

             - EP5/21.1 was not impacted. 

        - Resolved in 22.1.25.1000 & 23.1.4.1000.

   - DeficiencyPop Analysis has an issue that impacts solutions where documents can be scanned to child encounters in deficiency episodes.

        - DeficiencyPop only displays documents associated with the primary CSN/encounter and does not display documents associated with the child CSNs.

        - SD4E does not have this issue. 

        - Resolved in OnBase EP5 in 21.1.47.1000 (available 11/10/23) and will be resolved in upcoming 22.1 and 23.1 builds. 

             - Due to this issue, the minimum recommended build for the SMART on FHIR Hyperdrive integration for OnBase EP5/21.1 is now 21.1.47.1000 (see the Hyperdrive Wiki).

 

Healthcare Web Viewer

   - In some environments, high CPU usage may occur on VM hosts and/or client workstations where the Healthcare Web Viewer COM Integration for Epic is used.

   - Specific build ranges of OnBase EP5/21.1 and 22.1 are impacted, along with all released builds of 23.1.

   - Resolved in 21.1.47.1000.

   - See this page for more information: Potential for High CPU Usage with the Healthcare Web Viewer COM Integration for Epic

 

Integrated Scanning

   - SAS was not retaining the following user preferences/selections between launches:

             - Document Type (during indexing)

             - Window Size

             - Window Position

        - Resolved in 21.1.47.1000, 22.1.24.1000, and 23.1.4.1000. 

        - See this page for more information: SAS Will Not Retain Settings Between Launches

   - Improved Application Server resource utilization when launching FOS & SAS via the SMART on FHIR integration.

        - Also resolved an issue with FOS consuming multiple concurrent client licenses when multiple documents were uploaded and linked to Epic via FHIR.

        - Resolved in 21.1.47.1000, 22.1.25.1000, and 23.1.4.1000.