Few terms in healthcare get thrown around as loosely as “HIPAA violation.” It gets invoked when a nurse mentions a patient’s diagnosis to a friend outside of work, when a technician talks about a well-known patient who came through the clinic, or when a physician casually brings up a person’s rare diagnosos at a backyard barbecue — situations that sound like violations but often have nothing to do with the actual law. That confusion isn’t just an oversight, but rather, it points to a gap in understanding what HIPAA covers, who it applies to, and what genuinely puts an organization at risk.

For health care providers, compliance officers and IT professionals, the stakes behind that confusion are anything but casual. The Department of Health and Human Services (HHS) Office for Civil Rights (OCR) has issued settlements ranging from a few thousand dollars to over $16 million for the same underlying failures, such as a missed risk assessment, an unencrypted laptop, a chart accessed by the wrong person. This guide breaks down what actually constitutes a HIPAA violation, the most common ways organizations end up on OCR’s radar, what genuinely falls outside HIPAA’s scope, and what to do if you’re managing risk or responding to an incident right now.

If your organization handles PHI over email — one of the highest-risk channels for exactly this kind of violation — our HIPAA Compliant Email guide is a useful next read once you’ve worked through this one.

What Is a HIPAA Violation?

A HIPAA violation occurs when a covered entity, business associate, or a member of either’s workforce fails to comply with a standard set out in the HIPAA Privacy Rule, Security Rule, or Breach Notification Rule — or fails to follow an internal policy implemented to support HIPAA compliance.

That definition matters because it draws a hard boundary around who can actually commit one. HIPAA applies to:

• Covered entities — healthcare providers, health plans, healthcare suppliers, payers, and healthcare clearinghouses
• Business associates — vendors and contractors that create, receive, maintain, or transmit protected health information (PHI) on a covered entity’s behalf
• Workforce members — employees, volunteers, and contractors of either of the above

HIPAA does not apply to private individuals acting outside of a covered role — a distinction that trips up far more people than you’d expect, and one we’ll come back to later in this guide.

The Health Insurance Portability and Accountability Act (HIPAA) was designed to protect the confidentiality of medical records and patient data while still allowing healthcare organizations to function and share information when appropriate. A violation happens when that balance breaks down — when PHI is accessed, used, or disclosed in a way the law doesn’t permit, or when required safeguards simply aren’t in place.

The Three HIPAA Rules a Violation Can Break

Every HIPAA violation traces back to one (or more) of three core rules. Understanding which rule is in play helps clarify what actually went wrong — and what needs to be fixed.

Most real-world violations involve more than one rule at once, such as a stolen, unencrypted laptop is a Security Rule failure that can also trigger Breach Notification Rule obligations. Keeping the three rules distinct in your own documentation, though, makes it much easier to identify exactly where a gap exists.

Most Common Types of HIPAA Violations

These are the violation categories that show up most often in OCR settlements, and the ones every provider, payer, and supplier organization should actively guard against.

Unauthorized Access / Snooping

This is the violation most people have actually heard about, usually because of a celebrity or high-profile patient case that made headlines. A staff member accesses a patient’s medical record without a legitimate, job-related reason — often out of curiosity, not malice — and it still counts as a serious violation.

What’s easy to miss here: the violation is about the access itself, not just what happens to the information afterward. Looking at a chart you have no clinical reason to view is a violation the moment it happens, even if you never repeat, share, or act on what you saw. Hospitals take this seriously enough to flag high-profile patient charts automatically and audit access in real time — which is exactly why staff who snoop tend to get caught quickly, and why termination is the near-universal outcome when they do.

A useful way to think about it: the sensitivity of the underlying information isn’t what determines whether accessing it was a violation — the authorization to access it through that specific system is and if a job role requires it. Pulling PHI through a restricted system without a legitimate reason is a violation even in cases where the same information might, in theory, be available through some other, non-restricted channel. Improper access through the wrong door is still improper access.

Example: Dr. Huping Zhou was sentenced to four months in federal prison after accessing celebrity medical records 323 times with no legitimate reason. UCLA Health System was separately fined $865,000 related to similar unauthorized access incidents.

Failure to Conduct a Risk Analysis

