Single Sign-On – MiHIN
page-template-default,page,page-id-4549,mkd-core-1.0,wellspring-ver-1.2,mkdf-smooth-scroll,mkdf-smooth-page-transitions,mkdf-ajax,mkdf-grid-1300,mkdf-blog-installed,mkdf-header-standard,mkdf-fixed-on-scroll,mkdf-default-mobile-header,mkdf-sticky-up-mobile-header,mkdf-dropdown-default,mkdf-search-dropdown,wpb-js-composer js-comp-ver-4.12,vc_responsive

Single Sign-On


The Single Sign-On use case increases security by simplifying a user’s access and reducing the overall number of identities a participant must manage. The primary goal is to establish a single trusted identity and set of attributes that can be used by an individual or service between trusted data sharing organizations.

Currently, the task of electronically accessing health information often means logging into multiple, disconnected networks, portals, or databases. This means that users (physicians, nurses, pharmacists, etc.) must maintain and remember unique login IDs and passwords for each data source they use.

These multiple safeguards create obvious productivity-draining issues, including forgotten login information, passwords that need to be recovered and reset, or auto-lockout after multiple failed login attempts. Also, there are security risks inherent in users writing down passwords or keeping them simple or identical to ease memorization. The issues multiply with each additional login and password combination that a user must maintain, creating additional security risks and potentially taking a health professional’s valuable time away from caring for patients.

The following document(s) are available for this scenario:

Single Sign-On Use Case Summary

Single Sign-On Implementation Guide