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

TL;DR: A peer-reviewed study across 55 hospitals in four nations found clinicians can lose millions of hours a year to logins, with SSO and access management reducing fatigue, improving job satisfaction, and reclaiming 3.3 million hours of time according to Imprivata's cited research. In healthcare IAM, authentication is no longer just a security control, but a workflow and resilience issue.


At a glance

What this is: This is a healthcare IAM analysis showing that repeated logins are consuming clinician time and that single sign-on can reclaim productivity while easing security friction.

Why it matters: It matters because identity teams in hospitals must balance cyber controls with clinical throughput, and authentication design now directly affects both staff experience and patient care.

By the numbers:

👉 Read Imprivata's analysis of hospital login friction and SSO access management


Context

Hospitals are a clear case where identity friction becomes operational risk. Each additional application in the care pathway adds another authentication step, and when clinicians must repeat logins across EHRs, prescription systems, and lab portals, the cost is measured in time, fatigue, and workarounds rather than only in security metrics.

For IAM teams, this is fundamentally a human identity problem with direct governance consequences. SSO and access management reduce login burden, but the broader question is whether authentication policy is helping staff work safely or pushing them toward bypass behaviour that weakens compliance and user trust.


Key questions

Q: How should hospitals reduce login friction without weakening security?

A: Hospitals should centralise authentication with single sign-on, then apply session governance, role-based access, and reauthentication rules where data sensitivity demands it. The goal is to remove repetitive logins from care workflows while keeping auditability, privacy enforcement, and privilege boundaries intact. If users still need to bypass controls to do routine work, the design is failing operationally.

Q: Why does repeated authentication create risk in healthcare environments?

A: Repeated authentication creates risk because it increases cognitive load, slows care delivery, and encourages workarounds. In hospitals, that often shows up as shared sessions, delayed logout, or skipped security steps. Those behaviours weaken compliance and make access control less reliable. Friction becomes a governance problem when the control is too cumbersome to use consistently.

Q: How do you know if SSO is actually improving identity governance?

A: SSO is working when login counts fall, clinicians spend less time reauthenticating, and workaround behaviour declines without a rise in unauthorised access. The best signal is operational: staff can move through critical applications with less friction while privacy and audit requirements still hold. If user satisfaction improves but control evidence disappears, the programme needs recalibration.

Q: Who is accountable when hospital access controls create unsafe workarounds?

A: Accountability sits with the identity, clinical operations, and security teams together, because workflow design and access policy are inseparable in healthcare. If access controls push users toward insecure shortcuts, the programme owner must treat that as a governance failure, not a user discipline problem. Regulators and auditors will care whether the control was usable in practice.


Technical breakdown

Why repeated logins create a security and workflow bottleneck

In healthcare environments, every separate system often means a separate authentication event, session context, and timeout policy. That multiplicity increases cognitive load and creates friction at the point of care. When access is fragmented across EHRs, medication tools, and ancillary portals, clinicians spend time proving identity instead of using the system. The result is not only lost productivity but a higher chance of insecure shortcuts such as shared sessions, delayed logout, or avoided workflows. Single sign-on reduces that burden by centralising authentication and preserving access continuity across applications.

Practical implication: map every clinician workflow that still depends on repeated sign-ins and prioritise it for SSO consolidation.

How access management changes clinician session control

Single sign-on works best when paired with access management that governs session duration, reauthentication triggers, and application-level entitlements. In practice, this means one trusted login can unlock multiple systems without forcing clinicians back through the full password cycle for each task. The control value is not convenience alone. It is the ability to reduce authentication friction while still preserving auditability, privacy enforcement, and role-based access boundaries. For healthcare, that balance matters because interrupted workflow often drives the very noncompliance that security teams are trying to prevent.

Practical implication: pair SSO rollouts with session and entitlement policy reviews so convenience does not outpace control.

Why login friction becomes a governance issue, not just an IT issue

Login friction in hospitals affects staffing resilience, morale, and the practical enforceability of privacy controls. If a process is too slow or cumbersome, users adapt around it. That makes identity governance part of operational risk management, because the quality of authentication design affects whether policy is followed in the real world. The cited study shows the value case clearly, but the deeper lesson is that access design shapes clinical behaviour. Identity controls that ignore user workload invite workarounds, while controls aligned to care delivery support both compliance and service continuity.

Practical implication: treat clinician authentication as a governance control that must be tested against frontline workflow reality.


NHI Mgmt Group analysis

