Single sign-on in hospitals: security and workflow gains in care

At a glance

What this is: This is a study-backed analysis of single sign-on and access management in hospitals, showing that faster clinician access can improve both security and care delivery.

Why it matters: It matters because human IAM controls in clinical environments have to reduce authentication burden without weakening auditability, session control, or privacy protections.

By the numbers:

• Across 55 hospitals in the UK and Ireland, the study measured login and application access changes before and after SSO/AM deployment.
• Clinicians saw a 60% reduction in desktop login time after the solution deployment.
• Application access became over 50% faster after deployment.

Context

Single sign-on in hospitals is a human IAM control that reduces repeated authentication across clinical systems while preserving auditability and session control. In this article, the core issue is not just faster login, but whether access controls can support clinical work without pushing staff toward risky workarounds.

Healthcare environments are especially sensitive because clinicians often need access to many applications during time-critical workflows. When passwords, reauthentication prompts, and shared logins become part of the care process, identity controls stop being a back-office safeguard and become a direct operational constraint.

The article argues that security and usability cannot be separated in care settings. That is typical of modern hospital environments, where access design has a measurable impact on both workforce efficiency and the privacy risk created by informal authentication shortcuts.

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 repeated logins and session interruptions create security and operational risk in clinical environments?

A: Repeated authentication breaks clinician focus, slows care delivery, and increases the chance that users work around controls. In shared environments, those workarounds can produce abandoned sessions, credential exposure, or improper handoff between users. The risk is not just inconvenience. It is weakened control over access at the point of care, where speed and security must both hold.

Q: What are the signs that hospital access controls are too burdensome?

A: Common signs include frequent password prompts, delayed access to applications, shared logins, and staff staying signed in to avoid interruptions. Those behaviours suggest the control design is not aligned with the pace and context of clinical work.

Q: How do clinicians benefit when access controls are redesigned around workflow?

A: Clinicians spend less time authenticating and more time on patient care, while security teams gain a more auditable access model. The practical benefit is not just speed, but fewer workarounds and better session discipline across shared devices.

Technical breakdown

Why repeated hospital logins create control drift

Hospitals often use multiple clinical applications, each with its own authentication path, which creates repeated prompts and time pressure. That pressure leads to behaviour such as shared logins, delayed logouts, and other workarounds that weaken audit trails and session integrity. SSO reduces the number of times a clinician has to prove identity, but the governance value comes from pairing it with access management, reauthentication, and automatic locking. In practice, the technical problem is not simply password count. It is the accumulation of authentication friction across many systems, where each extra step increases the chance that policy will be bypassed in order to keep care moving.

Practical implication: reduce repeated login points, but only where session control and auditability remain intact.

How SSO and access management change clinical authentication

Single sign-on centralises the initial authentication event so clinicians can move between systems without re-entering credentials at every application. Access management then governs whether that session stays valid, when it must be reauthenticated, and how device context or smartcard integration is enforced. In the article, this combination is what allowed faster access without losing security controls. The important technical detail is that SSO alone does not create trust. It changes where trust is checked, moving control from each application to the session and identity layer that governs access across them.

Practical implication: design SSO as a governed access layer, not as a convenience layer only.

Why automatic locking and reauthentication matter for care workflows

Automatic locking and reauthentication preserve session integrity when clinicians move between workstations, wards, and shared endpoints. In hospitals, that matters because workstation and kiosk models often serve multiple users in rapid succession. Without those controls, productivity gains can translate into uncontrolled session persistence or casual credential sharing. The article shows that friction reduction can coexist with stronger security if access is time-bound to the clinical context and reassessed at the right moments. This is a human IAM pattern, not an NHI pattern, but it still depends on lifecycle discipline around the session.

Practical implication: enforce session timeout, reauthentication, and locking on shared clinical endpoints.

Threat narrative

Attacker objective: The practical objective is not a classic external intrusion, but operationally it becomes easier for unauthorized or misattributed access to occur when authentication friction normalises workarounds.

