DataBreaches.Net

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

Inappropriate access to patient records in the VA system: 2010 statistics

Posted on February 24, 2011 by Dissent

Earlier this month, I covered a VA privacy breach incident that had been reported in the Pittsburgh Tribune-Review.  At the time, I noted that it was not clear to me whether the incident had been included in the VA’s monthly report to Congress as I hadn’t seen anything like that case mentioned.

I wrote to the VA, who promptly explained why I had not seen a specific report on the incident:

This incident was rolled up as a mishandling incident and was not included in the August Monthly Report to Congress of Data Incidents (MRCDI). This type of incident is not usually included in the MRCDI, which generally consists of large or unusual breaches, missing equipment and representative cases in the categories of mismailings or mishandlings. The incident was reported to HHS as required by the HITECH Act and the two individuals who accessed the record inappropriately were reported to the human resources department for counseling.

The incident, however, made me realize that we had no specific numbers from the VA on how many cases of employee “snooping” they experience in the course of a year if such instances are rolled up in a broader category of incidents.

Today, a spokesperson for the VA responded to me with that information:

We had 48 incidents of employees intentionally inappropriately accessing records for the calendar year of 2010. The majority of them involved a health-related accident or illness and co-workers checking on the patient’s status. Some involved a media story or article and employees being nosy. A few involved looking at the records of ex boyfriends or ex girlfriends or ex spouses. A few involved spouses, parents, or adult children checking on family members’ appointment times or records.

Does 48 incidents in one year seem like a lot or relatively little to you? While each incident does matter in terms of privacy, given the enormity of the VA system and the number of people who have access to records, my sense is that 48 is not particularly high – although we need to keep in mind that the VA may not be detecting all such inappropriate access incidents.

Thanks to the VA for getting back to me so promptly with the information.


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

← Swiss Prosecutor Releases Person In Credit Suisse Data Theft Case
Cambridge Who’s Who attempt to block former employee from discussing alleged data loss fails in court →

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.