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:

  • PowerSchool commits to strengthened breach measures following engagement with the Privacy Commissioner of Canada
  • Two more entities have folded after ransomware attacks
  • Data breach feared after cyberattack on AMEOS hospitals in Germany
  • Global hack on Microsoft product hits U.S., state agencies, researchers say
  • Premier Health Partners issues a press release about a breach two years ago. Why was this needed now?
  • Bitcoin holds steady as hackers drain over $40 million from CoinCDX, India's top exchange
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

  • Scattered Spider Hijacks VMware ESXi to Deploy Ransomware on Critical U.S. Infrastructure
  • Hacker group “Silent Crow” claims responsibility for cyberattack on Russia’s Aeroflot
  • AIIMS ORBO Portal Vulnerability Exposing Sensitive Organ Donor Data Discovered by Researcher
  • Two Data Breaches in Three Years: McKenzie Health
  • Scattered Spider is running a VMware ESXi hacking spree
  • BreachForums — the one that went offline in April — reappears with a new founder/owner
  • Fans React After NASCAR Confirms Ransomware Breach
  • Allianz Life says ‘majority’ of customers’ personal data stolen in cyberattack (1)
  • Infinite Services notifying employees and patients of limited ransomware attack
  • The safe place for women to talk wasn’t so safe: hackers leak 13,000 user photos and IDs from the Tea app

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

  • Congress tries to outlaw AI that jacks up prices based on what it knows about you
  • Microsoft’s controversial Recall feature is now blocked by Brave and AdGuard
  • Trump Administration Issues AI Action Plan and Series of AI Executive Orders
  • Indonesia asked to reassess data privacy terms in new U.S. trade deal
  • Meta Denies Tracking Menstrual Data in Flo Health Privacy Trial
  • Wikipedia seeks to shield contributors from UK law targeting online anonymity
  • British government reportedlu set to back down on secret iCloud backdoor after US pressure

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.