DataBreaches.Net

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

U. of Cincinnati Medical Center not liable for employee’s Facebook post on a patient’s STD (updated)

Posted on November 10, 2015 by Dissent

Kevin Grasha has an update on a breach previously noted on this site.

University of Cincinnati Medical Center can’t be sued after an employee leaked private medical records about a patient who had syphilis, a judge ruled Monday.

The patient, a woman in her early 20s, filed the lawsuit last year. A screen shot of the woman’s private medical records from the hospital was posted on the Facebook group, “Team No Hoes,” in September 2013. The records listed the woman’s diagnosis as “maternal syphilis.” She was pregnant at the time.

Read more on Cincinnati.com.

In a way, and even though the patient may appeal the ruling, this ruling is consistent with other cases where covered entities were found not liable for employees’ egregious conduct that were outside the employee’s scope of work duties. In this case, the employee was reportedly in the financial services department.

It is not known what, if any, action HHS/OCR has taken as a result of their investigation into the incident.

Update: Jeff Drummond’s blog about this case mentions that this case has a different result than Hinchy v. Walgreens, a case that I covered last year, but temporarily forgot about it in writing up the Ohio case.  So we have cases in two states that found no employer liability and one case in a third state that found for the plaintiff/patient.


Related:

  • 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
  • Before Their Telegram Channel Was Banned Again, ScatteredLAPSUS$Hunters Dropped Files Doxing Government Employees (2)
  • Massachusetts hospitals Heywood, Athol say outage was a cybersecurity incident
  • Data BreachesProsper Data Breach Impacts 17.6 Million Accounts
  • Heritage Provider Network $49.99M Class Action Settlement
Category: ExposureHealth DataInsiderU.S.

Post navigation

← Indictment in Atlanta charges three in E*TRADE, Scottrade ID theft and fraud scheme
More than 1,000 Spotify email addresses and passwords leaked. Spotify denies any breach of their system/ →

2 thoughts on “U. of Cincinnati Medical Center not liable for employee’s Facebook post on a patient’s STD (updated)”

  1. Anonymous says:
    November 10, 2015 at 9:08 pm

    I am not responsible for what my employee does with the information I give them and the time I pay them for.

    If my employee causes me and others harm, not my problem.

    If my employee posts a screenshot of all my customers, or of my secret process, not my problem.

    If my employee posts all the emails she has privy to of my best government customers drunken exploits with that 3500$ call girl I paid for to keep the contract, not my problem.

    This better be appealed and won, otherwise I’ll just give up in believing people have certain rights to privacy.

    I’m annoyed at reading this, obviously.

    1. Dissent says:
      November 10, 2015 at 10:28 pm

      The opinion that it’s similar to (mentioned in my post) is a case in NY that did go up to the appellate court, who affirmed the dismissal of that patient’s lawsuit. You can read more about it here: http://www.databreaches.net/ny-court-of-appeals-rules-employer-not-liable-for-actions-of-employee-acting-outside-scope-of-employment/

Comments are closed.

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.