DataBreaches.Net

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

When UPMC wrist ID tells too much

Posted on May 2, 2008October 24, 2024 by Dissent

Steve Twedt of the Pittsburgh Post-Gazette reports:

Linda Berkley of Braddock was playing with her granddaughter Saturday evening when the infant grabbed the identification bracelet Mrs. Berkley had received earlier in the day at the UPMC Braddock emergency room.

As she pulled her arm away, Mrs. Berkley glanced at the bracelet and was horrified by what she saw — her full name, her full Social Security number, her birth date and her insurance policy number.

“If my granddaughter hadn’t been playing with it, I would have just clipped it off and thrown it away,” she said.

In an age when identity theft stories play out regularly on the nightly news, Mrs. Berkley said she was “shocked” that the hospital would put such sensitive personal information on ID bracelets. She said the information also was included in her discharge papers.

[…]

John Houston, UPMC vice president for privacy and information security, said the medical center issues new medical record numbers for new patients, but it still uses Social Security numbers for those already in the system, unless the patient requests a new number. Processing those requests can take several days.

“We are actively looking at methods to reduce our use of the SSN [Social Security number] as the MRN [medical record number], as well as to reduce the ‘display’ of the MRN on such items as the wristband,” Mr. Houston said in an e-mail statement.

Full story – Pittsburgh Post-Gazette

Category: Health Data

Post navigation

← UCSF waited six months before telling patients of data breach
Medical privacy still isn't protected (Letter to the Editor) →

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

  • Supplier to major UK supermarkets Aldi, Tesco & Sainsbury’s hit by cyber attack with ransom demand
  • UK: Post Office to compensate hundreds of data leak victims
  • How the Signal Knockoff App TeleMessage Got Hacked in 20 Minutes
  • Cocospy stalkerware apps go offline after data breach
  • Ex-NSA bad-guy hunter listened to Scattered Spider’s fake help-desk calls: ‘Those guys are good’
  • Former Sussex Police officer facing trial for rape charged with 18 further offences relating to computer misuse
  • Beach mansion, Benz and Bitcoin worth $4.5m seized from League of Legends hacker Shane Stephen Duffy
  • Fresno County fell victim to $1.6M phishing scam in 2020. One suspected has been arrested, another has been indicted.
  • Ransomware Attack on ADP Partner Exposes Broadcom Employee Data
  • Anne Arundel ransomware attack compromised confidential health data, county 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

  • Police secretly monitored New Orleans with facial recognition cameras
  • Cocospy stalkerware apps go offline after data breach
  • Drugmaker Regeneron to acquire 23andMe out of bankruptcy
  • Massachusetts Senate Committee Approves Robust Comprehensive Privacy Law
  • Montana Becomes First State to Close the Law Enforcement Data Broker Loophole
  • Privacy enforcement under Andrew Ferguson’s FTC
  • “We would be less confidential than Google” – Proton threatens to quit Switzerland over new surveillance law

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.