DataBreaches.Net

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

Amedisys notifies 6,909 patients after failure to locate 142 devices during inventory

Posted on March 14, 2015 by Dissent

On March 2nd, home health and hospice care provider Amedisys issued a press release that disclosed that during a risk management inventory of their devices, which commenced during the second half of 2014, they were unable to locate 142 encrypted computers and laptops. The devices had been assigned to Amedisys clinicians and other team members who left the company between 2011 and 2014.

As a result, Amedisys is notifying HHS and appropriate authorities, and on February 28, 2015, began sending notifications to 6,909 patients potentially impacted.

“Amedisys has no indication of external hacking into its network, and no evidence that any patients or former patients have suffered any actual harm,” the firm writes, noting that all devices are robustly protected with 256-bit disk encryption, administrator restrictions, and “several other security protections designed to safeguard the personal and medical information of the Company’s patients.”

Depending on the device, the information on the missing devices may have included any or all of the following: name, address, Social Security number, date of birth, Medicare and insurance ID numbers, medical records and other personally identifiable data.

For clinician-assigned laptops, these records related only to those patients assigned to the clinicians who used a device to provide healthcare services. As the firm notes, however, former employees had access to the encryption key for local access to their formerly assigned device although Amedisys disabled their network password. So clinicians who failed to return their devices on termination from the company would still have access to the patient information on their device.  An assessment of devices that Amedisys was able to recover, conducted by Booz Allen Hamilton, has reportedly shown that,

in the vast majority of cases, no one has accessed or used the patient information on the devices subsequent to the team member’s departure from Amedisys. As regards the minority of instances in which post-departure access occurred, we have no evidence to indicate that such access was made for any improper purpose.

Potentially impacted individuals are being offered identity theft protection services through Kroll, including credit monitoring, to protect against any possible harm that could arise from the incident.

The firm has retained Booz Allen Hamilton to assess and enhance its security and inventory systems and practices to ensure the protection of sensitive patient information.

Incident-Related Files:

  • Overview by Amedisys
  • Press Release
  • Letter to Patients
  • Frequently Asked Questions about the incident
  • Amedisys offer of identity theft protection services through Kroll
  • Sidley Austin LLP letter of March 2nd to NH Attorney General’s Office (pdf)

With the exception of their attorneys’ notification to New Hampshire, all files are on Amedisys’s web site, with the breach incident prominently linked from their home page. Amedisys’s breach disclosure and documents are a great example of clear writing and transparency. I realize some may raise questions about their security protocols and failure to ensure devices were returned on termination, but given that this happened, their response has been appropriate, I think, and they seem to be taking necessary steps to prevent a recurrence.

 

 

No related posts.

Category: Health DataLost or MissingU.S.

Post navigation

← Adventures in breach alerts, Saturday edition
Some IT staff at Victor Valley College return to work while security protocol breach investigation continues →

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

  • India’s Max Financial says hacker accessed customer data from its insurance unit
  • Brazil’s central bank service provider hacked, $140M stolen
  • Iranian and Pro-Regime Cyberattacks Against Americans (2011-Present)
  • Nigerian National Pleads Guilty to International Fraud Scheme that Defrauded Elderly U.S. Victims
  • Nova Scotia Power Data Breach Exposed Information of 280,000 Customers
  • No need to hack when it’s leaking: Brandt Kettwick Defense edition
  • SK Telecom to be fined for late data breach report, ordered to waive cancellation fees, criminal investigation into them launched
  • Louis Vuitton Korea suffers cyberattack as customer data leaked
  • Hunters International to provide free decryptors for all victims as they shut down (2)
  • SEC and SolarWinds Seek Settlement in Securities Fraud Case

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

  • German court awards Facebook user €5,000 for data protection violations
  • Record-Breaking $1.55M CCPA Settlement Against Health Information Website Publisher
  • Ninth Circuit Reviews Website Tracking Class Actions and the Reach of California’s Privacy Law
  • US healthcare offshoring: Navigating patient data privacy laws and regulations
  • Data breach reveals Catwatchful ‘stalkerware’ is spying on thousands of phones
  • Google Trackers: What You Can Actually Escape And What You Can’t
  • Oregon Amends Its Comprehensive Privacy Statute

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.