Release Notes 3.0.0 - 3.0.2

EPCS (E-Prescription Controlled Substances) for Epic Hyperspace and Hyperdrive, version 3.0

Release Notes

Overview - All Versions
Starting with release 3.0.0, the EPCS authentication plugin now supports both Hyperspace (VB) and Hyperdrive versions released in 2022 and later.

Version 3.0.3

• HEALTH-932 EPCS not responding during audit stage

Known Issues
-none-

Further Information

Version 3.0.2

• HEALTH-677 Fix for using biometric device for EPCS

Known Issues
-none-

Further Information
Please consult the product documentation for further information, including how to install and configure this release.

Version 3.0.1

• HEALTH-579, HEALTH-706 Hyperdrive was appearing frozen while EPCS PingMe was in process, with no indication it was waiting on anything. The PingMe window was appearing behind the Hyperdrive window and is now appearing on top to provide a better indication of what to do next

• HEALTH-721 Remove support for storing the SAML cert in the Enterprise trust store due to OS limitations on private key functionality in that store

• HEALTH-723 EPCS PingMe progress status screen was not showing after initiating a mobile PingMe request

• HEALTH-734 Fixed problems related to multiple consecutive EPCS order authorization failing

• HEALTH-706 EPCS not working without EpicAuth primary login badge tap application installed and configured

Version 3.0.0

• Support for Hyperdrive now included.
• Creating and configuring a SAML certificate to use for authentication is required if you are using Hyperdrive
• Identity Automation Epic Auth plugin v4.1.0 or greater is required when using Epic Auth for primary login in addition to EPCS