DataBreaches.Net

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

Kaiser Bellflower is fined (another) $187,500 for privacy breach

Posted on July 16, 2009 by Dissent

The Kaiser Permanente hospital in Bellflower has been hit with a $187,500 fine for failing for a second time to prevent unauthorized access to confidential patient information, state pubic health officials said today.

[Updated at 3 p.m.: A spokesman for the hospital said the fine was part of the ongoing investigation into employees improperly accessing the medical records of Nadya Suleman and her children. Disciplinary action has been taken against the employees, said Jim Anderson, a hospital spokesman. All the incidents occurred in January; a previous post said they had occurred in April and May.]

State officials said Kaiser Permanente Bellflower Medical Center compromised the privacy of four patients when eight employees improperly accessed records. This is the second penalty against the hospital, officials said.

The hospital was fined $250,000 in May for failing to keep employees from snooping in the medical records of Nadya Suleman, the woman who set off a media frenzy after giving birth to octuplets in January.

Read more in the Los Angeles Times.  Keep in mind that this is not HHS fining them under HIPAA, but the state fining them.

No related posts.

Category: Health Data

Post navigation

← Online thieves raid Hong Kong accounts
Oh look, a dumpster! Let’s throw the papers here… →

4 thoughts on “Kaiser Bellflower is fined (another) $187,500 for privacy breach”

  1. Anonymous says:
    July 17, 2009 at 4:12 pm

    Do you think employees need more training or do you think the hospital needs to up its privacy regulations?

  2. Anonymous says:
    July 17, 2009 at 4:30 pm

    Putting aside those who might snoop on patient files with the intent of selling the info to a tabloid, you can train people and train people and train people, but you can’t train the curiosity out of them. Firing employees needs to happen and it may be a deterrent for some other employees, but as long as some employees leave files open or stay logged in and walk away from their desks, I think people will snoop.

    Maybe if files had an automatic time out/disconnect and maybe if every employee who wanted to access a file had to use a biometric identifier and a big “Your access to the file will be logged,” there might be fewer incidents (assuming that the logs are audited).

    I don’t know what system Kaiser uses, but I do know that they are not the only medical facility to have problems of this kind.

    What do you think needs to be done?

  3. Anonymous says:
    July 17, 2009 at 5:32 pm

    Agreed! You can only train so much. Hospitals, no let me rephrase that……the Healthcare industry in general needs to deliver harsher and more immediate sanctions on employees, especially those who have had “the training”. As my company prepares for the Red Flag Rules, I hope the HHS, OIG, and other oversight entities stay true to their word and hold violators accountable.

  4. Anonymous says:
    July 17, 2009 at 6:08 pm

    What does your company tell employees in terms of policy on this? Do they tell them, “one strike and you’re out” and enforce that policy? Not asking you to name your company, but does your company actually audit logs to see who’s accessing which files, etc.? Some facilities are putting special ‘flags’ on celebrities’ files/records, but there’s an awful lot of snooping that goes on that involves family members, neighbors, etc. who are not celebrities.

    Enforcement — as well as privacy protection and security – needs to start with the employer.

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

  • McDonald’s McHire leak involving ‘123456’ admin password exposes 64 million applicant chat records
  • Qilin claims attack on Accu Reference Medical Laboratory. It wasn’t the lab’s first data breach.
  • Louis Vuitton hit by data breach in Türkiye, over 140,000 users exposed; UK customers also affected (1)
  • Infosys McCamish Systems Enters Consent Order with Vermont DFR Over Cyber Incident
  • Obligations under Canada’s data breach notification law
  • German court offers EUR 5000 compensation for data breaches caused by Meta
  • Air Force Employee Pleads Guilty to Conspiracy to Disclose Unlawfully Classified National Defense Information
  • UK police arrest four in connection with M&S, Co-op and Harrods cyberattacks (1)
  • At U.S. request, France jails Russian basketball player Daniil Kasatkin on suspicion of ransomware conspiracy
  • Avantic Medical Lab hacked; patient data leaked by Everest Group

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

  • DeleteMyInfo Wins 2025 Digital Privacy Excellence Award from Internet Safety Council
  • TikTok Loses First Appeal Against £12.7M ICO Fine, Faces Second Investigation by DPC
  • German court offers EUR 5000 compensation for data breaches caused by Meta
  • How to Build on Washington’s “My Health, My Data” Act
  • Department of Justice Subpoenas Doctors and Clinics Involved in Performing Transgender Medical Procedures on Children
  • Google Settles Privacy Class Action Over Period Tracking App
  • ICE Is Searching a Massive Insurance and Medical Bill Database to Find Deportation Targets

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.