LuxSci

Is ActiveCampaign HIPAA Compliant?

Email HIPAA Compliance

ActiveCampaign is a cloud-based marketing automation platform that helps organizations manage their email marketing, customer relationships, and sales automation, and it can be HIPAA compliant for enterprise deployments. The platform’s automation capabilities enable organizations to streamline their workflows and carry out marketing campaigns with less administrative overhead, saving both time and money. Additionally, ActiveCampaign’s advanced segmentation tools allow companies to personalize campaigns according to demographics, behavior, and past interactions.

While these capabilities are highly sought after by healthcare organizations who want to enhance their engagement with patients and customers, they require one characteristic above all in their marketing platform of choice: HIPAA compliance.

More specifically, for a company to send electronic protected health information (ePHI) through an email marketing platform, it must comply with the Health Insurance Portability and Accountability Act (HIPAA).

Let’s take a closer look

Is ActiveCampaign HIPAA Compliant?

Firstly, to address the question directly – is ActiveCampaign HIPAA compliant? – it is not HIPAA-compliant by default. Healthcare organizations can only conduct HIPAA compliant marketing campaigns if they are signed up for the Enterprise version of the solution.

Our findings revealed that companies are required to configure ActiveCampaign accordingly to ensure HIPAA compliance. Again, that healthcare organizations need to ensure compliance themselves – and how they do so – isn’t made 100% clear in any of the company’s literature.

ActiveCampaign’s Security Features

ActiveCampaign does not provide message-level encryption for outbound campaign emails (e.g., portal-based pickup or enforced encryption to recipients), so you generally should not put PHI in the body of campaign emails. This limits your ability to engage patients with personalized and relevant messages that result in more opens, clicks and conversions.ActiveCampaign’s sole mention of HIPAA compliance is on their security features page, on which they state:

ActiveCampaign is heavily focused on GDPR, SOC 2, and HIPAA compliance. We constantly improve our security to go above and beyond compliance standards.”

Now, while they don’t go into further detail, ActiveCampaign does indeed feature some security controls that lend themselves towards HIPAA compliance. These include:

  • Single Sign-On (SSO): users can sign into ActiveCampaign through an existing identity provider, such as Google, without requiring a separate set of credentials. This helps protect data through stronger access control and allows for simpler user authentication.
  • Multi-Factor Authentication (MFA): ActiveCampaign supports MFA, requiring users to verify their identity through text or time-based one-time password (TOTP) authentication. This adds another layer of security, in line with HIPAA regulations, and is something that could be more emphasized if changes to the Security Rule come into effect later this year. 
  • Automatic Session Timeouts: idle sessions are automatically logged out after a short amount of time: protecting them from session hijacking and related cyber threats. 

Additionally, users are responsible for setting up the proper email authentication protocols themselves, including:

  • SPF (Sender Policy Framework): Specifies authorized mail servers for your domain.DKIM (DomainKeys Identified Mail): Adds a digital signature to your emails, verifying their authenticity.DMARC (Domain-based Message Authentication, Reporting & Conformance): Provides instructions to email providers on handling messages that fail SPF or DKIM checks.

Setting up these protocols helps fight against email spoofing and phishing attacks, ensuring that your emails are recognized as legitimate by recipients’ mail servers.

Will ActiveCampaign Sign a BAA?

Now, even with some security features and stating they are focused on compliance, a marketing platform can’t truly comply with HIPAA regulations unless they sign a Business Associate Agreement (BAA).

ActiveCampaign’s BAA availability appears limited and may depend on plan level; confirm directly with ActiveCampaign.

Discover HIPAA Compliant Alternatives to ActiveCampaign

As this post illustrates, while it is possible to make ActiveCampaign HIPAA compliant, it’s not straightforward. Fortunately, there are alternative email and marketing solutions that are fully HIPAA-compliant – out-of-the-box – removing the guesswork and ambiguity from securing your digital communications and allowing you to focus on engaging with your patients and customers. This includes LuxSci Secure Marketing, which enables healthcare organizations to proactively reach patients and customers with HIPAA compliant email marketing campaigns that can securely include PHI for increased engagement, lead generation and sales.

Discover how LuxSci can elevate your secure healthcare engagement efforts with PHI data, resulting in better health outcomes for your patients, in addition to enhancing your brand identity and achieving your company’s growth objectives. Reach out today for a call or demo.

Picture of LuxSci

LuxSci

Get in touch

Find The Best Solution For Your Organization

Talk To An Expert & Get A Quote




A member of our staff will reach out to you

Get Your Free E-Book!

LuxSci High Email Deliverability Best Practices Paper

What you’ll learn:

Related Posts

LuxSci Automated Email Encryption

“Encryption Optional” Email Will Fail Audits in 2026 and Beyond

For years, healthcare organizations have relied on click-to-encrypt email workflows and secure portals as a practical compromise between usability and compliance. Or in some cases, they simply thought most of their emails did not need to be compliant. In regulated industries where data security and privacy are paramount, this approach was still considered “good enough.”

That era is ending.

As we progress into 2026 and beyond, regulators, auditors, and cyber insurers are sending a clear and consistent message: encryption that depends on human choice is no longer acceptable. It’s already happening. Encryption optional email isn’t merely raising concerns, it’s failing audits outright.

An Email Threat Landscape That’s Changing Faster Than Email Habits

Historically, email encryption was treated as a best practice rather than a hard requirement. If an organization could demonstrate that encryption tools existed and that employees had access to them, auditors were often satisfied. The box was checked, everybody moved on.

Today, the questions auditors ask are fundamentally different. Instead of asking whether encryption is available, they are asking whether sensitive data can ever leave the organization unencrypted. If the answer is yes, even in rare cases, or even accidentally, that’s no longer viewed as an acceptable gap. It’s viewed as inadequate control.

Why 2026 Is a Tipping Point for Email Security

Several forces are converging here in 2026 that make optional encryption increasingly untenable. Regulatory scrutiny around PHI and PII exposure continues to intensify. Breach costs and litigation are rising, with email remaining one of the most common vectors for data exposure and breaches. AI is also changing the game for cybercriminals, and attacks will continue to increase and be more sophisticated. As a result, cyber insurers are tightening underwriting requirements and demanding stronger, more predictable controls.

At the same time, email user behavior is unpredictable and inconsistent, which is a non-starter for data security in today’s world.