The Security Rule requires covered entities and business associates to conduct an organization-wide risk analysis identifying vulnerabilities to the confidentiality, integrity, and availability of ePHI. Skipping this step — or doing a superficial version of it — is one of the single most commonly cited failures in OCR settlements, because it’s foundational: nearly every other safeguard depends on knowing where your actual risks are.

Example: Premera Blue Cross paid $6,850,000, and Excellus Health Plan paid $5,100,000, both tied in part to failures to conduct adequate risk analyses before major breaches occurred.

Insufficient Access Controls

Access controls determine who can view or modify ePHI, and they need to be granular enough that staff can only access the minimum information necessary for their role. When access controls are too loose, such as shared logins, no role-based restrictions, no automatic logoff, organizations lose the ability to actually enforce the “minimum necessary” standard HIPAA requires.

Example: Anthem Inc. paid $16,000,000, the largest HIPAA settlement to date, following a breach connected in part to access control failures affecting nearly 79 million individuals.

Failure to Encrypt ePHI on Portable Devices

Laptops, phones, and USB drives leave the building. When they’re lost or stolen without encryption, an isolated incident becomes a reportable breach — because unencrypted PHI on a missing device is, by definition, unsecured PHI.

Example: Children’s Medical Center of Dallas paid $3.2 million after multiple incidents involving lost, unencrypted mobile devices containing ePHI.

Missing or Incomplete Business Associate Agreements

Any vendor that creates, receives, maintains, or transmits PHI on a covered entity’s behalf — from a billing company to an email provider — is a business associate under HIPAA, and business associates are legally required to sign a Business Associate Agreement (BAA) before handling that data. Skipping this step, or using a vendor without one, is a violation regardless of whether anything actually goes wrong with the data itself.

Example: North Memorial Health Care of Minnesota paid $1.55 million after failing to enter into a BAA with a business associate that later experienced a breach.

Impermissible Disclosures of PHI

This category covers PHI shared with someone who wasn’t authorized to receive it — a press release naming a patient, a social media post, filming patients without consent, or telling family or coworkers more than they’re entitled to know.

Example: New York Presbyterian Hospital paid $2,200,000 after filming patients for a documentary without proper consent.

Improper Disposal of PHI

Paper records tossed in regular trash instead of being shredded, or old hard drives discarded without being wiped, both count as impermissible disclosures — PHI doesn’t stop being protected just because someone’s done using it.

Example: Parkview Health paid $800,000 after leaving patient medical records unattended in a driveway during a records transfer.

Exceeding Breach Notification Deadlines

Once a breach of unsecured PHI is discovered, the Breach Notification Rule sets a hard 60-day deadline to notify affected individuals (and HHS, for breaches involving 500+ records). Missing that window turns a bad situation into a compounding one.

Example: Presence Health paid $475,000 for failing to notify affected individuals within the required timeframe following a breach.

Denying Patient Access to Records

Patients have a right to access their own medical records, generally within 30 days of a request, without excessive fees or unreasonable barriers. Denying or delaying that access is one of the more consistently enforced violation categories in recent years.

Example: Cignet Health of Prince George’s County paid $4,300,000 for denying 41 patients access to their own medical records.

Every one of these categories comes back to the same underlying question: does your organization actually have documented, enforced processes for who can touch PHI, how it’s protected, and what happens when something goes wrong? If email is part of that picture — and for nearly every healthcare organization, it is — our HIPAA Compliance Checklist walks through exactly what needs to be in place.

What Is Not a HIPAA Violation (Common Misconceptions)

HIPAA gets invoked constantly in situations it has nothing to do with — and clearing up that confusion matters, because it helps healthcare professionals, IT and compliance teams focus their actual attention where it belongs.

A family member discussing your health isn’t a HIPAA violation. HIPAA governs covered entities, business associates, and their workforces — not private individuals speaking in a personal capacity. Your mother telling a relative about your diagnosis might be a breach of your trust, but it’s not a HIPAA violation, because she isn’t bound by HIPAA in the first place.

Confusing HIPAA with FERPA or the ADA is common, and usually incorrect. Educational records fall under FERPA (the Family Educational Rights and Privacy Act), not HIPAA — a teacher discussing a student’s grades or attendance isn’t a HIPAA issue. Similarly, questions about a disability accommodation, like a mask exemption or a service animal, generally fall under the Americans with Disabilities Act (ADA), not HIPAA.

