DataBreaches.Net

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

With No Harm Threshold, Nearly All Breaches Substantiated in CA

Posted on August 26, 2010 by Dissent

Dom Nicastro provides some interesting data from California, where there is no “harm threshold” in mandated reporting requirements for breaches involving medical records:

Since California’s new law went into effect last year, the state has received 3,766 breach reports.

…. California’s investigations team has completed reviews of 1,953. It found that 98.7% of those breaches were found to be “substantiated medical breaches.”

Of course, if we left it up to entities to determine if sufficient risk of harm existed to warrant notification, we’d see substantially fewer breach reports and notifications to individuals. And that might be a good thing, according to attorney Jeff Drummond, whom Nicastro quotes in his article. Drummond raises the issue of worrying people needlessly and “notification fatigue” whereby we might get so many notifications that we fail to take action when we really need to. Of course, those arguments continue to miss the point that in a relationship of trust where confidentiality is crucial, patients have a right to know when the person they trusted to guard their private information failed to do so. How else can they decide whether to continue using that provider or not? The risk of ID theft is not the sole nor even most important reason for notifying people of breaches, despite Congress’s emphasis on ID theft or financial fraud.

Nicastro also reports some interesting findings from the breach reports California has investigated, noting that as of May 31, the state has been able to investigate 51.8 percent of the cases reported:

  • 2,914: Unintentional breach to person outside facility/healthcare system. Example: A patient’s prescription is faxed to the wrong number and ends up in a lawyer’s office instead of the corner pharmacy.
  • 559: Unintentional breach by healthcare worker within the facility/healthcare system. Example: A nurse faxes a patient record to cardiology instead of radiology.
  • 147: Malicious breach by healthcare worker. A healthcare worker looks at the medical record of a patient without any medical reason to do so.
  • 125: Breach of computer system theft, loss of electronic device/ medical records. Example: A hospital laptop is stolen from an employee’s personal car.
  • 21: Malicious breach by person other than a healthcare worker. Example: Someone visiting the hospital sees a medical file on a desk and decides to pick it up and start reading.

Of those classifications, the unintentional breach within the facility is probably the only group where I might agree that notification to individuals might not be necessary as other hospital employees are also bound to confidentiality.

Read more on Nicastro’s article on HealthLeaders Media.


Related:

  • Safaricom-Backed M-TIBA Victim of a Possible Data Breach Affecting Millions of Kenyans
  • Another plastic surgery practice fell prey to a cyberattack that acquired patient photos and info
  • Two U.K. teenagers appear in court over Transport of London cyber attack
  • ModMed revealed they were victims of a cyberattack in July. Then some data showed up for sale.
  • JFL Lost Up to $800,000 Weekly After Cyberattack, CEO Says No Patient or Staff Data Was Compromised
  • Massachusetts hospitals Heywood, Athol say outage was a cybersecurity incident
Category: Health Data

Post navigation

← Moffitt reviewing 492 patient records in privacy breach
OH: Woman Charged With Stealing ID of Job-Seekers →

1 thought on “With No Harm Threshold, Nearly All Breaches Substantiated in CA”

  1. Anonymous says:
    August 26, 2010 at 1:08 pm

    I can’t agree enough with the author. I’m a major a proponent for disclosure. We may risk de-sensitizing the consumer/patient to breaches, but that perspective comes primarily from an identity theft or financial harm point of view. The situation is very different where the disclosure of healthcare data can cause “irreparable harm” [Institute of Medicine] to a patient’s reputation or emotional state. A patient has the right to know of a breach and determine for themselves the implications of harm. If we have too many disclosures, the problem is not disclosures but the situation creating the disclosures. The other benefit to disclosures is that we are finally getting transparency around the issues in the industry. For a security professional is this very helpful in better understanding our exposures and establishing commensurate controls.

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

  • Suspected Russian hacker reportedly detained in Thailand, faces possible US extradition
  • Did you hear the one about the ransom victim who made a ransom installment payment after they were told that it wouldn’t be accepted?
  • 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

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

  • Lawmakers Warn Governors About Sharing Drivers’ Data with Federal Government
  • 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

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.