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.

 

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

  • CoinMarketCap Hacked, Scrambles to Remove Malicious Wallet Verification Popup
  • Montana Attorney General launches investigation into Lee Enterprises data breach
  • AT&T gets preliminary approval for $177 million data breach settlement
  • Aflac notifies SEC of breach suspected to be work of Scattered Spider
  • Former JBLM soldier pleads guilty to attempting to share military secrets with China
  • No, the 16 billion credentials leak is not a new data breach — a wake-up call about fake news (Updated)
  • Tonga’s health system hit by cyberattack (1)
  • Russia Expert Falls Prey to Elite Hackers Disguised as US Officials
  • Proposed class action settlement in In re Netgain Technology litigation
  • Qilin Offers “Call a lawyer” Button For Affiliates Attempting To Extort Ransoms From Victims Who Won’t Pay

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

  • The Markup caught 4 more states sharing personal health data with Big Tech
  • Privacy in the Big Sky State: Montana’s Consumer Privacy Law Gets Amended
  • UK Passes Data Use and Access Regulation Bill
  • Officials defend Liberal bill that would force hospitals, banks, hotels to hand over data
  • US Judge Invalidates Biden Rule Protecting Privacy for Abortions
  • DOJ’s Data Security Program: Key Compliance Considerations for Impacted Entities
  • 23andMe fined £2.31 million for failing to protect UK users’ genetic data

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.