Overview

Download a PDF of this guide.

Imprivata Patient Access leverages the Epic1 Generic Authentication framework to initiate external patient authentication, subsequently returning the authenticated patient to Epic. Following activation by the Generic Authentication framework, Imprivata Patient Access executes a standalone SMART on FHIR launch to enable secure authentication and data exchange with the Epic FHIR server. Additionally, Imprivata Patient Access uses the backend OAuth 2.0 for authentication with the customer's HL7 interface, facilitating secure photo uploads to Epic.

This documentation focuses on the steps required to enable and configure SMART on FHIR launch and photo upload in your environment. For instructions on configuring generic authentication, see Patient Lookup Setup and Support Guide.

To integrate with the SMART on FHIR and backend OAuth 2.0 technologies on Epic’s platform, Imprivata Patient Access has registered two applications on the Epic Vendor Service website.

Epic customers must request, download, and implement the Imprivata Patient Access application in their environments. The Imprivata Patient Access - Photo Upload application is optional, so if the Epic customer wants that feature, they must request, download, and implement both applications.

Below are the application names and client IDs required during the application request process.

Client IDs

Application Name Non-production Client ID Production Client ID Description
Imprivata Patient Access 303a4d28-aad2-48af-a40d-f3cc3c1c825f 233370ff-7785-4d83-8753-9477f5331dbf

Allows Imprivata Patient Access to perform standalone SMART on FHIR launch

Required to enable the main workflows of Imprivata Patient Access.
Imprivata Patient Access – Photo Upload e2673269-0ebe-4ed9-99cd-3ddf5b72ba12 8b3dfe11-91be-421b-80ae-cb53f8d7cf09

Allows Imprivata Patient Access to upload photos to customer using HL7 via HTTPs.

This is an optional feature.

Epic ProgID

ProgID: Imprivata.PatientAccess.EpicDesktop

The ProgID is used by Epic to determine which application to call when a biometric workflow for patient identification is triggered from within Epic.

This specific ProgID will cause Epic to invoke the Imprivata Patient Access Epic Connector in such workflows, enabling communication between Epic and the Imprivata Patient Access Registrar Client.

Documentation Resources

Review the following Epic documentation and tutorials, available from the Epic UserWeb for your organization: