As a provider, a question worth asking yourself these days is this: what degree of risk is there that you might have something on your website that could lead to a multi-million-dollar class-action lawsuit and a determination by the U.S. Department of Health and Human Services (HHS) Office for Civil Rights (OCR) that you violated the Health Insurance Portability and Accountability Act (HIPAA)?
As anyone who has seen the pop-up banners on many websites over the past few years knows, websites often use “cookies,” small packets of data, to track activities on the site. Sometimes, these cookies also share information with third parties.
Social media and online ad companies provide some of the most common cookies and other tracking tools to website owners. “Meta Pixel,” provided by Meta – Facebook’s parent company – and Google Analytics are among the most ubiquitous. But nearly every social media company, such as LinkedIn, Snapchat, TikTok, Twitter-slash-X, offers something.
These cookies are often used to figure out how effective advertising campaigns and websites are at driving people to sites and then prompting them to take certain actions, such as buying a product – or, potentially, making an appointment with a doctor.
In the process, these tools often send information back to a third party, such as Meta or Google.
And here’s where OCR and some plaintiffs think there might be a problem.
In the past year, dozens of class-action lawsuits have been filed against healthcare entities because of their websites’ use of Meta Pixel and other tools. We have four in federal court just here in Minnesota, where I am.
So far, these lawsuits have mostly targeted hospital systems. But they are starting to target smaller entities. For example, one was recently filed against a small clinic in Florida.
The central claim is that healthcare entities cannot share information people provide on their websites. Tracking technologies do that.
So, what’s the risk?
An older, similar case settled for $18.4 million.
One of the newer cases settled about a month ago for more than $12 million.
But on the other hand, federal courts have also dismissed (or mostly dismissed) several cases in the last few months.
Because these lawsuits are so new, it’s hard to say what the risk will ultimately be.
Unfortunately, the risk is not just a lawsuit. OCR issued guidance in December 2022 related to these tools. It took the position that many practices and uses of tracking technologies are barred by HIPAA’s Privacy Rule. It reminded readers that civil penalties may apply if the use violates HIPAA. Fortunately, it also gave some examples of where HIPAA does not apply.
If David Glaser were here, he would remind us that guidance is only guidance. It is not the law.
And one federal judge recently ruled that OCR’s interpretation, and I quote, “goes well beyond the meaning of what the statute can bear.”
So, what can you do to reduce your risk?
Start by evaluating:
- What tools are you using?
- Third-party versus internal tools
- What are your website’s capabilities?
- What parts of your website is it on?
- Main page
- Portal login
- Inside portal
- Video Privacy Protection Act
- Do you have one?
- Do people have to accept it to use your website?
- And as always, what benefit are you getting?
Ultimately, it is tough to say what the full risk is. Situations vary, and it may be fact-sensitive. And all this action regarding healthcare cookies is still new and changing.
So, while I’m not sure if it’s because my 3-year-old just discovered the glories of Sesame Street, or because I spend a lot of time thinking about cookies on my clients’ websites, either way, the Cookie Monster’s song “C is for Cookie” has been stuck in my head recently.
Cookie Monster sings, “C is for Cookie, that’s good enough for me.”
Cookie Monster is right:
C is for Cookie, and that might be good enough for Cookie Monster.
But C is also for “Class Action Lawsuit.”
Or a “Complaint” filed with the Office for Civil Rights.
Go get yourself a cookie to eat, and then check in on your website’s cookies.