For healthcare organizations, choosing the right product and service vendors is essential for achieving HIPAA compliance. One of the key prerequisites of a HIPAA-compliant vendor is the willingness to sign a Business Associate’s Agreement (BAA): a legal agreement that outlines both parties’ responsibilities and liabilities in securing protected health information (PHI). 

However, despite what some healthcare organizations have been led to believe, simply signing a BAA with a vendor doesn’t guarantee your use of their product or service will be HIPAA-compliant. In reality, a BAA is just the beginning, and there are several subsequent actions both healthcare organizations and their supply chain partners must take to ensure the compliant use of PHI, especially over communications channels like email. 

With this in mind, this post explores some of the reasons why signing a BAA on its own doesn’t ensure the security of PHI and protect your organization from HIPAA violations.

Business Associate Agreements (BAAs) Explained 

As touched upon above, a BAA is a legally-binding document established between a covered entity (CE), i.e., healthcare organizations, and a business associate (BA), i.e, any company that handles PHI in providing a CE with products or services. For a BA to handle patient or customer data on behalf of a CE, following HIPAA regulations, there must be a BAA in place. 

A BAA details:

• Each party’s roles, responsibilities, and liabilities in securing PHI.
• The permitted uses of PHI by the BA and, conversely, restrictions on any other use.
• The BA’s responsibilities in implementing appropriate administrative, technical, and physical security measures to best protect PHI.
• The BA’s obligations to report any unauthorized use, disclosure, or breach of PHI.
• That the BA is required to assist with patient rights support, i.e., data access, amendments, and accounting of disclosures, when appropriate.
• The BA’s obligations in making records available for audits or investigations.  
• The CE’s right to terminate the contract if the BA fails to fulfil their obligations in safeguarding PHI.

Additionally, if a BA employs a third-party company, i.e., a subcontractor, that will have access to a CE’s PHI, they are required to establish a BAA with that company. This then makes the subcontractor a “downstream BA” of the CE, and subject to the same obligations and restrictions placed on the original BA. This ensures the security protections mandated by HIPAA flow down the entire chain of custody for sensitive patient and customer data.

Compliance Considerations After Signing a Business Associate Agreement (BAA)

Now that we’ve covered what a BAA is and the role it plays in ensuring data privacy, let’s move on to exploring some of the key things you have to do following the singing of a BAA to ensure HIPAA compliance.  

1. Both Parties Must Implement HIPAA-Required Data Risk Mitigation Measures 

First and foremost, while a BAA details each party’s respective responsibilities in implementing measures to protect PHI, both still actually need to implement those required security features to achieve HIPAA compliance. 

The measures required under HIPAA’s Security Rule, including encryption and access control, are designed to mitigate and minimize the impact of data breaches. So, if a company suffers a security breach and later audits show the required security policies and controls were not in place, they would be subject to the consequences of HIPAA violations, including fines and reputation damage.   

Also, while a BAA stipulates that the BA is responsible for implementing the HIPAA-required safeguards for the PHI under their care, it doesn’t specify exactly which security measures they must implement. Subsequently, that’s left to the BA to interpret based on their understanding of HIPAA requirements, and how they conduct their required risk assessments.

For example, if you have a BAA with your email services provider, that alone may not be enough to keep your company or organization HIPAA compliant. That’s because the provider may not have the security measures your organization needs, and instead have a carefully worded BAA that will leave you vulnerable.

Let’s say your email marketing service provider is a “semi-HIPAA compliant” provider. In these cases, they may not offer email encryption, or the necessary access control measures your organization needs to send PHI and other sensitive information safely. The so-called HIPAA compliance may be limited only to data stored at rest on their servers only.

In short, although a BAA outlines each party’s commitment to securing data, both parties still have to follow through on implementing risk mitigation measures. Additionally, though a healthcare company has its BA’s assurances that they’ll have the appropriate safeguards in place, CEs often only have limited visibility into its ongoing security posture. As a result, asking the right questions and working with a proven HIPAA compliant provider are critical steps healthcare organizations must take to ensure full compliance.

