Last updated: November 8, 2026
Reviewed by an information security professional (CISSP) on November 11, 2026.
A HIPAA compliance checklist begins with a single question: are you a covered entity or a business associate? If so, HIPAA makes you protect patient information under the Privacy Rule, secure electronic health data under the Security Rule and report breaches under the Breach Notification Rule. The 25 steps below turn those rules into tasks you can assign and track, built around the Security Rule risk analysis.
Short answer: A HIPAA compliance checklist needs five areas: confirm whether HIPAA applies, satisfy the Privacy Rule (notices, patient rights, minimum necessary use), satisfy the Security Rule (risk analysis plus administrative, physical and technical safeguards), prepare for the Breach Notification Rule (60-day deadlines) and manage business associates. HHS’s proposed Security Rule update, published January 6, 2025, now carries a projected final action date of July 2027.
Key takeaways
- The Security Rule calls for an accurate and thorough analysis of risks to electronic protected health information (ePHI).
- Individuals get breach notices within 60 days of discovery; breaches affecting 500 or more people also go to HHS and, state by state, to the media.
- Smaller breaches are reported to HHS within 60 days after the end of the calendar year.
- Business associates have to sign agreements and tell covered entities about breaches within 60 days of discovery.
- The proposed Security Rule would make every implementation specification mandatory and add requirements like encryption, multifactor authentication and annual compliance audits.
Table of Contents
Does HIPAA apply to you?
Two groups fall under HIPAA:
- Covered entities: health plans, health care clearinghouses and health care providers that conduct certain transactions electronically, such as billing insurance.
- Business associates: vendors and contractors that create, receive, maintain or transmit protected health information (PHI) on behalf of a covered entity, such as billing companies, IT providers, cloud services and consultants.
Plenty of health and wellness apps people use on their own fall outside HIPAA, though other privacy laws may cover them. If you’re unsure, map who you work for and what data you handle before you build a program.

HIPAA compliance checklist: 25 steps
Part 1: Governance
- Confirm your status as a covered entity, business associate or both, and write down why.
- Appoint a privacy officer and a security officer. In a small practice, one person can fill both roles.
- Inventory where PHI lives, from paper records and EHR systems to email, cloud storage, laptops, phones and vendor systems.
- Adopt written policies and procedures for privacy, security and breach response, and retain them for at least six years.
- Train your workforce at hire and periodically afterward, and record attendance.
Part 2: Privacy Rule
- Publish a Notice of Privacy Practices explaining how you use and disclose PHI, and keep it up to date.
- Apply the minimum necessary standard, so people use and share only the PHI they need for a task.
- Honor patient rights, including access to their records, amendments and an accounting of certain disclosures.
- Respond to access requests on time. Patients generally get access within 30 days, with one 30-day extension in limited cases.
- Get written authorization for uses and disclosures that the rules don’t otherwise permit, such as most marketing.
Part 3: Security Rule
- Conduct a risk analysis covering all ePHI you create, receive, maintain or transmit.
- Implement a risk management plan that brings the risks you found down to a reasonable level.
- Control access with unique user IDs, role-based permissions and quick removal of access when people leave.
- Use strong authentication, including multifactor authentication for remote and administrative access.
- Encrypt ePHI on laptops, mobile devices, backups and in transit wherever reasonable.
- Turn on audit logs and review them for unusual access.
- Back up data and test recovery, so you can restore systems after ransomware or failure.
- Secure facilities and devices with physical controls, screen locks and secure disposal.
- Manage patches and vulnerabilities on a regular schedule.
Part 4: Breach Notification Rule
- Write an incident response plan that includes the four-factor breach risk assessment.
- Track discovery dates, because the 60-day clocks start at discovery.
- Prepare notice templates for individuals, HHS and the media.
Part 5: Business associates
- Sign business associate agreements with every vendor that handles PHI for you.
- Assess vendors’ security before sharing PHI and periodically after.
- Review the program at least annually and after major changes, such as new systems, mergers or incidents.
The HIPAA Security Rule risk analysis, step by step
Every HIPAA compliance program rests on the risk analysis, and the HIPAA security rule makes it mandatory. HHS guidance on risk analysis says organizations must carry out an accurate and thorough assessment of potential risks and vulnerabilities to the confidentiality, integrity and availability of ePHI, and it lists these elements:

- Scope: all ePHI in any electronic medium or location.
- Data collection: where ePHI is stored, received, maintained or transmitted.
- Threats and vulnerabilities: reasonably anticipated natural, human and environmental threats, and weaknesses that could be exploited.
- Current security measures: whether safeguards are in place and used properly.
- Likelihood and impact: how likely each threat is and how much harm it could cause.
- Risk level: a rating for each threat and vulnerability pair, with corrective actions.
- Documentation: a written record that feeds your risk management plan.
- Periodic review: reassessment after incidents, staffing or ownership changes and new technology.
HHS doesn’t mandate a format, so a small practice can use a spreadsheet. What counts is that it’s complete, specific to your environment and kept up to date.

