A hospital in Texas paid $2.175 million to the Office for Civil Rights because staffers accessed patient records without authorization. The violation touched multiple parts of HIPAA — the Privacy Rule, the Security Rule, and the enforcement provisions — all at once. That's the thing about this law. It's not one simple regulation. It's a layered structure, and each part has teeth.

If you've ever searched for the parts of HIPAA hoping for a clean breakdown, you've probably found dense legal summaries that don't translate to real operations. I've spent years helping covered entities and business associates actually implement these rules. Here's the breakdown you can use — practical, specific, and tied to real consequences.

HIPAA Isn't One Rule — It's Five Titles

Most people think of HIPAA as a privacy law. It's not. The Health Insurance Portability and Accountability Act of 1996 contains five distinct titles. Each one addresses a different slice of the healthcare system.

Only two of those titles — Title I and Title II — get regular attention. But ignoring the others can leave gaps in your understanding that matter during audits, litigation, or workforce training.

Let me walk you through each one.

Title I: Health Insurance Portability

This is the part most people forget exists, even though it's right there in the name. Title I protects workers and their families when they change or lose jobs. It limits the ability of group health plans to deny coverage based on pre-existing conditions.

If you work in benefits administration or HR, this title directly affects your enrollment processes and plan documentation. It also prohibits discrimination against employees based on health status.

Why Title I Still Matters in 2026

With the continued growth of contract and gig-economy healthcare workers, portability protections are more relevant than ever. Your organization's benefits team needs to understand these provisions — or risk compliance gaps that surface during Department of Labor reviews.

Title II: The One That Keeps Compliance Officers Up at Night

Title II is where the Privacy Rule, the Security Rule, the Enforcement Rule, and the Breach Notification Rule live. When most people ask about the parts of HIPAA, this is what they actually mean.

Title II established "Administrative Simplification" provisions. HHS was directed to create national standards for electronic healthcare transactions and to protect the confidentiality of protected health information — PHI.

The Privacy Rule

The Privacy Rule sets the boundaries for how covered entities use and disclose PHI. It gives patients rights: the right to access their records, request corrections, and receive an accounting of disclosures.

I've seen organizations get tripped up on the "minimum necessary" standard. You can't give an entire medical record to a billing clerk who only needs a procedure code. This rule demands that your workforce accesses only the PHI they need for their specific role.

The Security Rule

The Security Rule applies specifically to electronic PHI — ePHI. It requires three categories of safeguards: administrative, physical, and technical. Think risk assessments, access controls, encryption, and audit logs.

The HHS Security Rule page outlines these requirements in detail. If your organization hasn't completed a thorough risk analysis recently, you're already behind. OCR has made it abundantly clear — in case after case — that the absence of a risk analysis is the single most common finding in enforcement actions.

The Enforcement Rule

This part of Title II gives OCR the authority to investigate complaints, conduct audits, and impose civil monetary penalties. The penalty tiers range from $137 per violation (for unknowing violations) up to roughly $2.1 million per violation category per year.

Criminal penalties also exist under this rule. The Department of Justice can prosecute individuals who knowingly obtain or disclose PHI. Penalties can include up to 10 years in prison for violations committed with intent to sell or use PHI for personal gain.

The Breach Notification Rule

Added through the HITECH Act in 2009 and folded into HIPAA's framework, the Breach Notification Rule requires covered entities to notify affected individuals, HHS, and — for breaches affecting 500 or more people — the media. You have 60 days from discovery. No exceptions.

The OCR's Breach Portal — often called the "Wall of Shame" — lists every large breach publicly. If your organization lands there, the reputational damage often exceeds the financial penalty.

What Are the Five Parts of HIPAA?

