HIPAA compliance is not one requirement; it is a set of overlapping obligations spread across the Privacy Rule, the Security Rule and the Breach Notification Rule, plus the contracts that extend those obligations to vendors. This checklist pulls them into one place so a privacy officer, security officer or founder can see the whole picture on a single page.
Every item is labeled. “Required” means the cited regulation mandates it. “Addressable” applies only to Security Rule implementation specifications and means you must assess and document your decision — not that you may skip it. “Recommended practice” marks controls that are widely expected and help you meet the rule, but are not explicit mandates under the current regulation.
Use it as a self-check, not as proof of compliance. A checklist cannot tell you whether a control is designed well or working; that takes a documented HIPAA gap analysis or risk analysis.
Key points
- Applies to covered entities; business associates carry the Security Rule and contract-based Privacy Rule duties.
- “Addressable” is never “optional” — document the decision either way.
- Risk analysis is the foundation; most other Security Rule decisions depend on it.
- Policies, decisions and evidence must be retained for six years under §164.316 and §164.530(j).
How to read the labels in this checklist
The Security Rule divides its standards into implementation specifications that are either required or addressable (45 CFR §164.306(d)). The Privacy and Breach Notification Rules do not use that vocabulary — their provisions are simply mandatory for whoever they apply to. To keep things simple, we use three labels throughout.
| Label | What it means | What you must keep on file |
|---|---|---|
| Required | Mandated by the cited CFR section for the entities it applies to | Policy, procedure and evidence that it operates |
| Addressable | Security Rule specification you must assess for reasonableness and appropriateness; implement it, implement an equivalent alternative, or document why neither is reasonable | Written rationale tied to your risk analysis, plus evidence of what you did implement |
| Recommended practice | Widely accepted control that supports HIPAA goals but is not an explicit mandate under the current rule | Optional, but useful to show how risks were reduced |
Privacy Rule checklist
These items apply in full to covered entities. Business associates are bound to the Privacy Rule through their BAA and are directly liable for impermissible uses and disclosures.
| Item | Citation | Label |
|---|---|---|
| Designate a privacy official and a contact person for complaints | §164.530(a) | Required |
| Map uses and disclosures of PHI; confirm each fits a permitted purpose or has an authorization | §164.502, §164.506–§164.512 | Required |
| Apply minimum necessary to routine and non-routine uses, disclosures and requests | §164.502(b), §164.514(d) | Required |
| Publish and distribute a Notice of Privacy Practices | §164.520 | Required |
| Procedures for access, amendment, accounting, restrictions and confidential communications | §164.522–§164.528 | Required |
| Complaint process, sanctions policy and mitigation procedures | §164.530(d)–(f) | Required |
| Non-retaliation and no waiver of rights as a condition of treatment or payment | §164.530(g)–(h) | Required |
| Track individual-rights requests in a log with due dates | — | Recommended practice |
Security Rule checklist
The Security Rule applies to electronic PHI held by covered entities and business associates. The full list of standards is on our Security Rule requirements page; the items below are the ones most often missing in practice.
| Item | Citation | Label |
|---|---|---|
| Accurate, thorough, enterprise-wide risk analysis | §164.308(a)(1)(ii)(A) | Required |
| Risk management plan that reduces risks to a reasonable and appropriate level | §164.308(a)(1)(ii)(B) | Required |
| Sanction policy and information system activity review | §164.308(a)(1)(ii)(C)–(D) | Required |
| Named security official | §164.308(a)(2) | Required |
| Workforce clearance, authorization and termination procedures | §164.308(a)(3) | Addressable |
| Security incident response and reporting | §164.308(a)(6) | Required |
| Data backup, disaster recovery and emergency mode operation plans | §164.308(a)(7)(ii)(A)–(C) | Required |
| Periodic technical and nontechnical evaluation | §164.308(a)(8) | Required |
| Unique user IDs, emergency access procedure and audit controls | §164.312(a)(2)(i)–(ii), §164.312(b) | Required |
| Encryption at rest and in transit | §164.312(a)(2)(iv), §164.312(e)(2)(ii) | Addressable |
| Disposal and media re-use procedures | §164.310(d)(2)(i)–(ii) | Required |
| Multi-factor authentication for remote and privileged access | — | Recommended practice |
| Endpoint detection and response, vulnerability scanning, penetration testing | — | Recommended practice |
Breach Notification checklist
The Breach Notification Rule (§164.400–§164.414) applies to unsecured PHI. A full walkthrough is on our breach notification requirements page.
| Item | Citation | Label |
|---|---|---|
| Documented four-factor risk assessment to decide whether an incident is a reportable breach | §164.402 | Required |
| Notify affected individuals without unreasonable delay and no later than 60 calendar days after discovery | §164.404 | Required |
| Prominent media notice when a breach affects more than 500 residents of a state or jurisdiction | §164.406 | Required |
| Notify HHS: 500 or more contemporaneously with individual notice; fewer than 500 within 60 days after the end of the calendar year | §164.408 | Required |
| Business associates notify the covered entity no later than 60 days after discovery (or sooner if the BAA says so) | §164.410 | Required |
| Retain breach documentation and burden-of-proof records | §164.414, §164.530(j) | Required |
| Tabletop exercise of the breach workflow at least annually | — | Recommended practice |
Business associate checklist
See our guide to the HIPAA business associate agreement for the contract terms themselves.
| Item | Citation | Label |
|---|---|---|
| Inventory every vendor that creates, receives, maintains or transmits PHI | §164.308(b) | Required (to meet the BAA requirement) |
| Signed BAA with each business associate containing the required terms | §164.502(e), §164.504(e), §164.314(a) | Required |
| Business associates obtain BAAs from their own subcontractors | §164.502(e)(1)(ii), §164.308(b)(2) | Required |
| Vendor security due diligence before onboarding | — | Recommended practice |
| Periodic review of BAA inventory against actual data flows | — | Recommended practice |
Training and workforce checklist
| Item | Citation | Label |
|---|---|---|
| Train all workforce members on privacy policies and procedures, new hires within a reasonable period, and after material changes | §164.530(b) | Required |
| Security awareness and training program for all workforce, including management | §164.308(a)(5)(i) | Required (standard) |
| Security reminders, malware protection, log-in monitoring and password management | §164.308(a)(5)(ii)(A)–(D) | Addressable |
| Document attendance and content of each training | §164.530(b)(2)(ii), §164.316 | Required |
| Annual refresher and phishing simulations | — | Recommended practice |
Documentation and retention checklist
| Item | Citation | Label |
|---|---|---|
| Written security policies and procedures | §164.316(a) | Required |
| Retain required documentation for six years from creation or last effective date, whichever is later | §164.316(b)(2)(i), §164.530(j)(2) | Required |
| Make documentation available to those responsible for implementing it | §164.316(b)(2)(ii) | Required |
| Review and update documentation periodically and in response to changes | §164.316(b)(2)(iii) | Required |
| Central evidence repository with owners and review dates | — | Recommended practice |
Turning the checklist into a work plan
- 1
Mark each item
Score each line as in place, partially in place or missing, and note where the evidence lives.
- 2
Confirm the risk analysis
If the risk analysis is missing or stale, fix that first. Addressable decisions and risk management depend on it.
- 3
Prioritize by risk
Rank gaps by likelihood and impact, not by how easy they are. Missing BAAs and untested backups are usually near the top.
- 4
Assign owners and dates
Every gap gets a named owner, a target date and a definition of done.
- 5
Re-check on a schedule
Revisit the checklist at least annually and after major changes such as a new EHR, cloud migration or acquisition. Our ongoing HIPAA compliance support model is built around that cadence.
Frequently asked questions
Is this checklist enough to prove HIPAA compliance?
No. A checklist shows which elements exist; it does not show that they are designed well or operating. OCR expects a documented risk analysis, risk management and evidence such as logs, training records and signed BAAs.
Do business associates need to complete every item?
Business associates must comply with the Security Rule in full and with the Privacy Rule provisions that apply to them through their BAA. Items like the Notice of Privacy Practices are covered-entity duties, though a BAA may assign related tasks to the vendor.
What does “addressable” mean in practice?
You assess whether the specification is reasonable and appropriate for your environment. If it is, implement it. If not, implement an equivalent alternative or document why neither is reasonable. Skipping it without documentation is non-compliance.
Why is MFA labeled a recommended practice?
The current Security Rule requires person or entity authentication (§164.312(d)) but does not name a specific method. MFA is a strong way to meet that standard and is widely expected, but it is not an explicit mandate under the rule as currently in force.
How often should we run through this checklist?
At least annually and whenever there is a significant change in systems, vendors, services or regulation. Many organizations tie it to the periodic evaluation required by §164.308(a)(8).
Authoritative sources
- eCFR: 45 CFR Part 164 (Security and Privacy)
- HHS: The HIPAA Security Rule
- HHS: The HIPAA Privacy Rule
- HHS: Breach Notification Rule
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.