DataBreaches.Net

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

Case Note 210870 [2010] NZ Priv Cmr 24 : Medical centre fails to establish identity of requester and discloses health information about a patient to their former partner

Posted on January 12, 2011 by Dissent

From the Office of the Privacy Commissioner of New Zealand:

A man, M, who was involved in legal proceedings with his former partner, X, was a patient of a medical centre. The medical centre previously provided medical care to M and his family when he and X were still together.

X visited the medical centre with her new partner, N, and they requested historical information about the family and, in particular, an incident which involved one of the children a number of years before.

The medical centre assumed that N was M and so released all of the health information held about M, X and the children to the couple. This included a separate file relating to M which contained highly sensitive information about an anxiety disorder he was suffering from.

X then attached the information obtained from the medical centre to an affidavit presented to the Family Court in an attempt to show M as a bad parent. M was humiliated by the disclosure.

Rule 5 of the Health Information Privacy Code requires health agencies, such as the medical centre, to ensure that health information is protected, by reasonable security safeguards, against unauthorised disclosure.

In addition, section 45(a) of the Privacy Act requires agencies ensure that a requester is appropriately identified before providing them with personal or health information.

Rule 11 expects that a health agency shall not disclose health information to any individual unless the agency believes on reasonable grounds that an exception applies.

Here, the medical centre made an assumption that N was M and took no steps to ensure that this assumption was correct. Instead, it disclosed highly sensitive information about M to X and N.

We were satisfied that the medical centre breached rule 5 as it lacked the procedures and processes to ensure that steps were always taken to establish identity before releasing health information.

We were also satisfied that the disclosure of this information breached rule 11 as no exception applied to allow the medical centre to disclose the information.

We formed the view that the disclosure of M’s information to X and N caused M significant harm and we conveyed this view to the medical centre.

The medical centre accepted that its procedures were lacking, made extensive changes to its policy regarding the identification of information requesters, and trained its staff in their obligations under the Code.

The medical centre also agreed to apologise directly to M for its actions, pay him financial compensation and provide him and his children with free medical services for a set period of time.

We were satisfied with the steps that the medical centre took to ensure that the mistakes made with M’s health information were not repeated. M was satisfied with the settlement proposal that the medical centre offered to him personally. We closed our file.

Read more on Privacy.org.nz

H/T, @JCELaw


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

← UK: Dorset HealthCare Trust send confidential health faxes by mistake
(update) Vodafone fires staff after security breaches →

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.