DataBreaches.Net

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

University of Oklahoma Neurology Clinic notifies almost 20,000 of security breach

Posted on October 11, 2010 by Dissent

In the process of updating PHIprivacy.net to reflect breaches newly disclosed by the U.S. Dept. of Health and Human Services (HHS), I found reference to a breach for which I was able to find a companion statement.

The University of Oklahoma-Tulsa, Neurology Clinic recently notified HHS of an incident affecting 19,264 patients. According to HHS’s logs, the clinic reported that the incident occurred or was detected on or about July 25. In a statement dated September 24 and posted on their web site on October, the clinic states:

The University of Oklahoma’s Tulsa Neurology practice recently became aware that one of its clinic computers had been compromised by a virus. The Clinic is notifying individuals whose records were maintained on the computer of the discovery. Patients of Dr. John Cattaneo and of Neurology, LLC, a Tulsa practice where Dr. Cattaneo formerly practiced are being notified this week by letter.

The letters advise the patients that an intensive investigation determined that a virus capable of retrieving data from documents located on the computer had been discovered. Although it is not possible at this time to determine what documents on the computer, if any, were accessed by this virus, in an abundance of caution, the Clinic is notifying those individuals whose information and documents were stored there. Many of these documents included some or all of the following: patient name, telephone number, address, birth date, Social Security Number, medical record and insurance numbers, procedure billing codes, diagnosis codes, lab reports, office notes, radiology reports, and service dates. In some records, guarantor information was also included. The virus was detected on or about July 28, and its properties were determined during the investigation.

This incident serves as a useful example of why HHS’s summary logs are not really that helpful to those who track and analyze data breaches. Their logs note the incident as a “hacking/IT incident”  and their logs do not indicate the kinds of information involved in any particular breach. Hence, many of the incidents reported on their site might involve SSN, Medicare numbers, or financial info, but we simply can’t tell because their logs don’t tell us.

Perhaps all of those who track and analyze breaches should consider sending a joint letter to Congress and to HHS urging them to make more information on breaches available on their web site.


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 IncidentsEducation SectorHealth DataMalware

Post navigation

← Nine more breaches newly revealed on HHS's web site
Johnson & Johnson Seeks Access to Medical Records →

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.