To make things easier for our hospitalist groups at both major hospitals, we have implemented having a Vocera "app" within Epic. Essentially, there is an app section built into both Epic builds, and there is a Vocera button that launches Vocera Web Console within Epic.
What was noticed as a frustration point for our Physicians at both hospitals is that they traditionally utilize a autologon PC rather than logging into the PC with their NT/AD creds. This was communicated to the physicians that Web Console can only take Windows/AD credentials from the workstation, and cannot pull any other authentication from Vocera on a previous case opened.
Since we continue to get inquiries about this as an adoption point, as Vocera thought about maybe figuring out a way to work with native API within Epic to allow authentication to be made within Epic for Web Console/Staff Assignment? While I know that this is some work, it should be noted that numerous other applications use this technology and have gotten it to work. For example:
- Physician sits down at an autologin PC.
- Physician opens Epic.
- Physician opens their "apps" section, and clicks on Vocera.
- Vocera requires the Physician to log in.
- Same Physician then accesses Muse from their "apps" section.
- Muse doesn't require the Physician to log in. It authenticates based off the user's login into Epic.
Muse is able to accomplish this by use of API. Is this something that is possible to be looked at/put into development, or is the permanent answer always going to be that the only way it can authenticate on an autologon PC is via Windows/AD credentials from the workstation, and cannot pull any other authentication? Providers have noted that they would be more apt to use the text feature of Vocera through web console if they didn't have to login all of the time. It would also save the clinician's time.
Guest
