MFA for Electronic Prescribing for Controlled Substances (ePCS)

This is an Early Access feature. To enable it, contact Okta Support.

The guide below outlines the setup process to install the Okta Multifactor Authentication (MFA) provider for ePCS.

Electronic Prescribing for Controlled Substances (ePCS) eliminates paper prescriptions entirely by allowing clinical prescribers to electronically write prescriptions for controlled substances. It also permits pharmacies to receive, dispense and archive these e-prescriptions.

ePCS also creates new “Identity Proofing” responsibilities for vendors, prescribers, and pharmacies by requiring two-factor authentication, more robust audit trails and strict auditing procedures in order to comply with the Interim Final Rule regulating ePCS of the U.S. Drug Enforcement Administration (DEA).

The following diagram shows the information flow.

Topics

Before you begin

Ensure the following:

  • User:
    • Must exist in Okta
    • Must be assigned the Epic Hyperspace app in Okta
    • Must enroll in MFA prior to performing a ePCS transaction.
  • Administrator must configure Citrix servers to allow users write access to the log folder.
    Typically C:\Program Files (x86)\Okta\OktaHyperspaceLoginDevice\logs

Supported Factors

The following MFA Factors are supported:

Important Note

When integrating with Okta RADIUS, the maximum supported number of enrolled factors is dependent on the size of resulting challenge message. Okta recommends that no more than eight ( 8 ) factor be enrolled at one time.

MFA Factor Password Authentication Protocol
PAP
Extensible Authentication Protocol - Generic Token Card
EAP-GTC
Extensible Authentication Protocol - Tunneled Transport Layer Security
EAP-TTLS
Okta Verify (TOTP and PUSH) Supported Supported Supported - as long as challenge is avoided.
For example:
MFA-only or password, MFA for TOTP.
Push can work with primary auth + MFA as the push challenge is sent out-of-band.
Voice Call Supported Supported Not supported
SMS Authentication Supported Supported Not supported
Google Authenticator Supported Supported Supported - as long as challenge is avoided.
For example MFA only or password, MFA.
Symantec VIP Supported Supported Supported
Security Question Supported Supported Not supported
Custom TOTP Authentication Supported Supported Not supported
Duo(Push, SMS and Passcode only) Supported Not supported Not supported
YubiKey Supported Supported Supported

RSA Token

Supported

Supported

Supported

Email

Supported

Supported

Not supported

Info

Note

The U2F Security and Windows Hello MFA factors are not compatible with RADIUS-enabled implementations.
For additional information about the Radius apps refer to Configuring RADIUS applications in Okta.

 

Typical workflow

Task

Description

Configure TLS
Configure Okta for ePCS

Configure end users/groups, MFA factors and the Epic Hyperspace EPCS app.

Download the agent
Install the agent
  • Install the Okta Hyperspace agent.
Configure a Device in Chronicles
  • Configure a new device in Chronicle.
Configure Hyperspace
  • Configure Hyperspace to integrate with Okta.
Test User Login Process
  • Test login flow

Additional considerations