Single sign-on in hospitals shows the access-security trade-off

At a glance

What this is: This is a hospital SSO and access management study showing that reducing authentication friction can improve clinical workflow while preserving privacy and audit controls.

Why it matters: It matters because IAM teams in healthcare have to balance access speed, session integrity, and compliance without forcing clinicians into risky workarounds.

By the numbers:

• Using single sign-on and access management cut desktop login time by 60% across the study hospitals.
• Application access became over 50% faster after deployment.
• The broader model estimated 71 million hours of clinician time could be freed annually across eligible hospitals.

Context

Single sign-on in hospitals is an access governance problem as much as a usability problem. Clinicians often need to move across many applications under pressure, but mandatory passwords, shared logins, and repeated authentication events can slow care and encourage unsafe workarounds.

Imprivata’s discussion of the study centres on that tension: hospitals want strong privacy protection, auditability, and session control, yet the access path must stay fast enough for clinical work. The practical question for IAM teams is whether security controls are shaping behaviour or causing clinicians to bypass them.

The article’s core finding is that workflow-sensitive access controls can support both care delivery and compliance when session integrity, two-factor authentication, and automatic locking are preserved.

Key questions

Q: How should healthcare organisations reduce login friction without weakening access control for clinical systems?

A: Healthcare teams should combine strong identity controls with a workflow designed around fast clinical access. Single sign on, badge based authentication, and session continuity can reduce repeated logins while preserving security. The goal is not to remove control, but to make authentication less disruptive so clinicians spend more time on patient care and less time recovering passwords or relaunching applications.

Q: Why do clinicians create workarounds when access controls are too slow?

A: When authentication interrupts urgent workflows, clinicians often optimise for care delivery by staying logged in, sharing credentials, or avoiding logout steps. That behaviour is a governance signal, not user failure. It shows the access model is misaligned with the pace and context of clinical work.

Q: What are the signs that hospital SSO is working properly?

A: Look for shorter login times, fewer authentication interruptions, less reliance on shared accounts, and preserved auditability after deployment. If access is faster but sessions lose traceability or reauthentication is bypassed, the programme has improved convenience without fully preserving control.

Q: Should healthcare IAM prioritise session control or faster access?

A: Hospitals need both, but session control should not be traded away for speed. Fast access is only defensible when the identity layer still enforces attribution, automatic locking, and reauthentication where required. If those controls disappear, the gain in efficiency comes with a privacy and governance cost.

Technical breakdown

Why hospital SSO changes the authentication bottleneck

In clinical settings, the problem is not just authentication strength but the cumulative cost of repeated sign-ins across workstations and applications. Single sign-on reduces that friction by moving the user from repeated credential entry to a centralised authentication event, while access management handles session continuity and reauthentication rules. That matters in hospitals because clinicians often switch contexts quickly and cannot afford long interruptions. The security trade-off is straightforward: if access is made easier, the control boundary has to shift from repeated login prompts to stronger session governance and device-aware enforcement.

Practical implication: treat SSO as a control redesign, not a convenience layer, and ensure session controls remain explicit.

How access management preserves auditability in shared clinical workflows

Access management in hospitals must support multi-user desktops, kiosk stations, and clinician roaming without breaking accountability. That requires a consistent identity-to-session mapping, automatic locking when a session is idle, and reauthentication when control of the workstation changes hands. Without those controls, hospitals fall back to shared accounts or open sessions, both of which weaken audit trails and privacy assurance. The technical point is that fast access and traceability can coexist only when the access layer enforces who is present, when a session is active, and when a privilege context must be refreshed.

Practical implication: enforce automatic lock and reauthentication on shared clinical endpoints to preserve attribution.

Why smartcard and two-factor integration matters for clinical identity assurance

The article points to two-factor authentication and smartcard integration with the NHS Spine as the mechanism that prevented speed improvements from becoming a security regression. This matters because the healthcare environment still needs strong proof of identity even when access is streamlined. In practical terms, SSO does not replace authentication assurance. It changes where the assurance is concentrated, moving from multiple prompts to a stronger primary login and managed session controls. That model is especially relevant where clinicians access many systems in a short period and need both speed and non-repudiation.

Practical implication: anchor streamlined clinical access in strong primary authentication and keep reauthentication rules visible.

Threat narrative

Attacker objective: The objective is not a classic external breach but the creation of uncontrolled access conditions that undermine accountability, privacy, and safe clinical operations.

1. Entry occurs through repeated clinician logins to multiple systems, which create pressure to reuse sessions or rely on shared access patterns.
2. Credential and session abuse emerge when users avoid logout steps or share logins to keep care moving, reducing identity assurance and audit quality.
3. Impact appears as privacy risk, weaker attribution, and delayed care delivery when authentication friction drives unsafe workarounds.

