Who should own shared mobile governance in a hospital?

Why This Matters for Security Teams

Shared mobile governance in a hospital is not just a policy question. It decides who can approve device access, who can revoke it when a clinician changes roles, and who is accountable when a shared tablet, phone, or workstation becomes a pathway to patient data exposure. The control failure is usually organisational, not technical: ownership that sits in only one function tends to ignore either operational reality or security enforcement.

That is why hospitals need a cross-functional model that aligns identity, security, and care delivery. NIST’s Cybersecurity Framework 2.0 is clear that governance and risk ownership must be defined, not assumed, and NHIMG’s Top 10 NHI Issues shows how quickly shared access models drift when lifecycle accountability is unclear. For hospitals, the same pattern appears with mobile estates: shared devices are often secured in principle but unmanaged in practice. In practice, many security teams encounter weak shared-device governance only after a ward workflow has already bypassed policy to keep care moving.

How It Works in Practice

The best operating model is joint ownership with clear decision rights. IAM should own identity proofing, authentication policy, role mapping, and access revocation. Security should own hardening, monitoring, logging, incident response, and control testing. Clinical operations should own workflow design, device placement, shift handoff expectations, and escalation paths when a device is unavailable.

This works because shared mobile governance is really a custody-and-context problem. A device on a ward is not just an endpoint; it is a shared access point embedded in clinical workflow. If the device is locked down without input from operations, clinicians find workarounds. If operations control it without security oversight, entitlement sprawl and weak auditability follow. NHIMG’s Lifecycle Processes for Managing NHIs is useful here because the same governance logic applies: establish ownership across onboarding, use, rotation, and deprovisioning rather than treating access as a one-time event. For control design and review structure, NIST CSF 2.0 helps translate that joint ownership into governance, protection, and detection responsibilities.

A practical model usually includes:

• one policy owner for approved use cases and minimum controls
• one operational owner for ward-level device availability and custody
• one technical owner for identity, MDM, logging, and alerting
• one review cadence for exceptions, stale accounts, and lost-device events

This approach is strongest when shared mobile device are tied to a small number of standard workflows and centrally managed enrollment, because the governance burden stays predictable and auditable.

Common Variations and Edge Cases

Tighter ownership usually improves control consistency, but it also increases coordination overhead, so hospitals have to balance speed of care against approval discipline. That tradeoff becomes sharper in emergency departments, temporary surge wards, and contractor-heavy environments, where device turnover and access changes happen quickly.

There is no universal standard for this yet, but current guidance suggests the ownership model should change with the operating context. A highly standardised ward can support central IAM-led governance with clinical sign-off on exceptions. A fast-moving environment may need delegated operational control with security guardrails and daily review. The key is to avoid ambiguous ownership, because ambiguity is what causes stale badges, orphaned devices, and access exceptions to persist.

Hospitals should also distinguish between device custody and identity ownership. Clinical operations may control who physically uses a shared mobile device during a shift, but IAM still needs authority over access issuance and revocation. NHIMG’s Regulatory and Audit Perspectives is a good reminder that auditability matters as much as usability, especially where patient data and regulated workflows intersect. Where mobile programmes span multiple facilities or outsourced support teams, shared governance tends to break down when no single group can enforce revocation at the same pace as clinical change.

Related resources from NHI Mgmt Group

• Why do shared mobile devices create governance problems for IAM teams?
• How do shared devices change mobile access governance?
• What frameworks help with shared mobile access governance in healthcare?
• Who should own identity governance when Industry 4.0 links plant systems to enterprise applications?