DataBreaches.Net

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

Prime Healthcare and Shasta Regional still don't get HIPAA?

Posted on November 21, 2014 by Dissent

Remember the case of a patient whose PHI was disclosed to media by Shasta Regional Center and Prime Healthcare? If you don’t, just search this site for “Prime Healthcare,” and you’ll find a slew of coverage, including a $95,000 fine by California and a $275,000 settlement with OCR after they stubbornly insisted they had not violated HIPAA.

This week, Prime Healthcare and Shasta Regional Center issued a press release concerning the civil suit filed by the patient:

Prime Healthcare Services and Shasta Regional Medical Center announced today that a Superior Court jury vindicated the facility and its executives in a civil patient privacy case orchestrated by the SEIU-UHW as part of its corporate campaign against Prime Healthcare.

The case regarded an alleged violation of patient privacy rights at Shasta Regional Medical Center. The plaintiff had previously divulged her own medical records to the media, which printed and broadcast the information. The plaintiff’s daughter testified that a reporter showed up at a union meeting she attended with her mother and asked whether anyone wanted to share their medical information from Shasta Regional. At the behest of the union, the plaintiff agreed.

Prime Healthcare and Shasta Regional accurately contended that by this agreement, the patient had implicitly waived her privacy rights by giving the information to the media, which publicized it in newspapers across California and on television. A later review of the plaintiff’s medical records indicated that Shasta Regional personnel followed all state and federal guidelines related to patient care.

“A jury reviewed the facts and concluded that there was no public disclosure of private information, no violation of the plaintiff’s privacy rights and no harm to the patient by any of the executives, hospital, or Prime Healthcare,” said Troy Schell, general counsel. “This was part of SEIU-UHW’s malicious corporate campaign against the company and hospital. It’s a travesty that the union continues to focus on lies and corporate campaigns, wasting millions of dollars, rather than what is best for healthcare and communities. Prime Healthcare and Shasta Regional Medical Center remains committed to protecting patient rights, providing the highest quality of patient care and serving the community.”

That “vindication” has nothing to do with they violated HIPAA, of course, as there’s no private cause of action under HIPAA, even though we now have one case where HIPAA was used as the standard of care in deciding a privacy lawsuit.  So to repeat, lest Prime Healthcare and Shasta Regional continue with their b.s.:

A patient can choose to divulge their information to the media. That does not given the covered entity the right to disclose their information under HIPAA. It really was – and is – a no-brainer, which is why although they may claim vindication, both the state and federal government pursued charges against them.

Without the transcript of the jury trial, it’s hard to know how the jury could possibly conclude that there was no violation of privacy when both the state and federal government had already determined that not only was there a violation, but the entities’ conduct was so severe that it warranted prosecution and/or a monetary penalty.

Can a state revoke a facility’s license if they willfully violate HIPAA and then continue to insist they’ve done nothing wrong? Probably not, but it’s a thought.


Related:

  • Maintenance Note
  • CISA Alert: Reported Supply Chain Compromise Affecting XZ Utils Data Compression Library, CVE-2024-3094
  • System Status Note
  • System Status Note
  • Fraudster's fake data breach claims should remind media to be careful what we report
  • "Pompompurin" taken into custody after violating conditions of pre-sentencing release on bond (1)
Category: Uncategorized

Post navigation

← Gundersen sentenced for his role in scheme to hack 14 financial networks and DoD payroll system
SLC Security to WakeMed: Wake Up!!!! →

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

  • 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.