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:

  • Two more entities have folded after ransomware attacks
  • Data breach feared after cyberattack on AMEOS hospitals in Germany
  • Premier Health Partners issues a press release about a breach two years ago. Why was this needed now?
  • Theft from Glasgow’s Queen Elizabeth University Hospital sparks probe
  • North Country Healthcare responds to Stormous's claims of a breach
  • Texas Enacts Electronic Health Record Data Localization Law
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

  • Scattered Spider Hijacks VMware ESXi to Deploy Ransomware on Critical U.S. Infrastructure
  • Hacker group “Silent Crow” claims responsibility for cyberattack on Russia’s Aeroflot
  • AIIMS ORBO Portal Vulnerability Exposing Sensitive Organ Donor Data Discovered by Researcher
  • Two Data Breaches in Three Years: McKenzie Health
  • Scattered Spider is running a VMware ESXi hacking spree
  • BreachForums — the one that went offline in April — reappears with a new founder/owner
  • Fans React After NASCAR Confirms Ransomware Breach
  • Allianz Life says ‘majority’ of customers’ personal data stolen in cyberattack (1)
  • Infinite Services notifying employees and patients of limited ransomware attack
  • The safe place for women to talk wasn’t so safe: hackers leak 13,000 user photos and IDs from the Tea app

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

  • Congress tries to outlaw AI that jacks up prices based on what it knows about you
  • Microsoft’s controversial Recall feature is now blocked by Brave and AdGuard
  • Trump Administration Issues AI Action Plan and Series of AI Executive Orders
  • Indonesia asked to reassess data privacy terms in new U.S. trade deal
  • Meta Denies Tracking Menstrual Data in Flo Health Privacy Trial
  • Wikipedia seeks to shield contributors from UK law targeting online anonymity
  • British government reportedlu set to back down on secret iCloud backdoor after US pressure

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.