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 posts:

  • California fines 7 more entities for unauthorized access to patient info by employees
  • Quest Records LLC breach linked to TheDarkOverlord hacks; more entities investigate if they’ve been hacked
  • Updating: CaptureRx incident impacted more than 2.4 million. List of Entities.
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

  • Qantas customers involved in mammoth data breach
  • CMS Sending Letters to 103,000 Medicare beneficiaries whose info was involved in a Medicare.gov breach.
  • Esse Health provides update about April cyberattack and notifies 263,601 people
  • Terrible tales of opsec oversights: How cybercrooks get themselves caught
  • International Criminal Court hit with cyber attack during NATO summit
  • Pembroke Regional Hospital reported canceling appointments due to service delays from “an incident”
  • Iran-linked hackers threaten to release emails allegedly stolen from Trump associates
  • National Health Care Fraud Takedown Results in 324 Defendants Charged in Connection with Over $14.6 Billion in Alleged Fraud
  • Swiss Health Foundation Radix Hit by Cyberattack Affecting Federal Data
  • Russian hackers get 7 and 5 years in prison for large-scale cyber attacks with ransomware, over 60 million euros in bitcoins seized

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

  • The Trump administration is building a national citizenship data system
  • Supreme Court Decision on Age Verification Tramples Free Speech and Undermines Privacy
  • New Jersey Issues Draft Privacy Regulations: The New
  • Hacker helped kill FBI sources, witnesses in El Chapo case, according to watchdog report
  • Germany Wants Apple, Google to Remove DeepSeek From Their App Stores
  • Supreme Court upholds Texas law requiring age verification on porn sites
  • Justices nix Medicaid ‘right’ to choose doctor, defunding Planned Parenthood in South Carolina

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.