Updated 2025: Looking for a Business Associate Agreement? Download our FREE template.

Total HIPAA Logo

HIPAA Lawsuits: What You Need to Know About the Vermont Supreme Court Ruling

This week, the Vermont Supreme Court issued a landmark ruling, regarding HIPAA lawsuits, that could potentially change the way individuals hold their healthcare providers accountable for breaches of PHI (Protected Health Information).

Maybe you heard about this case but don’t understand the ruling or its significance. In this post, we break down everything you need to know about this recent development in HIPAA lawsuits.

HIPAA Lawsuits: The Case

To best understand the ruling, we must take a closer look at the case. A Vermont woman visited the emergency room to receive treatment for a laceration on her arm. During treatment, the patient’s nurse noticed that she seemed intoxicated and decided to test her blood alcohol level. The nurse found that the patient had a BAC of 0.215 – more than twice the legal limit.

Knowing the patient drove herself to the emergency room and planned to drive home, the nurse contacted local authorities who arrested the woman in the ER waiting room after her procedure. The patient believed the nurse violated her privacy rights under HIPAA and filed a lawsuit against the hospital.

Was This a HIPAA Violation?

The court ultimately ruled that the patient had the right to sue the hospital for this disclosure of PHI. However, this situation does not constitute a breach. Healthcare professionals can disclose a patient’s PHI if they believe the patient poses a threat to themselves or the general public.

In this case, the nurse reported the woman because she believed she would drive home while severely intoxicated. Therefore, the nurse had the right to disclose the patient’s health information to law enforcement.

HIPAA Lawsuits: The Ruling

Unsurprisingly, the court upheld the nurse’s right to report the patient to law enforcement. As mentioned previously, this disclosure is permitted under HIPAA because the nurse believed the woman posed a threat to the general public.

The part of the case is straightforward, however, another factor complicates the proceedings. Under HIPAA, individuals have no right to private cause for action. This means that patients are not permitted to sue healthcare providers for privacy violations.

Instead, patients file a complaint with the Office of Civil Rights (OCR) or their state attorney general. The state/federal government investigates incidents and levies fines and penalties against any entities in violation of HIPAA.

What is so unique about this case is that the Vermont Supreme Court upheld the patient’s right to sue her healthcare provider for violating her privacy. And again, while the nurse’s disclosure did not technically violate HIPAA, it did break the understood right to confidentiality between patients and providers.

HIPAA Lawsuits: What Happens Next?

The possibility of HIPAA lawsuits brought forth by patients and breach victims could change HIPAA enforcement. The case was ultimately unsuccessful; the court ruled in favor of the nurse. However, the court also legitimized private cause for action in HIPAA lawsuits, which could set a precedent for HIPAA related legal action. Therefore, it could be possible for individuals to sue covered entities and cite this case.

Consider all the groups that qualify as covered entities: healthcare providers, employers who sponsor group health plans, health insurance agents and brokers, and all of these groups’ business associates. This case could spread to impact for more individuals and entities than this one patient and hospital.

Our HIPAA compliance services help ensure that your business follows the basic HIPAA rules and guidelines to protect sensitive patient information. Our team of experts is dedicated to providing affordable rates and personalized solutions to help you become HIPAA compliant. We understand that navigating the complex requirements of HIPAA can be challenging, which is why we offer a comprehensive range of services to meet your unique needs. From risk assessments to employee training, we have the tools and expertise necessary to help your business achieve and maintain HIPAA compliance. Contact us today to learn more about how we can help you protect your patients, your employees, and your business.

Sources & Additional Resources:

Becker Hospital Review: “Vermont Supreme Court Rules Patients Can Sue Hospitals for Privacy Violations

Jackson Lewis: “Vermont Court Finds Patient Can Sue Hospital and an Employee for Breach of Confidentiality


Sharing is caring!

Documents

Looking for a Business Associate Agreement?

Download our free template to get started on your path toward HIPAA compliance.


Download Now

Want to stay informed?

Join our community, stay ahead of the curve on HIPAA compliance and receive free expert guidance.

State of HIPAA Compliance in 2025

Watch the recording of this webinar to learn more about how you can become and stay HIPAA compliant!

Document
Register for Webinar

Related Posts

Essential Guide to Email Authentication and Deliverability: How to Configure DMARC, SPF, and DKIM Records

Essential Guide to Email Authentication and Deliverability: How to Configure DMARC, SPF, and DKIM Records