Asking about someone’s health isn’t the same as disclosing it. HIPAA restricts what covered entities and their workforces can disclose, it doesn’t restrict what any individual, including a coworker, cashier, or stranger, can ask. Someone asking why you’re wearing a mask or requesting proof of a medical condition might be inappropriate or even illegal under a different law, but it isn’t itself a HIPAA violation.

Vague references aren’t the same as identifiable disclosures. HIPAA violations require that protected health information (PHI) be tied to an identifiable individual. Referring to “a patient” or “a young adult male” in casual conversation is too vague to trigger a violation. Naming a specific person — “my patient, Mike, who lives on Oak Street” — alongside health information crosses that line.

A simple way to keep the distinction clear:

• A nurse telling friends a specific patient’s name, date of birth, and diagnosis → HIPAA violation.
• A pharmacist telling a customer their prescription refill is delayed → not a HIPAA violation.

The line isn’t about whether something feels private. It’s about whether protected health information tied to an identifiable person was disclosed by someone bound by HIPAA in the first place.

HIPAA Violation Penalties: The 4-Tier Structure

OCR calculates civil penalties based on the violator’s level of culpability, not just the severity of the incident. Understanding which tier applies matters, because the same underlying mistake can result in wildly different consequences depending on whether it was a one-off oversight or a known, ignored risk.

Penalty amounts are periodically adjusted for inflation, and current maximum penalties can exceed $2 million annually per violation category — figures worth confirming against HHS’s current published rates before citing specific numbers internally.

Criminal penalties sit outside this civil tier structure entirely. Knowing or willful violations can result in criminal fines ranging from $50,000 to $250,000, plus up to 10 years in prison for the most serious offenses — typically reserved for cases involving intent to sell, transfer, or use PHI for personal gain or malicious harm.

How Are HIPAA Violations Discovered?

Violations don’t usually surface because someone confesses. They’re found through a handful of consistent channels:

• Audit logs and automated access-flagging. Most modern EHR systems automatically flag unusual access patterns — a chart accessed by someone outside the care team, or a spike in access to a high-profile patient’s record. This is precisely how most unauthorized-access violations come to light; systems are built to catch exactly this pattern.
• Patient complaints. Patients can, and do, file complaints directly with HHS when they believe their information was mishandled.
• Breach self-reporting. Covered entities and business associates are required to self-report breaches meeting certain thresholds.
• OCR compliance audits. HHS periodically conducts proactive audits of covered entities and business associates, independent of any specific complaint or breach.

One nuance worth understanding: not every violation escalates the same way. A single, isolated mistake, such as an email sent to the wrong recipient or a chart accidentally opened, is often handled through internal correction and documentation. A repeated pattern of the same behavior is a different story entirely, and is far more likely to become something an organization is required to report to HHS. This is one of the most important distinctions for healthcare organizations and compliance teams to build into internal escalation policies: document every incident, but treat repetition as a signal that internal correction alone is no longer sufficient.

How to Report a HIPAA Violation

If you’re a patient, employee, or compliance officer who has identified a potential violation, there are two established paths ti report a violation, and they aren’t mutually exclusive.

Step 1: Report it to the employer or covered entity directly. Most healthcare organizations have an internal compliance officer or reporting process specifically for this purpose. Internal reporting is often the fastest way to get a genuine mistake corrected before it escalates.

Step 2: File a complaint with HHS’s Office for Civil Rights. If internal reporting isn’t appropriate, isn’t effective, or the violation is serious enough to warrant it, complaints can be filed directly through HHS’s official complaint portal. Complaints generally must be filed within 180 days of when the violation was discovered, though extensions are sometimes granted for good cause.

A few practical notes:

• Anonymous reporting is possible, but limited. OCR accepts anonymous complaints, but the lack of contact information can restrict how thoroughly they’re able to investigate.
• Retaliation against someone who reports in good faith is itself prohibited under HIPAA.
• Not every complaint results in a formal investigation — OCR reviews each complaint to determine whether it falls within HIPAA’s scope before proceeding.

