A hospital HR manager pulls up a coworker's medical record after hearing a rumor about a pregnancy. A dental office supervisor mentions an employee's psychiatric medication during a staff meeting. A clinic director emails a worker's HIV status to a department head who has no business knowing it.

These aren't hypothetical scenarios. They're real examples of HIPAA violations by employers that I've encountered during audits and breach investigations over the years — and every single one of them resulted in consequences ranging from terminations to six-figure settlements.

If you manage employees at a covered entity or business associate, this post is your wake-up call. Let's walk through the most common ways employers violate HIPAA, what the Office for Civil Rights (OCR) actually does about it, and how to keep your organization off the enforcement list.

First, a Critical Distinction Most Employers Get Wrong

Here's where confusion starts: HIPAA doesn't regulate all employers. It regulates covered entities — health plans, healthcare clearinghouses, and healthcare providers who transmit health information electronically — and their business associates.

If you run a law firm or a retail store, HIPAA probably doesn't apply to your handling of employee health data. But if you run a hospital, a health plan, or a medical practice, you're a covered entity. And your workforce — every single person, from the CEO to the receptionist — is subject to HIPAA's Privacy and Security Rules when handling protected health information (PHI).

The violations I'm about to describe happen when people inside covered entities misuse their access to PHI. And it happens far more than you'd think.

Snooping on Employee Medical Records: The Violation That Never Dies

In my experience, the single most common employer-related HIPAA violation is unauthorized access to medical records. Someone with system access looks up a coworker's chart out of curiosity, concern, or malice.

This isn't a gray area. If it's not your job to access that record for treatment, payment, or healthcare operations, it's a breach. Period.

The UCLA Health System Case: $865,500

UCLA Health System paid $865,500 to settle allegations that employees repeatedly accessed celebrity patients' ePHI without authorization. The investigation by HHS found that UCLA failed to implement adequate safeguards — including proper access controls and audit trails — to prevent workforce members from snooping. You can review the resolution agreement on the HHS enforcement page.

Now imagine the same behavior applied to employees' records. A supervisor checks whether a subordinate visited the behavioral health clinic. An HR coordinator pulls up a colleague's prescription history. The mechanism is identical, and the penalty exposure is the same.

If you want your staff to understand exactly where this line is, our course Accessing Records: If It's Not Your Job, It's a Breach walks through real scenarios in under 30 minutes.

Supervisors Disclosing Employee Health Information

This one is alarmingly common. A manager learns that an employee was hospitalized — maybe through legitimate operational channels — and then shares that information with other staff members who don't need to know.

I worked with a mid-size clinic where a nursing supervisor told three other nurses that a coworker had been admitted for substance abuse treatment. She thought she was being compassionate, giving them context for the absence. OCR doesn't care about intentions. Unauthorized disclosure of PHI is unauthorized disclosure of PHI.

When "Need to Know" Gets Ignored

HIPAA's minimum necessary standard requires covered entities to limit PHI disclosures to the minimum amount necessary to accomplish the intended purpose. When a supervisor broadcasts an employee's diagnosis to the department, they've obliterated that standard.

The fix is straightforward but requires constant reinforcement: managers at covered entities must understand that employee health information accessed through the organization's health systems is PHI. It doesn't become "HR information" just because the person happens to work there.

Social Media: Where Careers Go to End

I've seen HIPAA violations on social media that made my jaw drop. A medical assistant posts a vague but identifiable reference to a coworker's ER visit. A nurse tweets about a colleague's positive drug test. A front-desk worker shares a photo from the break room — with a patient schedule visible on the whiteboard behind them.

Every one of these is a potential HIPAA violation when PHI is involved. And social media posts create permanent evidence that OCR investigators love to screenshot.

If your workforce uses social media — and they do — make sure they've completed training like our Social Media & PHI course, which covers exactly what can and can't be shared online.

Retaliation Against Employees Who File HIPAA Complaints