Taken together, these trends and behaviors point to a single requirement: email security controls must be automated. They must be enforced by systems, not dependent on employee memory, judgment, or good intentions.

The Reality of “Encryption Optional” in Practice

On paper, optional encryption can sound reasonable. In practice, it creates gaps large enough to open you up to a breach.

Secure portals are a good example. They require recipients to click a link, authenticate, and access content in a controlled environment. While this protects data in transit, and is a better approach than no security at all, it also introduces friction. And people don’t like friction. Senders forget to use the portal. Recipients ask for “just a quick email instead.” Shortcuts are taken to save time. And every shortcut becomes a risk.

Click-to-encrypt systems suffer from a similar problem. They rely on users to correctly identify sensitive data and remember to take action. But people often misclassify information, forget to click the button, or assume someone else has already secured the message. From an auditor’s perspective, this isn’t a training failure. It’s a set-up and control failure.

Email Security Defaults Are the New Normal

The latest message from regulators, auditors, and insurers is clear. If encryption is optional, data vulnerabilities become inevitable.

What can you do?

Below is a quick email security checklist to help you get started. Cyber insurers may require or recommend the following safeguards during the underwriting process, such as:

  • Multi-factor authentication (MFA)
  • Endpoint protection
  • Encrypted backups
  • Incident response planning
  • Encryption protocols for sensitive data in transit and at rest, including PHI in emails

In 2026 and beyond, healthcare organizations and regulated industries will be judged not by what they allow, but by what they prevent. Automated, encrypted email is the new. normal.

Want to learn more about LuxSci HIPAA compliant email? Reach out today.

LuxSci Oiva Health

LuxSci and Oiva Health Combine to Form Transatlantic Healthcare Communications Group

Boston & Helsinki, February 12, 2026 – LuxSci, a provider of secure healthcare communications solutions in the United States, and Oiva Health, a Nordic provider of Digital Care solutions in social and healthcare services, today announced that the companies are joining forces. Backed by Main Capital Partners (“Main”), the combination brings together two complementary platforms and teams, forming a strong transatlantic software group focused on secure healthcare communications.

Founded in 1999, LuxSci is a U.S. provider of HIPAA‑compliant, secure email, marketing, and forms solutions. Its application and infrastructure software enable organizations to securely deliver personalized, sensitive data at scale to support a broad range of healthcare communications and workflows including care coordination, benefits and payments, marketing, wellness communications, after care and ongoing care. Certified by HITRUST for the highest levels of data security, LuxSci serves dozens of healthcare enterprises and hundreds of mid‑market organizations.

Founded in 2010, Oiva Health is a provider of digital care and communications solutions in the Nordics. Headquartered in Finland, with additional offices in Denmark, Norway, and Sweden, Oiva Health offers digital care and digital clinic solutions – including digital visits, secure messaging, online scheduling and appointments, and caregiver communications – serving the long-term care, especially elderly care, and occupational healthcare verticals. The company employs approximately 60 people and has recently expanded across the Nordic region, with a growing presence in Norway and Sweden.

The combination of LuxSci and Oiva Health creates a larger, cross Atlantic group with complementary solutions, serving the U.S. and European markets. Together, the companies offer healthcare providers, payers, and suppliers a comprehensive suite of tools to communicate securely and compliantly, spanning communications, workflows, and virtual care delivery.

Daan Visscher, Partner and Co-Head North America at Main, commented: “We are pleased to announce this cross Atlantic transaction, creating an internationally active secure communications player within the healthcare and home care space. The combined product suite enables healthcare organizations to drive much needed efficiency gains in healthcare provision addressing a global trend of rising costs, aging population, and increasing pressure on resources needed to provide high-quality care.”

Mark Leonard, CEO of LuxSci, said, “We are thrilled to join forces with Oiva Health and believe that together we can truly make a difference in healthcare coordination, access, and delivery. We see an exciting path forward with our customers benefiting from an end-to-end, secure and compliant approach to optimizing both healthcare communications and today’s frontline workers, which we need now more than ever.”

Juhana Ojala, CEO at Oiva Health, concluded, “We look forward to this new chapter together with LuxSci. We are very excited about the strong alignment between our solutions, which especially strongly positions us to expand our flagship Digital Care offering to the high-potential U.S. care market – from care coordination to care delivery to in-home and institutional care.”

Nothing contained in this Press Release is intended to project, predict, guarantee, or forecast the future performance of any investment. This Press Release is for information purposes only and is not investment advice or an offer to buy or sell any securities or to invest in any funds or other investment vehicles managed by Main Capital Partners or any other person.

[END OF MESSAGE]

About LuxSci

LuxSci is a U.S.-based provider of secure healthcare communications solutions for the healthcare industry. The company offers secure email, marketing, forms and hosting, delivering HIPAA‑compliant communication solutions that enable organizations to safely manage and transmit sensitive data. Founded in 1999, LuxSci serves more than 1,900 customers across healthcare verticals, including providers, payers, suppliers, and healthcare retail, home care providers, and healthcare systems, as well as organizations operating in other highly regulated industries. LuxSci is HITRUST‑certified with example clients being Athenahealth, 1800 Contacts, Lucerna Health, Eurofins, and Rotech Healthcare, among others.

About Oiva Health

Oiva Health is a Digital Care provider in the Nordics, offering a comprehensive Digital Platform for integrated health and care services to digitalize primary healthcare, social care, hospital healthcare and long-term care services. The company was founded in 2010 and currently employs approximately 60 people in Finland, Denmark, Norway, and Sweden serving domestic municipalities, customers and partners, such as City of Helsinki, Keski-Suomi Welfare Region, Länsi-Uusimaa Welfare Region in Finland, and Viborg municipality in Denmark with its Digital Care platform. Annually over 5 million customer contacts are handled digitally through Oiva Health’s Digital Care and Digital Clinic platforms.  

About Main Capital Partners

Main Capital Partners is a software investor managing private equity funds active in the Benelux, DACH, the Nordics, France, and the United States with approximately EUR 7 billion in assets under management. Main has over 20 years of experience in strengthening software companies and works closely with the management teams across its portfolio as a strategic partner to achieve profitable growth and create larger outstanding software groups. Main has approximately 95 employees operating out of its offices in The Hague, Düsseldorf, Stockholm, Antwerp, Paris, and an affiliate office in Boston. Main maintains an active portfolio of over 50 software companies. The underlying portfolio employs approximately 15,000 employees. Through its Main Social Institute, Main supports students with grants and scholarships to study IT and Computer Science at Technical Universities and Universities of Applied Sciences.

