By NHI Mgmt Group Editorial TeamPublished 2025-11-07Domain: Governance & RiskSource: Imprivata

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.


At a glance

What this is: This analysis shows that single sign-on and access management can reduce clinician login friction while improving security, privacy compliance, and workflow efficiency in hospital environments.

Why it matters: It matters because IAM, PAM, and identity lifecycle teams need controls that reduce access burden without encouraging shared credentials, workarounds, or weaker auditability.

By the numbers:

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


Context

Single sign-on and access management in hospitals is not just an authentication convenience. In clinical settings, every extra login can interrupt care, increase fatigue, and encourage unsafe workarounds such as shared logins or staying signed in longer than policy intends.

For identity teams, this is a human IAM problem with security consequences. The core challenge is to reduce access friction while preserving auditability, session integrity, and strong authentication across high-pressure, multi-application workflows.

The research discussed here is a typical example of why healthcare identity programmes must be judged on both security control and operational fit. If the access model slows frontline work, users will eventually route around it.


Key questions

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. The goal is not to remove security checks, but to reduce repeated prompts that drive unsafe workarounds and interrupt care delivery.

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. In healthcare, those shortcuts weaken auditability and privacy protection, so access friction becomes an identity governance issue as well as an operational one.

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. Those metrics show whether access management is actually reducing friction while preserving auditability, session integrity, and secure access across busy clinical workflows.

Q: How can organisations tell whether access management is improving care delivery?

A: They should look for reduced login time, fewer interruptions, and more time returned to frontline work. If the control is effective, clinicians spend less time authenticating and more time on patient care, while security and privacy requirements remain intact.


Technical breakdown

Why hospital SSO changes the access model

Single sign-on changes the number of times a clinician must prove identity across EPRs and supporting applications. Instead of reauthenticating separately for each system, the user establishes a trusted session once and then moves through approved resources with fewer interruptions. In healthcare, that matters because workstation turnover, roaming staff, and multi-user environments create repeated authentication events that are hard to sustain during patient care. Strong SSO is not the same as weaker security. When paired with two-factor authentication, smartcard integration, and session locking, it can reduce login burden while keeping access evidence, authentication strength, and accountability intact.

Practical implication: reduce repeated prompts without weakening assurance by pairing SSO with session controls and strong authentication.

Session integrity in multi-user and kiosk environments

Hospitals often use shared workstations, kiosk-style devices, and roaming access patterns. That creates a risk that convenience features become shared access behaviours unless the session is explicitly managed. Automatic locking and reauthentication preserve session integrity when a clinician steps away or hands off a device, while still allowing rapid return to work. This is where access management differs from simple password reduction. The control objective is not merely faster entry, but controlled continuity of identity across a shifting clinical environment. Without that boundary, faster access can easily become persistent access.

Practical implication: enforce automatic lock and reauthentication on shared devices to stop convenience from becoming standing access.

Shared logins, workarounds, and the security debt they create

When clinical staff face repeated logins, they do not stop working. They improvise. The article describes shared logins and avoiding logouts as productivity workarounds, both of which weaken traceability and blur accountability. Those behaviours are a governance signal, not just a user complaint. They show that the access design is misaligned with task cadence and role mobility. In identity terms, the problem is not only authentication fatigue, but the accumulation of security debt when policy and workflow diverge. Reducing that gap is essential if audit, privacy, and operational resilience are all meant to hold at once.

Practical implication: treat user workarounds as evidence of identity design failure and remove the friction that drives them.



NHI Mgmt Group analysis

Clinical access friction is a governance failure, not a usability annoyance. The study shows that repeated logins, password fatigue, and shared-workstation behaviours are symptoms of an identity model that does not fit clinical work. In high-throughput care settings, identity controls must support accountability without forcing clinicians into unsafe shortcuts. The implication is that access governance has to be judged against real workflow, not policy intent.

Session-based access control is the right lens for shared healthcare environments. The combination of SSO, two-factor authentication, smartcards, automatic locking, and reauthentication works because it preserves a known identity boundary while reducing repeated prompts. That is especially relevant where clinicians move across desktops, kiosks, and departments. The practitioner takeaway is to design for session continuity with explicit termination, not assume a single workstation equals a single user for the whole shift.

