Start Free Trial
Home/Regulations/HIPAA Privacy Rule — Regulatory Reference
Regulatory Reference
Healthcare Federal (US) critical

HIPAA Privacy Rule — Regulatory Reference

PHI use and disclosure — minimum necessary principle enforced at retrieval; AI agents gated by need-to-know policy before PHI enters the agent's context window.

Key Provisions

45 CFR Part 164 Subpart E — Privacy of Individually Identifiable Health Information

Subpart E is the core of the HIPAA Privacy Rule. It governs all uses and disclosures of protected health information (PHI) by covered entities and their business associates, establishes the minimum necessary standard, defines individual rights over their health information, and sets requirements for notice of privacy practices.

AI agents operating in healthcare environments are typically classified as business associates when they process PHI on behalf of a covered entity. Every retrieval of PHI by an AI agent is a "use" under Subpart E and must have a permissible purpose. Without a governance layer that records what PHI each agent accessed and why, covered entities cannot demonstrate that uses were limited to permissible purposes. AutoPIL acts as the technical enforcement layer for Subpart E — every agent access is evaluated against a declared policy before PHI is retrieved, and each decision is logged in the audit chain.

§164.502(b) — Minimum Necessary Standard

Covered entities must make reasonable efforts to limit the use or disclosure of PHI to the minimum necessary to accomplish the intended purpose. The minimum necessary standard applies to all routine disclosures and any request for PHI.

AI agents are a particular compliance risk here because they typically request access at a broad connection level — a query against an EHR database can return far more fields than the agent actually needs. Application-level controls can filter output but do not govern the retrieval itself. AutoPIL enforces minimum necessary at the source level: each data source is classified by sensitivity, and agent policies specify which sources and sensitivity tiers a given agent may access. A clinical operations agent configured for scheduling cannot retrieve diagnostic records or prescription histories — the retrieval is blocked before it occurs.

§164.514 — De-identification Standards

PHI that has been properly de-identified is not subject to the Privacy Rule. Section 164.514 defines two acceptable methods: Safe Harbor (removal of 18 specified identifiers) and Expert Determination (statistical analysis confirming very low re-identification risk).

The AI governance risk is that agents trained or evaluated on de-identified data are then deployed against production systems containing identified PHI, without any policy boundary separating the two. AutoPIL's sensitivity classification in the source registry distinguishes identified PHI sources from de-identified research datasets. Agents authorised against de-identified sources can be explicitly restricted from accessing identified counterparts, maintaining the de-identification boundary at runtime.

§164.524 — Individual Right of Access to PHI

Covered entities must provide individuals with access to their PHI in a designated record set within 30 days of a request. They must also provide an accounting of disclosures — a record of to whom PHI was disclosed, when, and for what purpose.

When an AI agent accesses PHI and that access is later challenged by a patient under §164.524, covered entities need a complete accounting of what was accessed, when, and by which system. AutoPIL's audit chain is queryable by data source and time range, enabling the compliance team to produce an accurate accounting of AI agent disclosures without manual reconstruction from fragmented application logs.


How AutoPIL Enforces It
  • Pre-retrieval enforcement makes the minimum necessary principle technical — agents cannot retrieve PHI categories beyond their declared policy
  • Sensitivity ceilings in the source registry separate clinical data from administrative data at the governance layer
  • Audit chain supports §164.524 accounting of disclosures — queryable by patient data source, agent, and time window
  • De-identification boundaries enforced at source registration, not relying on application-level filtering
Policy EngineAudit LogSensitivity LabelsAgent RegistryKey ScopingCatalog
AutoPIL Policy IDs
HC-HIPAA-MN-001Minimum Necessary Enforcement at Retrieval
HC-HIPAA-DEID-001De-identification Boundary for AI Agents
Official Sources

This page is a working reference and not a substitute for qualified legal review. Verify against official sources before use in compliance artifacts.

AutoPIL Governance Platform

Enforce this regulation today

AutoPIL intercepts every AI agent data access call, enforces your policy, and writes a tamper-evident audit record — before sensitive data enters the agent context window.

Start Free Trial View All Industries