The sender of this press release is Main Capital Partners.

For more information, please contact:

Main Capital Partners
Sophia Hengelbrok (PR & Communications Specialist)

sophia.hengelbrok@main.nl

+ 31 6 53 70 76 86

HIPAA Compliant Email

Rethinking HIPAA Compliant Email – Not Just a Checkbox

The compliance-only mentality is outdated.

Let’s be honest—when most healthcare organizations think about HIPAA compliant email, it’s usually in the context of avoiding fines or satisfying checklists. And while yes, compliance is critical, viewing it only through the lens of risk management is a missed opportunity.

In reality, HIPAA compliant email, when implemented properly, is one of the most powerful tools for patient and customer engagement. Why? Because it unlocks the ability to leverage protected health information (PHI) safely, enabling personalized, timely, and high-impact email communication that drives better engagement, satisfaction, and outcomes.

What Makes Email Truly HIPAA Compliant?

As a reminder, HIPAA compliant email requires that protected health information (PHI) is safeguarded both in transit and at rest. That means your email provider must:

  • Use encryption at all times
  • Be access-controlled
  • Include audit logs
  • Be stored and transmitted in a secure manner
  • Provide a Business Associate Agreement

Regular email services just don’t cut it. In fact, most consumer or marketing email platforms like Sendgrid or Constant Contact, while great at sending email, are not HIPAA compliant or have limitations when it comes to using PHI in your messages. Even when bolted-on encryption solutions are used, they often lack the flexibility, scalability, and automation needed for safe and effective healthcare email engagement.

LuxSci goes beyond the basics with policy-based encryption, secure TLS, PKI encryption and escrow/secure portal options. LuxSci’s SecureLine™ encryption technology dynamically selects the appropriate encryption method based on recipient capabilities and messaging context and can be configured to enforce secure delivery automatically according to organizational policies. LuxSci also provides the ability to enforce advanced multi-factor authentication. Every message is tracked with full audit trails—no guesswork, no loose ends.

The Real Opportunity – Secure, Personalized Email with PHI

Using PHI to Drive Personalized Messaging
Imagine sending a personalized reminder to a diabetic patient about an upcoming check-up. Or reaching out to new mothers with postnatal care resources tailored to their needs. Or sending automated email workflows to all your members to accelerate and increase new plan enrollments. Or email customer and prospects about a new product upgrade or new service offering. The list goes on. That’s the power of PHI-personalized email—when done securely.

Targeted Segmentation with Sensitive Data
With HIPAA compliant email solutions like LuxSci, you can segment your audience based on real health data with high levels of precision, such as chronic conditions, appointment history, insurance status, health risks, and more, without compromising patient trust or security.

Breaking the One-Size-Fits-All Approach in Healthcare Email
Generic email blasts are over. Modern patients expect personalization. With LuxSci, you can deliver highly targeted, highly secure emails with encrypted content, while staying HIPAA compliant.

Real Business Results from Secure Email

Here’s how secure, personalized email can drive improved results across a range of healthcare communications, including:

  • Increased Patient Appointments and Follow-ups – Sending encrypted, personalized appointment reminders and follow-up notices can reduce no-shows and boost overall appointment volume.
  • Boosting Preventative Care with Outreach Campaigns – Preventative campaigns (think flu shots or cancer screenings) sent securely to the right segments can lead to higher response rates, better health outcomes, and a lower cost of care.
  • Improving Health Plan Enrollments – Targeted email outreach during open enrollment, tailored by eligibility or plan type, and powered by automated workflows leads to higher enrollments and lower call center costs.
  • Driving Awareness and Sales of New Services or Products – Have a product upgrade offer, new wellness program or telehealth service? Send secure, PHI-informed HIPAA compliant email to the right audience for increased sales and faster adoption.
  • Optimize Explanation of Benefits NoticesReplace snail mail with email that’s fast, reliable and trackable, ensuring customers are informed and compliance is met.

luxsci use cases Rethinking HIPAA Compliant Email – Not Just a Checkbox

The Healthcare Marketer’s Secret Weapon: Using PHI Responsibly

In a world moving away from third-party cookies, first-party data is more valuable than ever, and PHI is the most powerful form of it in healthcare. With secure HIPAA compliant email, PHI doesn’t have to be locked away. Marketers can safely use it to understand patient needs and send relevant, timely messages. PHI-driven segmentation lets you build hyper-targeted campaigns that speak to relevant conditions, unique needs and timely topics, increasing open rates, clicks throughs, and campaign conversions.

Meeting the Personalization Demands of Today’s Patients and Customers

HIPAA-compliant email is no longer just about checking a box. It’s about unlocking the full potential of your patient and customer data to drive better engagement, healthier outcomes, and measurable business results.

In closing, below are some final thoughts on how secure, HIPAA compliant email delivers long-term value for your organization and better connections with your patients and customers, including:

    • Future-Proofing Healthcare Engagement – Patients expect Amazon-level personalization. HIPAA-compliant tools let you meet those expectations securely.

    • Adapting to Data Privacy Regulations Beyond HIPAA – From GDPR to state-level privacy laws, secure communication is no longer optional, it’s foundational.

    • Building Trust Through Secure Communication – Each secure, personalized message sent is a trust-building moment with your patients and customers.

SecureLine in action v4 Rethinking HIPAA Compliant Email – Not Just a Checkbox

Why LuxSci? The Infrastructure Behind the Performance

With LuxSci’s secure email infrastructure and email marketing solutions, healthcare organizations can confidently personalize communication, reach patients more effectively, and fuel growth with PHI-safe segmentation, messaging, and email automation.

LuxSci takes data security and email performance to the next level by offering dedicated cloud infrastructure for each customer, which means your email campaigns aren’t slowed down by other vendors on shared cloud services and your attack footprint is much smaller. In short, you get higher delivery rates and throughput with proven HIPAA compliance and data security.

The future of healthcare engagement is personal, secure, and performance-driven—and it starts with HIPAA compliant email done right.

Reach out today with any questions or to learn more about LuxSci.


FAQs

1. Is HIPAA-compliant email necessary for marketing communications?
Yes—if your emails include or are based on PHI (like appointment reminders, condition-based messaging, or insurance info), you need HIPAA-compliant email and recipient consent to avoid legal risk and preserve patient trust.

