The AI Clinical Notes Privacy Problem
Updated for 2026
Hospitals and clinics use AI to write clinical notes. AI transcribes voice and drafts text. But this creates a HIPAA gap that manual review cannot close.
AI-generated notes expose patient records in three ways:
- Cross-contamination: AI may pull info from one patient into another patient's record. Medical AI studies have shown this risk.
- Context bleed: Patient info lands in the wrong field — a billing note, a research field, or a referral form. AI fills fields by context, not by field purpose.
- Vendor data use: Many AI vendors send notes back for model review unless you opt out. This sends patient info to third-party servers. Those servers may not have a signed BAA.
HHS published a proposed rule in 2025. It says entities using AI tools must include those tools in their risk analysis. This creates a formal rule for AI-assisted clinical work.
The 2025 HHS AI Risk Analysis Rule
HHS proposed new rules for covered entities that use AI. Each AI system that touches patient records must appear in the entity's risk analysis.
The rule has three parts:
Tech safeguards: Review each AI tool. Ask:
- Does it send patient records outside your systems?
- Does it store patient records on its servers after use?
- Does it write patient info into the wrong record?
Staff training: Training must cover AI-specific risks. This includes record mix-up cases.
Physical controls: Workstations running AI tools must be part of physical access controls.
AI clinical tools include voice-to-text services, AI note drafting tools, and coding tools.
Why Pre-Save Detection Works
The best tech control is PHI detection before the note saves to the EHR.
Without pre-save detection:
- AI writes the draft
- Staff reviews it by hand, under time pressure
- Note saves to EHR
- PHI errors are now in the permanent record
- Fixing them requires audit entries and a breach review
With pre-save detection:
- AI writes the draft
- PHI scan runs before the note saves
- Flagged items go to staff for review
- Staff fixes errors before saving
- The EHR record is clean from the start
Pre-save detection meets HIPAA Security Rule 164.312(b). That rule requires systems that record and check activity. The pre-save scan creates an audit record for every note reviewed.
The 18 PHI Categories in AI Notes
HIPAA Safe Harbor requires removing 18 categories of PHI (45 CFR 164.514(b)). AI notes can surface all 18 in ways you may not expect:
- Names — a patient names a family member in symptom history
- Location — home address in social history
- Dates — birth dates, admission dates, procedure dates
- Phone and fax numbers — contact info in referral notes
- Email addresses — patient-provided contact details
- SSNs — insurance context
- Medical record numbers — cross-referenced in AI summaries
- Health plan numbers — insurance context
- Account numbers — billing context
- License numbers — provider license info in referrals
- Vehicle IDs — accident context in trauma notes
- Device IDs — implant notes
- URLs — patient-submitted links to health records
- IP addresses — remote session logs
- Biometric IDs — fingerprint or voice print data
- Photographs — linked media in AI systems
- Any other unique ID — custom facility identifiers
AI models can create any of these from context. Detection must cover all 18 — not just SSNs and dates.
How to Add Pre-Save Detection
A pre-save PHI check follows five steps:
- AI writes the note draft
- Note text goes to a detection API before staff sees it
- Flagged items are shown in the draft view
- Staff reviews the flags during normal note review
- Staff saves the note — without flagged items, or with a logged reason
What the system needs:
- Speed: under 200ms so it does not slow the workflow
- Coverage: all 18 HIPAA categories plus local patterns such as your MRN format
- Scoring: items above 85% are auto-flagged; 50–85% need staff review; below 50% are shown for reference only
- Audit log: log each flagged item, its score, and the reviewer's decision
The audit log gives you direct proof for the HHS risk analysis. It shows you have controls for AI-generated PHI.
Use Case: Pre-Save Detection at a Medical Center
One academic medical center used an AI ambient system for physician notes. A 90-day audit found two mix-up cases. One note had another patient's birth date. A second had a family member's name and SSN from social history.
After adding pre-save PHI detection:
- All AI drafts were scanned before physician review
- Average scan time: 47ms — not felt in the workflow
- Over 90 days: 1,247 items were flagged across 8,400 notes
- Staff reviewed and resolved 94% of flagged items
- Zero record mix-up incidents after the launch
The system produces a monthly report. It shows detection rates, review rates, and entity types. This report serves as audit controls proof under HIPAA Security Rule 164.312(b).
Teams building this workflow can use anonym.legal's PHI detection API. It covers all 18 HIPAA categories at sub-200ms latency. See the PHI detection integration guide for setup steps. For end-to-end context, visit the healthcare use cases page.