DataBreaches.Net

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

Ca: Saskatchewan’s privacy commissioner and Saskatoon Health Region Authority at odds over privacy breach

Posted on August 4, 2015 by Dissent

David Giles reports that Ronald Kruzeniski, Saskatchewan’s information and privacy commissioner (IPC) and the Saskatoon Health Region Authority (SHRA) are at odds over whether disciplinary action taken against a snooping employee should be disclosed.

The dispute arose in the context of an employee who snooped on her own records and five others’ records without a need-to-know.

In the wake of the breach, the IPC had made a number of recommendations to SHRA, which Giles summarizes as:

  1. Suspend employees who have snooped. The length of the suspension should be dependent upon the seriousness and frequency of the snooping;
  2. Monitor employees who have snooped for a period of years instead of months;
  3. Work with eHealth Saskatchewan (eHealth) so that eHealth can audit and monitor the snooper for any electronic system eHealth is a trustee for;
  4. Terminate employees who have snooped intentionally and maliciously;
  5. Report the snooping to the professional regulatory body to whom the employee/practitioner may belong once the snooping has been investigated and substantiated;
  6. Disclose the details of the disciplinary action taken against the employee to the affected individual(s) and to all regional health authority employees and practitioners

Where the sides disagree is on point 6, Giles reports.

Read more about the disagreement on Global News.

Category: Commentaries and AnalysesHealth DataInsiderNon-U.S.

Post navigation

← WA: Labor Department vulnerable to data breach
AU: Sensis publishes hundreds of silent numbers online →

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

  • Ireland’s Data Protection Commission publishes 2024 Annual Report
  • The headlines suggested Freedman Healthcare suffered a ransomware attack that affected patient data. The reality was quite different.
  • Runsafe report: Medical device cyberattacks threaten patient care, strain budgets, top concern for healthcare sector
  • Ryuk ransomware’s initial access expert extradited to the U.S. from Ukraine
  • Alleged Geisinger hacker will defend himself pro se.
  • Tallahassee Memorial Healthcare reveals it was also impacted by Cerner/Legacy Oracle cyberattack
  • Hospital cyberattack investigation complete, no formal review needed (1)
  • Largest Ever Seizure of Funds Related to Crypto Confidence Scams
  • IMPACT: 170 patients harmed as a result of Qilin’s ransomware attack on NHS vendor Synnovis
  • DOJ’s Data Security Program: Key Compliance Considerations for Impacted Entities

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

  • 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
  • DOJ Seeks More Time on Tower Dumps
  • Your household smart products must respect your privacy – including your air fryer
  • Vermont signs Kids Code into law, faces legal challenges
  • Data Categories and Surveillance Pricing: Ferguson’s Nuanced Approach to Privacy Innovation

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.