Authentication is now a care-delivery control, not just an access gate. In hospitals, repeated login prompts consume clinician attention at the exact moment it is most expensive. That turns identity friction into an operational constraint that affects throughput, staff fatigue, and the reliability of privacy practices. The implication is that IAM decisions in healthcare must be judged against clinical workflow impact, not only against policy compliance.

Login fatigue creates an enforcement gap that security teams cannot ignore. When access is cumbersome, users work around controls through shared devices, delayed logout, or skipped steps. That pattern does not mean users are careless, it means the control design is misaligned with the environment. The implication is that access governance in healthcare must be measured by how well it reduces bypass behaviour, not by how many policies exist on paper.

SSO/AM is best understood as identity consolidation for high-friction human identity journeys. The value is not only reduced password volume but also lower cognitive overhead across multi-application clinical workflows. That matters because fragmented identity journeys create a cumulative tax on both security and care delivery. The implication is that hospitals should evaluate SSO as part of workforce resilience and patient safety planning, not as a narrow desktop convenience project.

Healthcare identity programmes need a clinical utility lens alongside a security lens. The article shows that time recovered through better access design can translate into better decisions, smoother workflows, and stronger compliance behaviour. That is a broader IAM lesson for human identity programmes in regulated environments: if a control adds friction without proportional risk reduction, it will be resisted. The implication is that identity teams should design for enforceable usability, not theoretical control purity.

From our research:

What this signals

Clinician identity friction is becoming a board-level operations issue. Hospitals that treat authentication as a pure security function will keep absorbing hidden productivity costs. As access journeys become more complex, identity teams should expect pressure to show measurable gains in throughput, staff satisfaction, and policy adherence, not just compliance coverage.

Login behaviour is a better signal than policy count. If clinicians are still bypassing controls to move through care tasks, the programme is too rigid for the environment. Teams should watch for declining logout discipline, repeated credential prompts, and higher ticket volume around access just as closely as they monitor audit findings.

Access modernisation will increasingly be judged by workforce impact. In regulated environments like healthcare, identity programmes that reduce friction while preserving control will have a stronger business case than programmes that optimise for control density alone. The next maturity step is proving that access governance supports care delivery instead of impeding it.


For practitioners

  • Map login-heavy clinical workflows end to end Identify where clinicians reauthenticate across EHRs, lab systems, prescribing tools, and shared workstations. Use that workflow map to prioritise the systems where SSO will remove the most repetitive access steps and the most risky bypass behaviour.
  • Pair SSO with session governance Define when reauthentication should occur, how long sessions remain valid, and which applications need stricter step-up checks. SSO should reduce credential burden, not eliminate visibility into who is accessing sensitive clinical data and when.
  • Measure authentication friction as an operational metric Track login counts per shift, time lost per user group, and the rate of workarounds such as shared sessions or delayed logout. These indicators show whether identity policy is helping staff comply or pushing them toward unsafe shortcuts.
  • Tie identity improvements to workforce resilience goals Position access modernisation as part of burnout reduction, productivity recovery, and care continuity. That framing helps leadership evaluate identity investment as a clinical operations issue as well as a cybersecurity programme.

Key takeaways

  • Repeated logins in hospitals are not a minor annoyance, because they consume clinician time, increase fatigue, and encourage unsafe workarounds.
  • The research case for SSO is strongest when identity teams measure both operational recovery and compliance behaviour, not just credential reduction.
  • Healthcare IAM programmes should be designed around clinical workflow reality, because access controls that staff cannot live with will not be followed consistently.

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-63Federated login and authentication assurance underpin hospital SSO design.
NIST CSF 2.0PR.AAIdentity and access authorization directly affects healthcare workflow control.
NIST Zero Trust (SP 800-207)PR.AC-1Zero Trust emphasizes continuous access decisions in sensitive clinical environments.

Use assurance levels and session rules to reduce friction without weakening authentication strength.


Key terms

  • Single sign-on: Single sign-on is an authentication pattern that lets a user sign in once and access multiple systems without repeating full logins. In healthcare, it reduces clinician friction and supports safer workflow continuity, but it still needs session controls and entitlement governance to preserve auditability and privacy.
  • Access management: Access management is the set of controls that governs how authenticated users move through applications, sessions, and entitlements. In a hospital setting, it helps ensure clinicians can reach the systems they need quickly while still enforcing role boundaries, logging, and reauthentication where risk demands it.
  • Authentication friction: Authentication friction is the operational burden created when users must repeatedly prove identity to complete routine work. In regulated environments, high friction can reduce compliance because people start bypassing controls, so identity teams must balance assurance with usability.

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: New Data Shows Hospitals Lose Millions of Hours to Logins, Driving Demand for Single Sign-On. Read the original.

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