Duo integrates with Epic Hyperspace to add two-factor authentication to Epic Hyperspace e-Prescription workflows.
Duo Authentication for Epic is a client-side .NET component that provides two-factor authentication for Epic Hyperspace 2010 and later (up to and including Hyperspace 2019). It must be installed on all Epic workstations to provide complete protection. Duo Authentication for Epic requires .NET Framework 4, Windows Installer 4.0 or later, and the Epic Hyperspace client installed on the local system to function; none of which are included with the Duo Epic installer.
In Epic Hyperspace terms, Duo Authentication for Epic is a "Direct authentication device"" capable of "User" authentication only. If configured as a "Passive authentication device", or to authenticate "Patient" logons, the Duo device will report an error message and return a failure to Epic.
Duo Authentication for Epic does not support inline self-enrollment, as Duo Security is not a qualified credential service provider (CSP) or certificate authority (CA) for EPCS identity verification purposes. You'll need to enroll your users ahead of time using directory synchronization, CSV import, or another method. Read the enrollment documentation to learn more about these options.
One-time passcodes (OTP) are validated to meet FIPS 140-2 Level 1 per the table below. For the purpose of EPCS compliance, choose between available authentication methods (OTP, Duo Push, phone call, or hardware token) that meet your compliance team’s interpretation of the Federal EPCS Guidelines.
|OTP Method||Meets EPCS compliance for FIPS 140-2 Level 1?|
|Hardware Token||Verify compliance with your token vendor|
|Duo Mobile Passcodes (iOS 6+)||Yes|
|Duo Mobile Passcodes (Android)||Yes with Duo Mobile for Android 3.25.0 and later|
|Duo Mobile Passcodes (Windows Phone)||Yes with Duo Mobile for Windows Phone 2.0 and later|
|Duo Mobile Passcodes (BlackBerry)||No - Disable BlackBerry use with an Operating System policy|
|SMS Passcodes||No - Disable SMS use with an Authentication Methods policy|
|Duo Bypass Codes||No - Do not issue bypass codes to EPCS users. Consider preventing your Help Desk admins from creating bypass codes for users.|
This application communicates with Duo's service on TCP port 443. Firewall configurations that restrict outbound access to Duo's service with rules using destination IP addresses or IP address ranges aren't recommended, since these may change over time to maintain our service's high availability. If your organization requires IP-based rules, please review this Duo KB article.
If Duo Authentication for Epic is unable to contact the Duo Security cloud service then Duo "fails closed" and reports the failure to Epic Hyperspace. The defined Epic application workflow determines the next action.
If you're delivering the Epic client via application virtualization (like Citrix XenApp or Microsoft Remote Desktop Services), you should install Duo Authentication for Epic at the application host — not the end-user workstation.
Duo has partnered with Identity.com, an identity verification provider, to validate your Duo end users' identity. Identity Proofing (or ID Proofing) requires that users answer a series of questions during enrollment as identity verification.
Deploying Duo's ID Proofing automatically disables use of the following Duo authentication methods that don't meet the FIPS 140-2 requirement with the Epic application.
Before moving on to the deployment steps, it's a good idea to familiarize yourself with Duo administration concepts and features like options for applications, available methods for enrolling Duo users, and Duo policy settings and how to apply them. See all Duo Administrator documentation.
Check your Windows version before starting. This configuration works with Windows Vista and later client operating systems, and Windows 2008 and later server operating systems.
The security of your Duo application is tied to the security of your secret key (skey). Secure it as you would any sensitive credential. Don't share it with unauthorized individuals or email it to anyone under any circumstances!
Run the Duo Authentication for Epic installer with administrative privileges on the system(s) where the Epic client is installed. Accept the license agreement and enter your integration key, secret key, and API hostname when prompted:
To add Duo Authentication to Epic Hyperspace, you will need to add the Duo application as an authentication device, and add that device as an authentication method to your desired context.
Please contact your Epic technical support representative for detailed instructions and more information about adding authentication devices.
Note that the Duo Prompt shown by the Epic application does not support self-service enrollment nor device management. The test user must be enrolled in Duo with a device for 2FA request approval.
To test your setup, log into Epic Hyperspace and perform a test e-Prescription workflow. The Duo Prompt appears after you enter your Epic username and password. Upon approval of the Duo authentication request on your selected device, the Duo client passes the approval to Epic Hyperspace and the e-Prescription workflow resumes.
If you cancel either the Epic or Duo authentication prompts, you are taken back to the signing step of the e-Prescription workflow.
Additional client-side configuration options for Duo may be configured via Active Directory Group Policy. To create and apply the Duo Authentication for Epic Group Policy Object (GPO):
Extract the contents of the zip file and copy the files into your domain's Administrative Templates store.
Apply the new GPO for Epic to domain member workstations by linking the policy to the desired OU or container.
For additional information about using GPOs and administrative templates, please see Microsoft's Group Policy documentation collection.
Please contact Duo Support if you need to configure the Duo Authentication for Epic client settings without using Group Policy.