Change user on lock screen

From Galen Healthcare Solutions - Allscripts TouchWorks EHR Wiki
Revision as of 19:16, 30 April 2018 by Crystal.Vervaecke (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Preference functionality

In the Web Framework preferences of Allscripts Enterprise EHR, there is a preference that enables or disables the 'Change' button to appear on the Lock screen. The preferences is located in Admin > Preferences and is entitled "SwitchUser".

WF Preference.JPG

This preference adds a button to the lock screen that will allow the logged-in user to be changed from the lock screen within the same session.

Change button.JPG

When the user changes and enters their username, it will navigate the new user to the same place in the last patient's chart before the previous user clicked the Lock button.

New user.JPG

This can be very beneficial for exam room workflows so that the physician can use the same session to get directly back to where the nurse/MA left off on the patient being seen and can make this workflow more efficient.


There are a couple of considerations to be aware of before enabling this preference, including:

1. If you have different workplaces built based on different user roles, this can cause a bit of confustion. For example, if your providers have a different workplace than your clinical staff and the change feature is used, the new user will be directed to the same place in the last user's workplace. This can be confusing since it may be an unfamiliar workplace for the new user, however there are no risks of the new user accessing elements of a different workplace if they do not have the associated security classifications. When the new user clicks somewhere else in the workplace, the system will refresh it and show them their correct workplace for the new user.

2. This preference has been known to be problematic based on your system auto-timeout settings as well as when working within a Citrix environment.


Back to Application Troubleshooting