Here's one that employers rarely see coming. Under 45 CFR § 160.316, covered entities cannot retaliate against any individual who files a HIPAA complaint, participates in an investigation, or opposes an act they reasonably believe violates HIPAA.

I've consulted with organizations where a manager fired or demoted an employee shortly after that employee reported a privacy concern. Even if the termination was unrelated, the timing creates a presumption of retaliation that OCR takes seriously.

What Retaliation Looks Like in Practice

  • Reducing an employee's hours after they report a coworker for snooping in records
  • Transferring an employee to a less desirable role after they file a complaint with HHS
  • Issuing a negative performance review shortly after an employee raises a privacy concern internally

Document everything. If you're disciplining an employee who recently filed a complaint, make sure the action is clearly tied to performance issues that predate the complaint — and that your documentation proves it.

Failing to Respond When Employees Cause Breaches

Sometimes the violation isn't the initial incident. It's the failure to respond.

Under the Breach Notification Rule, covered entities must notify affected individuals, HHS, and in some cases the media when a breach of unsecured PHI occurs. When an employee causes that breach — by snooping, by losing a laptop, by emailing PHI to the wrong person — and the organization fails to investigate and report it, the employer compounds the original violation with a notification failure.

The $4.3 Million Lesson from MD Anderson

The University of Texas MD Anderson Cancer Center was hit with a $4.3 million penalty after multiple breaches involving unencrypted devices. While this case centered on device security rather than employer-employee dynamics specifically, it illustrates a critical point: OCR doesn't just penalize the breach itself. They penalize the failure to have policies and safeguards in place before the breach happened. You can review the details on the HHS enforcement actions page.

Your incident response plan needs to be tested and ready before something goes wrong. Our First 60 Minutes: Incident Response training gives your team a step-by-step framework for those critical early decisions.

What Exactly Counts as a HIPAA Violation by an Employer?

To capture it concisely: a HIPAA violation by an employer occurs when a covered entity or business associate — acting through its workforce members, including managers, HR staff, and executives — uses or discloses PHI in ways that violate the Privacy Rule, fails to safeguard ePHI under the Security Rule, or retaliates against individuals who exercise their HIPAA rights. Common examples include accessing employee medical records without authorization, sharing employee diagnoses with colleagues who have no treatment or operational need, posting identifiable health information on social media, and failing to report and respond to breaches caused by workforce members.

The Training Gap That Makes All of This Worse

Here's what ties every one of these examples together: lack of training. Not the "check a box once a year" kind. Real, scenario-based training that makes people think before they act.

HIPAA requires covered entities to train all workforce members on policies and procedures related to PHI. But most organizations treat this as a compliance checkbox rather than a behavior-change tool. They run a generic PowerPoint once a year and wonder why employees keep snooping, sharing, and posting.

What Effective Workforce Training Actually Looks Like

  • Short, scenario-based modules that mirror real workplace situations
  • Role-specific content — what a supervisor needs to know differs from what a billing clerk needs
  • Documented completion records that prove compliance during an OCR investigation
  • Refresher training when policies change or after an incident occurs

Browse our full HIPAA training catalog to find courses built around the exact scenarios described in this post.

Protect Your Organization Before OCR Comes Knocking

Every example of HIPAA violations by employers I've shared here has a common thread: someone inside the organization either didn't know the rules or chose to ignore them, and leadership didn't have the safeguards in place to prevent or detect it.

You can't eliminate human error. But you can build systems that catch it early, train people who understand the stakes, and create a culture where PHI is treated with the gravity it deserves.

Start with your biggest risk areas — unauthorized access, supervisor disclosures, social media, and incident response. Get your workforce trained on the specific scenarios that lead to enforcement actions. And make sure your policies aren't just written but actually followed.

Because in my experience, the organizations that end up on OCR's enforcement page aren't the ones that had bad luck. They're the ones that had bad habits — and never fixed them.