2. CEs Must Stick to “In-Scope” Services

While a BA may provide a CE with a range of services, many limit the coverage of their BAAs to particular “in-scope” services. As a result, if a healthcare organization were to use a service outside the coverage of the BAA, i.e., an “out-of-scope” service, they’d risk exposing patient data and incurring HIPAA violations.

And, even when a service is in-scope, the BA is still required to configure it properly for it to be compliant. These configurations could include:

• Enabling encryption
• Establishing access control
• Activating multi-factor authentication (MFA)
• Turning on audit logging 

With this in mind, it’s crucial to ensure that the “complete” service or tool – not just a part of it – is covered by a BAA before using it to process PHI. Similarly, check the terms of your BAA for configuration or security best practices that offer guidance on fully HIPAA compliant use, and make sure your responsibilities as a CE are 100% clear.

3. Staff Must Be Trained to Securely Handle PHI 

Another key reason that signing a BAA doesn’t automatically result in HIPAA compliance is the likely need for both parties to educate their staff on how to securely handle sensitive data, such as PHI.

Firstly, as discussed above, only some of the services offered by a BA may be covered by its agreement. Subsequently, a healthcare organization’s employees need to be sufficiently trained on the use and disclosure of PHI, namely, the services in which they’re permitted to process PHI and which, in contrast, services are non-compliant.

By the same token, as well as implementing the stipulated safeguards, BAs are responsible for training their workforce on how to use and, where appropriate, configure them. This will help ensure the limited, correct use and disclosure of PHI as allowed by the BAA. 

4. Reporting Requirements

A BAA stipulates that a BA must notify the CE in the event of improper or unauthorized use of PHI. More specifically, this includes: 

• Reporting immediately any use or disclosure not permitted by the terms of the BAA.
• Notifying the CE of security incidents resulting in the potential exposure of  PHI.

However, the commitment to reporting in the BAA and the ability to deliver on that commitment are two different things entirely. Firstly, the BA must implement the policies and infrastructure that allow for timely incident reporting. This includes conducting risk analysis, implemeting continuous monitoring, and developing a robust incident response plan. 

Additionally, a key aspect of prompt, comprehensive reporting includes the BA ensuring that their staff are sufficiently trained to detect and report security events. As part of their training on the secure handling of PHI, a BA’s employees must be able to recognize common security issues and threats, such as improper email configurations and phishing attempts, and how to report them.

5. Subcontractor BAAs

While CEs must sign BAAs with their BAs for the compliant use and disclosure of PHI, they don’t have to sign such agreements with any subcontractors the BA may employ. Instead, it’s the responsibility of the BA to enter into their own business associate agreements with their subcontractors. As a result, the original security obligations are passed all the way down the data’s chain of custody. 

While a CE can take certain measures to enforce this, such as requesting proof of subcontractor BAAs – or even the ability to review subcontractors before beginning engagement – ultimately, they have little control over their security postures. Ultimately, this means that they have to trust that the original service BA does their due diligence in selecting security-minded subcontractors, with the right PHI safeguards in place.  

HIPAA Compliance Beyond a BAA with LuxSci

LuxSci’s secure healthcare communications solutions – including HIPAA compliant email, text, marketing and forms – are designed specifically with the stringent compliance requirements of the healthcare industry in mind. 

LuxSci also provides onboarding, comprehensive documentation, and support to ensure your infrastructure configurations align with HIPAA requirements, so you can confidently include PHI in your healthcare engagement communications campaigns.

Contact LuxSci today to discover more about achieving compliance beyond obtaining a BAA.

Email is still one of the most pervasive and trusted digital communication channels in use today — and it’s not going anywhere. For health insurance providers and health plan system administrators, email presents a major opportunity: the ability to communicate reliably, more personally, and more effectively with members and customers.

Despite this, some health insurers and plan providers are wary of utilizing email to its full potential for fear of running afoul of HIPAA regulations. Or worse, they think they’re HIPAA compliant when they may not be, or they don’t think they need to be compliant when it comes to certain communications.