Access productivity and security are not opposing goals when the control model is correctly aligned. The reported 60% reduction in desktop login time and more than 50% faster application access show that access management can support both care delivery and security outcomes. This matters because programmes that force a trade-off between auditability and speed usually lose both. The implication is to measure identity controls by whether they improve the work they are meant to protect.

Identity governance in healthcare must account for clinician behaviour under pressure. Hospitals do not fail because users dislike security in the abstract. They fail when security adds delay in moments where clinicians are trying to deliver care. That makes friction itself a risk input for IAM, PAM, and access governance decisions. The practitioner conclusion is to treat clinician workflow as part of the control design, not as a downstream user-training issue.

From our research:

  • 79% of organisations have experienced secrets leaks, with 77% of these incidents resulting in tangible damage, according to Ultimate Guide to NHIs.
  • 91.6% of secrets remain valid five days after the targeted organisation is notified, which shows how slowly identity-related exposure can be remediated in practice.
  • That remediation lag makes NHI Lifecycle Management Guide the next place to look if your programme also struggles with revocation, rotation, and offboarding discipline.

What this signals

Clinician-facing identity controls should be judged on the amount of time they return to care. In this study, the signal was not just faster authentication, but a measurable shift in clinician effort away from keyboard work and toward patient work. That is a useful programme-level model for health systems, where access governance has to support both security and throughput.

Access fatigue is a leading indicator of future identity workarounds. When clinicians are forced into repeated logins, they will predictably prefer shared access, delayed logout, or other shortcuts that erode control quality. Identity teams should treat rising friction as an early warning signal, not a user-experience complaint.

The broader implication is that healthcare IAM programmes need metrics that combine assurance and operational value. For readers building a stronger digital identity programme, the question is whether access controls are reducing risk without creating hidden workflow debt.


For practitioners

  • 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. Use those findings to target the highest-friction care settings first.
  • 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.
  • Measure success in time returned to care Track login duration, application access time, and hours returned to patient care, then report those measures alongside security and audit outcomes.

Key takeaways

  • The central problem is not authentication alone, but the operational harm caused when identity controls slow clinical work.
  • The evidence is concrete: hospitals saw major reductions in login time and large amounts of clinician time redirected back to care.
  • The right response is to align SSO, session integrity, and strong authentication with the realities of shared clinical workflows.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-63, NIST CSF 2.0 and NIST Zero Trust (SP 800-207) set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-63Strong authentication and session handling are central to the hospital access model.
NIST CSF 2.0PR.AC-1Identity proofing and access control underpin secure clinician access across shared devices.
NIST Zero Trust (SP 800-207)AC-1Zero trust supports continuous verification in shared and mobile clinical environments.

Use phishing-resistant, high-assurance authentication where clinical workflows demand both speed and accountability.


Key terms

  • Single Sign-On: Single sign-on is an access pattern that lets a user authenticate once and reach multiple approved applications without repeating credentials at every step. In healthcare, it reduces login burden while preserving accountability when paired with strong authentication and session controls.
  • Access Management: Access management is the control layer that determines how identities obtain, use, and retain access to systems and data. For clinical environments, it has to balance speed, auditability, and secure session handling across shared devices and fast-moving workflows.
  • Session Integrity: Session integrity is the assurance that an authenticated session remains tied to the right user and ends when it should. In hospital environments, it depends on locking, reauthentication, and clear handoff rules so convenience does not turn into uncontrolled access.
  • Workaround: A workaround is an informal user behaviour that bypasses intended controls to keep work moving. In identity programmes, recurring workarounds are often a sign that access design and operational reality are misaligned, which can weaken audit trails and privacy protections.

Deepen your knowledge

NHI governance, agentic AI identity, and machine identity lifecycle are core topics in our NHI Foundation Level course, the industry's only accredited NHI security programme. If you are responsible for identity security strategy or NHI governance in your organisation, it is worth exploring.

This post draws 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. Read the original.

NHIMG Editorial Note
Published by the NHIMG editorial team on 2025-11-07.
NHI Mgmt Group — the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org