AI & HIPAA Compliance

AI Tools Are Creating New HIPAA Risk — Most Organizations Haven't Assessed It

AI ambient scribes and generative AI chatbots adopted faster than almost any clinical or business software category on record, and the compliance infrastructure around them didn't keep pace. Being HIPAA compliant does not mean you're covered: California's wiretap and medical confidentiality statutes, and HIPAA's own Business Associate and risk-analysis requirements, create exposure that a standard HIPAA program was never built to catch. Three California health systems are already defending class actions over exactly this gap.

AI Ambient Scribes: Where HIPAA Compliance Alone Isn't Enough

The AMA's 2026 Physician Survey found 81% of physicians now use AI in their practice, up from 38% in 2023, and UCSF has reported roughly 70% of its physicians using AI scribes daily. That adoption curve is exactly what's behind a wave of 2025-2026 California class actions alleging something simpler than a data breach: hospitals let an AI tool record patient visits without asking. Patient Jose Saucedo's November 2025 suit against Sharp HealthCare alleges his visit audio was captured and transmitted to an AI scribe vendor without informed consent — and that his own patient portal falsely documented that he'd "consented." Washington v. Sutter Health, filed in federal court in April 2026, accuses Sutter Health and MemorialCare of the identical pattern with the same vendor.

The legal mechanism doing the damage is California's wiretap statute, not HIPAA. Penal Code Section 632 requires the consent of every party to a confidential communication before it can be recorded, and Section 637.2 gives anyone recorded without consent a private right of action for $5,000 per violation or three times actual damages — whichever is greater — with no need to prove actual harm. The Confidentiality of Medical Information Act stacks directly on top, adding $1,000 per violation in nominal damages plus attorney's fees. HIPAA's Privacy Rule doesn't require special consent to document a visit, so a clean HIPAA posture answers a completely different question than the one California's wiretap law asks.

• An AI scribe vendor is a HIPAA Business Associate — a signed, AI-specific BAA needs to exist before the first transcription, covering voice capture, NLP processing, retention, and a ban on training the vendor's models on your patients' audio.
• The Security Rule's foundational requirement (45 CFR 164.308(a)(1)) is a risk analysis covering every system that touches ePHI — an AI scribe's device-to-cloud-to-EHR data flow usually went live after the last Security Risk Assessment and was never added to it.
• Consent has to be built into the visit itself: encounter-specific verbal consent, a pre-visit written notice, a visible or audible recording indicator, and a written authorization on file — not a signature buried in an intake packet.

Shadow AI: The Governance Gap Nobody's Auditing

Every California organization we work with in 2026 already has a shadow AI problem, whether anyone on staff has named it yet or not. Varonis' 2025 State of Data Security Report found 98% of organizations have unverified or unsanctioned applications running somewhere in their environment, and unsanctioned AI tools are the fastest-growing category inside that number — staff pasting client lists into free AI writing tools, running documents through AI summarizers nobody in IT approved or even knows exist. IBM's 2025 Cost of a Data Breach Report found 63% of organizations have no AI governance policy at all, and where that absence turned into an incident, shadow AI added an average of $670,000 to the cost of a breach and exposed customer PII in 65% of cases versus a 53% baseline.

The healthcare-specific numbers are sharper still. Netskope research found 88% of healthcare organizations have already integrated cloud-based generative AI into daily operations, and 71% of healthcare workers are still using personal AI accounts for work tasks — with 81% of all data policy violations identified across healthcare organizations involving regulated healthcare data specifically. HHS guidance is direct on this point: protected health information entered into a public AI tool without a signed BAA is a HIPAA violation, regardless of whether an employee judged the data to be "de-identified" first.

A real shadow AI audit doesn't start with a policy questionnaire — it starts with an actual inventory: DNS and proxy logs, SaaS expense reports and card statements for subscriptions nobody requisitioned through IT, and browser extension telemetry cross-referenced against known AI platforms. From there we map exactly which tools are receiving PHI, PII, or proprietary data, and through which workflows, and hand you a prioritized remediation plan instead of a vague risk score.