164.502(f)·medium·Component: Privacy RuleWhat this control requires
Standard: Deceased individuals: A covered entity must comply with the requirements of this subpart with respect to the protected health information of a deceased individual for a period of 50 years following the death of the individual. From 160.103 (Definitions): Protected health information means individually identifiable health information: (1) Except as provided in paragraph (2) of this definition,[...] (2) Protected health information excludes individually identifiable health information: [...] (iv) Regarding a person who has been deceased for more than 50 years.
In plain English
Standard: Deceased individuals: A covered entity must comply with the requirements of this subpart with respect to the protected health information of a deceased individual for a period of 50 years following the death of the individual. In practice, this means you can prove you information requirements-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.502(f)) 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.
- Person. Document the trigger, the owner and the cadence.
- Requirements. Document the trigger, the owner and the cadence.
- Policy. Document the trigger, the owner and the cadence.
- Definitions:. Document the trigger, the owner and the cadence.
- Scope: requirements, management, individuals, policy, death, iv.
Evidence to collect
- Policy Document. A signed and version-controlled policy / standard / procedure document.
Signed policy or standard documents the safeguard. Focus: Deceased individuals.
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 PS-4(1) — Post-Employment Requirements
- ISO/IEC 27001:2022 A.8.26 — Application security requirements
- BSI C5:2020 SP-01 — Documentation, communication and provision of policies and instructions
- SOC 2 (2017 TSC) CC2.3 — External Communication on Internal Control Matters
- NIST SP 800-171 Rev. 3 3.5.11 — Authentication Feedback
Related controls in HIPAA (45 CFR Part 164)
- § 164.530(d)(1) — Complaints to the Covered Entity
- § 164.502(j)(2) — Disclosures by workforce members who are victims of a crime
- § 164.524(e) — Documentation
- § 164.504(g) — Requirements for a covered entity with multiple covered functions
- § 164.522(b)(1) — Confidential Communications Requirements
- § 164.528(d) — Documentation
References
- U.S. HHS Office for Civil Rights — HIPAA (45 CFR Part 164)
- Catalogue identifier:
§ 164.502(f)
Topics: governance riskpolicy management