DataBreaches.Net

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

Advocate Christ Medical Center demonstrates how NOT to respond to a HIPAA breach

Posted on October 6, 2019 by Dissent

Ok, we know mis-mailings and mix-ups happen, right.  But what allegedly happened with Advocate Christ Medical Center is yet another example of how NOT to respond to an incident while claiming you take privacy and security seriously.

CBS in Chicago reports that Advocate Christ Medical Center in Oak Lawn Illinois sent Darnell Payne some other patient’s complete records when he requested his own medical file.

But when he contacted them about their mistake and kindly offered to bring them back the other patient’s files, how did they respond? Did they say, “Oh, thank you so much but no need to do that… we’ll send someone over to you to pick them up immediately?”

No, they apparently did not.

According to Payne, the hospital’s only response was, “No, that’s impossible.” He said that is not only what the hospital said about the offer to bring back the records, but the very error itself.

“‘Impossible.’ Her statement to me was, ‘That’s impossible.’ (I said) ‘But I have it!’” Payne said. “(The hospital said), ‘There’s no way that that could have happened.’ But it did!”

But wait for it.  Their incident response gets even WORSE. When he re-requested his OWN records to get them, the hospital sent him a bill.

To this day, he reportedly still has the other patient’s records.

Paging OCR to Aisle 4…. paging OCR to Aisle 4.

Category: ExposureHealth DataPaperU.S.

Post navigation

← DCH Healthcare Systems pays hacker to end ransomware attack
Millions of Beeline Clients’ Data Leaked – Kommersant →

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

  • 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.
  • Chinese Hackers Hit Drone Sector in Supply Chain Attacks

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.