2. Can PHI be used in marketing emails under HIPAA?
Yes, with proper consent and secure, HIPAA compliant infrastructure like LuxSci’s, PHI can be safely used in emails for personalized, segmented campaigns.

3. How does LuxSci ensure high email deliverability for healthcare messages?
LuxSci uses dedicated cloud servers for each customer, active email reputation monitoring, and best-practice configurations to ensure high deliverability rates for sensitive emails.

4. Is LuxSci only for marketing teams?
No—LuxSci supports marketing, clinical, operations, and IT teams by enabling secure, compliant email communication across the entire organization.

5. What types of PHI can I use to segment campaigns using LuxSci?
You can segment based on chronic conditions, visit history, insurance status, provider details, age, gender, location, and more—all while staying fully compliant.

HIPAA compliant email

Most Popular LuxSci Blog Posts of 2025

As we close out 2025, healthcare communicators, IT and compliance leaders, and digital marketers face an ever-changing landscape of security threats, regulatory updates, and technology innovations. At LuxSci, we’re committed to helping you with continuous updates and guidance on the future of secure healthcare communications.

In case you missed it, or need a refresh, below are some of our most popular blog posts from 2025. Enjoy!

1. Improve Email Engagement and Marketing Results with Automated Workflows

Automated workflows are transforming how healthcare organizations engage patients and customers — enabling dynamic, event-driven campaigns that easily scale your outreach and keep you HIPAA compliant. In this post, we introduce LuxSci’s Automated Workflows capability for our Secure Marketing healthcare solution. Learn how sequence-based journeys can personalize outreach and optimize engagement with behavior-based triggers that improve campaign performance — without sacrificing data security.

Read the full post: LuxSci Enhances Secure Marketing with Automated Workflows

2. Healthcare Email Threat Readiness Strategies

Email remains a frontline channel for healthcare communications, and a prime target for cyber threats and criminals. This deep-dive into email threat readiness strategies covers essential practices like continuous monitoring, business continuity planning, and workforce training to mitigate email-borne security risks. Whether you’re responsible for clinical systems, marketing, or enterprise IT, this post provides a strategic playbook to strengthen your defenses, while maximizing your results.

Read the full post: Healthcare Email Threat Readiness Strategies

3. HIPAA Compliant Email — 20 Tips in 20 Minutes

For practical guidance you can apply right now, this on-demand webinar distills 20 key tips for HIPAA-compliant email across technical, legal, and operational domains. Whether you’re refining your infrastructure, improving deliverability, or modernizing your data security posture in 2026, this resource is a time-efficient way to elevate your compliance and security.

Read the post and watch the webinar on demand: HIPAA Compliant Email: 20 Tips in 20 Minutes

4. Is SendGrid HIPAA-Compliant? What You Should Know

Choosing the right email provider matters, especially when Protected Health Information (PHI) is at stake. In this post, we examine SendGrid’s capabilities in the context of HIPAA compliance, outline what it takes to send PHI securely, and offer guidance on evaluating third-party services for secure healthcare email and communication needs.

Read the full post: Is SendGrid HIPAA-Compliant?

5. LuxSci Shines in G2 Winter 2026 Reports

Customer feedback matters to LuxSci. In this post, we share the most recent news about LuxSci’s performance in the G2 Winter 2026 Reports, where we earned 20 badges across categories like Email Security, Encryption, Gateway, and HIPAA-Compliant Messaging. These reviews reflect not just product excellence, but trust from real users, which we work hard to build every day!

Read the full post: LuxSci Shines in G2 Winter 2026 Reports

Looking Ahead to 2026

We look forward to providing more information and insights on secure healthcare communications in the coming year, including the latest on HIPAA compliant email, PHI security, healthcare marketing, threat readiness, and personalized engagement. In the meantime, if you’re not already, follow us on LinkedIn below, and we’ll see you here in 2026!

Follow LuxSci on LinkedIn

You Might Also Like

Email HIPAA Compliance

What Is HIPAA Compliant Email Hosting?

HIPAA compliant email hosting provides secure email infrastructure that meets HIPAA Security Rule requirements for protecting electronic protected health information (ePHI). These hosting services implement administrative, physical, and technical protections while offering business associate agreements to healthcare organizations that need to transmit patient data via email communications. Healthcare providers rely heavily on email for patient communications, care coordination, and administrative tasks. Standard email hosting services lack the security controls and compliance features needed to protect PHI, making specialized HIPAA hosting solutions necessary for organizations handling sensitive health information.

Security Infrastructure Requirements

HIPAA compliant email hosting requires a security architecture that protects data at rest and in transit. Hosting providers must implement encryption protocols, access controls, and network security measures that meet or exceed HIPAA technical safeguards specifications. Data center facilities housing HIPAA compliant email servers need physical security controls including biometric access systems, surveillance cameras, and environmental protections. These facilities maintain certifications like SOC 2 Type II to show their commitment to security and operational excellence.

Network infrastructure must include firewalls, intrusion detection systems, and secure communication channels that prevent unauthorized access to email data. Hosting providers regularly implement network segmentation to isolate healthcare client data from other customers and security threats.

Business Associate Agreement Obligations

Healthcare organizations using third-party email hosting services must establish business associate agreements (BAAs) with their hosting providers. These contracts outline how the hosting company will protect PHI and comply with HIPAA regulations on behalf of the healthcare organization. Hosting providers accepting BAA responsibilities agree to implement appropriate security measures, report potential breaches, and allow healthcare organizations to audit their compliance practices. The BAA also limits how hosting companies can use or disclose PHI beyond the services specified in the agreement.

Liability provisions within BAAs help protect healthcare organizations from compliance violations caused by hosting provider security failures. Healthcare organizations remain responsible for ensuring their hosting providers maintain adequate security controls and comply with HIPAA requirements.

Data Backup and Recovery Capabilities

HIPAA compliant email hosting services must provide reliable backup and disaster recovery systems that protect against data loss while maintaining security controls. These systems ensure healthcare organizations can restore email communications and maintain business continuity after technical failures or security incidents. Backup procedures need encryption and access controls that match the security standards applied to primary email data. Hosting providers typically maintain multiple backup copies across geographically distributed facilities to protect against localized disasters or system failures.

Recovery time objectives and recovery point objectives help healthcare organizations evaluate hosting provider capabilities and ensure service levels meet their operational needs. Many providers offer guaranteed recovery times and service level agreements that include financial penalties for failing to meet performance commitments.

