TL;DR: ePHI now flows through AI assistants, browser extensions, writing tools and agents that were never built for clinical data, with Lumia Security warning that HIPAA risk follows legitimate workflows. Healthcare governance has to inspect shared content, not just approved applications, if compliance is going to hold.
Editorial analysis by NHI Mgmt Group, based on content published by Lumia Security: “The HIPAA Security Rule Wasn't Written for AI. And That's Exactly Why It Matters Now.”.
Key questions
Q: Why do AI assistants create HIPAA risk even when users are authorised?
A: Authorisation to use a tool does not equal authorisation to share ePHI through it.
Q: How can organisations tell whether AI governance is actually working?
A: Organisations can tell AI governance is working when they can inventory every agent, explain its purpose, show who owns it, and prove that permissions are tightly scoped.
Q: What breaks when organisations rely on allow lists for AI tools in healthcare?
A: Allow lists answer which applications are permitted, but they do not control what users paste into those tools.
Practitioner guidance
- Define AI use cases by data sensitivity Map specialised clinical AI, general productivity tools and clinical reference tools to separate governance rules so the same application is not treated as the same risk in every context.
- Inspect AI prompts and outputs for ePHI Monitor the content of interactions, not just the applications in use, so clinical summaries, case notes and intake details are identified before they reach external services.
- Require annual technical verification from AI vendors Tie business associate review to evidence of implemented safeguards, then reconcile that evidence with the actual tools and workflows that are handling ePHI.
Bottom line: The article's central warning is that HIPAA risk now follows ePHI into AI assistants, browser extensions and other productivity tools that were never built for clinical data.
Glossary terms: Semantic ePHI leakage, Content-Aware Control, Business associate verification, AI governance surface area
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
AI governance for healthcare has become an identity and data-governance problem, not just a tooling problem. The article shows that the real control surface is the interaction between a verified user, a specific workflow and the content being shared. That makes AI governance inseparable from identity governance because the same person may move ePHI across sanctioned and unsanctioned services in one session. The control question is whether the organisation can prove what was shared, where and under which authority. Practitioners should treat AI usage classification as part of governance design, not as a policy appendix.
A few things that frame the scale:
- 52% of respondents see AI security decision-making power shifting toward platform and infrastructure teams rather than the executive suite, according to the 2026 Infrastructure Identity Survey.
- Only 44% of organisations have implemented any policies to manage their AI agents, despite 92% agreeing that governing AI agents is critical to enterprise security, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: Should healthcare organisations treat all AI tools as the same compliance risk?
A: No. Specialised clinical AI, general productivity tools and clinical reference tools may all be used by the same workforce, but they should not be governed the same way. Risk depends on the data, the user intent and the workflow. A useful policy distinguishes between tools built for ePHI and tools that should never receive it.
👉 Read our full editorial: HIPAA AI governance now defines ePHI exposure in healthcare