DataBreaches.Net

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

Alberta's Privacy Commissioner launches privacy breach investigations

Posted on January 25, 2014 by Dissent

From the no-surprise dept., Alberta’s Privacy Commissioner announced an investigation into the Medicentres breach affecting 620,000:

Information and Privacy Commissioner Jill Clayton has confirmed that she will launch an investigation into the recently reported Medicentres privacy breach, as well as a broader review of the way privacy breaches are reported in the health sector in this province.

Commissioner Clayton released the following statement:

“This incident raises concerns about how privacy breaches are reported generally. Therefore, in addition to the Medicentres investigation, we will also be conducting a thorough review of the broader issue of privacy breach reporting by the health sector in Alberta.

“The Minister has encouraged individuals who have been personally affected by this breach to file complaints with my office and I would like to reinforce that message. I would also like to address the recent questions raised about why the information was not released to the public sooner.

“Currently, there are no provisions under Alberta’s Health Information Act (HIA) requiring a health custodian to report a breach to my Office or notify affected individuals. When we do receive reports of this nature, it is done on a voluntary basis. Decisions about when and if affected individuals will be notified of a breach are the responsibility of the custodian. I have no authority to require custodians to notify affected individuals.

“When a custodian self-reports a breach to the OIPC, we work with them to assess the potential risk and make recommendations about how to respond to the breach and prevent a similar incident in the future. When there is the potential for harm to individuals, it is always our practice to recommend immediate, direct notification to all affected parties.

“In terms of reporting these incidents to the public or the Government of Alberta, I have no authority to do so. Section 91(1) of the Health Information Act (HIA) prohibits me from releasing any information obtained in performing my duties, powers, and functions under the Act.

“Under Alberta’s private sector privacy law, the Personal Information Protection Act (PIPA), organizations must report a breach of personal information to my Office where they determine there is a real risk of significant harm to an individual. In such a case, I can require the organization to notify affected individuals.

“I have advocated in the past for mandatory breach reporting and notification provisions to be added to the FOIP Act, most recently in my submissions to the FOIP Act review. This case is an important reminder of the need for these types of provisions in the Health Information Act as well and I will be formally asking the government to consider such an amendment. The extension of the mandatory breach notification to the public and health sectors will strengthen the protection of privacy legislation in Alberta.


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

← Data security breach hits Portland-area employees of PCC Structurals (updated)
NY: Audit of charter school finds serious IT security deficiencies →

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

  • 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
  • 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

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

  • 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
  • Always watching: How ICE’s plan to monitor social media 24/7 threatens privacy and civic participation

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.