Email Server Administration and Maintenance

Managed email hosting services handle server administration tasks including software updates, security patches, and performance optimization. This approach helps healthcare organizations maintain HIPAA compliance without requiring internal technical expertise for email infrastructure management. Server maintenance activities must follow change control procedures that document modifications and assess potential security impacts. Hosting providers schedule maintenance during off-peak hours to minimize disruptions to healthcare operations and patient communications.

Performance tracking helps ensure email systems can handle healthcare organization communication volumes without delays that might impact patient care. Hosting providers monitor server resources, email delivery rates, and system availability to identify potential issues before they affect service quality.

Integration with Healthcare Applications

HIPAA compliant email hosting platforms often provide APIs and integration capabilities that connect with electronic health record systems, practice management software, and other healthcare applications. These integrations enable automated email communications while maintaining security and compliance controls. Directory services allow healthcare organizations to manage user accounts and access permissions centrally. Integration with existing authentication systems like Active Directory helps maintain consistent security policies across all organizational technology resources.

Email archiving features help healthcare organizations meet record retention requirements while providing search capabilities for compliance audits and legal discovery requests. These archives maintain the same security controls as active email data and provide long-term storage for regulatory compliance.

Cost Structure and Service Models

HIPAA compliant email hosting services typically use subscription-based pricing models that scale with the number of users or email volumes. Pricing often includes security features, compliance support, and administrative services that would require significant internal resources to implement independently. Hosted solutions eliminate the capital expenses associated with purchasing and maintaining email server hardware. Healthcare organizations can redirect IT budget from infrastructure costs toward other patient care priorities while ensuring email communications remain secure and compliant.

Service level agreements define hosting provider responsibilities and performance guarantees. These agreements generally include uptime commitments, support response times, and security incident response procedures that help healthcare organizations plan their operations and ensure reliable email communications.

How Do You Know if Software is HIPAA Compliant?

How Do You Know if Software is HIPAA Compliant?

As in any industry, the healthcare sector is eager to embrace any new technology solution that increases productivity, enhances operational efficiency, and cuts costs. However, the rate at which healthcare companies – and their patients and customers – have had to adopt new software and digital tools has skyrocketed since the pandemic. And while a lot of this software is beneficial, a key question arises: is it HIPAA compliant? While an application may serve an organization’s needs – and may be eagerly embraced by patients – it also needs to have the right measures in place to safeguard protected health information (PHI) to determine if it is indeed HIPAA compliant.

Whether you’re a healthcare provider, software vendor, product team, or IT professional, understanding what makes software HIPAA compliant is essential for safeguarding patient data and insulating your organization from the consequences of falling afoul of HIPAA regulations. 

With this in mind, this post breaks down the key indicators of HIPAA compliant software, the technical requirements you should look for, and best practices for ensuring your software is HIPAA compliant.

What Does It Mean for Software to Be HIPAA-Compliant?

The Health Insurance Portability and Accountability Act (HIPAA)  sets national standards for safeguarding PHI, which includes any data related to a patient’s health, treatment, or payment details. In light of this, any applications and systems used to process, transmit, or store PHI must comply with the stringent privacy, security, and breach notification requirements set forth by HIPAA.

Subsequently, while healthcare organizations use a wide variety of software, most of it is likely to be HIPAA-compliant. Alarmingly, many companies aren’t aware of which applications are HIPAA-compliant and, more importantly, if there’s a need for compliance in the first place.   

However, it’s important to note that HIPAA itself does not certify software. Instead, it’s up to software vendors to implement the necessary security and privacy measures to ensure HIPAA compliance. Subsequently, it’s up to healthcare providers, payers, and suppliers to do their due diligence and source HIPAA compliant software. 

How to Determine If Software Is HIPAA Compliant

So, now that we’ve covered why it’s vital that the applications and systems through which sensitive patient data flows must be HIPAA compliant, how do you determine if your software meets HIPAA requirements? To assess whether software is HIPAA compliant, look for these key indicators:

1. Business Associate Agreement (BAA)

A HIPAA compliant software provider must sign a Business Associate Agreement (BAA) with covered entities, i.e., the healthcare company. A BAA is a legal contract that outlines the vendor’s responsibility for safeguarding PHI. If a software provider doesn’t offer a BAA, their software is NOT HIPAA compliant.

Now, if a vendor offers a BAA, it should be presented front and center in their benefits, terms or conditions, if not on their website homepage as part of their key features. If a vendor has taken the time and effort to make their infrastructure robust enough to meet HIPAA regulations, they’ll want to make it known to reassure healthcare organizations of their suitability to their particular needs.  

2. End-to-End Encryption

A key requirement of the HIPAA Security Rule is that sensitive patient data is encrypted end to end during its transmission. This means being encrypted during transit, i.e., when sent in an email or entered into a form, and at rest, i.e., within the data store in which it resides.

In light of this, any software that handles PHI should use strong encryption standards, such as:

  • Transport Layer Security (TLS – 1.2 or above): for secure transmission of PHI in email and text communications. 
  • AES (Advanced Encryption Standard) 256: the preferred encryption method for data storage as per HIPAA security standards, due to its strength.

3. Access Controls and User Authentication

One of the key threats to the privacy of patient data is access by unauthorized parties. This could be from employees within the organization who aren’t supposed to have access to PHI. In some, or even many, cases, this may come down to lax and overly generous access policies. However, this can result in the accidental compromise of PHI, affecting both a patient’s right to privacy and, in the event patient data is unavailable, operational capability. 

Alternatively, the exposure of PHI can be intentional. One on hand, it may be from employees working on behalf of other organizations, i.e., disgruntled employees about to jump ship to a competitor. More commonly, unauthorized access to patient data is perpetrated by malicious actors impersonating healthcare personnel. To prevent the unintended exposure of PHI, HIPAA compliant infrastructure, software and applications must support access control policies, such as:

  • Role-based access control (RBAC): the restriction of access to PHI based on their job responsibility in handling PHI, i.e.., an employee in billing or patient outreach. A healthcare organization’s security teams can configure access rights based on an employee’s need to handle patient data in line with their role in the company. 
  • Multi-factor authentication (MFA): this adds an extra layer of security beyond user names and passwords. This could include a one-time password (OTP) sent via email, text, or a physical security token. MFA is very diverse and can be scaled up to reflect a healthcare organization’s security posture. This could include also biometrics, such as retina and fingerprint scans, as well as voice verification.
  • Zero-trust security: a rapidly emerging security paradigm in which users are consistently verified, as per the resources they attempt to access. This prevents session hijacking, in which a user’s identity is trusted upon an initial login and verification. Instead, zero trust continually verifies a user’s identity.  
  • Robust password policies: another simple, but no less fundamental, component of user authentication is a company’s password policy. While conventional password policies emphasize complexity, i.e., different cases, numbers, and special characters, newer password policies, in contrast, emphasize password length. 

