DataBreaches.Net

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

Ca: Hamilton’s Paramedic Service mistakenly sent patient info to wrong hospitals

Posted on February 6, 2024 by Dissent

Roger Collins reports:

The Hamilton Paramedic Service says it has been mistakenly sending the personal information of some of its patients to the wrong hospital.

Over the last four years, according to the municipal healthcare service, some paramedics have accidentally selected the incorrect hospital when submitting a patient’s records in correspondence to where they were being transported.

An out-of-city hospital flagged the issue in late October after they received patient records for someone who wasn’t in their care.

Once the Hamilton Paramedic Service was made aware of the issue, it began an internal review to determine the cause and extent of the breach.

According to a spokesperson with the City of Hamilton, 306,000 patient health records were looked over during the audit.

Of those 306,000 records, it was determined that only 162 patients were affected.

No personal information was ever made publicly available.

Read more at CHCH.com, while I ponder the “only 162 were affected.” ONLY 162??? That’s a lot of people who suffered a medical privacy breach.

Category: ExposureHealth DataNon-U.S.

Post navigation

← Millions at risk of fraud after massive health data hack in France
HHS’ Office for Civil Rights Settles Malicious Insider Cybersecurity Investigation for $4.75 Million →

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

  • 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
  • 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
  • UBS reports data leak after cyber attack on provider, client data unaffected
  • Scania confirms insurance claim data breach in extortion attempt

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

  • 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
  • Anne Wojcicki Wins Bidding for 23andMe

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.