Breaches seen in the wild

• Taiwan autonomous AI agent cyberattack 2026: Up to eight autonomous AI agents cracked 85 Taiwanese government accounts, pivoted through SSO and exfiltrated 2,564+ personnel records.
• Salesloft OAuth token breach: hackers stole OAuth tokens to access Salesforce data via Salesloft.

Read and download The State of NHI & AI Agent Breach Report 2026, covering 150+ breaches impacting Non-Human Identities including AI Agents.

NHI Mgmt Group analysis

Hospital access is a workflow governance problem, not just an authentication problem: this study shows that clinicians will predictably work around access friction when identity controls slow care. The security programme therefore has to be designed around clinical reality, not only policy intent. In healthcare, the decisive question is whether access governance preserves both speed and attributable use.

Session integrity is the control that lets SSO scale safely in hospitals: faster login only becomes acceptable when automatic locking, reauthentication, and strong primary authentication stay in place. Without those controls, SSO would simply make it easier to stay logged in unsafely. The lesson for IAM teams is that convenience must be paired with explicit session boundaries.

Access management can return time to care because it removes identity friction from the clinical path: the study’s value is not only operational efficiency but reduced incentive for shared credentials and other workarounds. That is an identity governance outcome, not just a productivity metric. Practitioners should treat friction reduction as a security control when it replaces unsafe behaviour.

Clinical login latency: the article surfaces a governance concept that is easy to miss, namely the cost of repeated authentication as an identity risk factor. When logins are slow enough to interrupt care, the control is no longer functioning as intended because users route around it. The practitioner takeaway is to measure access friction as part of security design, not only user experience.

Healthcare IAM succeeds when privacy, auditability, and throughput are designed together: the article aligns with the broader principle that identity controls in regulated environments must be clinically usable to remain secure. This is especially relevant where access patterns are high-frequency and context-switch heavy. The implication is that security architecture should be validated against operational behaviour, not policy assumptions alone.

What this signals

Clinicians will route around slow access controls: when repeated authentication interrupts patient care, workarounds become a predictable operational response. IAM teams should therefore treat login latency as a governance signal, because a control that users systematically bypass is no longer enforcing the intended security boundary.

Hospital SSO programmes should be judged by whether they preserve attributable access on shared endpoints, not only by whether they shorten login time. The real programme risk is not friction reduction itself, but friction reduction implemented without session boundaries that survive workstation sharing and roaming use.

For practitioners

• Map login friction to workaround risk Measure where clinicians abandon logouts, reuse sessions, or rely on shared access because authentication interrupts care. Use those findings to prioritise access controls that remove the trigger for unsafe behaviour.
• Preserve session integrity on shared endpoints Require automatic locking and reauthentication on multi-user desktops, kiosks, and roaming workstations so a session stays attributable when control of the device changes hands.
• Anchor streamlined access in strong primary authentication Keep two-factor authentication or comparable proofing at the point of initial access, then reduce downstream prompts through SSO rather than by weakening assurance.
• Track access governance outcomes in clinical terms Report time saved, access delays removed, and workaround reduction alongside auditability and privacy outcomes so security and care teams evaluate the same control set.

Key takeaways

• Hospitals face a recurring access-security trade-off: if login is too slow, clinicians work around it, but if access is loosened too far, auditability and privacy suffer.
• The study links faster access with measurable operational impact, including shorter login time and millions of clinician hours redirected to patient care.
• The control that matters most is not SSO alone but SSO combined with strong authentication, automatic locking, and reauthentication on shared clinical endpoints.

Key terms

• Single Sign On: Single Sign On is a login method that lets a user access multiple applications with one authenticated session. Technically, an identity provider issues a trusted authentication assertion or token after the user signs in, and connected services accept that proof instead of requiring separate passwords for each application.
• Session Integrity: Session integrity is the assurance that an authenticated connection remains trustworthy after sign-in. It covers token use, channel validation, and device posture, because attackers often target the session after the login event rather than the login event itself.
• Access Management: Access Management is the set of controls that authenticate a user or workload and decide what it can reach at run time. It includes sign-in, session control, policy enforcement, and authorisation decisions, all of which become harder to manage when identities are non-human and highly automated.
• Workaround behaviour: The informal actions users take when approved access processes are too slow, complex, or inconvenient. In identity governance, workaround behaviour is a control signal because it shows that the designed security path is not the path users actually follow.

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 building or maturing an IAM programme, it is worth exploring.