4. Audit Logs & Monitoring

A key HIPAA requirement is that healthcare organizations consistently track and monitor employee access to patient data. It’s not enough that access to PHI is restricted. Healthcare organizations must maintain visibility over how patient data is being accessed, transferred, and acted upon (copied, altered, deleted). This is especially important in the event of a security event when it’s imperative to pinpoint the source of a breach and contain its spread.

In light of this, HIPAA compliant software must:

  • Maintain detailed audit logs of all employee interactions with PHI.
  • Provide real-time monitoring and alerts for suspicious activity.
  • Support log retention for at least six years, as per HIPAA’s compliance requirements.

5. Automatic Data Backup & Disaster Recovery

Data loss protection (DLP) is an essential HIPAA requirement that requires organizations to protect PHI from loss, corruption, or disasters. With this in mind, a HIPAA-compliant software solution should provide:

  • Automated encrypted backups: real-time data backups, to ensure the most up-to-date PHI is retained in the event of a security breach.
  • Comprehensive disaster recovery plans: to rapidly restore data in case of cyber attack, power outage, or similar event that compromises data access.  
  • Geographically redundant storage: a physical safeguard that sees PHI. stored on separate servers in different locations, far apart from each other. So, if one server goes down or is physically compromised (fire, flood, power outage, etc.,) patient data can still be accessed. 

6. Secure Messaging and Communication Controls

For software that involves email, messaging, or telehealth, i.e., phone or video-based interactions, in particular, HIPAA regulations require:

  • End-to-end encryption: for all communications, as detailed above.
  • Access restrictions: policies that only enable those with the appropriate privileges to view communications containing patient data.
  • Controls for message expiration: automatically deleting messages after a prescribed time to mitigate the risk of unauthorized access.
  • Audit logs: to monitor the inclusion or use of patient data.

7. HIPAA Training & Policies

Even the most secure software can be compromised if its users aren’t sufficiently trained on how to use it. More specifically, the risk of a security breach is amplified if employees don’t know how to identify suspicious behavior and who to report it to if an event occurs. With this in mind, it’s prudent to look for software vendors that:

  • Offer HIPAA compliance and cyber safety awareness training for users.
  • Implement administrative safeguards, such as usage policy enforcement and monitoring.
  • Support customizable security policies to align with your organization’s compliance needs.

Shadow IT and HIPAA Compliance

Shadow IT is an instance of an application or system being installed and used within a healthcare organization’s network without an IT team’s approval. Despite its name, shadow IT is not as insidious as it sounds: it’s simply a case of employees unwittingly installing applications they feel will help them with their work. The implications, however, are that:

  1. IT teams are unaware of said application, and how data flows through it, so they can’t secure any PHI entered into it.
  2. The application may have known vulnerabilities that are exploitable by malicious actors. This is all the more prevalent with free and/or open-source software.

While discussing the issue of shadow IT in general, it’s wise to discuss the concept of “shadow AI” – the unauthorized use of artificial intelligence (AI) solutions within an organization without its IT department’s knowledge or approval. 

It’s easily done: AI applications are all the rage and employees are keen to reap the productivity and efficiency gains offered by the rapidly growing numbers of AI tools. Unfortunately, they fail to stop and consider the data security risks present in AI applications. Worse, with AI technology still in its relative infancy, researchers, vendors, and other industry stakeholders have yet to develop a unified framework for securing AI systems, especially in healthcare. 

Consequently, the risks of entering patient data into an AI system – particularly one that’s not been approved by IT – are considerable. The privacy policies of many widely-used AI applications, such as ChatGPT, state the data entered into the application, during the course of engaging with the platform, can be used in the training of future AI models. In other words, there’s no telling where patient data could end up – and how and where it could be exposed. 

The key takeaway here is that entering PHI into shadow IT and AI applications can pose significant risks to the security of patient data, and employees should only use solutions vetted, deployed, and monitored by their IT department. 

Best Practices for Choosing HIPAA Compliant Software

Now that you have a better understanding of how to evaluate software regarding HIPAA compliance, here are some best practices to keep in mind when selecting applications to facilitate your patient engagement efforts:

Look for a BAA: quite simply, having a BAA in place is an essential requirement of HIPAA-compliant software. So, if the vendor doesn’t offer one, move on.

Verify encryption standards: ensure the software encrypts PHI both at rest and in transit.

Test access controls: choose HIPAA-compliant software that allows you to restrict access to PHI based on an employee’s role within the organization. 

Review audit logging capabilities: HIPAA compliant software should track every PHI interaction. This also greatly assists in incident detection and reporting (IDR), as it enables security teams to pinpoint and contain cyber threats should they arise.

Ensure compliance support: knowing the complexities of navigating HIPAA regulations, a reputable software vendor should provide comprehensive documentation on configuring their solution to match the client’s security needs. Better yet, they should provide the option of cyber threat awareness and HIPAA compliance training services. 

Create a List of Software Vendors: combining the above factors, it’s prudent for healthcare organizations to compile a list of HIPAA compliant software vendors that possess the features and capabilities to adequately safeguard PHI.

Choosing HIPAA Compliant Software

Matching the right software to a company’s distinctive workflows and evolving needs is challenging enough. However, for healthcare companies, ensuring the infrastructure and applications within their IT ecosystem also meet HIPAA compliance standards requires another layer of, often complicated, due diligence. 

Failure to deploy a digital solution that satisfies the technical, administrative, and physical security measures required in a HIPAA compliant solution exposes your organization to the risk of suffering the repercussions of non-compliance. 

If select and deploy the appropriate HIPAA compliant software, in contrast, your options for patient and customer engagement are increased, and you’ll be able to include PHI in your communications to improve patient engagement and drive better health outcomes. Schedule a consultation with one of our experts at LuxSci to discuss whether the software in your IT ecosystem meets HIPAA regulations. and how we can assist you in ensuring your organization is communicating with patient and customers in a HIPAA compliant way.

HIPAA Compliant

