Posted by
Shawn Riley in Wednesday, September 1st 2010
It can be frustrating to remember multiple passwords for different computer applications. Not to mention the fact that as a clinician it is very time consuming logging in and out of applications over and over, especially if you have to look up the patient every time. Instead of struggling to remember the different user names and passwords, there is now an easy way to manage multiple logins with a single-sign on product (SSO). A SSO server stores these different passwords in a safe database and makes it available to the user (typically physician or nurse) transparently during the login process. The end result is that the user has to sign in just once.
Advantages of a Single Sign On product
SSO products offer benefits to both users as well as organizations. End users have to remember only one password instead of multiple details for different applications. This eliminates the need for users to resort to unsecure practices such as writing their passwords in visible areas where it is accessible to other users. Also, they are required to log in only once a day, and this offers easier and quicker access to all clinical applications and data.
For organizations, opting for a SSO product reduces operational costs, as they do not have to spend time and money on retrieving forgotten passwords for employees. Furthermore, from a security point of view, SSO systems are easier for the management and IT team to protect, update and secure data. For example, restrictions on a minimum password length and special character can be imposed, users can be ‘locked out’ of their account after several unsuccessful attempts; and reset their passwords at regular intervals, inactivity session timeouts can be enforced, and so on.
Maneuvering the EMR is often much easier with a SSO, especially when you have different applications holding different patient information. Systems like Meditech and AllScripts have single sign on interfaces, but even with these systems, you need to have a different login for things like PACS, ECM, ERP, etc. SSO simplifies the process for the provider considerably. An SSO typically handles “user-context” (the interface to the user of the computer), but may also handle “patient-context” (the ability to look up the patient in each of your applications instead of the physician or nurse looking them up). We will cover patient context in another article, but it is a feature to watch for.
Desirable features of SSO …click here to read more