HIPAA compliance for small practices: where to start
Small practices often assume they need a costly program before they can start. A realistic first 90 days looks like this:
- Week 1 to 2: name your privacy and security officers and list every system and vendor that touches PHI.
- Week 3 to 6: complete a documented risk analysis, even a simple spreadsheet, using HHS’s elements.
- Week 7 to 10: fix the highest risks first, usually multifactor authentication on email, encrypted devices and tested backups.
- Week 11 to 12: collect signed business associate agreements, adopt core policies and train staff.
That order tackles the HIPAA compliance gaps most likely to trigger a breach or an enforcement problem, and it produces the documentation you’ll need if regulators come asking.
What to have ready if regulators ask
When HHS’s Office for Civil Rights investigates after a complaint or breach report, it usually asks for documentation. Keep these organized and current:
- Your most recent risk analysis and risk management plan.
- Privacy and security policies and procedures.
- Signed business associate agreements.
- Training records.
- Incident logs, breach risk assessments and notification records.
- Evidence of access controls, audit log reviews and backups.
Any HIPAA compliance checklist is only as strong as the evidence behind it.
HIPAA breach notification deadlines
HHS’s Breach Notification Rule summary says an impermissible use or disclosure of PHI is presumed to be a breach unless a risk assessment shows a low probability that the PHI was compromised. That assessment weighs the nature and extent of the PHI, who received it, whether it was actually acquired or viewed, and how well the risk was mitigated.
| Who to notify | When |
|---|---|
| Affected individuals | Without unreasonable delay, no later than 60 days after discovery |
| Media serving the area | For breaches affecting more than 500 residents of a state or jurisdiction, within the same 60 days |
| HHS, 500 or more individuals | Without unreasonable delay, no later than 60 days after the breach |
| HHS, fewer than 500 individuals | Annually, within 60 days after the end of the calendar year of discovery |
| Covered entity (from a business associate) | Without unreasonable delay, no later than 60 days after discovery |
State breach notification laws may set shorter deadlines, so check state rules as well.
The proposed HIPAA Security Rule update
On January 6, 2025, HHS published a proposed rule to strengthen the Security Rule, the first update since 2013. McDermott Will & Schulte reports that the 2026 Unified Agenda lists the rulemaking as a long-term action with a projected final action date of July 2027, pushed back from the May 2026 date shown earlier. The proposal would:
- Make all implementation specifications required, removing the “addressable” distinction.
- Add or expand requirements for encryption and multifactor authentication.
- Require technology asset inventories and network maps.
- Require compliance audits at least every 12 months, with risk analysis updates at least annually.
- Require penetration tests every 12 months and vulnerability scans every six months.
- Require business associate verification at least every 12 months and stronger backup and recovery controls.
None of this is final, and the requirements may change. Many of these controls already match good practice and OCR’s enforcement expectations, though, so working toward them now lowers risk either way.
Worked example: a 12-person dental practice
Picture a hypothetical dental office with 12 staff, a cloud-based practice management system, a billing service and an IT contractor.
- Status: it bills insurance electronically, so it’s a covered entity. The billing service, IT contractor and cloud vendor are business associates.
- Inventory: PHI lives in the practice management system, imaging software, email, a shared drive, front-desk paper files and staff phones used for appointment reminders.
- Risk analysis findings: shared front-desk logins, no multifactor authentication on email, unencrypted backups on an external drive and no signed agreement with the IT contractor.
- Fixes: unique logins with role-based access, multifactor authentication, encrypted cloud backups with tested restores, and a signed business associate agreement.
- Ongoing: annual training, an updated risk analysis each year and after the move to a new imaging system, and a log of any privacy incidents.
HIPAA compliance checklist for business associates
Business associates carry direct obligations under HIPAA, not only contract duties. A short checklist for vendors:
- Sign a business associate agreement with each covered entity client, and with your own subcontractors that handle PHI.
- Run your own risk analysis under the HIPAA Security Rule; your clients’ analysis doesn’t cover your systems.
- Limit use and disclosure to what the agreement permits.
- Report breaches to the covered entity without unreasonable delay and no later than 60 days after discovery.
- Prepare for security questionnaires and, if the proposed rule is finalized, annual verification requests from clients.
- Return or destroy PHI at the end of the relationship where feasible.
HIPAA compliance and AI tools
More and more staff paste notes, emails and documents into AI assistants. When that content includes PHI, HIPAA applies to the tool:
- Use only tools covered by a business associate agreement for any PHI. Most consumer AI chatbots don’t offer one on free or personal plans.
- De-identify data when you can, removing names and other identifiers before using general-purpose tools.
- Apply minimum necessary, sharing only what the task requires.
- Update your risk analysis to include AI tools, including where data is stored and who can access it.
- Train staff on which tools are approved for PHI and which aren’t.
AI scribes, chart summarizers and coding assistants can save time, but each is one more place PHI lives, so add it to your inventory.
A quarterly HIPAA compliance calendar
- Quarter 1: update the risk analysis and risk management plan; confirm business associate agreements are current.
- Quarter 2: run workforce training and a phishing exercise; review access lists and remove stale accounts.
- Quarter 3: test backups and restores; tabletop an incident response scenario.
- Quarter 4: review policies, the notice of privacy practices and vendor security; plan next year’s priorities, including any final Security Rule changes.
Common HIPAA compliance mistakes
- Skipping or reusing a generic risk analysis. It must reflect your actual systems.
- Missing business associate agreements, especially with IT and cloud vendors.
- Shared logins that make access impossible to audit.
- Unencrypted laptops and backups.
- Slow responses to patient access requests.
- Treating HIPAA as a one-time project instead of an ongoing program.