Is Microsoft Forms HIPAA Compliant?

Microsoft Forms is considered HIPAA compliant only when properly configured within a Microsoft 365 Enterprise or Business environment with an executed Business Associate Agreement (BAA). Unlike various competing products, Microsoft includes Forms among its covered services in its BAA, allowing healthcare organizations to collect protected health information when implemented with proper security controls and organizational policies.

Microsoft Business Associate Agreement Coverage

Microsoft offers a BAA that covers Microsoft Forms when used within a properly licensed Microsoft 365 environment. This agreement establishes Microsoft as a business associate under HIPAA regulations and defines responsibilities for protecting healthcare information. The BAA covers Microsoft Forms along with other Microsoft 365 services such as Exchange Online, SharePoint Online, and Teams. Healthcare organizations must execute this agreement before using Microsoft Forms to collect protected health information. The BAA establishes contractual protections beyond standard terms of service and the requirements of becoming HIPAA compliant.

Required Configuration for HIPAA Compliance

Making Microsoft Forms HIPAA compliant requires specific configuration beyond simply signing a BAA. Organizations must implement appropriate access controls using Microsoft 365 administrative settings to restrict form creation and data access to authorized personnel. Enabling audit logging through the Microsoft 365 Compliance Center helps track who creates, modifies, and accesses form data. Organizations need to configure retention policies that align with HIPAA record-keeping requirements. Multi-factor authentication adds an essential security layer for employees accessing protected health information. These technical controls work together to create a compliant environment for collecting patient information.

Security Features in Microsoft Forms

Microsoft Forms includes several security capabilities that support HIPAA compliance requirements. The platform encrypts data both during transmission and storage within Microsoft’s infrastructure. Access controls integrate with Microsoft 365 identity management to restrict form data visibility. Audit capabilities track form creation, modification, and response activities. Microsoft’s cloud infrastructure meets various compliance certifications beyond HIPAA, including FedRAMP, ISO 27001, and SOC standards. These underlying security measures provide the technical foundation for compliant form implementation when properly configured.

Limitations and Compliance Considerations

While Microsoft Forms can be HIPAA compliant, certain limitations require attention from healthcare organizations. The standard form templates do not include healthcare-specific authorization language required by the HIPAA Privacy Rule. Organizations must customize forms to include appropriate patient consent statements and privacy notices. Certain advanced features like form branching may create complexity in tracking what information appears to which respondents. Organizations need policies governing form creation and approval to ensure all necessary compliance elements appear consistently. These limitations require procedural controls beyond technical configuration.

Implementation Best Practices

Healthcare organizations implementing Microsoft Forms for collecting protected health information can benefit from following established best practices. Creating standardized form templates with pre-approved compliance language helps maintain consistency. Limiting form creation permissions to trained staff members reduces compliance risks. Regular privacy and security training for all employees who handle form data improves organizational awareness. Conducting periodic audits of form content and access patterns identifies potential compliance issues. Integrating forms with secure document storage in SharePoint improves information governance. These practices can enhance the security of patient information collected through electronic forms.

Alternative Form Solutions and Considerations

Microsoft Forms can be considered HIPAA compliant, but organizations should evaluate whether it provides the optimal solution for their needs. Specialized healthcare form platforms may offer additional features like electronic signature capture, direct EHR or CDP integration, or healthcare-specific templates. Microsoft Forms works best for organizations already invested in the Microsoft 365 ecosystem who need integrated form capabilities. The decision between Microsoft Forms and alternatives like LuxSci depends on factors including existing technology investments, integration requirements, complexity of form needs, and organizational resources for configuration and maintenance.

patient engagement solutions

HIPAA And Explanation of Benefits Notifications

Explanation of benefits notifications are detailed summaries of healthcare claims processing that health plans send to members after receiving and adjudicating medical service claims from healthcare providers. These documents contain protected health information including patient names, dates of service, provider details, diagnostic codes, and payment information that falls under HIPAA privacy and security requirements. Healthcare providers, payers, and suppliers must understand how HIPAA regulations govern the creation, transmission, and storage of explanation of benefits communications to maintain compliance while serving their members effectively. Understanding the intersection of HIPAA requirements and explanation of benefits processes helps healthcare organizations avoid costly violations while maintaining transparent communication with patients about their healthcare coverage and claims.

Privacy Requirements for Explanation of Benefits Content

HIPAA privacy regulations establish specific requirements for how explanation of benefits documents can include, display, and protect patient information during all phases of the communication process. Health plans must ensure that explanation of benefits contain only the minimum necessary information required to inform patients about their claims processing while avoiding unnecessary disclosure of sensitive medical details. This requirement means that diagnosis codes, procedure descriptions, and provider notes should be limited to what patients need to understand their coverage and payment responsibilities.

The privacy rule permits health plans to include certain types of information in explanation of benefits without obtaining additional patient authorization, as these communications fall under permitted uses for payment and healthcare operations. Patient names, dates of service, provider names, and basic claim information can be included because they serve legitimate business purposes in helping patients understand their insurance coverage. Detailed clinical notes, mental health treatment specifics, or other sensitive medical information may require additional privacy protections or patient consent.

Explanation of benefits documents must include clear privacy notices that inform patients about how their protected health information is being used and their rights regarding this information. These notices should explain how patients can request restrictions on information use, file complaints about privacy practices, and access their complete medical records. Health plans must also provide contact information for privacy officers who can address patient concerns about their explanation of benefits communications.

The minimum necessary standard requires health plans to evaluate whether all information included in explanation of benefits serves a legitimate purpose for patient understanding or claims administration. This evaluation should consider whether patients truly need access to specific diagnostic codes, provider credentials, or detailed procedure descriptions to understand their coverage. Regular review of explanation of benefits content helps ensure compliance with privacy requirements while maintaining useful communication with plan members.

Security Safeguards for Electronic Explanation of Benefits

Electronic transmission and storage of explanation of benefits requires implementation of administrative, physical, and technical safeguards to protect the protected health information contained within these documents. Administrative safeguards include appointing security officers responsible for explanation of benefits systems, conducting regular workforce training on privacy requirements, and establishing procedures for granting and revoking access to explanation of benefits databases. These safeguards help ensure that only authorized personnel can access patient information during explanation of benefits processing.

