DataBreaches.Net

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

University of Missouri Health Care breach involved 1,288 patients’ payment billing information

Posted on August 19, 2011 by Dissent

University of Missouri Health Care recently notified HHS of a breach involving the records on 1,288 patients. According to a news release on their web site issued June 21:

University of Missouri Health Care and the University of Missouri Police Department are investigating a missing package containing patient billing information.

On June 14, University of Missouri Health Care officials failed to receive an expected delivery of copies of patient payment information and immediately notified the MU Police Department. In addition, University of Missouri Health Care officials immediately began a review to identify and notify the patients whose information was missing.

The health system sent letters today notifying 1,288 patients whose billing information was included in the missing package.

The package had been sent by private courier to University of Missouri Health Care from a Kansas City bank that serves as the clearinghouse for MU Health Care’s billing. The contents of the missing package included copies of payments received by the bank between June 6-13.

Patients with questions can get more information at http://www.muhealth.org/ProtectedInformation or they can call Cheryl Hopson, supervisor of joint customer service, at (573) 882-2013 or (800) 877-2372 or Misty Woods, service coordinator of joint customer service, at (573) 884-1983 or (800) 877-2372.

University of Missouri Health Care has terminated its contract with the courier responsible for delivering the missing package.

“Safeguarding the privacy of patient information is our top priority, and to that end, we have taken immediate action steps to investigate the missing information, notify the patients affected and help the patients protect their accounts from identify theft,” said Jim Ross, chief executive officer.

According to the FAQ on the incident:

The contents of the missing package included copies of payments received by the bank between June 6-13 for 1,288 patients of University of Missouri Health Care. No Social Security numbers were included in these documents, and no cash or checks are missing. The type of information missing included bank account numbers, partial credit card numbers, and names and addresses. We notified the patients individually by letter June 21.

The University advised those affected to change their bank account numbers and/or credit card numbers:

To guard against the possibility of identity theft, we are advising the patients whose information was included in this package that they may want to contact their banks to change account numbers or contact their credit card companies to request new cards be issued.

The University also offered those affected discounted credit protection services through Experian.


Related:

  • US company with access to biggest telecom firms uncovers breach by nation-state hackers
  • 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
  • NY: Gloversville hit by ransomware attack, paid ransom
  • 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.
Category: Breach IncidentsEducation SectorHealth DataLost or MissingSubcontractorU.S.

Post navigation

← University of Missouri Health Care reports breach affecting 1,288 patients' payment billing information
WARNING: 44,000+ hotmails, yahoos, facebooks and more leaked by @neatstuffs..!! →

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

  • Suspected Russian hacker reportedly detained in Thailand, faces possible US extradition
  • Did you hear the one about the ransom victim who made a ransom installment payment after they were told that it wouldn’t be accepted?
  • 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

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.