DataBreaches.Net

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

(Update) Henry Ford Hospital breach affected 3,700

Posted on November 23, 2010 by Dissent

As an update to previous coverage on the Henry Ford Health System breach involving a stolen laptop containing unencrypted PHI:

1. The breach affected 3,700 patients according to the hospital’s notification to HHS under the breach notification requirement of HITECH.

2. The hospital posted a notice to its web site on Nov. 19:

Henry Ford Health System has notified patients who were affected by a breach of unsecured personal health information after learning that an employee’s laptop computer storing the information was stolen from an unlocked urology medical office.

While the laptop was password protected, the patient information stored on the computer could potentially be viewed on the computer.

As a result of the Sept. 24 theft, Henry Ford notified the affected patients in a letter mailed last week from Chief Privacy Officer Meredith Phillips. The letter explained what happened, what information was stored on the laptop, and what steps the health system is taking to prevent future breaches of patient information.

Under federal law, health care organizations are required to notify patients within 60 days of a breach of unsecured health information.

“The security of our patients’ health information is very important to us, and we sincerely apologize for what happened,” Phillips says. “This laptop did not have the proper security protections that we require for laptop computers storing patient information.”

The laptop contained patient information related to prostate services received between 1997 and 2008 and included some but not all of the following information: Patient name, medical record number, date of birth, mailing and e-mail addresses, telephone number, treatment and doctor visits. No Social Security numbers or health insurance identification numbers were stored on the laptop.

While the stolen laptop had elements of patient information, Phillips says, it did not contain the patient’s medical record or allow access into the patient’s medical record.

To address any patient questions or concerns, Henry Ford set up a toll-free telephone number – 1.888.313.1027 – that is available 24 hours a day, seven days a week. Additionally, the health system offered the affected patients free credit monitoring for one year from Equifax to ensure their information is not used inappropriately.

After learning of the stolen laptop on Sept. 24, Henry Ford launched a thorough investigation to determine the identity of the affected patients and the nature of their information stored on the laptop, and ascertain whether proper security protections were installed.

To prevent future patient information breaches, Phillips says employees will be re-educated in the steps necessary to protect patient information stored on computers. She also says the process will be improved for how employees obtain a laptop computer for work purposes.


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

← Federal Appeals Court Overturns Vermont Law that Restricted Commercial Use of Physician Information
Puerto Rico Dept of Health reports breach affecting 400,000; Triple-S Salud fined $100k →

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

  • Suspected Russian hacker reportedly detained in Thailand, faces possible US extradition
  • Did you hear the one about the ransom victim who made a ransom installment payment after they were told that it wouldn’t be accepted?
  • 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

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.