1. Entry occurs when clinicians face too many passwords, repeated prompts, or slow access to critical systems, which drives them toward shared logins and other workarounds.
2. Escalation happens when those workarounds weaken identity assurance and reduce the reliability of audit trails, making it harder to attribute access to a specific user and context.
3. Impact is delayed care, weaker privacy protection, and a more fragile security posture across high-volume clinical workflows.

Breaches seen in the wild

• 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

Clinical authentication friction is an identity control issue, not just a user-experience problem. In hospitals, repeated logins and multiple passwords do more than slow clinicians down. They create the conditions for shared credentials, skipped logout steps, and weaker auditability, which means the control itself starts to erode under operational pressure. The governance conclusion is straightforward: if access design does not fit care delivery, policy compliance will decay in practice.

Workaround-driven access is a privacy and accountability risk, even when the system is technically compliant. The article shows that clinicians will adapt when login burden becomes excessive, and those adaptations can undermine the very controls mandated by data protection and audit requirements. This is a classic human IAM failure mode, where the nominal security design is correct but the operating environment makes it unsustainable. Practitioners should treat workflow friction as a measurable risk signal, not a soft usability concern.

SSO/AM shifts the control conversation from authentication frequency to session governance. Once login steps are reduced, the more important questions become when a session expires, how reauthentication is triggered, and whether access remains attributable across shared endpoints. That is why the article’s strongest finding is not speed alone. It is that security can improve when identity controls are designed around the realities of clinical work rather than abstract access policy.

Identity controls in healthcare must be judged on both safety and throughput. In a clinical setting, delayed access is not a neutral inconvenience. It can affect patient flow, clinician stress, and the temptation to bypass policy. The field should stop treating security and productivity as opposing outcomes and instead assess whether access governance supports both without creating new informal behaviours.

Named concept: workflow friction risk. This is the point at which authentication burden becomes a governance problem because users begin compensating for policy with unsafe behaviour. In this article, that risk appears through slow logins, repeated interruptions, and the use of workarounds to preserve clinical pace. Practitioners should measure identity controls by the behaviours they induce, not only by the policies they satisfy.

What this signals

Workflow friction is now a human IAM governance signal. When access controls regularly interrupt care, the programme is not just dealing with user dissatisfaction. It is facing a control-adherence problem, because the environment starts rewarding behaviours that weaken auditability and privacy.

Clinical identity programmes should move their centre of gravity from password policy to session governance. If clinicians can authenticate once and retain accountable, time-bound access across the workflow, the organisation gets both better security posture and less operational drag.

The broader lesson is that secure access in healthcare is only durable when it matches clinical pace. Controls that ignore that reality often create the very exceptions they were meant to prevent.

For practitioners

• Map authentication friction across clinical workflows Measure where repeated logins, password prompts, and workstation switching most often interrupt care, then prioritise those paths for redesign.
• Pair SSO with session governance Require automatic locking, reauthentication, and auditable session continuity on shared clinical endpoints so faster access does not weaken accountability.
• Eliminate shared-login workarounds Find teams still relying on shared credentials or staying logged in to avoid delay, then remove the workflow pressure that makes those behaviours attractive.
• Use access design as a productivity control Treat login time, application access speed, and clinician frustration as operational metrics alongside security controls when evaluating IAM changes.

Key takeaways

• Hospital access controls can become a security problem when they create enough friction that clinicians adopt risky workarounds.
• The study links faster access to better workflow, but the deeper governance point is that session integrity has to survive the move to frictionless login.
• Healthcare IAM should be measured on both auditability and clinical throughput, because controls that slow care often lose adherence.

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 Governance: The practice of binding access to a specific task, time window, and execution context, then revoking it when the work is done. For non-human identities, session governance matters because tokens and delegated permissions often persist longer than the action they were created to support.
• Access Workaround: An access workaround is any unofficial method people use to get around an identity control that slows them down or blocks progress. Workarounds are a governance signal, because they show that policy design and operational reality are no longer aligned.
• Clinician Workflow: Clinician workflow is the sequence of tasks, movements, and access needs that support patient care at the bedside and across care settings. Security controls that ignore this workflow tend to create friction, workarounds, and shadow processes, so access design must reflect how care is actually delivered.

Deepen your knowledge

NHI governance, identity lifecycle management, and workload identity security 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.