New ‘Reference Architecture’ Guide Helps Customers Implement Imprivata OneSign Single Sign-On with Epic Systems

Joel Alcon
Oct 15, 2018

We know how time-consuming it can be to identify the various types of clinical workflows within a healthcare organization and then deploy technology securely without creating disruptions for end-users. How do you enable single sign-on into the EHR for each clinician, even though some may be accessing via shared workstations or through virtual desktops? These types of questions are top-of-mind for organizations that are implementing single sign-on (SSO) with Epic for the first time, as well as for existing SSO customers that are making significant architectural changes, such as migrating from another EHR to Epic, or implementing virtual desktops and applications.

As a result, we created a reference architecture guide, Imprivata OneSign with Locally Hosted Epic EHR, to help organizations address these challenges and plan for, design, and implement Imprivata OneSign with Epic in a way that improves security without sacrificing end-user satisfaction with technology or introducing disruptions to clinical workflows. The architectures detailed in this guide are well-proven configurations that have been designed around the clinician experience and have been successfully implemented by hundreds of Imprivata customers. The technical guidance was developed by Imprivata technical teams and are a foundation of Imprivata test and development methodologies. By following the recommendations in this guide, customers can expect to minimize the time spent with technology and reduce the operational risks involved in the planning, design, and implementation of Imprivata OneSign with Epic.

To introduce this guide to our customers, we recently held a webinar and took the opportunity to survey attendees to learn more about their process for planning, designing, and implementing new technology. We found that most organizations are taking a user-centric approach and engaging either physicians, nurses, and/or the CMIO/CNIO when implementing new end-user-facing technology. We anticipate that as organizations install Imprivata OneSign with Epic, or as they plan any significant architectural changes within their organization, they will leverage our reference architecture to identify workflows that may fit their technology needs and their clinical workflows.

The reference architecture guide, Imprivata OneSign with Locally Hosted Epic EHR, is only available to Imprivata customers and can be found on the Imprivata Support and Learning Center. If you have any questions – whether you are an existing customer or an organization looking to implement enterprise single sign-on with your deployment of Epic – we encourage you to contact us.