DataBreaches.Net

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

Do your office staff and answering service know how to respond to a notification?

Posted on August 12, 2019 by Dissent

Over the years, there have been numerous occasions when I’ve called a doctor’s office or service  to alert them to a data leak or HIPAA breach.  In some cases, I’ve reached office staff.  In other cases, it may be an answering service.

All too often, however, most of the people who have taken my calls do not seem to know  what to do next. So some ignore my calls and messages, erroneously deciding they are scam or fishy calls (and yes, I use my real name and give a work phone number when I call entities). Others take my call, but then don’t know to whom to transfer it or escalate it. And in some cases, people have actually asked me to call back if people are out to lunch.

Yesterday, another inappropriate response to a notification occurred with yet another medical practice. A surgicenter had misdirected a fax to my fax number days earlier, but I only discovered it on Sunday afternoon.

The fax contained a named patient’s medical history, their ECG, and their surgery schedule.

Although it was Sunday, I promptly called the surgicenter to alert them to their error. My call was answered by a person, and after identifying myself as Dr. [Doe], I told them that the surgicenter had erroneously faxed PHI about [Patient Name] to my office. My call was then transferred to another person.

But rather than just taking the information and relaying it or telling me what they would do next, the second person started to tell me, “Okay. You’ll have to call back after…”

I interrupted her.

“I’m not calling anyone back. This is YOUR HIPAA breach, not mine. I did you the courtesy of alerting you. If your doctors want to know more they can call me at…” And I hung up after repeating my name and phone number.

If you are a covered entity, make sure that your answering service and front-line office personnel know what to do if someone calls to alert you to a HIPAA breach. Do not count on people to call back. And let your staff know what alerts cannot wait until the office re-opens and need to be escalated to you immediately.  To be on the safe side, maybe just instruct them to notify you immediately of any calls claiming that there is a data security or privacy issue.

I cc:d Northwell Health on my tweets about this as this surgicenter is part of their system. Maybe in one of their mailings to all of their providers, they can emphasize the need for such training.

 


Related:

  • Resource: NY DFS Issues New Cybersecurity Guidance to Address Risks Associated with the Use of Third-Party Service Providers
  • TX: Kaufman County Faces Cybersecurity Attack: Courthouse Computer Operations Disrupted
  • Bombay High Court Orders Department of Telecommunications to Block Medusa Accounts After Generali Insurance Data Breach
  • KT Chief to Resign After Cybersecurity Breach Resolution
  • Cyber-Attack On Bectu’s Parent Union Sparks UK National Security Concerns
  • Attorney General James Announces Settlement with Wojeski & Company Accounting Firm
Category: Breach IncidentsCommentaries and AnalysesU.S.

Post navigation

← Delta Airlines sues [24]7.ai over 2017 data breach
NV: Renown Health warns lost thumb drive could put some patient information at risk →

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.