DataBreaches.Net

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

Stolen hard drive could affect 582 Ohioans enrolled in United Healthcare Medicare plans – but they’re just finding out more than 3 months later

Posted on October 12, 2011 by Dissent

Tim Tresslar reports:

United Healthcare said Tuesday a hard drive containing information on 582 Ohioans who are members of its Medicare plans has been stolen from a vendor.The Minnetonka, Minn.-based company said it is notifying the affected members by mail. United HealthCare’s commercial health plans are not affected.

The hard drive belonged to Futurity First Insurance Group, a provider of sales and marketing services for the United Healthcare Medicare Advantage, Medicare Part D prescription drug, Evercare and Medicare Supplement plans, a news release states.

Futurity First sent the hard drive to a vendor for repair and it was stolen on or about June 28. The vendor told Futurity about the theft on Aug. 12.

Nearly a month later, on Sept. 14, Futurity told United Healthcare about the stolen hard drive.

The drive included member names, Social Security numbers and, in some cases, the birth dates and private health information, United Healthcare said.

The insurer said it is offering affected members one year with Debix, an identity protection service, for free.

Source: Dayton Daily News

Okay, those delays are too long. The unnamed vendor didn’t report the theft for a month and a half? And then Futurity didn’t report it to UHC for another month? That it took UHC a month to disclose the breach neither surprises nor upsets me, as I don’t think one month is unreasonable, even though some states have much stricter requirements. But the totality of the situation – that personal data that could be used for ID theft were stolen on June 28 and individuals have not yet received notification/warning three and a half months later – that is too much.

What makes this is even more aggravating, in my opinion, is that this drive was not storing information used for treatment – it was for marketing/sales purposes. While marketing is an accepted business operation, that personal data were put at risk for marketing seems a poor data protection decision. Does a company really need Social Security numbers to market?  Why couldn’t other types of IDs been created or used?

And how was the drive stolen from the vendor? Was it left in an employee’s car? Was there a burglary at the repair firm? Did Futurity have a contract with this vendor that required certain security protections – and if so, were those protections implemented?

Business associates are a major source of data security risk in the healthcare sector. I hope that HHS investigates this breach.


Related:

  • KT Chief to Resign After Cybersecurity Breach Resolution
  • Cyber-Attack On Bectu’s Parent Union Sparks UK National Security Concerns
  • Attorney General James Announces Settlement with Wojeski & Company Accounting Firm
  • JFL Lost Up to $800,000 Weekly After Cyberattack, CEO Says No Patient or Staff Data Was Compromised
  • A business's cyber insurance policy included ransom coverage, but when they needed it, the insurer refused to pay. Why?
  • Before Their Telegram Channel Was Banned Again, ScatteredLAPSUS$Hunters Dropped Files Doxing Government Employees (2)
Category: Breach IncidentsBusiness SectorHealth DataSubcontractorTheftU.S.

Post navigation

← Sony attacked again – 93,000 usernames and passwords compromised
Hacker attacks against retailers up 43 percent →

1 thought on “Stolen hard drive could affect 582 Ohioans enrolled in United Healthcare Medicare plans – but they’re just finding out more than 3 months later”

  1. JJ says:
    October 12, 2011 at 10:23 am

    UnitedHealthcare is pushed by AARP: https://www.aarpmedicareplans.com/landing/medicare-part-d.html

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

  • 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
  • The Case for Making EdTech Companies Liable Under FERPA
  • NHS providers reviewing stolen Synnovis data published by cyber criminals

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

  • 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
  • Always watching: How ICE’s plan to monitor social media 24/7 threatens privacy and civic participation
  • Who’s watching the watchers? This Mozilla fellow, and her Surveillance Watch map

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.