Healthcare

AI in healthcare without putting PHI in someone else's logs

Drafting patient communications with AI? Emil detects and blocks PHI — names tied to conditions, medical record numbers, the 18 Safe Harbor identifiers — and fails closed if a classifier is unavailable.

The problem

  • Admin staff paste patient details into ChatGPT to draft messages — a HIPAA disclosure to a non-BAA vendor.
  • PHI in an AI provider's training or logs is a reportable breach with per-record penalties.
  • Most AI tools have no BAA and no way to keep PHI out.

What Emil catches for healthcare

  • Patient names linked to conditions or treatment
  • Medical record and account numbers
  • The 18 HIPAA Safe Harbor identifiers
  • Dates, contact details, and other PHI

Regulations this maps to

  • HIPAA Privacy & Security Rules
  • HITECH breach notification
  • State health-privacy laws

A content filter reduces regulatory risk but isn't compliance on its own. Review presets with counsel.

Questions

Can staff use ChatGPT with patient information?
Only behind a control. Emil detects PHI — names tied to conditions, MRNs, the 18 Safe Harbor identifiers — and blocks or redacts it before the prompt reaches the AI, so PHI never reaches a vendor without a BAA.
What happens if a classifier is down?
Emil fails closed for PHI: if a safety classifier is unavailable, the request is blocked rather than allowed through. Sensitive data is never let out on a best-effort basis.
Does Emil retain PHI?
No — it processes text in memory and stores only finding metadata (type + severity), never the PHI itself.
Is Emil itself HIPAA compliant?
Emil is built to keep PHI from reaching ungoverned AI tools and maps to HIPAA's safeguards. Compliance is a program, not a product — Emil is a strong technical control within it; pair it with your policies, training, and BAAs.

Other industries