DataBreaches.Net

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

wtf?

Posted on July 8, 2015 by Dissent

ESPN obtained medical charts that show Giants DE Jason Pierre-Paul had right index finger amputated today. pic.twitter.com/VI5cbS1uCw

— Adam Schefter (@AdamSchefter) July 8, 2015

How did ESPN obtain those charts? If Pierre-Paul gave the records to ESPN with permission to share publicly, that’s his right, of course, but did he, or did someone just share his medical records – records that are typically protected by HIPAA? ESPN is not a HIPAA-covered entity as far as I know. Did someone on the team leak them or did Pierre-Paul knowingly share this?

Update 1: Russ Britt reports:

The news of Pierre-Paul’s injury first broke on Sunday when a hospital worker reportedly told a friend of the accident. That person then posted the news on Twitter.

If that is accurate, then yes, this likely did involve a HIPAA violation, and hopefully, the hospital is investigating. And if the hospital worker also leaked the medical record, then the worker’s employment should be terminated immediately.

h/t, John Holstein


Related:

  • Another plastic surgery practice fell prey to a cyberattack that acquired patient photos and info
  • Two U.K. teenagers appear in court over Transport of London cyber attack
  • ModMed revealed they were victims of a cyberattack in July. Then some data showed up for sale.
  • JFL Lost Up to $800,000 Weekly After Cyberattack, CEO Says No Patient or Staff Data Was Compromised
  • Massachusetts hospitals Heywood, Athol say outage was a cybersecurity incident
  • Heritage Provider Network $49.99M Class Action Settlement
Category: Health Data

Post navigation

← IE: More than 100 breaches of HSE patient data in past year
‘I’m COMING for you, DIRTBAG!’: Ex-Sony chief Smedley to Kid Lizard hacker →

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.