Topic starter
25/06/2026 10:47 pm
TL;DR: Hospital digitalisation still breaks down when identity workflows are introduced without clinical adoption, training, and governance, according to Imprivata’s interview with Michaela Hansen. The bigger issue is not software access alone but whether identity controls fit frontline work without forcing unsafe workarounds.
Editorial analysis by NHI Mgmt Group, based on content published by Imprivata: “#MitarbeiterMittwoch: Fünf Fragen an… Michaela Hansen, Clinical Workflow Specialist”.
Key questions
Q: How should hospitals reduce identity friction for frontline clinicians?
A: Hospitals should design identity journeys around clinical tasks, not around internal IT convenience.
Q: Why do hospital IAM rollouts fail when the technology itself is sound?
A: Because technical correctness does not guarantee clinical usability.
Q: What are the signs that clinical identity workflows are not working in practice?
A: Common signs include repeated help desk tickets, frequent access delays, staff inventing shortcuts, and complaints that digital workflows take longer than the manual ones they replaced.
Practitioner guidance
- Map identity controls to clinical tasks Document how authentication, access approval, and application switching affect nurses, physicians, and support staff during real shifts.
- Build go-live support into the control design Assign floor support, named champions, and rapid issue resolution during rollout so staff can complete work without reverting to informal access paths.
- Validate role profiles before first use Review whether each staff profile contains the access needed for the actual clinical workflow, not just the minimum on paper, so tickets do not become the primary access mechanism.
Bottom line: Hospital identity governance fails when clinical workflows, training, and support are not built into the access model from the start.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
25/06/2026 11:28 pm
Clinical identity governance fails when adoption is treated as optional. Hospitals do not experience IAM as a policy problem alone. They experience it as whether the workflow helps or hinders patient care, and that means training, support, and clinician involvement are part of the control surface. The practical conclusion is that access design has to be measured by frontline usability, not only by technical completeness.
A question worth separating out:
Q: Who needs to own clinical identity governance in a hospital environment?
A: It has to be shared ownership. IT can manage policy and controls, but clinical leadership must sponsor adoption, and frontline champions must reinforce how the workflow works in practice. Without that mix, identity governance stays technically correct but operationally weak.
👉 Read our full editorial: Clinical workflow identity in hospitals is still a governance problem