HIPAA (45 CFR Part 164) 164.512(f)(6) — Disclosures for law enforcement purposes

What this control requires

Permitted disclosure: Reporting crime in emergencies. (i) A covered health care provider providing emergency health care in response to a medical emergency, other than such emergency on the premises of the covered health care provider, may disclose protected health information to a law enforcement official if such disclosure appears necessary to alert law enforcement to: (A) The commission and nature of a crime; (B) The location of such crime or of the victim(s) of such crime; and (C) The identity, description, and location of the perpetrator of such crime. (ii) If a covered health care provider believes that the medical emergency described in paragraph (f)(6)(i) of this section is the result of abuse, neglect, or domestic violence of the individual in need of emergency health care, paragraph (f)(6)(i) of this section does not apply and any disclosure to a law enforcement official for law enforcement purposes is subject to paragraph (c) of this section.

In plain English

Permitted disclosure: Reporting crime in emergencies. In practice, this means you can prove you information management-level controls on a defined cadence.

Why it matters

HIPAA non-compliance is a strict-liability matter: OCR civil monetary penalties are assessed per-record per-violation (up to USD 1.9 million per identical-violation calendar year as of 2024), and willful neglect can trigger criminal referral.

What an auditor looks for

HHS OCR investigators and SOC-2+HIPAA auditors look for the specific 45 CFR § citation, whether the safeguard is required vs addressable (and if addressable, the documented decision), the implementation specification, the workforce member responsible, and the records that show it runs.

Within Privacy Rule, the assessor will trace your implementation back to the catalogue reference (§ 164.512(f)(6)) and look for objective evidence on the latest two assessment cycles.

How to implement

Policy Management

Docs. Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA.

Operational checklist

• Information. Document the trigger, the owner and the cadence.
• Other. Document the trigger, the owner and the cadence.
• Policy. Document the trigger, the owner and the cadence.
• Law. Document the trigger, the owner and the cadence.
• Disclosures. Document the trigger, the owner and the cadence.
• Scope: management, policy, i, section, neglect, domestic violence, law enforcement purposes, b.

Evidence to collect

• Policy Document. A signed and version-controlled policy / standard / procedure document.

Signed policy or standard documents the safeguard. Focus: Disclosures for law enforcement purposes.

Common pitfalls

• Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

• NIST SP 800-53 Rev. 5 PT-3(2) — Automation
• BSI C5:2020 SP-01 — Documentation, communication and provision of policies and instructions

Related controls in HIPAA (45 CFR Part 164)

• § 164.512(f)(5) — Disclosures for law enforcement purposes: crime on premises
• § 164.512(f)(3) — Disclosures for law enforcement purposes- PHI of a possible victim of a crime
• § 164.512(f)(4) — Disclosures for law enforcement purposes- an individual who has died as a result of suspected criminal conduct
• § 164.512(c) — Disclosures about victims of abuse, neglect or domestic violence
• § 164.510(a)(3) — Uses and Disclosures for Facility Directories in Emergency Circumstances
• § 164.512(a) — Uses and disclosures required by law

References

• U.S. HHS Office for Civil Rights — HIPAA (45 CFR Part 164)
• Catalogue identifier: § 164.512(f)(6)

Topics: governance riskpolicy management