HIPAA compliance means an organization that is subject to the Health Insurance Portability and Accountability Act of 1996 meets the requirements of the HIPAA Administrative Simplification rules at 45 CFR Parts 160, 162 and 164 — principally the Privacy Rule, the Security Rule and the Breach Notification Rule — and can show, through documentation and practice, that it does so.
That definition sounds tidy, but in practice HIPAA compliance is less a finish line than a way of operating. The rules are written to scale to organizations of very different sizes, so they rarely prescribe a specific product or setting. Instead they require you to understand your own risks, choose reasonable safeguards, write down what you decided and why, and revisit those decisions as your environment changes.
Key points
- HIPAA applies to covered entities and their business associates — not to every organization that touches health data.
- There is no government-issued HIPAA certification for organizations, products or consultants.
- The Security Rule is risk-based: a documented risk analysis under §164.308(a)(1)(ii)(A) is the foundation.
- Compliance is ongoing; policies, risk analysis, training and BAAs need regular review.
Who has to comply with HIPAA
HIPAA does not apply to all health information everywhere. It applies to specific types of organizations defined in 45 CFR §160.103.
Covered entities
- Health plans — including group health plans, HMOs, health insurers and government programs such as Medicare and Medicaid.
- Health care clearinghouses — entities that convert nonstandard health information into standard formats, or vice versa.
- Health care providers who transmit health information electronically in connection with a HIPAA standard transaction, such as claims or eligibility checks. A provider who never conducts these transactions electronically may fall outside the definition, although that is increasingly uncommon.
Business associates
A business associate is a person or organization that creates, receives, maintains or transmits protected health information on behalf of a covered entity (or of another business associate) to perform a function or service. Billing companies, cloud hosting providers, EHR and SaaS vendors, IT managed service providers, transcription services and many consultants are typical examples. Since the 2013 Omnibus Rule, business associates are directly liable for complying with the Security Rule and for certain Privacy Rule obligations, and their own subcontractors that handle PHI are business associates too. Our guide to business associate compliance covers this in more depth.
What counts as protected health information
Protected health information (PHI) is individually identifiable health information held or transmitted by a covered entity or business associate, in any form — electronic, paper or oral. It covers information about a person's past, present or future physical or mental health, the care they received, or payment for that care, when the information identifies the person or could reasonably be used to identify them.
Electronic PHI (ePHI) is the subset the Security Rule protects. A spreadsheet of appointment times with patient names is ePHI. So is a support ticket in which a clinic user pastes a patient's lab result. The same data held by a consumer fitness app that has no relationship with a covered entity is usually not PHI under HIPAA, though it may be regulated by the FTC or by state law.
Information that has been properly de-identified under §164.514 — through either the Safe Harbor method or an expert determination — is no longer PHI.
The rules that make up HIPAA compliance
For a section-by-section walkthrough, see HIPAA compliance requirements.
| Rule | Where it lives | What it governs |
|---|---|---|
| Privacy Rule | 45 CFR Part 164, Subpart E (§§164.500–534) | Permitted uses and disclosures of PHI, minimum necessary, patient rights, notice of privacy practices, administrative requirements |
| Security Rule | 45 CFR Part 164, Subpart C (§§164.302–318) | Administrative, physical and technical safeguards for ePHI |
| Breach Notification Rule | 45 CFR Part 164, Subpart D (§§164.400–414) | Assessing incidents and notifying individuals, HHS and sometimes the media |
| Enforcement Rule | 45 CFR Part 160, Subparts C–E | Compliance reviews, investigations, civil money penalties and hearings |
What compliance looks like in practice
Regulators and auditors look for evidence, not intentions. An organization that is operating a credible HIPAA program can usually show the following:
- A designated privacy official and security official (§164.530(a) and §164.308(a)(2)) — in a small practice this may be the same person.
- A current, documented risk analysis covering all ePHI, and a risk management plan that tracks how identified risks are being reduced.
- Written policies and procedures that reflect how the organization actually works, retained for six years from creation or last effective date (§164.316(b)(2) and §164.530(j)).
- Workforce training with attendance records, and a sanctions policy that is applied consistently.
- Signed business associate agreements with every vendor that handles PHI on the organization's behalf.
- Access controls, audit logging and other technical safeguards appropriate to the risks identified.
- An incident response and breach notification process that has been used or at least rehearsed.
- A process for patient rights requests, especially timely right of access under §164.524.
Required versus addressable safeguards
The Security Rule labels some implementation specifications "required" and others "addressable." Addressable does not mean optional. For each addressable specification, the organization must assess whether it is reasonable and appropriate in its environment, then implement it, implement an equivalent alternative, or document why neither is reasonable. Encryption of ePHI at rest and in transit is the best-known addressable specification — and in most modern environments, documenting a decision not to encrypt is very hard to defend.
Common misconceptions
- "We're HIPAA certified." There is no official HIPAA certification. HHS does not certify organizations, products or consultants.
- "Our cloud provider signed a BAA, so we're compliant." A BAA allocates responsibilities; it does not configure your systems or train your staff. Cloud security is a shared responsibility.
- "We did a risk assessment a few years ago." A risk analysis must be kept current and reviewed when systems, vendors or threats change.
- "HIPAA only covers electronic records." The Privacy Rule covers PHI in every form, including paper and conversation.
- "Using a compliant tool makes us compliant." No software can be compliant on your behalf; compliance depends on how you use it.
What happens when compliance falls short
The HHS Office for Civil Rights (OCR) enforces the Privacy, Security and Breach Notification Rules. Most enforcement begins with a complaint or a reported breach. OCR may provide technical assistance, reach a resolution agreement with a corrective action plan, or impose civil money penalties. Penalties are structured in four tiers based on culpability — from violations the entity did not know about and could not reasonably have known about, up to willful neglect that is not corrected — and the dollar amounts are adjusted for inflation every year. Criminal penalties for knowingly obtaining or disclosing PHI are enforced by the Department of Justice.
Recent OCR resolution agreements have repeatedly cited the failure to conduct an accurate and thorough risk analysis. If you are starting from scratch, a HIPAA security risk assessment is usually the right first step.
Where to start
If you are new to HIPAA, start by confirming whether you are a covered entity, a business associate or neither. Then inventory where PHI lives and flows, complete a risk analysis, and build policies around what you find. Our step-by-step guide on how to become HIPAA compliant walks through the full sequence, and the HIPAA compliance checklist gives you a working list to track progress.
Frequently asked questions
Is HIPAA compliance mandatory?
Yes, for covered entities and business associates. Organizations outside those definitions are not subject to HIPAA, though they may be subject to FTC rules or state health privacy laws.
Can a company be HIPAA certified?
No. HHS does not offer or recognize any HIPAA certification. Third parties can assess your program against HIPAA requirements, but no assessment confers official certification or guarantees compliance.
Does HIPAA require encryption?
Encryption is an addressable implementation specification under §164.312. You must assess it and either implement it, implement an equivalent alternative, or document why it is not reasonable and appropriate. Encrypted PHI that meets HHS guidance also benefits from the breach notification safe harbor.
Who enforces HIPAA?
The HHS Office for Civil Rights enforces the civil provisions. State attorneys general may also bring civil actions under HITECH, and the Department of Justice handles criminal cases.
How long do HIPAA records need to be kept?
Required HIPAA documentation — policies, procedures, risk analyses and similar records — must be retained for six years from the date of creation or the date it was last in effect, whichever is later. Medical record retention periods are set by state law, not HIPAA.
Authoritative sources
- HHS — HIPAA for Professionals
- eCFR — 45 CFR Part 164
- HHS — Summary of the HIPAA Security Rule
- HHS — Enforcement and compliance
This page is general information, not legal advice. Regulations and guidance change; confirm current requirements with the official sources above and, where needed, qualified legal counsel.