How to Avoid HIPAA Violations & Fines

For Organizations

• Conduct — and document — a genuine risk assessment. This isn’t a one-time checkbox; risk assessments should be revisited whenever systems, vendors, or workflows change.
• Sign a BAA with every vendor that touches PHI, including email, billing, and IT service providers — no exceptions.
• Implement role-based access controls so staff can only access the minimum PHI necessary for their specific role.
• Encrypt ePHI in transit and at rest, especially on portable devices and email, where enforced encryption remains one of the most consistently under-implemented safeguards.
• Train staff regularly, not just at onboarding. A single training session at hire rarely holds up against years of evolving risk.

For Individual Staff Members

• Only access patient records tied to a legitimate, job-related reason — never out of curiosity, even for patients you know personally.
• Never discuss identifiable patient information outside of your care team, including with family, friends, or on social media.
• Report suspected violations, including your own mistakes, immediately rather than waiting to see if anyone notices.
• Treat every device and email containing PHI as if it could be lost, stolen, or misdirected tomorrow, because eventually, statistically, one will be.

Since email remains one of the highest-volume channels for exactly this kind of accidental exposure, secure, HIPPA compliant solutions, such as LuxSci’s SecureLine encryption technology, are built specifically to remove the guesswork — enforcing encryption automatically rather than relying on staff to remember to apply it correctly every time.

HIPAA vs. State Privacy Laws

HIPAA sets a federal floor, not a ceiling. States are free to enact privacy laws that are stricter than HIPAA, and when they do, the stricter standard generally governs. This matters for multi-state healthcare organizations especially, such as a provider, payer, or supplier operating across state lines may need to comply with HIPAA everywhere, plus additional, more stringent requirements in specific states.

This guide focuses on federal HIPAA requirements, but compliance officers should treat HIPAA as the baseline, not the finish line, when evaluating their organization’s full regulatory exposure.

What Should I Do Now?

Understanding what counts as a HIPAA violation is the first step. Actually closing the gaps that lead to one is the harder, ongoing work — and email is one of the most common places that work quietly falls through the cracks.

Here are three ways to keep moving forward:

1. Read our HIPAA Compliant Email guide to understand exactly what makes an email platform compliant — and where standard email tools like Gmail and Microsoft 365 fall short.
2. Work through our HIPAA Compliance Checklist to audit your organization’s current safeguards against what HIPAA actually requires.
3. Explore LuxSci’s SecureLine encryption technology to see how enforced encryption and a signed BAA work together to close the exact gaps that show up most often in OCR settlements.
4. Read our Definitive Guide on the New HIPAA Security Rule, making email encryption mandatory in 2027

Frequently Asked Questions

1. What are the most common HIPAA violations?

The most common violations include unauthorized access to patient records, failure to conduct a risk analysis, insufficient access controls, failure to encrypt ePHI on portable devices, missing Business Associate Agreements, impermissible disclosures of PHI, improper disposal of records, and exceeding breach notification deadlines.

2. What’s the difference between a HIPAA violation and a FERPA or ADA issue?

HIPAA governs protected health information handled by covered entities and business associates in healthcare settings. FERPA governs education records, and the ADA governs disability discrimination and accommodation. A teacher discussing grades falls under FERPA, not HIPAA. A question about a disability accommodation typically falls under the ADA, not HIPAA.

3. How do I report a HIPAA violation?

Report it directly to the employer or covered entity first, if appropriate. If that isn’t effective or the violation is serious, file a complaint with HHS’s Office for Civil Rights within 180 days of discovering the violation, using the official HHS complaint portal.

4. Can I sue someone for violating HIPAA?

No. HIPAA does not provide a private right of action, meaning individuals cannot sue directly under HIPAA. Patients can file a complaint with HHS/OCR, and in some cases may have separate legal remedies under state privacy or negligence laws.

5. Is looking up a patient’s chart without a work reason a HIPAA violation, even if I don’t share the information?

Yes. Accessing a patient’s record without a legitimate, job-related reason is a violation the moment it happens — it doesn’t require sharing, saving, or acting on the information afterward. This is one of the most consistently enforced categories, particularly for high-profile or celebrity patients whose charts are routinely audited.