Skip to content
HIPAA ComplianceConsulting

HIPAA Guide

How to Become HIPAA Compliant: Building a Program Step by Step

The practical sequence for building a HIPAA compliance program from the ground up — and why there is no certificate at the end, only an ongoing program you can evidence.

5 min read Reviewed

Organizations often ask how to "get HIPAA compliant" as if it were a license to apply for. It isn't. There is no HIPAA certification issued by HHS, no registration, and no point at which a regulator signs off on your program. What you can do is build a program that meets the requirements of 45 CFR Parts 160 and 164, document it well, and keep it running.

The sequence below is the order we find works for most organizations — from a two-provider practice to a growing SaaS business associate. Steps overlap, and several of them are never really finished. That is by design: HIPAA expects you to reassess as your systems, vendors and threats change.

Key points

  • There is no HIPAA certification; compliance is demonstrated through documented, ongoing practice.
  • Start with scoping and a risk analysis — everything else should follow from what it finds.
  • Addressable safeguards still require a documented decision.
  • Build in recurring reviews from the start rather than treating compliance as a project with an end date.

Before you begin: confirm your role

Your obligations depend on whether you are a covered entity, a business associate, both, or neither. A provider that bills insurers electronically is a covered entity. A software company storing PHI for clinics is a business associate. A direct-to-consumer wellness app with no covered-entity customers may not be subject to HIPAA at all, though the FTC Health Breach Notification Rule and state laws may apply. Getting this right first prevents you from building the wrong program — and if the answer is unclear, involve legal counsel.

The program-building sequence

  1. 1

    Assign accountable officials

    Designate a privacy official (§164.530(a)) and a security official (§164.308(a)(2)). Give them authority, time and a reporting line to leadership. In small organizations one person may hold both roles; what matters is that responsibility is explicit and documented.

  2. 2

    Inventory PHI and map data flows

    List every system, device, vendor and paper process that creates, receives, maintains or transmits PHI. Include the less obvious places: shared mailboxes, backups, analytics tools, support ticketing, developer laptops, fax servers. A risk analysis is only as good as this inventory.

  3. 3

    Conduct a risk analysis

    Perform an accurate and thorough assessment of risks and vulnerabilities to the confidentiality, integrity and availability of ePHI, as required by §164.308(a)(1)(ii)(A). Identify threats, existing controls, likelihood and impact, and assign risk levels. A HIPAA security risk assessment done properly produces a ranked list of risks, not just a questionnaire.

  4. 4

    Build a risk management plan

    Under §164.308(a)(1)(ii)(B), implement security measures sufficient to reduce risks to a reasonable and appropriate level. Turn the risk analysis into a plan with owners, target dates and status. This is the step regulators most often find missing — organizations identify risks and then never close them.

  5. 5

    Implement safeguards

    Address the administrative (§164.308), physical (§164.310) and technical (§164.312) safeguards. For each addressable specification, decide whether to implement it, implement an equivalent alternative, or document why neither is reasonable. Typical early priorities are unique user IDs, access reviews, audit logging, encryption, backup and recovery, and device controls.

  6. 6

    Write policies and procedures

    Document how your organization meets each applicable requirement. Policies should describe what you actually do — generic templates that nobody follows create risk rather than reducing it. Retain them for six years from creation or last effective date (§164.316(b)(2), §164.530(j)).

  7. 7

    Put business associate agreements in place

    Identify every vendor that handles PHI for you and execute a BAA that meets §164.504(e) and §164.314(a). If you are a business associate, flow the same obligations down to your subcontractors. Keep a register showing who has signed and when agreements are due for review.

  8. 8

    Address Privacy Rule operations

    Covered entities need a notice of privacy practices (§164.520), processes for patient rights such as access (§164.524) and amendment, minimum-necessary practices, and a complaint process. Business associates should know which Privacy Rule obligations their BAAs impose on them.

  9. 9

    Train the workforce

    Train all workforce members on the policies relevant to their roles (§164.530(b)) and run security awareness training (§164.308(a)(5)). Record who was trained and when, and apply a documented sanctions policy when rules are broken.

  10. 10

    Prepare for incidents and breaches

    Define how security incidents are reported, investigated and documented (§164.308(a)(6)), and how potential breaches are assessed under §164.402 and notified under §§164.404–410. A short tabletop exercise will expose gaps faster than any document review.

  11. 11

    Evaluate and repeat

    Perform periodic technical and nontechnical evaluations (§164.308(a)(8)), and update the risk analysis when you add systems, change vendors, move to the cloud or experience an incident. Many organizations run a full review annually, with lighter checks quarterly.

