HIPAA
The U.S. law that governs the privacy and security of protected health information.
Executive Summary
HIPAA, the Health Insurance Portability and Accountability Act, is a U.S. federal law that sets national standards for protecting sensitive health information. Its rules are enforced by the U.S. Department of Health and Human Services (HHS). The Privacy Rule governs how protected health information can be used and disclosed, and the Security Rule sets requirements for safeguarding health information held or transmitted in electronic form.
What It Is
HIPAA is a set of U.S. regulations that protect the confidentiality and security of health information. It applies to covered entities, which generally include health plans, health care clearinghouses, and most health care providers that transmit health information electronically, as well as to their business associates, which are vendors that handle protected health information on their behalf. Protected health information, often abbreviated PHI, is individually identifiable health information, and when it is in electronic form it is referred to as ePHI. The two rules most relevant to security and compliance professionals are the Privacy Rule, which sets limits on how PHI may be used and shared, and the Security Rule, which requires administrative, physical, and technical safeguards for ePHI. The Breach Notification Rule requires notifying affected individuals and regulators after certain breaches.
Why It Matters
Health data is highly sensitive and highly targeted, and mishandling it carries legal, financial, and reputational consequences. HIPAA violations can lead to significant penalties and mandatory public reporting of large breaches, and business associate obligations mean the law reaches far beyond hospitals into technology vendors, billing companies, and cloud providers. For organizations that touch health data, HIPAA compliance is a condition of doing business. For professionals, HIPAA expertise is in demand across health care, health technology, and any vendor in the health supply chain, and it pairs naturally with broader security and privacy skills.
How It Works
Compliance starts with determining whether an organization is a covered entity or a business associate and mapping where PHI and ePHI live and flow. The Security Rule is risk-based: organizations must perform a risk analysis, then apply administrative safeguards (such as workforce training and access management), physical safeguards (such as facility and device controls), and technical safeguards (such as access controls, audit logging, and protections for data in transit and at rest). The Privacy Rule constrains how PHI may be used and disclosed and grants individuals rights over their information. Business associate agreements bind vendors to protect the PHI they handle. When a reportable breach occurs, the Breach Notification Rule sets out who must be told and when. Because the environment changes, the risk analysis and safeguards must be reviewed and updated over time.
Architecture Diagram
Visual Workflow
Common Attacks
- Failing to perform or document a thorough risk analysis of ePHI
- Overlooking business associates so vendor handling of PHI is unmanaged
- Granting workforce access to PHI far beyond what each role requires
- Leaving ePHI unprotected on lost or stolen laptops and mobile devices
- Not having a breach response ready, delaying required notifications
Common Mistakes
- Assuming HIPAA applies only to hospitals and not to vendors that handle PHI
- Treating the risk analysis as a one-time document instead of a living process
- Confusing the Privacy Rule with the Security Rule and addressing only one
- Skipping business associate agreements or using ones that are never enforced
- Neglecting audit logging, which is needed to detect and investigate misuse
Best Practices
- Conduct and regularly update a documented risk analysis of ePHI
- Apply least-privilege access and log access to PHI
- Encrypt ePHI on devices and in transit where reasonable and appropriate
- Sign and maintain business associate agreements with every relevant vendor
- Train the workforce on privacy and security and make breach reporting easy
- Keep an incident and breach notification plan ready and tested
Quick Checklist
- Organization's role as covered entity or business associate is determined
- PHI and ePHI data flows are mapped
- A current, documented risk analysis exists
- Administrative, physical, and technical safeguards are in place
- Business associate agreements cover every vendor that handles PHI
- Breach notification plan is documented and workforce training is current
Recommended Tools
Tracks HIPAA safeguards, risk analysis, and evidence
Enforces least privilege and records who touched PHI
Protects ePHI on devices and in transit
Tracks business associates and their agreements
Industry Standards
Requires administrative, physical, and technical safeguards for ePHI
Governs permitted uses and disclosures of PHI and individual rights
Widely referenced help for implementing the Security Rule
Career Relevance
HIPAA is a core competency for GRC analysts, compliance analysts, security auditors, and CISOs in health care and health technology, who run risk analyses, implement safeguards, manage business associate agreements, and prepare for audits. Privacy officers and vendor risk teams also rely on it. For the privacy and AI governance professionals AI-Governance-Jobs.com serves, HIPAA is a leading example of how sensitive data is regulated and a template for governing health-related AI systems responsibly.
Interview Questions
- Who must comply with HIPAA, and what is the difference between a covered entity and a business associate?
- Explain the difference between the Privacy Rule and the Security Rule.
- What are the three categories of safeguards in the Security Rule?
- Why is the risk analysis so central to HIPAA compliance?
- What triggers obligations under the Breach Notification Rule?
Related Certifications
Further Reading
Key Takeaways
- HIPAA is the U.S. law protecting the privacy and security of health information, enforced by HHS.
- It applies to covered entities and to business associates that handle PHI on their behalf.
- The Privacy Rule governs use and disclosure of PHI; the Security Rule protects ePHI.
- The Security Rule is risk-based and requires administrative, physical, and technical safeguards.
- HIPAA expertise is in demand across health care and the broader health technology supply chain.
FAQ
Does HIPAA apply to technology vendors?
Often yes. A vendor that creates, receives, maintains, or transmits protected health information on behalf of a covered entity is generally a business associate and must comply with applicable HIPAA requirements, usually under a business associate agreement.
What is the difference between PHI and ePHI?
PHI is protected health information, meaning individually identifiable health information in any form. ePHI is that same information in electronic form. The Security Rule specifically addresses safeguarding ePHI.
Is there a HIPAA certification for organizations?
HIPAA is a legal requirement rather than a formal government certification like some standards. Organizations demonstrate compliance through their risk analysis, safeguards, agreements, and documentation, and various third parties offer assessments, but there is no single official HIPAA certificate that guarantees compliance.
Related Careers
Related certifications
ISC2 HCISPPISACA CISACertified in Healthcare Privacy and Security (CHPS)Current openings
Suggested learning path
- Ground the basics with CS-001 Cybersecurity
- Study this sheet: HIPAA
- Go deeper: GDPR
- Go deeper: PCI DSS
- Validate it: work toward ISC2 HCISPP
- Find the role: browse current openings