DataBreaches.Net

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

Reminder that small-n medical privacy breaches can cause harm

Posted on November 26, 2022 by Dissent

Over on PogoWasRight.org this morning, I linked to a post by Eric Goldman involving litigation over a medical privacy breach.  One plaintiff claimed to have suffered significant harm in her life due to a hospital employee mailing her information to an unrelated third party who then posted it online.

I mention that case because although many sites (including this one) tend to report dramatic headlines about data breaches in the medical sector where, the larger the number affected, the louder the headline. The reality, though, is that breaches involving a single individual or a few patients often cause great harm. These N=1 or small-number breaches do not appear on HHS’s public breach tool, although they do get reported to HHS.

Sometimes, we learn about these small incidents because local news media reports on them or bloggers like Eric Goldman inform us about them. And sometimes, we find out because they appear on state attorney general breach sites.

Today, DataBreaches read a breach notification letter to one patient.

In this case, Mattapan Community Health Center in Massachusetts informed a patient about their investigation into the patient’s complaint that a former employee had inappropriately accessed their protected health information and posted it online. The letter offers no information on the former employee’s motivation to access this patient’s protected health information or post it.

MCHC’s investigation confirmed the patient’s report. The letter informed the patient about what steps they were taking in response:

To address the situation with the former employee, the Health will be sending her a cease and desist letter ordering her to, among other things, permanently delete the posts with your PHI and PI, destroy or return any Health Center PHI and PI related to you or others that are in her possession, and refrain from any communication of any sort that discloses protected information about you by any means, including but not limited to personal contact, mail, electronic mail, instant message, text message, telephone communications, via web or telephone-based applications, or any type of social media.

Does that seem like enough?

Additionally, we continue to educate and reinforce to the Health Center staff about the importance of privacy and their duty to maintain privacy even after they have left our employment to reduce the risk of this type of incident from occurring again. We are also offering you credit monitoring and identity protection services through the service of your choice at no cost to you for 24 months.

Does that seem like enough?

Would you expect to see more about the fact that the health center had neither prevented nor detected inappropriate access when it occurred in July and only learned of the breach when the patient contacted them to complain in October?  What will the health center do to improve their ability to prevent and quickly detect such breaches?

You can read the notification letter found at https://www.mass.gov/doc/assigned-data-breach-number-28607-mattapan-community-health-center/download below.

28607

Related:

  • KT Chief to Resign After Cybersecurity Breach Resolution
  • Cyber-Attack On Bectu’s Parent Union Sparks UK National Security Concerns
  • Attorney General James Announces Settlement with Wojeski & Company Accounting Firm
  • JFL Lost Up to $800,000 Weekly After Cyberattack, CEO Says No Patient or Staff Data Was Compromised
  • A business's cyber insurance policy included ransom coverage, but when they needed it, the insurer refused to pay. Why?
  • Before Their Telegram Channel Was Banned Again, ScatteredLAPSUS$Hunters Dropped Files Doxing Government Employees (2)
Category: Breach IncidentsHealth DataInsiderU.S.

Post navigation

← Southampton County, Virginia reports ransomware incident (updated)
Iran blames Israel for Fars News Agency hack →

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

  • District of Massachusetts Allows Higher-Ed Student Data Breach Claims to Survive
  • End of the game for cybercrime infrastructure: 1025 servers taken down
  • 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

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

  • As shoplifting surges, British retailers roll out ‘invasive’ facial recognition tools
  • 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

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.