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.

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

  • Fresno County fell victim to $1.6M phishing scam in 2020. One suspected has been arrested, another has been indicted.
  • Ransomware Attack on ADP Partner Exposes Broadcom Employee Data
  • Anne Arundel ransomware attack compromised confidential health data, county says
  • Australian national known as “DR32” sentenced in U.S. federal court
  • Alabama Man Sentenced to 14 Months in Connection with Securities and Exchange Commission X Hack that Spiked Bitcoin Prices
  • Japan enacts new Active Cyberdefense Law allowing for offensive cyber operations
  • Breachforums Boss “Pompompurin” to Pay $700k in Healthcare Breach
  • HHS Office for Civil Rights Settles HIPAA Cybersecurity Investigation with Vision Upright MRI
  • Additional 12 Defendants Charged in RICO Conspiracy for over $263 Million Cryptocurrency Thefts, Money Laundering, Home Break-Ins
  • RIBridges firewall worked. But forensic report says hundreds of alarms went unnoticed by Deloitte.

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

  • Massachusetts Senate Committee Approves Robust Comprehensive Privacy Law
  • Montana Becomes First State to Close the Law Enforcement Data Broker Loophole
  • Privacy enforcement under Andrew Ferguson’s FTC
  • “We would be less confidential than Google” – Proton threatens to quit Switzerland over new surveillance law
  • CFPB Quietly Kills Rule to Shield Americans From Data Brokers
  • South Korea fines Temu for data protection violations
  • The BR Privacy & Security Download: May 2025

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[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.