DataBreaches.Net

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

Update on Phoebe Putney Hospital breach

Posted on January 10, 2014 by Dissent

WALB is just all over a breach involving Phoebe Putney Hospital in Georgia that was disclosed yesterday. Today, WALB reports that two employees have been fired over the breach, which the hospital still hasn’t described as a theft:

Phoebe officials say a computer forensics investigation showed only 13 people’s social security numbers were recorded on that missing computer hard drive. But it contained names, addresses, and possibly medical diagnosis information of nearly 6,800 people.

According to the November 7th police report, a hospital employee rearranging her office at the Behavioral Health Outreach Clinic boxed up her Dell desktop computer and left it outside her office in a locked hallway. The next morning it was gone.

“There was a custodial worker who believed that the computer, because it was inside a box, was trash,” said Phoebe Vice President, Chief Compliance and Privacy Officer Audrey Pike. “And so the box was discarded. According to the police report he threw it in the dumpster, but when they checked the next day it was gone.

Read more on WALB.

How often do we see employees fired over breaches? It happens, but usually we see that they’ve been “re-trained.” For the hospital to fire two employees – each for violating a different part of the hospital’s policies – strikes me as a bit unusual. But I bet all the remaining hospital employees will be extra cautious/compliant going forward.

Category: Health Data

Post navigation

← More on today's HHS update: newly disclosed incidents
Update: Former Virginia Beach General Hospital nurse's aide sentenced for using patients’ personal info to commit tax fraud →

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

  • Copilot AI Bug Could Leak Sensitive Data via Email Prompts
  • FTC Provides Guidance on Updated Safeguards Rule
  • Sentara Health terminates remote employees after realizing they couldn’t be sure who was doing the work.
  • Hackers Break Into Car Sharing App, 8.4 Million Users Affected
  • Cyberattack pushes German napkin company into insolvency
  • WMATA Train Operators Arrested in Health Care Fraud Scheme
  • Washington Post investigating cyberattack on journalists, WSJ reports
  • Resource: State Data Breach Notification Laws – June 2025
  • WestJet investigates cyberattack disrupting internal systems
  • Plastic surgeons often store nude photos of patients with their identity information. When would we call that “negligent?”

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

  • Vermont signs Kids Code into law, faces legal challenges
  • Data Categories and Surveillance Pricing: Ferguson’s Nuanced Approach to Privacy Innovation
  • Anne Wojcicki Wins Bidding for 23andMe
  • Would you — or wouldn’t you?
  • New York passes a bill to prevent AI-fueled disasters
  • Synthetic Data and the Illusion of Privacy: Legal Risks of Using De-Identified AI Training Sets
  • States sue to block the sale of genetic data collected by DNA testing company 23andMe

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.