How should healthcare IT teams decide between shared and 1-to-1 mobile devices for clinical workflows?

Why This Matters for Security Teams

Shared and 1-to-1 devices are not just an endpoint procurement choice. In clinical settings, they shape how fast staff can document care, how reliably devices are cleaned and recovered, and how much identity and access friction clinicians tolerate. A poor fit creates workarounds, which often become security gaps. NIST Cybersecurity Framework 2.0 frames this as a governance and operational resilience issue, not only a device management issue.

For healthcare IT, the decision should follow workflow reality: unit-based roles with shift handoffs often benefit from shared devices, while clinicians who need persistent access across locations may justify 1-to-1 assignment. The security question is whether the model preserves least privilege, fast revocation, and usable controls for login, session timeout, and device return. NHIMG research on the Ultimate Guide to NHIs shows that 97% of NHIs carry excessive privileges, a reminder that convenience-driven access models can quietly expand risk when governance is weak.

In practice, many security teams discover that device assignment problems surface only after staff begin sharing credentials, skipping lockouts, or delaying device returns rather than through an intentional workflow design review.

How It Works in Practice

The right model starts with role, mobility, and continuity requirements. Shared devices usually work best where clinicians move as a group, such as med-surg floors, ED, transport, and bedside rounding teams. These devices can be staged with standard apps, fast user switching, barcode scanning, and mandatory cleaning workflows. 1-to-1 devices are better when a clinician needs persistent task queues, secure off-shift messaging, or repeated access to the same patient panel. The goal is to reduce friction without creating unmanaged personal endpoints.

Security controls should differ by model. Shared devices need stronger session controls, automatic logout, roaming profile design, and fast reissue of access for the next user. 1-to-1 devices need stronger ownership controls, remote wipe, break-glass escalation paths, and a clear recovery process for lost or reassigned hardware. Identity matters as much as hardware: device access should be tied to user authentication and context, while backend services should use separate workload identities and secrets handling. For broader identity hygiene, NHIMG’s IOS app secrets leakage report and GitHub Action tj-actions Supply Chain Attack illustrate how quickly secrets spread once convenience outruns control.

• Use shared devices when the clinical workflow is shift-based, predictable, and handoff-heavy.
• Use 1-to-1 devices when continuity, mobility, or off-shift contact is essential.
• Require MDM, strong authentication, session timeouts, and rapid device recovery for both models.
• Measure cleaning, charging, and turnaround time before expanding shared-device pools.

These controls tend to break down in high-turnover environments with limited device inventory because staff fall back to informal sharing and delayed sign-out.

Common Variations and Edge Cases

Tighter device control often increases operational overhead, requiring organisations to balance security assurance against clinician throughput and support capacity. That tradeoff is especially visible in emergency departments, perioperative units, and float pools, where a single workflow may not fit every role. Current guidance suggests there is no universal standard for this yet; the best answer is the one that maps cleanly to staffing patterns, cleaning capacity, and recovery procedures.

Some edge cases justify a hybrid model. For example, a nurse may use a shared workstation on wheels during rounds but receive a 1-to-1 smartphone for secure messaging and authentication. Likewise, physicians may keep a 1-to-1 tablet for persistent chart review while still relying on shared clinical stations for medication administration. In both cases, the organisation should define which data and functions are allowed on which device class, rather than assuming the same policy fits every endpoint. NIST Cybersecurity Framework 2.0 remains useful here because it pushes teams to define governance, protect assets, and recover them consistently.

Healthcare IT teams should also watch for hidden exceptions, such as contractors, rotating residents, and telehealth staff, because those groups often need temporary access that does not fit either pure shared or pure 1-to-1 ownership. The safest design is the one that can revoke access cleanly when a shift ends, a contract closes, or a device is lost.

Related resources from NHI Mgmt Group

• How should regulated teams decide between shared SaaS and tenant-owned identity platforms?
• How should healthcare teams reduce password reset tickets without disrupting clinical workflows?
• How should healthcare organisations secure shared mobile devices without slowing clinicians down?
• What should security and clinical teams do before scaling shared mobile programmes?