Shared healthcare devices expose identity gaps in clinical IAM

At a glance

What this is: This Imprivata research shows that shared clinical devices often remain signed in, credentials are commonly shared, and basic authentication practices still leave patient data exposed.

Why it matters: It matters because shared-device IAM in clinical settings sits directly between workflow speed and patient-data protection, so weak sign-in practices become an operational and compliance problem.

By the numbers:

• 74% of shared-use devices are often left signed in after use.
• 79% of staff admit to sharing credentials.
• 44% of respondents cite data security as the most frequent challenge for shared-use device adoption.
• 26% of organisations still rely on traditional usernames and passwords to access shared devices.

Context

Shared-use clinical devices create an identity problem, not just a device-management problem. In healthcare, the same handheld or workstation may pass between clinicians many times a day, so access must be closed, re-opened, and re-verified without slowing care delivery.

The gap appears when sign-in state, credential sharing, and session persistence are treated as acceptable shortcuts. That combination weakens the chain between the person at the bedside and the patient data on screen, which is where clinical IAM has to hold.

In this article, the risk is typical rather than exceptional: shared-device adoption is widespread, and the control failures described are the kinds that emerge when convenience outpaces access governance.

Key questions

Q: What breaks when clinicians rely on shared logins or leave medical devices signed in to one user?

A: Shared logins and unattended sessions break accountability, data integrity, and access control. In a clinical setting, another user can act under the wrong identity, audit logs become unreliable, and patient records can be updated under the wrong clinician. That creates both compliance exposure and operational risk, because the organization can no longer trust who accessed the device or what was recorded.

Q: Why do shared credentials create more risk in healthcare than in many other sectors?

A: Shared credentials weaken attribution in environments where timing, responsibility, and patient safety all matter. In healthcare, staff hand off devices across shifts, contractors enter and leave quickly, and the same endpoint may touch sensitive records many times a day. That combination makes reuse and persistence especially dangerous because the identity trail becomes unreliable.

Q: When should healthcare teams prioritise passwordless access over passwords on shared devices?

A: Teams should prioritise passwordless access when clinicians use shared devices repeatedly during a shift and password entry creates lockouts, workarounds, or credential sharing. In that setting, passwords become a usability problem that turns into a security problem. Faster verified access usually reduces the incentive to bypass controls while preserving individual accountability.

Q: How do organisations know shared-device IAM is actually working?

A: Shared-device IAM is working when devices do not stay authenticated across handoffs, clinicians do not need to share credentials, and help desk lockouts decline without increasing unsafe shortcuts. The clearest signal is that access is re-established quickly for each user while audit trails still tie actions to a single identity.

Technical breakdown

Why shared clinical devices create identity persistence risk

Shared clinical devices are identity-bearing endpoints. If a clinician authenticates once and the session remains open, the device effectively becomes a reusable access path for the next person. That is not a hardware issue alone; it is a lifecycle issue for authentication state, session state, and entitlement reuse. In healthcare, where devices move across staff shifts and care settings, the main failure is not remote compromise but local access persistence. The access path survives the user who created it. Practical implication: treat sign-out, session expiry, and re-authentication as part of clinical identity governance, not as optional usability settings.

Practical implication: treat sign-out, session expiry, and re-authentication as part of clinical identity governance, not as optional usability settings.

Why usernames and passwords fail on shared devices

Traditional credentials assume a relatively stable user-device relationship. Shared devices break that assumption because the device is reused, the operator changes frequently, and memorised passwords encourage shortcuts such as credential sharing or reuse. Passwords also do not express who is physically present at the point of care, which is the key trust question in a shared clinical workflow. When access friction is high, clinicians route around controls. That turns the authentication layer into a productivity bottleneck and increases the chance that security exceptions become normal practice. Practical implication: move shared-device access toward stronger, faster authentication that still distinguishes individual users.

Practical implication: move shared-device access toward stronger, faster authentication that still distinguishes individual users.

How single sign-on and passwordless access change the control model

Single sign-on reduces repeated prompts across clinical applications, while passwordless authentication and biometrics can shorten the gap between user intent and verified access. The security value is not convenience by itself. It is that the identity control becomes fast enough for clinical work without encouraging shared credentials or persistent sign-in. In practice, this shifts the control point from remembering secrets to verifying presence and identity at the moment of use. That matters on shared endpoints because a control that people will not follow is not an effective control. Practical implication: design the access flow around rapid re-authentication, not around credential recall.

Practical implication: design the access flow around rapid re-authentication, not around credential recall.

