The short answer
Don't put protected health information (PHI) into an AI tool unless your organization has approved that tool for PHI and a business associate agreement (BAA) is in place. A personal or free AI account is unlikely to meet that bar.
This guide is general information, not legal advice.
What HHS has said about vendors
HHS guidance on cloud computing sets out a useful test. A cloud provider that stores or processes electronic PHI for a covered entity is a business associate, and the parties must sign a BAA. HHS says this holds even if the provider can't view the data because it's encrypted and it has no key. Using such a provider without a BAA violates the HIPAA Rules.
That guidance is about cloud providers, not AI specifically. We didn't find HHS guidance that addresses AI vendors directly. The cautious reading is that the same test applies: if a vendor handles PHI for you, treat it as a business associate.
Where it goes wrong
- Pasted notes. Someone asks an AI tool to summarize a visit or draft a letter.
- Attachments. A referral or lab result is uploaded for a quick explanation.
- Screenshots. PHI can appear in an image as easily as in text.
- Connected apps. An AI note taker joins a call or reads a mailbox.
- Personal accounts. Your BAA doesn't cover an account your organization doesn't control.
What to do
- Inventory the AI in use, including apps connected to Microsoft 365.
- Approve specific tools for specific uses, and check each BAA.
- Write it down. Say what staff can and can't do, in plain language, and collect sign-off.
- Put a control at the point of risk. Block identifiers before they're sent, and warn on the rest.
- Keep evidence of your policy, decisions and what was stopped.
Where AILeakShield fits
The HIPAA framework pack sets your data rules in a few clicks, and the evidence pack supports your audit. We sign BAAs. No single tool makes an organization compliant, so this supports your compliance program rather than replacing it. Start with a free report.