For related security compliance coverage, see our guide to SOC 2 Type 1 vs Type 2, which many health tech vendors pursue alongside HIPAA.
Our Take / Expert Perspective
Our take: the risk analysis remains the most important item on any HIPAA compliance checklist, and the proposed Security Rule update only underlines that.
HIPAA’s Security Rule has always been flexible: organizations pick safeguards based on their own risk analysis, and many specifications are “addressable.” In practice, that flexibility let plenty of small providers skip the hard work of a documented risk analysis. The proposed rule would take away most of that room by making specifications mandatory and adding concrete requirements like multifactor authentication, encryption, asset inventories and annual audits.
The final rule has slipped to a projected July 2027, and it may change before then. Don’t take that as a reason to wait. Ransomware and email compromise drive many health care breaches, and the proposal’s controls are the ones that stop them. Organizations that adopt them now will have less to do once the rule is final and fewer breaches to report in between. That’s our forecast from the proposal’s direction, not a prediction of the final text.
Business associates face growing scrutiny from covered entities. Expect annual verification requests, security questionnaires and contract terms that reach beyond a basic agreement.
Our recommendation: update your risk analysis this quarter, close the multifactor authentication, encryption and backup gaps first, and confirm that every vendor touching PHI has signed a business associate agreement.
Frequently Asked Questions
What should a HIPAA compliance checklist include?
It needs governance (officers, policies, training), the Privacy Rule (notice of privacy practices, patient rights, minimum necessary), the Security Rule (risk analysis and safeguards), the Breach Notification Rule (incident response and 60-day notices) and business associate management.
How often should a HIPAA risk analysis be done?
HHS sets no fixed frequency but expects the risk analysis to be ongoing, with reassessment after incidents, staffing or ownership changes and new technology. Many organizations update it every year, and the proposed Security Rule would require at least annual updates.
Who needs to comply with HIPAA?
Covered entities, meaning health plans, health care clearinghouses and providers that conduct certain transactions electronically, and their business associates that handle PHI on their behalf.
What are the HIPAA breach notification deadlines?
Notify individuals without unreasonable delay and no later than 60 days after discovery. Breaches of 500 or more people also go to HHS within 60 days, and to the media when more than 500 residents of a state are affected. Smaller breaches are reported to HHS once a year.
Is there an official HIPAA certification?
No. HHS doesn’t certify anyone as HIPAA compliant. Some companies offer customers third-party assessments or SOC 2 reports mapped to HIPAA safeguards as evidence.
Is the HIPAA Security Rule changing?
HHS proposed changes on January 6, 2025, among them mandatory implementation specifications, encryption and multifactor authentication. The 2026 Unified Agenda projects final action in July 2027, so the current rule still governs.
This article is for general information only and is not legal advice. Laws differ by state, province and country; consult a qualified attorney for your situation.
Sources
- HHS: Guidance on risk analysis requirements under the HIPAA Security Rule, checked November 8, 2026
- HHS: Breach Notification Rule, checked November 8, 2026
- McDermott Will & Schulte: Final action on HIPAA Security Rule modifications now projected for July 2027, checked November 8, 2026
- aiandblog: SOC 2 Type 1 vs Type 2 and our Editorial Policy
Photos: Vitaly Gariev and Wonderlane on Unsplash.










Leave a Reply