DataBreaches.Net

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

Judge Dismisses Lawsuit Charging LabCorp with HIPAA Violation

Posted on June 26, 2018 by Dissent

Fred Donovan reports:

June 25, 2018 – US District Court Judge Rudolph Contreras dismissed a lawsuit by Hope Lee-Thomas accusing LabCorp of a HIPAA violation for not providing adequate privacy protections at its Providence Hospital computer intake station.

Lee-Thomas argued in her lawsuit that LabCorp failed to shield her PHI from public view at its computer intake station at Washington, DC-based Providence Hospital. The station was next to a Quest Diagnostics computer intake and her information was visible to the person using the Quest station, she said in her compliant (sic).

Read more on HealthIT Security.


Related:

  • 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
  • How a hacking gang held Italy’s political elites to ransom
  • Uncovering Qilin attack methods exposed through multiple cases
  • Predatory Sparrow Strikes: Coordinated Cyberattacks Seek to Cripple Iran's Critical Infrastructure
Category: Commentaries and AnalysesHealth DataOf NoteU.S.

Post navigation

← Michigan Medicine notifies patients of health information data breach
Eight Arrested in Africa-Based Cybercrime and Business Email Compromise Conspiracy →

5 thoughts on “Judge Dismisses Lawsuit Charging LabCorp with HIPAA Violation”

  1. Justin Shafer says:
    June 26, 2018 at 1:53 pm

    “HHS responded that it would not pursue her claim”…

    Surprise, Surprise! =)

  2. Adrin says:
    June 27, 2018 at 8:30 am

    If they are that close and in the same office then the 2 have a BAA agreement.

    1. Dissent says:
      June 27, 2018 at 9:01 am

      I doubt that the two labs have a BAA with each other over and above their BAA with the hospital, but it would be nice to confirm that.

      1. Adrin says:
        June 27, 2018 at 12:20 pm

        To be in the Hospital they would have a BAA, with the Hospital. It is common for a practice to have on phlebotomist that works for the lab and not the practice and that person will do blood draws for other labs. The lab tech could be an employee of Labcorp or Quest or the Hospital. If Hospital then no question of HIPAA. Other 2 may be a grey area.

        I also recall something about contractors/vendors. Even if there isn’t a signed BAA it is assumed. Although I can’ find it now. I do love how they make a statement near the end that makes you wonder. “This is only sample language and use of these sample provisions is not required for compliance with the HIPAA Rules. ”

        Think she would have been better off if the complaint said that she could see another patient’s data on the screen.

      2. Adrin says:
        June 27, 2018 at 12:27 pm

        :O Sorry my bad after reading the complaint. The hospital has a bad setup and should change it. I was thinking the stations were accessible but employee only. What an out.

        ” complaint failed to state a claim upon which relief can be
        granted because HIPAA does not provide individuals with a private cause of action.”

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

  • Maryland Privacy Crackdown Raises Bar for Disclosure Compliance
  • 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

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.