Required by HIPAA versus good practice

Not everything on a security vendor's list is a HIPAA requirement. Keeping the distinction clear helps you prioritize and explain decisions.

ActivityStatus under the current rule
Risk analysis and risk managementRequired — §164.308(a)(1)(ii)(A)–(B)
Security awareness trainingRequired standard — §164.308(a)(5)
Audit controlsRequired standard — §164.312(b)
Encryption at rest and in transitAddressable — must be assessed and documented
Multi-factor authenticationRecommended practice; supports access control and authentication standards
Penetration testingRecommended practice; can support the evaluation standard
SOC 2 or HITRUSTMarket expectation in some sectors; not a HIPAA requirement

How long it takes

Timelines depend on size, complexity and how much already exists. A small practice with a single EHR and a handful of vendors can stand up a credible baseline relatively quickly. A multi-site organization or a SaaS platform with many integrations takes longer, mostly because inventorying data flows and remediating technical findings takes time. A HIPAA gap analysis at the outset gives you a realistic picture of how far you have to go.

Why compliance is never "done"

Every requirement above has a maintenance dimension. Staff join and leave, vendors change, systems are upgraded, and new threats appear. OCR evaluates whether your program was functioning at the time of an incident, not whether it existed at some point in the past. Build calendars for access reviews, policy reviews, training refreshers, BAA renewals and risk analysis updates — or consider ongoing HIPAA compliance support if you lack internal capacity.

Mistakes that slow programs down

Most of these mistakes trace back to skipping the early steps. A properly scoped HIPAA security risk assessment gives you a ranked list of risks rather than a questionnaire, and HIPAA policies and procedures written after that analysis describe controls you actually operate.

  • Buying policy templates before understanding the environment they need to describe.
  • Treating the SRA Tool output as the finished risk analysis without validating scope and findings.
  • Leaving shadow IT — personal messaging apps, unsanctioned file sharing — out of the inventory.
  • Signing a cloud provider's BAA and assuming the configuration is therefore compliant.
  • Running a one-time project and letting documentation go stale.

Frequently asked questions

Is there an official HIPAA compliance certificate?

No. HHS does not certify organizations as HIPAA compliant, and no private certificate has official standing. You demonstrate compliance through documentation and practice.

What is the first thing we should do?

Confirm whether you are a covered entity or business associate, then inventory where PHI lives and complete a risk analysis. Most other decisions depend on what the risk analysis finds.

Can we use the HHS Security Risk Assessment Tool?

Yes. The SRA Tool from ONC and OCR is free and useful, particularly for smaller providers. Using it does not by itself ensure compliance — you still need to scope it accurately and act on the results.

Do we need a consultant to become HIPAA compliant?

Not necessarily. HIPAA does not require outside help. Many organizations use a consultant for the risk analysis or a gap analysis and run the program internally afterward. No consultant can guarantee compliance.

How often should we update our risk analysis?

HIPAA does not set a fixed interval, but it must be kept current. Many organizations review it at least annually and whenever significant changes occur in systems, vendors or operations.

Authoritative sources

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.

Talk through your HIPAA obligations with a consultant

Tell us about your organization, how you handle patient information, and what’s prompting the review. We’ll suggest a practical scope — and tell you if you don’t need us.