DataBreaches.Net

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

Firewall error by M2ComSys exposed 32,000 patients' information (Update 1)

Posted on August 9, 2013 by Dissent

A vendor’s firewall error has resulted in approximately 32,000 patients in 48 states being notified that some of their protected health information was exposed on the Internet.  The vendor was medical transcription service M2ComSys, contracted by Cogent Healthcare. The latter provides physicians called hospitalists to hospitals operated by Genesis Health Systems. Neither Genesis Health Systems or Cogent Healthcare were directly responsible for the breach, which occurred when the vendor’s firewall was down between May 5 and June 24.

Deirdre Cox Baker reports on the local impact in Iowa, where 1,164 patients are being notified:

No Social Security numbers, credit or banking information were involved, said Ken Croken, a spokesman and vice president for Davenport-based Genesis.

What was involved was information about individual patient cases that was discussed between hospitalists and primary care physicians. This includes dictation of follow-up care information, or “care notes,” for the patient’s regular physician.

Getahn Ward reports from Tennessee, where fewer were affected. He explains:

The accessible information included care notes with varying combinations such as physician’s name, patient date of birth, diagnosis description, summary of treatment provided, medical history and medical record number, but it didn’t include copies of the patients’ medical records or Social Security numbers, the company said.

Cogent is providing notification to affected patients and is offering them a year of credit monitoring services, even though it is not aware of any records being accessed or misused.

The firm has terminated its contract with M2ComSys.

Update 1: A template of Cogent’s notification letter to patients was submitted to California, and is available here.  The letter explains, in part:

Cogent Healthcare, Inc. also began a full-scale investigation to determine how the incident occurred and to determine which data and individuals were involved. The care notes were first accessed on May 5, 2013. Access to the site ended on June 24, 2013. We are generally unable to identify who accessed the notes. In some cases, the notes were indexed by Google.

In addition to the forensic investigation, Cogent also took other steps:

We have ended our relationship with M2 and taken physical possession of the hardware held by M2 that stored our PHI. We have confirmed with Google that it has removed all evidence of PHI from their files. We have initiated a security review of other Cogent Healthcare, Inc. vendors who have access to PHI to confirm their security procedures.

In an attachment to the letter, Cogent lists all of its entities that have been impacted by the breach:

  • Cogent Healthcare of California, P.C.
  • Cogent Healthcare of Washington, P.C.
  • Cogent Healthcare of Ocala, L.L.C.
  • Cogent Medical Care, P.C.
  • Cogent Healthcare of Texas, P.A.
  • Endion Medical Healthcare, P.C. d/b/a Endion SeniorCare
  • Cogent Healthcare of Montana, P.C.
  • Cogent Healthcare of Arizona, P.C.
  • Cogent Healthcare of Georgia, P.C.
  • Cogent Healthcare of Iowa, P.C.
  • Cogent Healthcare of New Jersey, P.C.
  • Inpatient Specialists of Southwest Florida, LLC
  • Cogent Healthcare of Kentucky, P.S.C.
  • Cogent Healthcare of Wisconsin, S.C.
  • Comprehensive Hospital Physicians of Florida, Inc.
  • Cogent Healthcare, Inc.
  • Cogent Healthcare IPA of New York, Inc.
  • Cogent Healthcare of Brockton, P.C.
  • Cogent Healthcare of North Carolina, P.C.
  • Cogent Healthcare of South Carolina, P.C.
  • Cogent Healthcare of Daly City, P.C.
  • Cogent Healthcare of Jackson, MS, LLC
  • Cogent Healthcare of Pensacola, L.L.C.
  • Cogent Healthcare of Pennsylvania, Inc.

It’s a very impressive breach response and notification letter.


Related:

  • JFL Lost Up to $800,000 Weekly After Cyberattack, CEO Says No Patient or Staff Data Was Compromised
  • Massachusetts hospitals Heywood, Athol say outage was a cybersecurity incident
  • Heritage Provider Network $49.99M Class Action Settlement
  • Integris Health Agrees to $30 Million Settlement Over 2023 Data Breach
  • They were victims of a massive data breach in 2009. Interior Health denied it for a decade.
  • Watsonville Community Hospital had a data breach -- or two. It would be helpful to know which.
Category: Health Data

Post navigation

← Smartphone Experts notifies customers of hack (Update 5)
LulzSec Hacker Gets Year in Prison for Sony Attack →

1 thought on “Firewall error by M2ComSys exposed 32,000 patients' information (Update 1)”

  1. Anonymous says:
    August 13, 2013 at 7:52 pm

    CLASS-ACTION! Medical history???? I would have preferred my social security number listed!!! I’M PISSED!!!!!!!!

Comments are closed.

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

  • 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
  • Always watching: How ICE’s plan to monitor social media 24/7 threatens privacy and civic participation

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.