When email is encrypted properly, it becomes a direct, compliant channel for everything from new plan enrollments and policy changes to Explanation of Benefits (EOBs) and reimbursements. With the right encryption methods and best practices in place, you can deliver the kind of personalized, efficient experiences that today’s members and customers expect, while meeting the highest standards for privacy and security.

With this in mind, let’s explore the most impactful HIPAA compliant email use cases for health plan administrators and health insurance providers – and how enabling secure, fully encrypted email with LuxSci can improve member engagement, drive more efficient processes, speed payment, and deliver better results and outcomes.

Email: A Highly Trusted Healthcare Communication Channel

Everyone uses email. It’s a daily habit for billions of people – including your members and customers. Email is also a top channel for baby boomers, and it will continue to be for years to come.

Simply put, people are familiar and comfortable with how email works, they trust it, and email doesn’t require the installation and use of another app or logging into a separate portal. For health plans and insurers, this means you can meet members and customers directly where they already are, through a highly used method of communication.

A Private and Preferred Option for Key Healthcare Conversations

When designed with security in mind, email is perfectly suited for delivering sensitive healthcare information, i.e., protected health information (PHI) and conversations about an individual’s health condition, related treatment, and insurance coverage. Just as importantly, it’s can be less invasive than SMS, and more effective – not to mention cheaper – than printed mail, making it an ideal choice for critical, high-touch communications, such as member benefits, policy updates, and billing.

HIPAA Compliance: Securing Better Digital Engagement

HIPAA compliance often gets framed as a limitation; in reality, however, it provides the framework for secure, scalable communications in healthcare.

With the right HIPAA compliant email solution, health plan administrators and health insurers can:

• Deliver personalized content directly to members and customers – securely
• Automate secure communications and related workflows
• Avoid the additional friction of portals – and capture non-portal users
• Ensure privacy and legal protection for sensitive data

Rather than avoiding email for sensitive communications, more and more organizations are now embracing secure email to improve engagement, click-throughs and conversions. This translates to more timely plan enrollments, more policy renewals and faster payments.

Compliance Enables Engagement, Not the Other Way Around

When you build compliance into your communications strategy, you unlock more ways to engage with members effectively. Confident in the safeguards you have in place to protect sensitive member and customer data, you can personalize your email communications, segmenting members according to their healthcare needs, their status within your organization, or their individual situation (recently joined, long-time member, disengaged, etc).

Consequently, HIPAA compliance doesn’t have to slow you down, as it’s persistently perceived to, it actually enables you to harness the possibilities of personalization to drive better engagement and better results.

HIPAA Compliant Email Use Cases for Health Plan Administrators and Insurers 

Let’s turn our attention to five highly applicable use cases for HIPAA compliant email for health plans and insuers, and how they can benefit your company, as well as your members or customers. 

Use Case #1: Sending Explanation of Benefits (EOBs)

Why It Matters: Reliable delivery, faster payments

In most cases, EOBs are still sent via physical mail, which is slow, costly, often misunderstood, and may never reach the intended recipient for myriad reasons. Conversely, with HIPAA compliant email, you can deliver digital EOBs directly to members in a format they can understand and trust is secure – at a much lower cost.

Benefits

• Increased deliverability
• Reduce printing and mailing costs
• Reduced carbon footprint
• The ability to track message activity, i.e., if delivered, opened, etc.

Try the LuxSci EOB ROI calculator here, and see how you can save millions of dollars per month with HIPAA compliant email EOBs.

Use Case #2: New Plan Enrollments

Why It Matters: Secure enrollments, faster and on time

Enrollment is a crucial moment on the member journey. With secure email, you can onboard new members more quickly by reaching them directly via their inbox, providing them with their enrollment instructions, required logins, delivering their plan details, and supplying coverage summaries. All of which can be achieved without them having to wait for the mail or chase portal logins.

Benefits

• Real-time delivery of enrollment and onboarding materials
• Immediate coverage confirmation
• Easier to troubleshoot potential issues
• Enhanced support with secure reply options