Here's a concise answer for quick reference:

  • Title I: Health Insurance Reform — protects coverage when workers change or lose jobs.
  • Title II: Administrative Simplification — contains the Privacy Rule, Security Rule, Enforcement Rule, Breach Notification Rule, and Transaction Standards.
  • Title III: Tax-Related Health Provisions — sets rules for medical spending accounts and related tax benefits.
  • Title IV: Application and Enforcement of Group Health Plan Requirements — further defines coverage for pre-existing conditions and continuation of coverage.
  • Title V: Revenue Offsets — covers company-owned life insurance and treatment of individuals who lose U.S. citizenship for tax purposes.

Titles III, IV, and V rarely surface in compliance training, but they're part of the statute. When someone asks about the parts of HIPAA, knowing all five signals competence.

The Rules That Actually Drive Day-to-Day Compliance

In my experience, four rules under Title II determine whether your organization passes or fails an OCR audit. Every member of your workforce — not just your compliance officer — should know them.

Administrative Safeguards Are the Foundation

Risk analysis. Workforce training. Sanctions policies for employees who violate the rules. Contingency planning. These administrative safeguards make up the bulk of the Security Rule's requirements. They're also where I see the most failures.

A comprehensive HIPAA Introduction Training for 2026 should cover each of these safeguards and explain how they connect to real scenarios your staff will encounter.

Physical and Technical Safeguards Close the Loop

Physical safeguards cover facility access, workstation security, and device disposal. Technical safeguards address access controls, audit controls, integrity controls, and transmission security.

If your nurses are accessing ePHI on shared workstations without unique logins, you have a technical safeguard failure. If those workstations sit in an unlocked hallway, you have a physical safeguard failure too. Our HIPAA Training for Nurses addresses exactly these clinical workflow risks.

Business Associate Agreements: The Part Everyone Underestimates

The HITECH Act extended HIPAA's reach to business associates — vendors, contractors, and subcontractors who handle PHI on behalf of a covered entity. If your cloud storage provider, billing company, or IT managed services firm touches PHI, they must sign a Business Associate Agreement.

I've reviewed BAAs that were signed a decade ago and never updated. That's a compliance gap. Your BAAs should reflect current regulatory requirements, specify breach notification timelines, and define permitted uses of PHI with precision.

The $5.55 Million Mistake: Real Enforcement in Action

In 2017, Memorial Healthcare System paid $5.5 million to settle HIPAA violations involving unauthorized access to ePHI by employees and affiliated physician office staff. OCR found that the organization failed to implement proper audit controls and access management — core parts of HIPAA's Security Rule.

That case illustrates how interconnected the parts of HIPAA really are. A workforce training failure becomes a Security Rule violation, which triggers the Breach Notification Rule, which lands on the Enforcement Rule's penalty schedule.

How to Build Compliance Across All Parts of HIPAA

Here's my practical framework after years of consulting:

  • Start with a current risk analysis. Document every system that stores, transmits, or processes ePHI. Identify threats and vulnerabilities. Assign risk levels.
  • Train every workforce member. Not once. Annually. Role-based training is critical — front desk staff face different risks than IT administrators.
  • Review and update your policies. Policies written in 2015 don't account for telehealth, cloud computing, or modern phishing attacks.
  • Audit your BAAs. Confirm every vendor relationship is documented and agreements are current.
  • Test your breach response plan. Run a tabletop exercise. Time your notification process. Fix the gaps before OCR finds them.

You can explore the full range of training options at HIPAACertify's course catalog to find role-specific programs that match your organization's needs.

Stop Treating HIPAA Like a Checkbox

The organizations that end up on the Wall of Shame aren't usually negligent. They just treated HIPAA like a one-time project instead of an ongoing operational discipline. Every part of HIPAA — from Title I's portability protections to Title II's enforcement mechanisms — exists because Congress recognized that healthcare data is uniquely sensitive.

Your staff doesn't need to memorize statutory language. But they do need to understand how these parts connect to the work they do every day — admitting patients, sending claims, configuring firewalls, shredding documents.

That understanding is the difference between a compliant organization and a cautionary tale.