Subscribe to the Non-Human & AI Identity Journal

Notifications
Clear all

Single sign-on in hospitals: what it means for IAM teams


(@nhi-mgmt-group)
Member Moderator
Joined: 1 year ago
Posts: 8151
Topic starter  

TL;DR: Single sign-on and access management cut desktop login time by 60%, sped application access by more than 50%, and redirected 3.3 million clinician hours annually across 55 hospitals, according to Imprivata research from Imprivata and George A. Gellert, published in AHISP. The security lesson is clear: in healthcare, access friction is itself an operational and privacy risk, not just a user-experience issue.

NHIMG editorial — based on content published by Imprivata: clinician time savings and financial value of workstation single sign-on and access management in the United Kingdom and Ireland

By the numbers:

Questions worth separating out

Q: How should hospitals reduce login friction without weakening identity controls?

A: Hospitals should use single sign-on with strong authentication, session locking, and reauthentication so clinicians can move quickly without losing accountability.

Q: Why do repeated logins create security risk in clinical environments?

A: Repeated logins increase fatigue and encourage behaviours such as shared credentials, delayed logout, and session reuse.

Q: What should identity teams measure after deploying SSO in hospitals?

A: Teams should measure login duration, application access time, user-switching events, and the frequency of workarounds.

Practitioner guidance

  • Map login friction to clinical workflow risk Measure how many authentication events each role faces per shift, then compare that with observed workarounds such as shared logins or staying signed in.
  • Pair SSO with strong assurance controls Deploy single sign-on together with two-factor authentication, smartcard integration, automatic locking, and reauthentication so that faster access does not reduce session integrity.
  • Treat workarounds as control failures If clinicians are bypassing logout or sharing accounts, classify that as an access governance defect and redesign the workflow before expanding the rollout.

What's in the full report

Imprivata's full article covers the operational detail this post intentionally leaves for the source:

  • The full study methodology, including how login times were measured across 55 hospitals and multiple clinical settings.
  • The hospital-by-hospital financial value model behind the reported clinician time savings.
  • The workflow differences between multi-user desktops, kiosks, and roaming clinician environments.
  • The research paper's published findings and supporting context in AHISP.

👉 Read Imprivata's analysis of clinician time savings from single sign-on and access management →

Single sign-on in hospitals: what it means for IAM teams?

Explore further

View Full Forum →  |  NHI Foundation Course →



   
Quote
Share: