DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

Fairmont Medical Center fires 6 employees for snooping

Posted on September 30, 2010 by Dissent

A few weeks ago, the Mayo Clinic fired an employee who had been snooping in patient records for years.   Now Meg Alexander reports that Fairmont Medical Center – Mayo Health has fired six employees for breaching patient confidentiality:

Six employees have been fired by Fairmont Medical Center because of a breach in patient confidentiality, according to a written statement from the health care organization.

Mayo Health System recently was notified that some of its employees may have inappropriately accessed the personal health information of one patient.

“An employee alerted leadership, and that employee … did the right thing,” said Jason Howland, communications coordinator.

An internal review was immediately launched, and it was determined six employees, those who have been fired, had violated policy protecting confidential personal health information, the statement said.

Read more in the Fairmont Sentinel.  It seems that all six had inappropriately accessed the same patient’s records, but the reason for their curiosity was not revealed.


Related:

  • Pro-Russian hackers target Belgian telecom websites in DDoS attack
  • Veradigm's Breach Claims Under Scrutiny After Dark Web Leak
  • UK: Woman charged after NHS patients' records accessed in data breach
  • Landmark civil penalty of AU$5.8 million issued under Australia’s Privacy Act
  • Safaricom-Backed M-TIBA Victim of a Possible Data Breach Affecting Millions of Kenyans
  • Another plastic surgery practice fell prey to a cyberattack that acquired patient photos and info
Category: Health Data

Post navigation

← UK: Health records loss 'breached data protection rules
Canada’s pursuit of tax cheats starts with stolen data →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • Doctor Alliance Data Breach: 353GB of Patient Files Allegedly Compromised, Ransom Demanded
  • St. Thomas Brushed Off Red Flags Before Dark-Web Data Dump Rocks Houston
  • A Wiltshire police breach posed possible safety concerns for violent crime victims as well as prison officers
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Almost two years later, Alpha Omega Winery notifies those affected by a data breach.
  • Court of Appeal reaffirms MFSA liability in data leak case, orders regulator to shoulder costs
  • A jailed hacking kingpin reveals all about the gang that left a trail of destruction
  • Army gynecologist took secret videos of patients during intimate exams, lawsuit says
  • The Case for Making EdTech Companies Liable Under FERPA
  • NHS providers reviewing stolen Synnovis data published by cyber criminals

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • Data broker Kochava agrees to change business practices to settle lawsuit
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Changes in the Rules for Disclosure for Substance Use Disorder Treatment Records: 42 CFR Part 2: What Changed, Why It Matters, and How It Aligns with HIPAAs
  • Always watching: How ICE’s plan to monitor social media 24/7 threatens privacy and civic participation
  • Who’s watching the watchers? This Mozilla fellow, and her Surveillance Watch map

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net
Security Issue: security[at]databreaches.net
Mastodon: Infosec.Exchange/@PogoWasRight
Signal: +1 516-776-7756
DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.