‘Reference Architecture’ guide helps customers implement Imprivata OneSign Single Sign-On with Epic systems
We know how time-consuming it can be to identify 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 (SSO) 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 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.
Insightful guidance for optimizing Imprivata OneSign with locally hosted Epic
Our reference architecture guide, Imprivata OneSign with Locally Hosted Epic EHR, was created to help organizations address these challenges and plan for, design, and implement this technology in a way that improves security without sacrificing end user satisfaction 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 successfully implemented by hundreds of Imprivata customers. This guidance was developed by Imprivata technical teams and comprises the 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.
Leveraging feedback to improve the customer experience
To introduce this guide to our customers, we held a webinar and surveyed attendees to learn more about their process for planning, designing, and implementing new technology. We found that most organizations follow a user-centric approach, including by engaging 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, this reference architecture/guide will prove useful for identifying workflows that fit their specific technology needs and clinical workflows.
Interested in accessing this guide?
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’re an existing customer or an organization looking to implement enterprise SSO with your deployment of Epic – we encourage you to contact us.