Topic starter
06/11/2026 6:40 pm
TL;DR: Healthcare identity programmes can look complete while hundreds of legacy clinical applications remain outside governance, leaving revocation delayed for days or weeks and exposing patient data during offboarding gaps, according to READI. The issue is not dashboard visibility alone; it is whether every application can be provisioned and deprovisioned reliably across the full estate.
Editorial analysis by NHI Mgmt Group, based on content published by READI: “Identity governance in healthcare: the clinical application blind spot.”.
Key questions
Q: How should healthcare teams handle offboarding for disconnected applications?
A: Healthcare teams should map every account, service account, API key and certificate tied to the application, then remove or disable them through a controlled offboarding checklist.
Q: Why do legacy systems make healthcare identity governance harder?
A: Legacy systems extend the life of weak authentication, limited patching, and poor segmentation.
Q: How do you detect disconnected applications in an identity programme?
A: Disconnected applications are systems that still hold accounts, roles, secrets or integrations outside your identity controls.
Practitioner guidance
- Map disconnected clinical systems first Create a current inventory of applications that still rely on local admins, manual tickets, or department-level access handling, then classify them by patient-data sensitivity and offboarding risk.
- Make revocation the test of control Require every leaver workflow to confirm that access was removed in the target application, not only that the identity platform closed the case.
- Prioritise legacy systems with patient data Move the clinical applications with the highest sensitivity and the weakest integration path to the front of the remediation queue, because those systems create the longest exposure windows.
Bottom line: Healthcare identity governance can look complete while critical clinical applications still sit outside enforceable control.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/11/2026 6:42 pm
Clinical application blind spots are an identity governance failure, not a connector problem. A programme can schedule reviews and close certifications while still leaving legacy systems outside control because the coverage model stops at the integration boundary. The result is a two-tier identity estate in which the easiest applications are governed and the most sensitive ones remain informal. Practitioner conclusion: measure governance by revocation reach, not by dashboard completeness.
A few things that frame the scale:
- 64% of valid secrets leaked in 2022 are still valid and exploitable today, proving that detection alone is not enough without automated revocation, according to the State of Secrets Sprawl 2026.
- 91.6% of secrets remain valid five days after the targeted organisation is notified, showing a critical gap in remediation procedures, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: What is the best way to reduce access risk after a healthcare acquisition?
A: The best way is to run an acquisition-driven identity clean-up that maps every inherited account, service account, API key and privileged role before cutover. Use automated lifecycle actions to disable duplicate identities, merge authoritative sources, rebind accounts to named owners and force credential rotation. Then perform targeted access reviews for clinicians, contractors and third-party admins.
👉 Read our full editorial: Healthcare identity governance falters where clinical apps sit outside IGA