Use Case #3: Policy Change and Renewal Notifications

Why It Matters: Transparency and speed build trust

Policy updates, such as changes to deductibles, coverage, or provider networks, must be communicated clearly and as soon as possible. HIPAA compliant email makes it simple to notify members and deliver legally required communications reliably and securely.

Benefits

• Keep members better informed and more empowered to make healthcare decisions
• Meet regulatory deadlines
• Align with compliance requirements
• Reduce call center volume from confused policyholders 

Use Case #4: Payments, Reimbursements and Financial Communications

Why It Matters: Payment and coverage clarity drives satisfaction, business continuity

From payment confirmations to out-of-pocket estimates, secure email gives members clear, timely financial updates, allowing them to plan accordingly. This makes them feel their healthcare providers are being open with them and transparent in communications for payments.

In contrast, confusion about benefits, coverage, and costs diminishes trust, which strains communication and makes effective engagement difficult. Financial clarity also accelerates your organization’s internal processes, enhancing efficiency and your ability to provide the best possible service to members. 

Benefits

• Increased member trust and satisfaction
• Speed up reimbursement cycles
• Reduce payment confusion
• Enable secure document submission (e.g., receipts, claims)

Use Case #5: Education and Preventive Health Campaigns

Why It Matters: Proactive education supports better health outcomes

Use HIPAA compliant email to send targeted content, including preventive screening reminders, wellness resources, and seasonal health tips, while effectively securing PHI. Members benefit by taking a more active role in their healthcare journeys and committing to better health, which reduces healthcare costs and improves outcomes.

Benefits

• Educated members are more involved in their healthcare journey
• Personalized health education based on member history
• Secure mass communication that meets HIPAA standards
• Improved health outcomes and engagement

LuxSci for Health Plan Administrators and Insurers

HIPAA compliance isn’t the end of the conversation – it’s really the beginning of smarter and more secure engagement that has a real impact on business results, as well as member and customer satisfaction.

LuxSci is a trusted provider of secure email solutions tailored for healthcare organizations. With over 20 years of experience supporting HIPAA compliance and HITRUST certification, LuxSci enables compliance, marketing, operations, and IT teams to send high-volume, secure, personalized email – all without compromising privacy or performance.

Key Features

• Automated encryption (TLS, PGP, S/MIME), which sets encryption according to message sensitivity and the recipient’s email security posture
• Secure SMTP and API-based sending
• Real-time tracking and delivery reporting
• Automated workflows
• Configurable access controls and user management
• Full BAA coverage and dedicated infrastructure

Whether you’re sending thousands of onboarding emails or automating payment updates, LuxSci helps you do it securely, seamlessly, and at scale.

Ready to unlock the full potential of HIPAA compliant email?

Contact LuxSci today to discover more about how our solutions can enable more effective, more personalized healthcare communication. 

Health Plan Administrator and Insurance Provider Secure Email Use Cases FAQs

How Does HIPAA Enable Better Email Communications for Health Plans?

HIPAA provides the framework for secure, HIPAA compliant communication of electronic protected health information (ePHI), allowing health plans and insurers to safely send personalized, high-impact emails to members.

Can We Use Email for Mass Communications Involving PHI?

Indeed, you can. LuxSci provides the infrastructure to send thousands, or even millions, of encrypted email communications containing PHI –  securely, compliantly, and with fully encrypted content.

Is Secure Email More Effective Than Traditional Member Portals?

In many cases, yes: Secure email bypasses portal fatigue, created by the friction of your members having to log into a separate platform to receive key communications. Conversely, secure email platforms, like LuxSci, deliver  messages directly to the inbox where members are more likely to read and respond.

What Makes Luxsci Different from Other Secure Email Providers?

LuxSci’s solutions have been built from the ground up with the stringent compliance and secuirty needs of healthcare organizations in mind. This translated into providing HIPAA-compliant email communication without sacrificing usability, supporting high-volume sending, flexible encryption options, and seamless integration into your existing systems.