HIPAA Security Rule
The part of HIPAA that requires administrative, physical and technical safeguards for health information that is created, stored or sent electronically.
In more detail
It applies to covered entities and business associates and requires them to protect the confidentiality, integrity and availability of electronic protected health information. Each implementation specification is either required, or addressable, which means you implement it or document why an equivalent alternative is reasonable, so addressable never means optional. A risk analysis is the foundation from which the other safeguards are chosen. In January 2025 HHS proposed an update that would make almost every specification required.
Related terms
- HIPAA — A United States law from 1996 that, among other things, sets rules for protecting the privacy and security of people's health information.
- PHI — Health information that can be linked to a person, such as a diagnosis, test result or treatment record, held by an organisation that HIPAA regulates.
- covered entity — Under HIPAA, a health plan, a healthcare clearinghouse, or a healthcare provider that carries out standard health transactions electronically.
- security control — A safeguard that reduces a risk, grouped by timing as preventive (stops a change), detective (notices it) or corrective (undoes it).
Taught in
- Regulatory Compliance: SOC 2, HIPAA, GDPR & PCI-DSS — Cybersecurity Fundamentals, GRC & Cryptography