Hyperdrive Updates - Follow for Email Notifications

[CurtisFox]

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
  • 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.