HIPAA (45 CFR Part 164) 164.512(f)(5) — Disclosures for law enforcement purposes: crime on premises

What this control requires

Permitted disclosure: Crime on premises. A covered entity may disclose to a law enforcement official protected health information that the covered entity believes in good faith constitutes evidence of criminal conduct that occurred on the premises of the covered entity.

In plain English

Permitted disclosure: Crime on premises. 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)(5)) 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.
• 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, law enforcement purposes, disclosure.

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: crime on premises.

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.

• BSI C5:2020 SP-01 — Documentation, communication and provision of policies and instructions
• NIST SP 800-53 Rev. 5 PT-3(2) — Automation
• ISO/IEC 27001:2022 A.5.5 — Contact with authorities
• SOC 2 (2017 TSC) CC2.3 — External Communication on Internal Control Matters
• GDPR Article 62 — Joint operations of supervisory authorities

Related controls in HIPAA (45 CFR Part 164)

• § 164.512(f)(4) — Disclosures for law enforcement purposes- an individual who has died as a result of suspected criminal conduct
• § 164.512(f)(3) — Disclosures for law enforcement purposes- PHI of a possible victim of a crime
• § 164.512(f)(6) — Disclosures for law enforcement purposes
• § 164.512(k)(6) — Uses and disclosures for specialized government functions - Providing public benefits
• § 164.502(j)(2) — Disclosures by workforce members who are victims of a crime
• § 164.510(a)(3) — Uses and Disclosures for Facility Directories in Emergency Circumstances

References

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

Topics: governance riskpolicy management