Physical safeguards protect the computer systems, equipment, and facilities where explanation of benefits are created, stored, and transmitted from unauthorized access or environmental hazards. Health plans must implement access controls for data centers, secure workstation configurations for staff accessing explanation of benefits systems, and media disposal procedures for devices containing patient information. Protections help prevent unauthorized individuals from accessing explanation of benefits data through physical security breaches.

Technical safeguards focus on access controls, audit logging, data integrity measures, and transmission security for explanation of benefits systems. Health plans must implement user authentication systems that verify the identity of individuals accessing explanation of benefits data, maintain detailed audit logs of all system activities, and use encryption to protect explanation of benefits during transmission and storage. Technical controls help detect and prevent unauthorized access to patient information.

Regular security assessments of explanation of benefits systems help identify vulnerabilities that could lead to data breaches or unauthorized disclosures. Health plans should conduct penetration testing, vulnerability scanning, and security audits of their explanation of benefits platforms to ensure that technical safeguards remain effective against evolving cyber threats. Documentation of these assessments demonstrates ongoing commitment to protecting patient information in explanation of benefits communications.

Patient Rights and Access to Explanation of Benefits

Patients have specific rights under HIPAA regarding their explanation of benefits, including the right to receive copies in accessible formats, request amendments to incorrect information, and control how these documents are delivered to them. Health plans must accommodate reasonable requests for explanation of benefits in alternative formats, such as large print, electronic delivery, or translation into other languages when patients have communication barriers. Accommodations help ensure that all patients can understand their coverage and claims processing regardless of their individual circumstances.

The right to request amendments applies when patients identify errors in their explanation of benefits, such as incorrect dates of service, wrong provider information, or inaccurate claim amounts. Health plans must have established procedures for handling these amendment requests, including timeframes for responding to patients and processes for investigating and correcting errors. When amendments are approved, health plans must notify patients and update their records accordingly.

Patients can designate how they prefer to receive explanation of benefits notifications, including requesting that documents be sent to alternative addresses for safety reasons or medical necessity. Health plans must honor these requests when they are reasonable and help protect patient privacy or safety. This flexibility allows patients to maintain control over their personal information while ensuring they receive important coverage information.

Access rights extend to requesting accounting of disclosures related to explanation of benefits information, allowing patients to understand who has received their protected health information and for what purposes. Health plans must maintain records of explanation of benefits disclosures and provide this information to patients upon request. These accounting requirements help patients monitor how their information is being shared and identify any unauthorized uses.

Disclosure Rules for Explanation of Benefits Information

HIPAA establishes specific rules governing when and how health plans can disclose explanation of benefits information to third parties, including healthcare providers, family members, and business partners. Disclosure for treatment purposes allows health plans to share relevant explanation of benefits information with healthcare providers who need this data to coordinate patient care or understand coverage limitations. These disclosures must be limited to information necessary for the specific treatment purpose.

Payment-related disclosures permit health plans to share explanation of benefits information with healthcare providers for billing and claims processing purposes. Providers may need access to explanation of benefits data to understand payment amounts, coverage decisions, and patient responsibility amounts. These disclosures help facilitate efficient payment processing while maintaining patient privacy protections.

Healthcare operations disclosures allow health plans to share explanation of benefits information for quality improvement activities, care coordination, and administrative functions that support patient care. These uses must serve legitimate business purposes and comply with minimum necessary standards. Health plans must evaluate whether proposed disclosures serve appropriate healthcare operations purposes before sharing explanation of benefits information.

Disclosure to family members or personal representatives requires either patient authorization or demonstration that the person has legal authority to act on behalf of the patient. Health plans cannot automatically share explanation of benefits information with spouses, adult children, or other family members without proper authorization. Emergency situations may provide exceptions to this requirement when immediate disclosure is necessary for patient safety or care coordination.

Business Associate Requirements for Explanation of Benefits Processing

Third-party vendors involved in explanation of benefits processing must operate as business associates under HIPAA and comply with specific privacy and security requirements when handling protected health information. Business associate agreements must clearly define how vendors will protect explanation of benefits data, limit its use to authorized purposes, and implement appropriate safeguards during processing activities. Agreements of this nature help ensure that outsourced explanation of benefits functions maintain the same privacy protections required of health plans.

Common business associates in explanation of benefits processing include printing companies, mailing services, electronic delivery platforms, and customer service providers. Each of these relationships requires careful evaluation of privacy and security risks, along with appropriate contractual protections. Health plans must verify that business associates have adequate security measures in place before allowing them to handle explanation of benefits information.

Business associates must implement their own administrative, physical, and technical safeguards for explanation of benefits data and ensure that any subcontractors also comply with HIPAA requirements. This includes providing security training to their workforce, maintaining audit logs of information access, and reporting security incidents to the health plan. Business associates also must return or destroy explanation of benefits information when their contracts end, unless retention is required for legal purposes.

Regular monitoring and oversight of business associate performance helps ensure ongoing compliance with HIPAA requirements for explanation of benefits processing. Health plans should conduct periodic audits of business associate security practices, review incident reports, and verify that contractual obligations are being met. This oversight helps identify potential compliance issues before they result in privacy violations or security breaches.

Compliance Monitoring and Breach Response

Healthcare organizations must establish comprehensive monitoring programs to ensure that explanation of benefits processing remains compliant with HIPAA requirements and identify potential issues before they result in violations. Regular audits should examine explanation of benefits content for appropriate privacy protections, verify that security safeguards are functioning correctly, and assess whether disclosure practices comply with regulatory requirements. Audits help demonstrate ongoing commitment to protecting patient information.

Incident response procedures specifically address explanation of benefits-related security breaches or privacy violations, including notification requirements and remediation steps. Health plans must have clear procedures for investigating potential breaches, determining whether notification is required, and implementing corrective actions to prevent future incidents. Training on incident response helps ensure that staff can recognize and respond appropriately to explanation of benefits security issues.

Documentation requirements include maintaining records of explanation of benefits policies, training activities, security assessments, and compliance monitoring efforts. This documentation helps demonstrate compliance efforts during regulatory investigations and supports continuous improvement of explanation of benefits processes. Health plans should retain documentation for required periods and ensure that records are complete and accessible when needed.

Staff training programs must address HIPAA requirements specific to explanation of benefits processing, including privacy obligations, security procedures, and appropriate handling of patient information. Training should be provided to all personnel involved in explanation of benefits creation, transmission, and storage, with regular updates to address regulatory changes and emerging threats. Competency assessments help verify that staff understand their responsibilities for protecting patient information in explanation of benefits communications.