Skip to main content
Intelligent Security Governance — 340+ Frameworks Powered by Ayurak AI
Blog/Compliance Guides

HIPAA Compliance: Requirements, Enforcement and a Practical Path

A practitioner's reference to HIPAA: who it covers, what the Privacy, Security and Breach Notification Rules require, how OCR enforces them, and how to build a workable compliance program.

HIPAA Compliance: Requirements, Enforcement and a Practical Path

HIPAA is the US federal framework that governs how health information is protected, used and disclosed. It applies to health plans, most healthcare providers, healthcare clearinghouses and the vendors that handle protected health information on their behalf. There is no official HIPAA certification: compliance is something you demonstrate to the regulator, not a badge you earn from an auditor.

What it is

HIPAA is the Health Insurance Portability and Accountability Act of 1996, a US federal law. The requirements most security teams work with come from regulations issued by the Department of Health and Human Services (HHS) under that law. They are found in 45 CFR Parts 160, 162 and 164, and are enforced by the HHS Office for Civil Rights (OCR).

The main components are:

  • Privacy Rule: sets limits on how protected health information (PHI) may be used and disclosed, and gives individuals rights over their records.
  • Security Rule: requires administrative, physical and technical safeguards for electronic PHI (ePHI).
  • Breach Notification Rule: requires notice to affected individuals, HHS and, in some cases, the media after a breach of unsecured PHI.
  • Enforcement Rule: sets out investigation procedures and penalties.

The HITECH Act of 2009 strengthened HIPAA by extending direct liability to business associates, adding breach notification and raising penalties. The Omnibus Rule of 2013 implemented those changes. HIPAA is mandatory for entities in scope. It is also in a period of change: HHS has proposed updates to the Security Rule, and recent Privacy Rule amendments have been challenged and partly vacated in court, so confirm the current text before relying on any summary, including this one.

Who it applies to

HIPAA applies by entity type, not by company size or revenue. There are two main groups:

  • Covered entities: health plans, healthcare clearinghouses, and healthcare providers that transmit health information electronically in connection with standard transactions such as billing insurers.
  • Business associates: organizations that create, receive, maintain or transmit PHI on behalf of a covered entity. Examples include cloud hosting providers, billing companies, EHR vendors, analytics firms and law firms with access to PHI. Subcontractors of business associates are business associates too.

Jurisdiction is US federal law, but a non-US company that handles PHI for a US covered entity can be a business associate. Not all health data is PHI. Consumer health apps that have no relationship with a covered entity generally fall outside HIPAA, though other regimes, such as FTC rules and state laws, may apply.

Key requirements and control areas

Privacy Rule

  • Uses and disclosures of PHI are permitted for treatment, payment and healthcare operations, and otherwise generally require authorization or a specific exception.
  • The minimum necessary standard limits access and disclosure to what is needed for the purpose.
  • Individuals have rights to access their records, request amendments, receive an accounting of certain disclosures and receive a notice of privacy practices.
  • Covered entities must designate a privacy official, train the workforce and maintain policies and sanctions.

Security Rule

The Security Rule is organized into administrative, physical and technical safeguards, plus organizational and documentation requirements. Its standards are flexible and scalable, and its implementation specifications are labeled either required or addressable. Addressable does not mean optional: you must implement the specification, implement an equivalent alternative, or document why neither is reasonable. Key areas include:

  • Risk analysis and risk management: an accurate, thorough assessment of risks to ePHI, followed by measures that reduce them. This is the requirement OCR cites most often in enforcement.
  • Security management and governance: a designated security official, sanction policy, and regular review of system activity.
  • Workforce security and access management: authorization, role-based access, and termination procedures.
  • Contingency planning: data backup, disaster recovery and emergency mode operation.
  • Technical safeguards: unique user identification, access control, audit controls, integrity controls, person or entity authentication and transmission security. Encryption is addressable under the current text, though it is central to the breach safe harbor and to most real-world programs.
  • Physical safeguards: facility access, workstation use and security, and device and media controls.
  • Business associate contracts: a written business associate agreement (BAA) is required before PHI is shared, setting out permitted uses, safeguards and breach reporting.
  • Documentation: policies and records of required actions must be retained, generally for six years.

Breach Notification Rule

An impermissible use or disclosure of unsecured PHI is presumed to be a breach unless a documented risk assessment shows a low probability that the PHI was compromised. Covered entities must notify affected individuals without unreasonable delay and no later than 60 days after discovery. Breaches affecting 500 or more individuals also require notice to HHS and, in many cases, to the media, while smaller breaches are reported to HHS annually. Business associates must notify the covered entity. PHI that has been encrypted in accordance with HHS guidance is not considered unsecured.

Assessment, audit and enforcement

HIPAA has no certification body and no official attestation. Compliance is self-managed and tested through regulator action. OCR investigates complaints, breach reports and compliance reviews, and has run periodic audit programs. State attorneys general can also bring civil actions under HITECH.

