Healthcare

AI security for healthcare: keep PHI out of AI tools

Clinicians and staff want AI for notes, letters and summaries. AILeakShield shows you which AI tools are in use and stops protected health information before it reaches the ones that shouldn't have it.

We sign Business Associate Agreements.

Sample data shown. Select the image to enlarge it.

Where PHI slips into AI

Nobody means to break the rules. It usually happens when someone is trying to save time.

Summarizing a visit

A clinical note is pasted into a chat tool to draft a letter or summary.

Explaining a result

A lab report or referral is uploaded for a quick explanation.

Screenshots

PHI in an image is as sensitive as PHI in text.

AI note takers

A meeting assistant connected to Microsoft 365 joins calls and reads calendars.

Personal accounts

A BAA covers the vendor and account you contracted with, not someone's personal login.

Billing and revenue cycle

Patient and payment details are pasted in to draft an appeal or explain a denial.

What HIPAA means for AI vendors

HHS guidance on HIPAA and cloud computing says a cloud provider that creates, receives, maintains or transmits ePHI for you is a business associate, and a BAA is required, even if it only holds encrypted data and has no key. That guidance predates today's AI tools. The cautious reading is that the same test applies: if a vendor handles PHI for you, treat it as a business associate. Our HIPAA and AI guide goes further.

How AILeakShield helps

One pack sets the rules. The rest shows you, and an auditor, that they're working.

The HIPAA pack

Blocks PHI, personal identifiers and credentials, and warns on financial and network details. You see every change before it's applied.

Find the AI in use

See AI sites, extensions, desktop apps and Microsoft 365 apps in one list, with each vendor's risk.

Restrict what isn't approved

Show staff a clear notice on restricted tools, and let them request access.

Files and images

Inspect attachments, and read the text in screenshots and scanned PDFs.

Coaching at the moment

Warnings explain the risk, and written reasons are recorded.

Audit trail without the content

Blocked and overridden sends are recorded by category, without the PHI itself.

How healthcare teams roll it out

Nothing changes for staff until you decide.

  1. See what's connected

    Start with the free Microsoft 365 report, with nothing to install.

  2. Watch for two weeks

    Deploy to managed browsers in monitor mode. Nothing is blocked.

  3. Decide and enforce

    Approve the tools you trust, restrict the rest, and turn on your data rules.

  4. Keep the evidence

    Decisions, overrides and sign-offs are recorded for your next review.

Frequently asked questions

Does this make us HIPAA compliant?

No. No single tool does. Administrative safeguards, workforce training, physical safeguards and contingency planning are outside this product. AILeakShield enforces one control and records the evidence.

Do you sign a BAA?

Yes, we sign Business Associate Agreements.

What does it not see?

Coverage is managed browsers and the secure workspace. PHI moving inside your EHR, e-fax or clinical systems is beyond what this product can see.

How accurate is it on clinical text?

Detection is strong on identifiers and clinical document patterns. Free-text clinical narrative with no identifiers can warn rather than block, so it works alongside training and policy.

Is PHI stored in AILeakShield?

Blocked content is never stored. Other prompt text is cleared at the end of each day (UTC), and the audit trail keeps the category and action taken.

See what AI can reach today

Start with a free report of the AI connected to your Microsoft 365. It doesn't read any email, files or chats.