DataBreaches.Net

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

HIPAA, Twitter, and the Siren's Call

Posted on October 14, 2010 by Dissent

After my dismay at how a breach seemed to be casually revealed on Twitter last weekend, I thought I’d keep an eye out for situations in which use of social media might raise the specter of the HIPAA privacy rule. In the example below, I do not think that the twitterer violated the rule in any particular tweet nor in the aggregate,  but when we start to aggregate information, it becomes increasingly possible that someone might recognize themselves or a family member.   Indeed, I wouldn’t be surprised if others looked at the same situation and argued that there has been a HIPAA violation. See what you think:

In response to the above tweets, another twitterer replied, “Nd u just violated #hipaa.”

The original twitterer responded, “you clearly don’t know HIPPA then, I never mentioned any names.”

Ignoring, for the moment, my wholly untested hypothesis that people who spell the HIPAA acronym correctly are more likely to comply with it, who’s right?

We all know that it’s possible to identify a patient without using their name, but the twitterer may well be correct that she didn’t violate HIPAA by her tweets.  So far, all that’s been revealed is the date of the tweet, that it was an emergency room, and the time period during which the patients were seen in the ER.

But does the fact that the twitterer provides a picture of herself in her profile increase the risk of knowing who the patients are or of the patients recognizing themselves in her tweet?

And does it matter that she  gives  latitude and longitude/GPS coordinates in her profile?

I haven’t checked, but suppose it turned out to be a small community with only one hospital in the area.  Would that make a difference in both the risk of identifying patients or patients recognizing themselves as being one of the people she tweeted about?

We can probably all share the  twitterer’s desire to discuss something that was unusual at work.  There are times we may want to vent, or we may have a really unusual case that we’re tempted to share.  Resisting the siren’s call to tweet or share in a world where the repeated message is “share more” can become increasingly difficult.   But contrast her tweets to that of  another twitterer who tweeted earlier the same day:

Two different twitterers. Both with something they wanted to talk about, but two different decisions as to whether to say anything in a public space or not.

Given the risks inherent in posting anything in social media that refers to patients, I  think the second twitterer has chosen the more prudent path.


Related:

  • Former U.S. Soldier Pleads Guilty to Hacking and Extortion Scheme Involving Telecommunications Companies
  • DOGE Denizen Marko Elez Leaked API Key for xAI
  • Four people bailed after arrests over cyber attacks on M&S, Co-op and Harrods
  • Texas Enacts Electronic Health Record Data Localization Law
  • United Australia Party confirms ransomware attack, personal data and email correspondence exposed
Category: Uncategorized

Post navigation

← UK doctors’ personal data found on used hard drive sold online
CIO Fired After Others May Have Accessed Her EHR →

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

  • New TeleMessage SGNL Flaw Is Actively Being Exploited by Attackers
  • North Country Healthcare responds to Stormous’s claims of a breach
  • Gladney Adoption Center had serious data exposures in the past few months. What will they do to prevent more?
  • Former U.S. Soldier Pleads Guilty to Hacking and Extortion Scheme Involving Telecommunications Companies
  • DOGE Denizen Marko Elez Leaked API Key for xAI
  • Four people bailed after arrests over cyber attacks on M&S, Co-op and Harrods
  • RansomedVC is back — and is still attacking its competitors
  • Texas Enacts Electronic Health Record Data Localization Law
  • United Australia Party confirms ransomware attack, personal data and email correspondence exposed
  • Armenian National Extradited to the United States Faces Federal Charges for Ransomware Extortion Conspiracy

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

  • Texas Enacts Electronic Health Record Data Localization Law
  • Upstate NY county clerk again refuses to enforce Texas abortion judgment
  • Attorney General James Leads Coalition Urging Congress to Protect Americans from Masked ICE Agents
  • Attorney General Tong Announces $85,000 Settlement with TicketNetwork for Violations of the Connecticut Data Privacy Act​
  • Fourth Circuit upholds West Virginia ban on abortion pills
  • Meta fixes bug that could leak users’ AI prompts and generated content
  • The EU’s Plan To Ban Private Messaging Could Have a Global Impact (Plus: What To Do About It)

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.