DataBreaches.Net

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

CCRM Dallas-Fort Worth Notifies Patients of Data Security Incident

Posted on December 16, 2018 by Dissent


CCRM Dallas-Fort Worth has become aware of a potential data security incident that may have resulted in the inadvertent exposure of patients’ personal and health information. Although at this time there is no indication that an unauthorized party actually accessed or viewed patient information or evidence of patient information being misused, we have taken steps to notify anyone who may have been affected by this incident.


On October 4, 2018, we discovered that a former nurse’s email account had been accessed by an unknown, unauthorized third party. Upon learning that some patients had received spam email messages from the nurse’s account, the practice immediately contacted its IT vendor to deactivate the account and determine what information may have been impacted. The investigation determined that an intruder could have viewed or accessed patients’ names, addresses, email addresses, health information, insurance information and medical history within the account, and for a limited number of patients, Social Security numbers and driver’s license numbers.


Although there is no evidence that an unauthorized third party actually viewed or accessed patient health information and we are not aware of anyone’s information being misused, we take your privacy and security very seriously and have taken steps to prevent a similar event from occurring in the future. Notification letters mailed on December 3, 2018 include additional information about what happened and a toll-free number where patients can learn more about the incident. The call center is available Monday through Friday between 10 AM to 10 PM Central at 1-800-939-4170.


The privacy and security of patient information is a top priority for CCRM, which deeply regrets any inconvenience or concern this incident may cause.

Source:  CCRM.    According to HHS’s public breach tool, 1,117 patients were notified of this incident.  Again, why is so much ePHI in an employee’s email account? Was it really all needed for that week or was some of it already addressed and maybe should have been transferred to secure storage or other files? 

Great thanks to “Russy,” who found this one when I couldn’t find it.


Related:

  • KT Chief to Resign After Cybersecurity Breach Resolution
  • Cyber-Attack On Bectu’s Parent Union Sparks UK National Security Concerns
  • A business's cyber insurance policy included ransom coverage, but when they needed it, the insurer refused to pay. Why?
  • Before Their Telegram Channel Was Banned Again, ScatteredLAPSUS$Hunters Dropped Files Doxing Government Employees (2)
  • Attorney General James Secures $14.2 Million from Car Insurance Companies Over Data Breaches
  • Months After Being Notified, a Software Vendor is Still Exposing Confidential and Sealed Court Records
Category: Breach Incidents

Post navigation

← NYS A.G. Underwood Announces Settlements With Five Companies Whose Mobile Apps Failed To Secure User Information Transmitted Over The Internet
How To Protect Healthcare Records In A Zero Trust World →

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.