top of page

How to Achieve HIPAA Compliance: 7-Step Guide

Dr. Tara Isaacs
Oct 20
9 min read

Table of Contents

  • What HIPAA Compliance Actually Requires (and What It Doesn't)

  • Step 1: Conduct a Risk Analysis That Meets HIPAA Risk Assessment Requirements

    • What Your Risk Analysis Must Document

    • How Often to Repeat the Risk Analysis

  • Step 2: Appoint a Privacy and Security Officer

  • Step 3: Build Your HIPAA Compliance Checklist Around the Three Safeguard Categories

    • The HIPAA Privacy Rule: Who Can See PHI and Why

    • The HIPAA Security Rule: Protecting ePHI Specifically

    • Administrative Safeguards

    • Technical Safeguards: Access Control, Encryption, and Audit Controls

    • Physical Safeguards

    • Organizational Requirements and Documentation

    • What the Privacy Rule and Security Rule Do Not Cover

  • Step 4: Write Policies, Procedures, and a Sanction Policy

  • Step 5: Use a HIPAA Business Associate Agreement Template Correctly

    • Vendor Management Beyond the BAA

  • Step 6: Deliver HIPAA Training for Employees That Sticks

    • Remote and Hybrid Workforce Training Gaps

  • Step 7: Prepare an Incident Response Plan Before You Need One

    • The Breach Notification Rule: Timelines You Must Hit

    • The Five Phases of a Workable Plan

    • Tabletop Exercises: Where Plans Actually Get Tested

    • Documentation: The Part Auditors Actually Read

    • Budgeting for Compliance and Ongoing Costs

  • Frequently Asked Questions

Last Updated: September 22, 2026

What HIPAA Compliance Actually Requires (and What It Doesn't)

Learning how to achieve HIPAA compliance starts with a hard truth: the rules are not a checklist you finish once. HIPAA compliance is the ongoing practice of protecting protected health information (PHI) through administrative, physical, and technical safeguards, and being able to prove it.

Step 1: Conduct a Risk Analysis That Meets HIPAA Risk Assessment Requirements

A risk analysis is the foundation of every other HIPAA decision you'll make. Get it wrong and your entire compliance program rests on guesses.

What Your Risk Analysis Must Document

Your written analysis should capture, at minimum:

  • Every system, device, and location that touches ePHI

  • Threats and vulnerabilities for each one

  • Current controls and their effectiveness

  • Likelihood and impact ratings

  • A prioritized remediation plan with owners and dates

How Often to Repeat the Risk Analysis

Repeat it at least annually and whenever something material changes: a new EHR module, a cloud migration, an acquisition, or a remote work policy. A common mistake is treating the analysis as a one-time audit artifact; it should be a living document your security officer updates quarterly.

Step 2: Appoint a Privacy and Security Officer

HIPAA requires a named Privacy Officer and a Security Officer. One person can hold both roles in smaller organizations, but the responsibilities cannot go unassigned.

Pro Tip Name a backup for each role and document the delegation in writing. When your Security Officer resigns, auditors will ask who was responsible on the day of an incident. A verbal handoff won't survive that question.

Step 3: Build Your HIPAA Compliance Checklist Around the Three Safeguard Categories

Every HIPAA compliance checklist maps to three categories: administrative, technical, and physical safeguards. Miss one and you have a gap an auditor will find. But first you need to understand the two rules those safeguards live inside: the Privacy Rule and the Security Rule.

Compliance officer reviewing a HIPAA compliance checklist and digital security dashboard in an office

The HIPAA Privacy Rule: Who Can See PHI and Why

The Privacy Rule, enforced by the HHS Office for Civil Rights, governs the use and disclosure of protected health information in any form, paper, verbal, or electronic. Its core mechanisms are the minimum necessary standard, the permitted uses and disclosures framework, and the patient rights it grants.

  • Minimum necessary: For most uses and disclosures, limit PHI to the smallest amount needed to accomplish the purpose. Treatment, payment, and healthcare operations are broad exceptions, but even there, role-based access should reflect the minimum necessary principle.

  • Permitted uses and disclosures: Treatment, payment, and operations do not require patient authorization. Everything else generally does, with narrow exceptions for public health reporting, law enforcement requests meeting specific criteria, and serious threats to health or safety.

  • Patient rights: Individuals can access their records, request amendments, receive an accounting of disclosures, request restrictions, and ask for confidential communications. Each right has a defined response window, commonly 30 days for access requests, with one 30-day extension permitted.

  • Notice of Privacy Practices: You must give patients a written notice explaining how their PHI is used and disclosed, and document acknowledgment of receipt.

The HIPAA Security Rule: Protecting ePHI Specifically

The Security Rule applies only to electronic PHI. It requires covered entities and business associates to ensure the confidentiality, integrity, and availability of ePHI, protect against reasonably anticipated threats, protect against impermissible uses or disclosures, and ensure workforce compliance.

Administrative Safeguards

These are your policies, people, and processes: risk analysis, workforce training, access management, and contingency planning. They carry the most weight in an investigation because they show intent and governance. Key specifications include a designated security official, workforce clearance procedures, termination procedures, and periodic evaluation of your security posture.

Technical Safeguards: Access Control, Encryption, and Audit Controls

Technical safeguards cover the systems themselves. The core requirements are:

  • Access control: Unique user identification, emergency access procedures, automatic logoff, and encryption where reasonable and appropriate.

  • Audit controls: Mechanisms that record and examine activity in systems containing ePHI. Logs must be retained and reviewable.

  • Integrity controls: Policies and mechanisms that protect ePHI from improper alteration or destruction.

  • Person or entity authentication: Verify that the person seeking access is who they claim to be, MFA is the practical standard today.

  • Transmission security: Guard against unauthorized access to ePHI transmitted over a network, typically through encryption.

Physical Safeguards

Physical safeguards protect the facilities and devices: locked server rooms, workstation positioning that blocks screen viewing, device and media disposal procedures, and visitor controls. Remote work has made this category harder, not optional. Laptops leaving the building, home offices, and personal devices all fall under physical safeguard obligations.

Organizational Requirements and Documentation

Beyond the three safeguard categories, the Security Rule imposes organizational requirements: business associate agreements, documentation of policies and procedures, and a six-year retention requirement for Security Rule documentation. Auditors will ask for the version of a policy in effect on a specific date, not the current draft.

Safeguard Category

Core Focus

Typical Evidence

Administrative

Policies, training, risk analysis

Signed policies, training logs

Technical

Access control, encryption, audit logs

System configs, log exports

Physical

Facilities, devices, media

Access records, disposal logs

Pro Tip Build your checklist from the Security Rule's implementation specifications, not from a generic template. Mark each specification as required or addressable, and for every addressable item, write one sentence explaining your decision. That sentence is often the difference between a clean audit and a finding.

What the Privacy Rule and Security Rule Do Not Cover

Neither rule tells you which firewall to buy or which EHR to use. They set outcomes and let you choose the mechanism. That flexibility is why two organizations with very different technology stacks can both be compliant, and why copying another organization's checklist rarely works.

Step 4: Write Policies, Procedures, and a Sanction Policy

Policies state what your organization requires; procedures explain how people follow them. HIPAA expects both, in writing, plus a sanction policy that defines consequences for violations.

Step 5: Use a HIPAA Business Associate Agreement Template Correctly

A HIPAA business associate agreement template is a contract that binds vendors handling PHI to the same protections you owe your patients. It is required before any business associate touches ePHI.

Vendor Management Beyond the BAA

Before signing, request the vendor's SOC 2 report, its own risk analysis summary, and its breach notification timeline. After signing, reassess annually. Track every vendor with a simple register: name, data touched, contract date, last review, and risk rating. When a vendor has a breach, that register is how you know within hours whether you're affected.

Watch Out Never let a vendor begin handling ePHI while the BAA is still in legal review. Unauthorized disclosure during that window is a reportable breach, even if the contract is signed the following week.

Step 6: Deliver HIPAA Training for Employees That Sticks

HIPAA training for employees is required at onboarding and whenever job duties or policies change. Annual refreshers are the common standard, but frequency matters less than retention.

Remote and Hybrid Workforce Training Gaps

Remote work creates gaps most training programs ignore: home Wi-Fi security, family members seeing screens, personal devices syncing work email, and printing PHI at home. Add a short remote-work module and require acknowledgment. Document completion dates for every employee, including contractors.

Step 7: Prepare an Incident Response Plan Before You Need One

An incident response plan defines who does what in the first hours after a suspected breach. HIPAA doesn't hand you a template, but it does expect you to detect, contain, assess, and notify within required timeframes. The Breach Notification Rule sets the clock, and the plan is how you meet it without improvising.

The Breach Notification Rule: Timelines You Must Hit

Under the Breach Notification Rule, once you determine that a breach of unsecured PHI has occurred, you must notify affected individuals without unreasonable delay and no later than 60 days from the date of discovery. Discovery is not the date of the incident, it is the date you knew or should reasonably have known, which is why detection and triage speed matter.

  • Fewer than 500 individuals: Notify affected individuals within 60 days, and notify HHS within 60 days after the end of the calendar year in which the breach was discovered.

  • 500 or more individuals: Notify affected individuals, HHS, and, for breaches affecting 500 or more residents of a state or jurisdiction, prominent media outlets in that area, all without unreasonable delay and no later than 60 days from discovery.

  • Business associates: A business associate must notify the covered entity of a breach without unreasonable delay and no later than 60 days from discovery. The covered entity then carries the notification obligations.

  • Content of notification: The notice must describe what happened, the types of PHI involved, steps individuals should take, what you are doing to investigate and mitigate, and contact information.

The Five Phases of a Workable Plan

Build yours around five phases: detection, containment, assessment, notification, and post-incident review. Each phase needs a named owner, a decision criterion, and a documented output.

  1. Detection: How do you learn about an incident? Sources include SIEM alerts, employee reports, vendor notifications, and patient complaints. Every source needs a documented intake path.

  2. Containment: Immediate steps to stop the bleeding, disabling accounts, isolating systems, revoking credentials, preserving logs before they roll over.

  3. Assessment: The breach determination. Was PHI involved? Was it unsecured? Does the low-probability-of-compromise exception apply? This decision starts the 60-day clock, so document the reasoning.

  4. Notification: Individuals, HHS, and media where required. Pre-draft notification letters and have your legal contact and communications lead identified in advance.

  5. Post-incident review: Root cause analysis, corrective action plan, and updates to your risk analysis. This phase is where the next incident gets prevented.

Tabletop Exercises: Where Plans Actually Get Tested

Run a tabletop exercise at least twice a year. A useful scenario is a lost laptop containing unencrypted ePHI, or a ransomware event on a server that stores billing records. Walk through the five phases with the actual people who would be involved, and time each decision.

Key Takeaway The plan's value is not just the document. It's the tabletop exercise you run, where you may discover that your call tree is outdated and your legal contact is on vacation.

Documentation: The Part Auditors Actually Read

Keep a breach log that records every suspected incident, the date of discovery, the determination made, the reasoning, and the notifications sent. Even incidents that turn out not to be breaches should be logged with the rationale. If HHS investigates, that log is your evidence of a reasonable, consistent process, and often the difference between a resolved inquiry and a civil money penalty.

Budgeting for Compliance and Ongoing Costs

Compliance is a recurring line item, not a project. Budget for annual risk analysis, training delivery, log management, encryption tooling, vendor assessments, tabletop exercises, and legal review of agreements. Pricing for external support depends on your size, systems, and current gaps, so request a scoped quote rather than assuming a figure.

Frequently Asked Questions

What are the four key rules of HIPAA compliance?

HIPAA has four main rules: the Privacy Rule (governs how PHI is used and disclosed), the Security Rule (sets standards for protecting ePHI electronically), the Breach Notification Rule (requires notification when unsecured PHI is exposed), and the Enforcement Rule (covers penalties and investigations). The Omnibus Rule updated all four in 2013 to extend requirements to Business Associates. Your compliance program must address each rule.

Is HIPAA compliance a one-time process or ongoing?

It is ongoing. HIPAA requires regular risk analyses, updated policies when operations change, recurring workforce training, and continuous monitoring of access controls and audit logs. A risk analysis from three years ago does not cover a new cloud system or remote work arrangement. Regulatory oversight has increased, and auditors expect documentation showing your compliance program evolves with your organization's technology and workforce.

What happens if we fail a HIPAA audit or experience a data breach?

Consequences range from corrective action plans to financial penalties that scale with the level of negligence, from lack of awareness to willful neglect. A data breach also triggers notification requirements to affected individuals, the Department of Health and Human Services, and sometimes the media. Beyond fines, breaches damage patient trust and can expose your organization to lawsuits. An incident response plan and documented compliance efforts reduce both the severity and the penalty exposure.

How do we handle HIPAA compliance for a remote or hybrid workforce?

Remote work expands your ePHI footprint beyond the office. Require encryption on all laptops and mobile devices, enforce multi-factor authentication for remote access, and use VPNs or zero-trust access controls. Physical safeguards still apply at home: locked storage for paper records and privacy screens. Update your risk analysis to include home offices, and make sure HIPAA training for employees covers remote-specific scenarios like video calls in shared spaces and securing home Wi-Fi networks.

Schedule a consultation

 
 
 

Comments


bottom of page