Breaches seen in the wild

• iOS apps leaking hard-coded secrets: Cybernews found 71% of 156,080 iOS apps leak hard-coded secrets, with open cloud storage and Firebase databases exposing user data.

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

Shared clinical device risk is an IAM governance problem disguised as endpoint convenience. The article shows that workflow efficiency can conceal unmanaged access persistence, credential sharing, and weak authentication state. In clinical settings, the core issue is not whether the device is mobile but whether the identity attached to it is still governed when the user moves on. The practitioner takeaway is that device sharing must be treated as a controlled identity lifecycle, not a convenience exception.

Credential sharing on point-of-care devices normalises identity ambiguity. When 79% of staff admit to sharing credentials, the programme has already lost the ability to connect action to accountable identity in a reliable way. That weakens auditability, complicates incident reconstruction, and erodes the trust model for patient-data access. The practitioner takeaway is that shared access has to be designed so that help desk convenience never depends on person-to-person credential transfer.

Authentication friction becomes a security failure when it drives bypass behaviour. If clinicians are locked out, they will find the fastest path back to care delivery, and that often means unsafe workarounds. The problem is not multifactor authentication in the abstract, but controls that do not match the pace and context of bedside work. The practitioner takeaway is to measure whether authentication controls are preserving both user accountability and clinical throughput.

Shared-device programmes need policy, not just tooling. The article links comprehensive shared mobile programmes with materially better ROI, which suggests that governance discipline and operational consistency are doing as much work as the technology itself. In identity terms, a shared-device policy defines when a session ends, how identity is re-established, and who owns the control exception. The practitioner takeaway is to govern shared clinical access as a repeatable programme with clear lifecycle rules.

Healthcare shared access needs a named concept: identity persistence on shared endpoints. This is the condition where a clinician's verified session outlives the person who started it and becomes the next user's access path. It is distinct from generic device exposure because the risk sits in the continued identity state, not the endpoint alone. The practitioner takeaway is to design controls around closing identity persistence, not just locking devices.

From our research library:

• 60% of healthcare organisations do not assess a vendor's security before signing a contract that grants access to protected health information, according to Ponemon Institute's 2023 Third-Party Risk in Healthcare report.

What this signals

Identity persistence on shared endpoints: Clinical devices should be governed as short-lived identity carriers, not as neutral hardware. If the session outlives the user, the access model has failed even when the device remains physically in the ward.

The practical decision point for healthcare IAM teams is whether re-authentication can be made fast enough to survive bedside reality. If it cannot, staff will continue to route around controls, and the programme will measure compliance on paper while losing it in practice.

For practitioners

• Enforce automatic session termination on shared devices Require sign-out or session expiry at handoff points so the next clinician must re-establish identity before any patient data is visible.
• Replace shared passwords with fast verified access Use single sign-on, passwordless methods, or biometrics so clinicians do not need to share credentials to regain access during care delivery.
• Inventory devices that remain signed in after use Track which shared endpoints routinely retain authenticated sessions, then prioritise those locations for tighter logout and re-authentication rules.
• Align help desk workflows with identity governance Make lockout recovery preserve individual accountability, so support processes do not encourage password sharing or permanent session reuse.

Key takeaways

• Shared clinical devices expose a governance gap when sessions, credentials, and user accountability are allowed to drift apart.
• The article shows widespread workflow pressure, including signed-in devices and credential sharing, which makes patient-data exposure a predictable outcome rather than an edge case.
• Healthcare teams should close the identity persistence window on shared endpoints and replace shared logins with fast, individual re-authentication.

Key terms

• Shared Clinical Device: A shared clinical device is a phone, tablet, or similar endpoint used by multiple staff members to support care delivery. In governance terms, it is an access-bearing asset because it can hold sessions, cached credentials, and application pathways that must be managed across shifts and locations.
• Identity Persistence: A situation where an attacker maintains access by abusing identity mechanisms such as tokens, OAuth applications, backdoor accounts, or modified permissions. Unlike endpoint persistence, it often blends into normal administration and survives unless lifecycle and consent controls are actively reviewed.
• Passwordless Authentication: An authentication approach that removes passwords and uses a device-bound cryptographic key plus local user verification. It reduces phishing and replay risk, but it only improves assurance when enrollment, recovery, and revocation are tightly governed.
• Clinical IAM: Clinical IAM is the identity and access management discipline applied to healthcare operations, especially at the point of care. It must balance speed, accountability, and patient-data protection across shared devices, fast staff movement, and high interruption environments.

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.