Essential Guide to Email Authentication and Deliverability: How to Configure DMARC, SPF, and DKIM Records
*This process is technical and requires access to your Domain Name Server (DNS). It’s recommended to have an IT professional handle these configurations to avoid potential issues. If you proceed yourself, back up your current settings with screenshots or copies before making any changes.
Organizations rely heavily on email for marketing and communication, making it a prime target for malicious actors. Phishing, spoofing, and other email attacks can inflict significant financial and reputational damage. In response to this growing threat, email providers are tightening their security measures, and businesses that aren’t paying attention risk having their emails blocked.
A recent announcement from Microsoft, highlighted in their Tech Community blog, highlights that Outlook is implementing stricter requirements for high-volume senders to protect users from unwanted and potentially harmful messages. This move serves as a clear signal: email authentication is no longer optional – it’s required for all organizations, regardless of their sending volume.
The key to making sure your emails reach their intended recipients is all in the configuration and alignment of your Domain-based Message Authentication, Reporting and Conformance (DMARC), Sender Policy Framework (SPF), and DomainKeys Identified Mail (DKIM) records. These protocols verify an organization actually sent the emails and tells receiving servers your messages are legitimate and shouldn’t be sent to spam folders or blocked.
What makes SPF, DKIM, and DMARC so crucial?
SPF (Sender Policy Framework): This record lists the authorized mail servers permitted to send emails on your behalf. When your email server receives an email, it checks it and verifies if the sending server’s IP address matches the list in your SPF record. This helps prevent attackers from spoofing your domain using unauthorized servers.
DKIM (DomainKeys Identified Mail): DKIM adds a digital signature to your outgoing emails. This signature is cryptographically linked to your domain and verified by the receiving server using a public key published in your DNS records. DKIM ensures the integrity of the email content and confirms that it hasn’t been tampered with in transit.
DMARC (Domain-based Message Authentication, Reporting & Conformance): DMARC builds upon SPF and DKIM. It tells receiving servers what to do with emails that fail SPF and/or DKIM checks. You can set policies to “none” (monitor), “quarantine” (send to spam), or “reject” (block). DMARC also enables reporting, allowing you to gain valuable insights into who sends emails using your domain and identify potential spoofing attempts.
Microsoft’s Stance: A Wake-Up Call
The stricter requirements being implemented by Outlook for high-volume senders emphasize the need for organizations to set up and review their authentication protocols. While the current focus is on high-volume senders, it is clear: email providers are looking for authenticated mail. Failing to correctly set up your DMARC, SPF, and DKIM records will lead to deliverability issues of emails.
What Your Company Needs to Do Now:
Regardless of size or email volume, every company should take the following steps to make sure its email authentication is configured correctly. Here’s a checklist:
Audit Your Existing Records: Check for existing SPF, DKIM, and DMARC configurations. Are they accurate and up-to-date?
Implement Missing Records: If you are missing any of these records, add them immediately. *Consult with your IT team or email service provider for guidance.
Check Alignment: It’s crucial to make sure there is alignment between your SPF, DKIM, and DMARC records. This means that the domain used for SPF and the signing domain in DKIM should match the “From” address domain in your emails. DMARC relies on this alignment to function effectively.
Start with a Monitoring Policy: For DMARC, it’s often best to start with a “none” policy to monitor how your emails are being handled and identify any legitimate sending sources that might not be properly authenticated.
Gradually Enforce Stronger Policies: Once you clearly understand your email flows and have addressed any authentication issues, move gradually towards stronger DMARC policies like “quarantine” or “reject” to protect your domain from spoofing actively.
Regularly Review and Update: The email landscape is constantly changing. Regularly review and update your authentication records as needed, especially when changing your emails or third-party sending services.
The Benefits of Proper Email Authentication:
Properly configuring and aligning your DMARC, SPF, and DKIM records offers significant benefits:
Improved Email Deliverability: Your legitimate emails are more likely to reach the inbox, avoiding spam folders and blocks.
Enhanced Brand Reputation: Protecting your domain from spoofing builds trust with your recipients and safeguards your brand’s reputation.
Increased Security: You significantly reduce the risk of using your domain for phishing and other malicious activities.
Compliance with Evolving Standards: By staying ahead of the curve, you ensure your email practices align with the increasingly stringent requirements of email providers.
The message is clear: email authentication is no longer optional. The recent emphasis from major providers like Microsoft underscores its critical importance in maintaining reliable and secure email communication. By taking the steps to audit and align your DMARC, SPF, and DKIM records, your organization can protect itself, customers, and reputation. Don’t wait until your emails are blocked – act now to secure your email.
Have questions or need help with your HIPAA compliance? Schedule a call with our experts today. https://www.totalhipaa.com/get-started/
To check your DMARC Records go here
https://www.totalhipaa.com/dmarc-lookup-free/
All records, a free and easy tool to use
https://easydmarc.com/

Save & Share Cart
Your Shopping Cart will be saved and you'll be given a link. You, or anyone with the link, can use it to retrieve your Cart at any time.
Back Save & Share Cart
Your Shopping Cart will be saved with Product pictures and information, and Cart Totals. Then send it to yourself, or a friend, with a link to retrieve it at any time.
Your cart email sent successfully :)