DataBreaches.Net

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

Dr. Douglas C. Morrow, OD Notifies Patients of Data Security Incident

Posted on February 24, 2022 by Dissent

Look at the timeline.  Was this a ransomware incident that encrypted data and made it more difficult to investigate? Why did it take so long from some of these benchmarks to notification?

AUBURN, Ind., Feb. 23, 2022 /PRNewswire/ — On May 16, 2021, Dr. Douglas C. Morrow, OD (“Dr. Morrow”) experienced a data security incident that prevented users from accessing systems and data. Upon discovering this incident, Dr. Morrow immediately launched an investigation and engaged a digital forensics firm to help determine what happened and what information may have been accessed. On October 29, 2021, the investigation determined that the attacker gained access to Dr. Morrow’s data and may have acquired protected health information.

Why did it take more than 5 months from the incident with an investigation that was immediately launched to figure out that there had been access to data and possible acquisition of protected health information?

On December 8, 2021, Dr. Morrow identified individuals whose protected personal information may have been compromised. The types of information potentially accessed varied by individual, but may have included name, address, Social Security number, driver’s license, medical information, and health insurance information. The specific types of medical information and/or health insurance information that may have been accessed include Member/Medicaid ID numbers, treatment/diagnosis information, dates of service, provider name(s), patient account number(s), and medical record number(s).

Impacted individuals were notified beginning on February 23, 2022.

If individuals were identified on December 8, why did it take until February 23 to send letters? And how many patients were notified?

Seriously… the “no later than 60 calendar days” notification requirement has to have teeth or it should be revoked or amended. In this case, based on the timeline provided by the provider, what do you use as the date of discovery for determining when notification had to be made by (under HIPAA/HITECH)?

Read more at PRNewswire.


Related:

  • JFL Lost Up to $800,000 Weekly After Cyberattack, CEO Says No Patient or Staff Data Was Compromised
  • Hackers Say They Have Personal Data of Thousands of NSA and Other Government Officials
  • UK: 'Catastrophic' attack as Russians hack files on EIGHT MoD bases and post them on the dark web
  • Massachusetts hospitals Heywood, Athol say outage was a cybersecurity incident
  • Data BreachesProsper Data Breach Impacts 17.6 Million Accounts
  • Heritage Provider Network $49.99M Class Action Settlement
Category: HackHealth Data

Post navigation

← Russian hackers infect network devices with new botnet malware
KS: Hays schools hacked with ransomware →

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

  • 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
  • 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

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

  • 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
  • Always watching: How ICE’s plan to monitor social media 24/7 threatens privacy and civic participation

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.