Outcomes of an investigation range from technical assistance to resolution agreements with monetary settlements and multi-year corrective action plans. The law sets tiered civil money penalties based on the level of culpability, with annual caps per violation category that are adjusted for inflation, so check the current figures. Criminal penalties apply to knowing misuse of PHI and are handled by the Department of Justice.

In practice, many covered entities ask business associates for third-party evidence such as a SOC 2 report, HITRUST certification or a completed security questionnaire. These are commercial expectations, not HIPAA requirements. OCR has also stated that it considers whether an organization has followed recognized security practices when deciding on enforcement outcomes, under a 2021 amendment to HITECH.

A practical path to meeting HIPAA

  1. Determine your status. Decide whether you are a covered entity, a business associate or both, and for which lines of business.
  2. Inventory PHI and ePHI. Map where PHI is created, received, stored and transmitted, including cloud services, backups, logs, email and third-party tools.
  3. Assign responsibility. Appoint privacy and security officials and define who owns each safeguard.
  4. Perform an enterprise-wide risk analysis. Cover every system that touches ePHI, document threats, vulnerabilities, likelihood and impact, and keep it current when systems or processes change.
  5. Build a risk management plan. Prioritize remediation, assign owners and dates, and track completion.
  6. Write and adopt policies. Cover the Privacy, Security and Breach Notification Rules, including addressable specifications and the reasoning where you chose alternatives.
  7. Implement technical controls. Enforce MFA and least-privilege access, encrypt data at rest and in transit, enable audit logging with review, and test backups and recovery.
  8. Manage business associates. Keep an inventory, execute BAAs, assess vendor security and review them periodically.
  9. Train the workforce. Provide onboarding and recurring training, and apply sanctions consistently.
  10. Prepare for incidents. Document response and breach assessment procedures and rehearse them, including the notification timelines.
  11. Review continuously. Re-run risk analysis periodically and after significant change, and retain documentation for six years.

How it maps to other frameworks

These overlaps are real but partial. Meeting one framework does not mean you meet HIPAA.

  • NIST CSF and NIST SP 800-66: NIST publishes guidance on implementing the HIPAA Security Rule (SP 800-66) that cross-references SP 800-53 controls and the Cybersecurity Framework. This is the closest mapping.
  • ISO 27001: its risk assessment, access control, logging, supplier and continuity controls overlap substantially with the Security Rule safeguards. It does not address the Privacy Rule or breach notification specifics.
  • SOC 2: the Security, Availability and Confidentiality criteria overlap with many technical and administrative safeguards. A SOC 2 report is often used as vendor evidence but is not a HIPAA attestation.
  • HITRUST CSF: a certifiable framework that incorporates HIPAA requirements among others. It is voluntary and run by a private organization.
  • State health privacy laws: several states impose stricter or additional requirements, so HIPAA is a floor rather than a ceiling.

FAQs

Is there an official HIPAA certification?

No. HHS does not certify organizations or products as HIPAA compliant. Vendors who claim to be "HIPAA certified" are using a private assessment or marketing language. What matters is whether you can show OCR your risk analysis, policies, safeguards and records.

Do we need a BAA with our cloud provider?

If the provider creates, receives, maintains or transmits ePHI for you, it is a business associate and a BAA is required, even if it cannot view the data because it is encrypted. Major cloud providers offer BAAs, usually limited to specific eligible services, so confirm that the services you use are covered.

Are addressable specifications optional?

No. You must assess whether each is reasonable and appropriate, then implement it, implement an equivalent alternative, or document why neither is appropriate. Skipping one without documentation is a common finding.

How often must we do a risk analysis?

The rule requires an ongoing process rather than naming a fixed interval. Most programs perform a full analysis at least annually and repeat it when there are significant changes such as new systems, acquisitions or incidents.

Does HIPAA apply to a startup building a health app?

Only if it is a covered entity or acts as a business associate, for example by handling PHI for a provider or health plan. An app that collects data directly from consumers with no covered-entity relationship is usually outside HIPAA, but may be subject to FTC and state requirements.

How Aristiun helps

HIPAA programs depend on evidence that safeguards exist and keep working, and on a risk analysis that reflects how systems actually run. Aristiun is the AI-powered compliance automation and threat modeling platform, powered by Ayurak AI, and it supports that work across the HIPAA framework and the other regimes you maintain.

  • Automated evidence collection: gather evidence from connected systems such as AWS, Azure, GCP and GitHub, without manual screenshots or spreadsheets.
  • Control monitoring and gap analysis: get alerts when controls drift out of compliance, and use AI-powered validation to identify gaps before an investigation or customer review does.
  • Cross-framework mapping: map each piece of evidence to the relevant controls across all applicable frameworks, so one evidence base can serve HIPAA, SOC 2 and ISO 27001 together.
  • Threat modeling and vendor risk: generate threat models from code, IaC and architecture diagrams to inform your risk analysis, and map vendor controls to your requirements when assessing business associates.

Found this insightful?

Share it with your security team or save it for later.

Get Started

Ready to secure your organization?

See how Aristiun automates compliance and strengthens your security posture across 340+ frameworks.