DataBreaches.Net

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

Prime Healthcare and Shasta Regional Center settle HHS complaint, to pay $275,000

Posted on June 12, 2013 by Dissent

I don’t know if you can hear me, but I generally groan when I read a settlement that permits the party to make no admission of guilt. The FTC permits it, and HHS also permits it. I understand why they may choose to do that, but seriously, there are some breaches that are just so egregious that they demand a finding or acknowledgement of guilt.

Since January of last year, I’ve been covering the privacy debacle that is the Prime Healthcare/Shasta Regional Medical Center case (previous coverage here, here, here, here, and here, here). To say that I consider their conduct to be one of the most obvious cases of a knowing HIPAA breach would be to put it mildly, despite the entities’ denials of any wrongdoing and repeated assertions that their conduct is permissible.  Today,  Chad Terhune of the Los Angeles Times reports that while they continue to appeal the state’s $95,000 penalty for the breach, they have reached a settlement with HHS over the breach:

Hospital chain Prime Healthcare Services Inc. has agreed to pay $275,000 to settle a federal investigation into alleged violations of patient privacy.

The case stemmed from allegations that Prime Healthcare and its Shasta Regional Medical Center violated patient confidentiality by sharing a woman’s medical files with journalists and sending an email about her treatment to nearly 800 hospital employees.

Last year, California regulators fined the Ontario hospital chain $95,000 for the unauthorized disclosure of medical information in this matter. The company said it’s appealing that state fine.

In the federal settlement announced Tuesday, Prime Healthcare did not admit to any wrongdoing. The company and hospital said they “firmly believe that they would have prevailed in this matter based upon the merits.” (emphasis added by me)

That statement is from their press release, where they wrote:

In reaching the agreement, SRMC admitted to no wrongdoing pertaining to the alleged violation of patient privacy. Prime Healthcare and SRMC firmly believe that they would have prevailed in this matter based upon the merits. However, in view of the unnecessary expense to both SRMC and to the taxpayers of the United States, they reached an agreement to settle the matter and pay $275,000 as a “Resolution Amount.”

Oh, they’re worried about expense to taxpayers? How considerate of them.

In light of their repeated public statements, I really really wish HHS had not settled this case. I realize that $275,000 may seem like a large fine given that it was “only” one patient whose data were intentionally disclosed, but to allow them to insist that they did nothing wrong is offensive.

Read more on the L. A. Times. As of the time of this posting, HHS has not posted any press release on its site with the settlement agreement, so I’ll have more on this later.


Related:

  • 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
  • Integris Health Agrees to $30 Million Settlement Over 2023 Data Breach
Category: Health Data

Post navigation

← EPIC Urges Federal Health Agency to Safeguard Mental Health Records
House panel to probe alleged seizure of medical records by IRS →

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

  • 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
  • A jailed hacking kingpin reveals all about the gang that left a trail of destruction
  • Army gynecologist took secret videos of patients during intimate exams, lawsuit says

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

  • 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
  • Always watching: How ICE’s plan to monitor social media 24/7 threatens privacy and civic participation
  • Who’s watching the watchers? This Mozilla fellow, and her Surveillance Watch map

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.