DataBreaches.Net

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

St. Mary’s Hospital Campus in Jefferson City notifies 301,000 of limited PHI left behind in a 2014 move

Posted on August 7, 2018 by Dissent

And this is why I always wait to close out monthly stats in healthcare.  The following incident just showed up on HHS’s public breach tool today as having been reported to them on July 30, and affecting 301,000 patients. St. Mary’s Hospital’s notice, below, indicates that the entity was not sure of the number affected. 

JEFFERSON CITY, MO – On June 1, 2018, SSM Health St. Mary’s Hospital – Jefferson City was notified that documents and other materials containing patient information were discovered in isolated locations at the former hospital campus, while it was being readied for demolition. Upon notification, SSM Health promptly secured the information and launched an immediate investigation.

St. Mary’s Hospital has confirmed that all formal medical records were safely and securely transferred prior to the move to the new facility on November 16, 2014. The type of information located at the old facility largely consisted of administrative and operational supporting documents for various departments. The documents included demographic, financial, and/or clinical data, but in most instances involved very limited information such as name or medical record number alone. A comprehensive review of the recovered information is underway, and the hospital has also retained a document services firm to assist in cataloging all recovered documents.

Although at all times security safeguards and deterrents were in place to protect the facility, the investigation has confirmed that the safeguards were not adequate to ensure the security of the patient information and other materials with absolute confidence between the date of the move until the date that the hospital was notified on June 1, 2018.  For this reason, we are notifying affected individuals out of an abundance of caution.  Given the age and type of information recovered, the hospital does not yet have a reliable estimate of the number of individuals impacted, however it’s actively working to identify every patient whose information has been recovered.

With the recovery of the patient information, SSM Health feels that this incident does not represent a significant risk to patients, however, it does constitute a privacy breach under Health Insurance Portability and Accountability Act (HIPAA). The Office for Civil Rights has been notified, and St. Mary’s is in the process of sending notification letters containing additional information to the impacted patients who can be identified and located.

The hospital is also reviewing and revising its policies and procedures regarding proper record storage, retention and destruction, as necessary. “We are taking immediate steps to resolve this situation and prevent something similar from ever happening again,” said Phil Gustafson, interim regional president of Operations, SSM Health of Mid-Missouri. “We take very seriously our role of safeguarding our patients’ personal information, and deeply regret any inconvenience or concern this situation may cause our patients.”

If patients have additional questions, they can call toll-free 1-888-648-8404 to get more information.

###

SOURCE: SSM Health St. Mary’s Hospital – Jefferson City


Related:

  • Protected health information of 462,000 members of Blue Cross Blue Shield of Montana involved in Conduent data breach
  • TX: Kaufman County Faces Cybersecurity Attack: Courthouse Computer Operations Disrupted
  • Attorney General James Announces Settlement with Wojeski & Company Accounting Firm
  • JFL Lost Up to $800,000 Weekly After Cyberattack, CEO Says No Patient or Staff Data Was Compromised
  • Before Their Telegram Channel Was Banned Again, ScatteredLAPSUS$Hunters Dropped Files Doxing Government Employees (2)
  • Massachusetts hospitals Heywood, Athol say outage was a cybersecurity incident
Category: ExposureHealth DataPaperU.S.

Post navigation

← FCC admits it was never actually hacked
Telemedicine company exposed data of more than 2 millions patients in Mexico →

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

  • Lawmakers Warn Governors About Sharing Drivers’ Data with Federal Government
  • 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

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.