DataBreaches.Net

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

Can entities name rogue employees in disclosing a breach? Maybe.

Posted on September 13, 2011 by Dissent

I’ve often commented how entities shield the names of rogue employees or contractors.  Here’s a letter to an editor  from Ann Cavoukian, Information Privacy Commissioner for Ontario, about the paper’s coverage of an insider privacy breach:

Your article suggests the North Bay and District Hospital was unable to reveal to patients the name of the nurse who had inappropriately accessed their files. Why?

The reason given was the privacy of the nurse. To be clear, in my orders under the Personal Health Information Protection Act (PHIPA) I have consistently said that an individual whose health record has been accessed by an unauthorized staff person has a right to know how the organization has responded to the breach.

Privacy considerations do not prevent the identity of the staff member responsible for the breach being disclosed to the affected individuals.

In this case, there were most likely other reasons why the hospital chose not to identify the responsible nurse, for example, their human resources practices. However, privacy is not the problem – it does not present a barrier to such disclosure.

Ann Cavoukian

Information Privacy Commissioner

Update: The paper now reports that the hospital will reveal the name – but only to those who have received notification letters.

Category: Health Data

Post navigation

← Panda Security Hacked and Defaced by X-NerD
New HIPAA rules won’t enhance privacy, but they will burden physicians →

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

  • McLaren provides written notice to 743,131 patients after ransomware attack in July 2024
  • A state forensics lab was leaking its files. Getting it locked down involved a number of people.
  • CoinMarketCap Hacked, Scrambles to Remove Malicious Wallet Verification Popup
  • Montana Attorney General launches investigation into Lee Enterprises data breach
  • AT&T gets preliminary approval for $177 million data breach settlement
  • Aflac notifies SEC of breach suspected to be work of Scattered Spider
  • Former JBLM soldier pleads guilty to attempting to share military secrets with China
  • No, the 16 billion credentials leak is not a new data breach — a wake-up call about fake news (Updated)
  • Tonga’s health system hit by cyberattack (1)
  • Russia Expert Falls Prey to Elite Hackers Disguised as US Officials

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

  • The Markup caught 4 more states sharing personal health data with Big Tech
  • Privacy in the Big Sky State: Montana’s Consumer Privacy Law Gets Amended
  • UK Passes Data Use and Access Regulation Bill
  • Officials defend Liberal bill that would force hospitals, banks, hotels to hand over data
  • US Judge Invalidates Biden Rule Protecting Privacy for Abortions
  • DOJ’s Data Security Program: Key Compliance Considerations for Impacted Entities
  • 23andMe fined £2.31 million for failing to protect UK users’ genetic data

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.