DataBreaches.Net

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

“Small” breach, big impact, redux

Posted on August 29, 2015 by Dissent

In November 2013, I blogged about the case of a privacy breach at Northern Inyo Hospital that was so devastating to the patient that she was going to move away. The breach was a willful insider breach that impacted a custody dispute.

That same year, and unbeknownst to most people, there was a lawsuit filed over another insider breach that similarly devastated the patient involved. This one involved the Ronald Reagan UCLA Medical Center and an employee of OB/GYN Dr. John Edwards accessing the system’s database and then disseminating sensitive information about an employee-patient, Norma Lozano. Dr. Edwards is affiliated with UCLA, but Ms Lozano was not his patient and there was no reason for anyone in his office to access her records. According to media reports, an unnamed temporary employee of Dr. Edwards, allegedly accessed Lozano’s medical records in September 2012, made copies with her cell phone and sent them to Lozano’s former boyfriend — the father of Lozano’s then unborn child — and another person.

Lozano sued UCLA, and her case made it to court this past week. You can read a recap of the case on Patch, MyNewsLA.

It is not clear to me whether this incident was ever reported to the California Department of Public Health and of so, what action the CDPH took in response. What is disturbing is that in its defense, UCLA claims the responsibility lies with Dr. Edwards for providing his password to his temporary employee.

But does it? While I agree that Dr. Edwards had an obligation to train his employees and establish access controls and monitor his employees’ conduct, shouldn’t the hospital, recognizing the risk of snooping and inappropriate access, have done more to prevent such situations? Should only celebrities have higher levels of data protection? I don’t think so.

It is not clear to me why Dr. Edwards was dropped from the case as a defendant, and why the unnamed employee was not also sued, but I hope everyone takes note that a major hospital system seems to be saying that it’s not their responsibility to protect you from improper access to your records from employees of its affiliated doctors.

Think about whether that is a satisfactory situation.

 

 


Related:

  • US company with access to biggest telecom firms uncovers breach by nation-state hackers
  • The 4TB time bomb: when EY's cloud went public (and what it taught us)
  • Some lower-tier ransomware gangs have formed a new RaaS alliance -- or have they? (1)
  • 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
  • Uncovering Qilin attack methods exposed through multiple cases
Category: Breach IncidentsCommentaries and AnalysesHealth DataU.S.

Post navigation

← More reaction to the Third Circuit opinion in FTC v. Wyndham
Boston University notifies medical research participants after server compromise →

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

  • Suspected Russian hacker reportedly detained in Thailand, faces possible US extradition
  • Did you hear the one about the ransom victim who made a ransom installment payment after they were told that it wouldn’t be accepted?
  • 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

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

  • Lawmakers Warn Governors About Sharing Drivers’ Data with Federal Government
  • 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

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.