DataBreaches.Net

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

70,000 Adventist Health Tulare patients being notified of HIPAA breach by payment collections associate

Posted on June 9, 2024 by Dissent

Adventist Health Tulare has issued a press release about a breach at a business associate in Nebraska.

The June 7 press release states, “A data security incident was recently discovered by Signature Performance, an agency working on behalf of Adventist Health Tulare to collect payment for services.”

Their investigation determined that an unknown party accessed certain files on Signature Performance’s network. “Signature Performance discovered that more than 70,000 patients were affected by this breach. Every case is different for each patient, and each patient will receive a letter from Signature Performance regarding what information is impacted,” they write.

A copy of the full statement can be found on Adventist Health’s website. It is not linked from Adventist Health’s homepage or from Adventist Health Tulare’s home page, and it is not linked from their News section. Given that patients may not recognize the name Signature Performance as a return address on postal mail, Adventist should have a prominently linked notice on its website to make patients aware they may be receiving mail from Signature Performance.

What we don’t know so far

A careful reading of the press release suggests at least two gaps in our understanding of this incident, apart from obvious questions such as how the attacker gained access.

When did Signature Performance first discover the breach of their system?

Adventist Health says that Signature Performance “recently discovered….” What do they mean by “recently?”  DataBreaches notes that in February of this year, Signature Performance notified the Maine Attorney General’s Office of a breach that reportedly affected 7,122 people. That breach occurred between January 17 and January 18 and was discovered on January 18, 2024.

Is this the same incident that Adventist Health Tulare is now reporting as recently discovered, or is this a second or new incident at Signature Performance? DataBreaches submitted a contact form inquiry to Signature Performance today to ask if the incident reported by Adventist Health Tulare is the same incident they reported to Maine in February. No reply has been received as yet.

When did Signature Performance first notify Adventist Health of the breach?

Adventist’s press release does not disclose when Signature Performance first notified them of the breach. Signature Performance is sending out the individual notification letters, but when was Adventist first notified? Have they known about this since January or February, or is this really a new incident and they were only very recently notified?


Related:

  • 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.
  • Toys “R” Us Canada customers notified of breach of personal information
  • Gatineau gymnastics centre warns members of possible data breach
  • Data breach in 42 Latvian municipalities: DVI imposes 300,000 euro fine on ZZ Dats
  • Confidence in ransomware recovery is high but actual success rates remain low
Category: Commentaries and AnalysesHackHealth DataSubcontractorU.S.

Post navigation

← Christie’s discloses cyberattack in May
RansomHouse: investigation and findings by Analyst1 →

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

  • 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
  • The Case for Making EdTech Companies Liable Under FERPA
  • NHS providers reviewing stolen Synnovis data published by cyber criminals

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

  • 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
  • Who’s watching the watchers? This Mozilla fellow, and her Surveillance Watch map

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.