LuxSci

Can You Send PHI Through HIPAA Email?

HIPAA Compliant Email

Yes, you can send protected health information (PHI) under HIPAA through email when using appropriate security measures and compliant email systems designed to protect protected health information during electronic transmission. Sending PHI through email requires encryption, access controls, audit logging, and other safeguards that meet regulatory standards for protecting patient information in digital communications. Healthcare providers, payers, and suppliers can transmit protected health information via email when they implement proper security protocols and use compliant email platforms. Understanding how to send HIPAA through email safely helps organizations maintain regulatory compliance while conducting routine business communications and patient care coordination activities.

Security Requirements for Sending HIPAA Through Email

Sending PHI through email requires end-to-end encryption that protects messages and attachments from unauthorized access during transmission and storage. Healthcare organizations cannot use standard email platforms like Gmail, Yahoo, or Outlook for transmitting protected health information without additional security measures. Encryption protocols transform readable text into coded format that only authorized recipients can decrypt and access. uthentication mechanisms verify the identity of both senders and recipients before allowing access to encrypted email content. Digital certificates provide additional verification that messages originated from legitimate healthcare organizations and have not been tampered with during transmission. Secure transmission protocols protect email communications from interception by unauthorized parties during delivery to intended recipients.

Permitted Uses When Sending HIPAA Through Email

Healthcare organizations can send HIPAA through email for treatment, payment, and healthcare operations without obtaining patient authorization. Treatment communications include sharing patient information between healthcare providers involved in care coordination, referrals, and consultation activities. Payment-related emails may include billing information, insurance claims, and financial communications with patients or payers. Healthcare operations encompass quality improvement activities, staff training materials, and administrative communications that support patient care delivery. Patient communications via secure email may include appointment reminders, lab results, and discharge instructions when appropriate safeguards are implemented. For business associate communications, HIPAA through email is permissible when vendors have signed the appropriate agreements and maintain compliant systems.

Prohibited Practices When Sending HIPAA Through Email

Regular email platforms without encryption cannot be used for sending HIPAA through email due to inadequate security protections. Healthcare organizations cannot send protected health information via text message, social media platforms, or other unsecured digital communication channels. Forwarding encrypted emails to non-compliant systems compromises security and violates HIPAA requirements. Sending protected health information to unauthorized recipients constitutes a privacy violation regardless of the security measures used. Healthcare staff cannot use personal email accounts for work-related communications involving patient information. Storing protected health information in unsecured cloud storage systems or sharing login credentials for secure email accounts creates compliance risks and potential security breaches.

Technical Implementation for HIPAA Through Email

Healthcare organizations implementing systems for sending PHI through email need secure email gateways that integrate with existing IT infrastructure. These systems automatically encrypt outgoing messages containing protected health information and provide secure delivery mechanisms for recipients. Message encryption occurs before transmission, ensuring that sensitive content remains protected throughout the delivery process. Recipient verification systems confirm that emails reach intended recipients and prevent unauthorized access to protected health information. Secure message retrieval processes may require recipients to authenticate their identity before accessing encrypted content. Audit logging capabilities track all email activities, including message transmission, recipient access, and any forwarding or reply activities involving protected health information.

Staff Training for HIPAA Through Email Compliance

Healthcare organizations must train staff on proper procedures for sending HIPAA through email and recognizing when additional security measures are needed. Training programs cover identification of protected health information, appropriate use of secure email systems, and policies for handling patient communications. Staff members learn to distinguish between communications that require encryption and those that can use standard email platforms. Policy education includes guidelines for password management, secure login procedures, and incident reporting requirements when security concerns arise. Regular refresher training keeps staff updated on changing regulations and organizational policies for email security. Competency assessments verify that staff members understand their responsibilities when handling protected health information in email communications.

Compliance Monitoring and Risk Management

Healthcare organizations need ongoing monitoring programs to ensure that practices for sending HIPAA through email remain compliant with regulatory requirements. Regular audits review email security configurations, user access controls, and compliance with organizational policies. Risk assessments identify potential vulnerabilities in email systems and communication processes that could lead to privacy violations. Incident response procedures address potential security breaches or unauthorized disclosures involving email communications. Documentation requirements include maintaining records of security training, policy updates, and compliance monitoring activities. Organizations benefit from establishing clear accountability structures and regular review processes that demonstrate ongoing commitment to protecting patient privacy in all email communications involving protected health information.

Picture of Erik Kangas

Erik Kangas

With 30 years engaged in to both academic research and software architecture, Erik Kangas is the founder and Chief Technology Officer of LuxSci, playing a core role in building the company into the market leader for HIPAA compliant, secure healthcare communications solutions that it is today. An international lecturer on messaging security, Erik also advises and consults on email technology strategies and best practices, secure architectures, and HIPAA compliance. Erik holds undergraduate degrees in physics and mathematics from Case Western Reserve University, and a doctoral degree in computational biophysics from MIT. Erik Kangas — LinkedIn

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

HIPAA Security Rule Email Encryption Requirements

HIPAA Compliant Email

Your Email Platform Is Becoming Critical Healthcare Infrastructure

Most healthcare organizations view email as a utility, a necessary tool for sending messages between staff, communicating with patients, sending out newsletters, connecting workflows, and so on. Historically, IT teams focused on keeping it running, security teams worried about phishing, and compliance teams made sure sensitive emails were encrypted.

Today, however, that view is rapidly becoming outdated.

Email has evolved into one of healthcare’s most critical digital infrastructure components, and also one of it’s biggest security threats. It’s a core channel for patient engagement, care coordination, revenue cycle operations, digital marketing, remote monitoring, and increasingly, AI-powered communications. The organizations that recognize this shift are building communications platforms designed for security, performance, automation, and growth. With the new HIPAA Security Rule requiring email encryption on the horizon, those companies that don’t may find themselves constrained by systems that were never intended to support modern healthcare.

Email Is No Longer Just a Messaging Tool

Healthcare organizations now depend on email to support dozens of mission-critical workflows every day.

Patients receive appointment reminders, registration instructions, imaging results, billing notifications, Explanation of Benefits (EOBs), prescription updates, preventive care reminders, patient education, and post-discharge follow-up.  Marketing teams deliver personalized wellness campaigns and service line promotions. Clinical systems generate transactional notifications. Revenue cycle teams rely on secure digital communications to accelerate payments and reduce paper costs.

For many organizations, mission-critical patient communications flow through email every month.

When viewed collectively, email is more than a simple communications channel. It has become operational infrastructure with high levels of security needed and increasing compliance requirements.

The Stakes Continue to Rise

As healthcare becomes more digital, every communication carries greater business and clinical importance.

A delayed billing email may postpone payment. A failed appointment reminder can increase no-show rates. An undelivered care management message may impact patient outcomes. A misconfigured security policy can expose protected health information (PHI). Poor deliverability can undermine expensive patient engagement initiatives before they ever reach the inbox.

These are no longer isolated IT issues. Email can affect revenue, patient satisfaction, operational efficiency, compliance, and organizational reputation.

Today’s healthcare leaders require email infrastructure to provide the same reliability and visibility they demand from electronic health records, identity management systems, and other core infrastructure.

AI Is Raising the Bar Even Higher

There’s little doubt that artificial intelligence (AI) promises to transform patient communications.

Healthcare organizations everywhere are exploring AI-generated patient education, personalized outreach, intelligent scheduling, multilingual communications, and automated follow-up programs.

But AI also increases the importance of the underlying communications infrastructure.

Generating more personalized emails means little if organizations cannot:

  • Automatically protect PHI.
  • Apply consistent security policies.
  • Maintain complete audit trails.
  • Deliver messages reliably.
  • Integrate with EHRs, RCM and CRM platforms, and customer data platforms.
  • Demonstrate compliance during an audits.

In many ways, AI amplifies both the opportunities and the risks. Your email platform can help determine whether AI initiatives succeed or create new compliance and operational challenges.

Infrastructure Matters More Than Features

Healthcare buyers have traditionally evaluated email platforms based on individual features such as encryption, spam filtering, or secure portals.

Those capabilities remain important, but they no longer tell the whole story.

Today’s healthcare organizations should be evaluating communications platforms the same way they evaluate any mission-critical infrastructure.

Questions increasingly include:

  • Can it support both transactional and marketing communications?
  • Does it automatically enforce security policies without relying on user decisions?
  • Can it integrate with EHRs, CRM systems, CDPs, and business applications?
  • Will it scale during peak communication periods?
  • Does it provide detailed audit logging and reporting?
  • Can it adapt as regulatory expectations evolve?
  • Does it maintain high deliverability at enterprise scale?
  • Does it support single-tenant dedicated infrastructure for high performance and increased security?

These infrastructure characteristics often determine long-term success far more than any single feature comparison.

Email and the Future Of Secure Healthcare Communications

Healthcare is steadily moving toward a world where nearly every patient interaction is digital, personalized, and data-driven.

Healthcare leaders often ask whether they need a more secure email solution. That may be the wrong question.

The better question is whether their communications infrastructure is ready for where healthcare is headed over the next decade.

If you want talk about the future of your healthcare email infrastructure, reach out today and schedule a 30-minute assessment call with our experts.

Set Up a Call

HIPAA Security Rule Update

The HIPAA Security Rule Missed Its May Deadline — Here’s What We Know

The proposed HIPAA Security Rule update has become one of the most closely watched healthcare compliance developments in recent years. Designed to strengthen cybersecurity protections for electronic protected health information (ePHI), the proposal could significantly reshape how healthcare organizations approach risk management, ePHI encryption, and mandatory email encryption requirements.

A final rule was expected as early as May 2026. However, that deadline has now passed without publication from the U.S. Department of Health and Human Services (HHS) Office for Civil Rights (OCR).

So, what happens next—and what should healthcare IT directors, CISOs, and compliance officers do now?

Where Things Stand Today

The HIPAA Security Rule Notice of Proposed Rulemaking (NPRM) was published on January 6, 2025, with the goal of strengthening cybersecurity protections for ePHI in response to escalating ransomware attacks, healthcare breaches, and growing concerns about cyber resilience across the healthcare sector.

The proposal generated thousands of public comments from healthcare providers, payers, business associates, technology vendors, and industry groups. OCR has spent much of the past year reviewing this feedback and evaluating the operational and financial impact of the proposed changes.

Although the Spring Unified Regulatory Agenda identified May 2026 as a target date for a final rule, that milestone came and went without publication. As of June 2026, the proposed HIPAA Security Rule update remains under review.

While some organizations may be tempted to take a wait-and-see approach, the missed deadline should not be interpreted as a signal that the initiative has stalled. If anything, the proposal offers valuable insight into the future direction of healthcare cybersecurity regulation.

The Growing Focus on Mandatory Email Encryption

One of the most discussed aspects of the proposed HIPAA Security Rule update is encryption.

Under the current HIPAA Security Rule, encryption is generally classified as an “addressable” implementation specification. Organizations can choose alternative safeguards if they document and justify their decisions through a risk analysis process.

The proposed changes would significantly reduce that flexibility. Instead, many security safeguards, including encryption controls, would become more prescriptive and difficult to avoid.

While the final language has not yet been released, healthcare organizations should pay close attention to the proposal’s clear message: protecting ePHI through encryption is increasingly viewed as a baseline cybersecurity requirement.

This is particularly important for email communications.

Email remains one of the most widely used communication channels in healthcare, supporting everything from patient engagement and care coordination to billing, scheduling, and marketing communications. As regulators continue to focus on reducing data breach risks, mandatory email encryption is emerging as a likely area of increased scrutiny.

What Healthcare Organizations Should Do Now

The current delay creates an opportunity, not a reason to postpone action.

Healthcare organizations can begin preparing for likely requirements today by evaluating the security controls highlighted throughout the proposed rule.

Key areas to review include:

  • Encryption of ePHI across systems and communications channels
  • Comprehensive asset inventories and ePHI data mapping
  • Enhanced risk analysis and risk management processes
  • Multifactor authentication (MFA)
  • Vulnerability scanning and penetration testing
  • Incident response planning and testing
  • Backup and recovery procedures
  • Email security and secure email encryption practices

Organizations that proactively strengthen these areas now will be better prepared regardless of the final rule’s implementation timeline.

Why Secure Email Encryption Should Be a Priority

For many healthcare organizations, email remains one of the largest compliance and security risks.

Human error, misdirected messages, phishing attacks, and inconsistent encryption practices continue to contribute to breaches involving protected health information. As a result, secure email encryption is increasingly becoming a foundational component of healthcare cybersecurity strategies.

Organizations that rely on manual encryption processes or employee judgment alone may find it difficult to meet evolving regulatory expectations.

Instead, healthcare organizations should look for solutions that automate encryption decisions, reduce user error, and provide flexibility based on the sensitivity of the communication.

At LuxSci, we have long believed that security and usability must work together. We are 100% focused on secure healthcare communications, helping healthcare providers, payers, and suppliers protect sensitive data while improving patient and customer engagement. Our proven secure email solutions, used by leading companies including Athenahealth, 1-800 Contacts, and Hinge Health, help organizations protect ePHI with automated encryption capabilities that support both compliance and operational efficiency. Our unique SecureLine encryption technology enables organizations to apply the appropriate level of protection while maintaining a seamless experience for patients, customers, and staff.

For organizations already using Microsoft 365 or Google Workspace, LuxSci Secure Email Gateway can add HIPAA-compliant email security and encryption without requiring users to change their existing workflows. This approach helps reduce risk, while preserving productivity and user adoption.

The Bottom Line

The HIPAA Security Rule final rule may have missed its anticipated May deadline, but the cybersecurity challenges driving the proposal remain very real.

The OCR is still expected to make the rule change, which could require mandatory encryption of ePHI by early 2027.

The time to prepare is now!

Healthcare organizations should view the proposed HIPAA Security Rule update as an advance warning of where regulatory expectations are heading. Stronger cybersecurity controls, enhanced risk management, ePHI encryption, and mandatory email encryption requirements are all likely to remain central themes in future compliance efforts.

The organizations that begin preparing now will not only be better positioned for future regulatory changes, but will also strengthen their ability to protect patient data, reduce risk, and build trust in an increasingly challenging threat landscape.

At LuxSci, we’re proud to support the healthcare industry’s ongoing digital transformation through secure healthcare communications. Our HIPAA-compliant solutions for secure email, email marketing, and forms empower organizations to safely use and protect PHI, while delivering better patient experiences and outcomes.

Ready to strengthen your healthcare cybersecurity strategy?

Learn more about LuxSci and our complete suite of HIPAA compliant email and marketing solutions, or schedule a consultation with one of our healthcare communication experts today.

Contact us today!

LuxSci G2

LuxSci Awarded 20 Badges in the G2 Summer 2026 Reports

We’re excited to announce that LuxSci has again been recognized by G2 with 20 badges in its just-released Summer 2026 Reports, highlighting our continued leadership in secure healthcare communications and HIPAA compliant email solutions.

The new LuxSci G2 recognitions span several categories, including:

  • Best Estimated ROI
  • Best Support
  • High Performer
  • Leader

These latest LuxSci G2 awards reflect what matters most to our customers: delivering secure, HIPAA compliant healthcare communications backed by responsive support and measurable business results.

As one of the most trusted providers of HIPAA compliant email, marketing, and forms solutions, we’re proud to see our commitment recognized across multiple product categories and customer satisfaction metrics.

Recognition Built on Customer Experience

LuxSci’s G2 rankings are based on verified customer feedback and real-world user experiences, making these badges especially meaningful to our team.

This year’s Summer Reports recognized LuxSci for consistently delivering value to healthcare organizations looking to securely engage patients and customers while maintaining compliance with HIPAA requirements.

Among the highlights, the LuxSci G2 recognition includes:

  • Best Estimated ROI, reflecting the measurable value customers achieve through secure healthcare communications and personalization
  • Best Support, reinforcing LuxSci’s long-standing reputation for responsive, knowledgeable customer service
  • High Performer badges across multiple categories for customer satisfaction and product performance
  • Leader recognition for delivering secure, scalable communications solutions trusted by healthcare organizations

At LuxSci, we believe secure communications should also drive better engagement, stronger outcomes and operational efficiency. These recognitions reinforce our focus on helping healthcare providers, payers and suppliers personalize communications while protecting sensitive patient data.

Supporting the Future of Personalized Healthcare Engagement

LuxSci’s secure healthcare communication and patient engagement solutions empower organizations to safely communicate with patients and customers through:

  • HIPAA-compliant high volume email
  • Secure email marketing
  • Secure forms and data collection
  • Flexible encryption with SecureLine technology

Our solutions are designed to help healthcare organizations improve engagement, streamline workflows and personalize the healthcare journey while maintaining the highest standards of security and compliance.

These latest LuxSci G2 recognitions also build on LuxSci’s broader reputation for security, performance and customer success. Security and trust remain foundational to everything we do, alongside our commitment to delivering smart, responsive support for our customers.

Thank You to Our Customers

We’re grateful to our customers for their continued trust, collaboration and feedback. Their reviews and insights help shape our products and drive ongoing innovation across the LuxSci product set.

To learn more about LuxSci’s secure healthcare communications solutions, contact our team to schedule a secure email assessment or demo.

Connect with us today!

Follow us on LinkedIn

You Might Also Like

HIPAA Email Policy

What Should a HIPAA Email Policy Include?

A HIPAA email policy should include procedures for PHI handling, encryption requirements, user access controls, patient authorization processes, breach response protocols, and staff training requirements. The policy must define acceptable email usage, specify security measures for different types of communications, establish audit procedures, and outline consequences for violations to ensure comprehensive compliance with HIPAA Privacy and Security Rules. Healthcare organizations often develop email policies reactively after compliance issues arise rather than proactively addressing HIPAA requirements. HIIPAA email policy development helps prevent violations while enabling efficient email communications that support patient care and organizational operations.

Scope and Applicability Definitions

Policy coverage must clearly define which email activities fall under HIPAA requirements and which personnel must follow established procedures. HIPAA email policy should address both internal communications between staff members and external communications with patients, providers, and business partners. PHI identification guidelines help staff recognize when email messages contain protected health information that requires additional security measures. These guidelines should include examples of obvious PHI like patient names and medical record numbers as well as less obvious information that could identify patients. Exception procedures provide guidance for emergency situations when standard email security measures might delay urgent patient care communications. These procedures should balance patient safety needs with privacy protections while documenting when and why exceptions occur.

User Authentication and Access Control Procedures

Password requirements must specify minimum standards for email account security including length, complexity, and change frequency. The policy should address both initial password creation and ongoing password management to maintain account security over time. Account management procedures define how email access is granted, modified, and terminated based on employment status and job responsibilities. The policy should specify who has authority to approve access changes and how quickly modifications must be implemented. Remote access guidelines establish security requirements for accessing organizational email systems from outside locations or personal devices. These guidelines should address virtual private network usage, device security standards, and restrictions on PHI access from unsecured networks.

Email Content and Communication Standards

PHI usage guidelines specify when patient information can be included in email communications and what security measures apply to different types of content. The policy should distinguish between internal communications among healthcare team members and external communications with patients or other organizations. Subject line restrictions help prevent inadvertent PHI disclosure through email headers that might be visible to unauthorized recipients or stored in unsecured log files. Staff should understand how to reference patients and medical conditions without revealing specific identifying information. Attachment handling procedures define security requirements for medical records, test results, and other documents transmitted via email. HIPAA email policy should specify encryption standards, file naming conventions, and restrictions on certain types of sensitive information.

Encryption and Security Implementation Requirements

Encryption standards must specify which types of email communications require encryption and what methods meet organizational security requirements. The policy should address both automatic encryption for all emails and selective encryption based on content sensitivity. External communication requirements define additional security measures for emails sent outside the healthcare organization to patients, referring providers, or business partners. These requirements might include patient portal usage, secure email gateways, or alternative communication methods for highly sensitive information. Mobile device security addresses special considerations for accessing email from smartphones and tablets used for patient care activities. The policy should specify device encryption requirements, application restrictions, and procedures for lost or stolen devices.

Patient Authorization and Consent Management

Consent documentation procedures define when patient authorization is required for email communications and how these authorizations should be obtained and recorded. The policy should distinguish between treatment communications that do not require authorization and marketing or administrative communications that do. Authorization tracking systems help staff verify patient consent status before sending emails that require authorization. HIPAA email policy should specify how consent information is maintained and accessed while protecting patient privacy and supporting audit requirements. Revocation procedures establish how patients can withdraw consent for email communications and how these changes are implemented across organizational systems. Staff should understand how to process revocation requests promptly while maintaining records of authorization changes.

Incident Response and Breach Management Protocols

Violation reporting procedures define how staff should report potential HIPAA violations or security incidents involving email communications. The policy should specify who receives reports, what information must be included, and timeframes for reporting different types of incidents. Investigation processes outline how the organization will assess potential violations to determine whether they constitute HIPAA breaches requiring patient notification or regulatory reporting. These processes should include roles and responsibilities for investigation team members. Corrective action procedures establish how the organization will address confirmed violations and prevent similar incidents in the future. HIPAA email policy should include disciplinary measures for staff violations and system improvements for prevention measures.

Training and Compliance Monitoring Elements

Initial training requirements specify what HIPAA email education all staff must receive before gaining access to organizational email systems. The policy should define training content, delivery methods, and documentation requirements for compliance tracking. Refresher training schedules ensure that staff receive updated information about email security requirements and organizational policy changes. The policy should specify training frequency and procedures for tracking completion across different employee groups. Audit procedures define how the organization will monitor email usage to identify potential violations and assess policy effectiveness. The policy should specify audit frequency, scope, and reporting requirements while protecting legitimate email privacy expectations for non-PHI communications.

What is the HIPAA Security Rule?

What is the HIPAA Security Rule? Understanding Its Impact and Upcoming Changes for ePHI

The HIPAA Security Rule is a critical part of The Health Insurance Portability and Accountability Act (HIPAA): legislation specifically designed to establish national security standards to protect the electronic protected health information (ePHI) held by healthcare organizations. Compliance with the HIPAA Security Rule is essential for safeguarding sensitive patient data against security breaches, cyber threats and even physical damage. 

However, as cyber threats grow in both variety and, more alarmingly, sophistication and technological advancements, the Office for Civil Rights (OCR), which enforces the Security Rule, has proposed updates to further strengthen the data security and risk management postures of healthcare organizations. 

In light of these upcoming changes to the HIPAA Security Rule and their importance to healthcare organizations, this post details the existing HIPAA Security Rule and what it entails. From there, we’ll look at the proposed modifications to the HIPAA Security Rule, helping you to understand how it will affect your organization going forward and, subsequently, how to best prepare for potential changes coming later this year to remain compliant.

What is the HIPAA Security Rule?

Added to HIPAA in 2003, the Security Rule introduced a series of mandatory safeguards to protect the increasing amount of digital data, i.e., ePHI, and the increasing prevalence of electronic health record (EHR) systems, customer data platforms (CDPs) and revenue cycle management (RCM) platforms. 

The HIPAA Security Rule centers around three fundamental categories of safeguards:

  1. Administrative Safeguards
    • Risk modeling: frequent risk assessments to identify, categorize, and manage security risks.
    • Workforce security policies: including role-based access controls.
    • Contingency planning for emergency access to ePHI:  i.e., disaster recovery and business continuity planning.
  2. Technical Safeguards
    • Access controls: implementing controls to restrict access to ePHI, e.g., Zero Trust, user authentication, and automatic timeouts. 
    • Audit controls: to track access to sensitive patient data.
    • Encryption protocols: to protect ePHI end-to-end, in transit and at rest.
  3. Physical Safeguards
    • Onsite security measures: to prevent unauthorized physical access, e.g., locks, keycards, etc.
    • Surveillance equipment: cameras and alarms, for example, to signal unauthorized access. 
    • Secure disposal of redundant hardware: devices containing ePHI must be properly disposed of by companies that specialize in data destruction. 

The HIPAA Security Rule: The Dangers of Non-Compliance

Consequently, should a healthcare company fail to comply with the safeguards outlined in the HIPAA Security Rule, it can result in severe consequences, including:

  • Civil penalties: up to $2.1 million per violation; repeat offenses can result in multi-million dollar settlements.
  • State-Level HIPAA Fines: in addition to federal HIPAA penalties, states, such as California and New York, can impose fines for compliance violations under the Health Information Technology for Economic and Clinical Health (HITECH) Act
  • Criminal charges: for willful neglect, unauthorized collection of ePHI, and, the malicious use of patient data (including its sale). This can result in up to 10 years in prison. 
  • Reputational damage: demonstrating an inability to secure ePHI results in a loss of patient trust, making them less inclined to purchase your services or products. More alarmingly, cybercriminals will also become aware that your company’s IT infrastructure is vulnerable, which could invite more attempts to infiltrate your network and steal ePHI.  

Proposed Updates to the HIPAA Security Rule

Now that we’ve discussed the present HIPAA Security Rule, and the consequences for failing to implement its required threat mitigation measures, let’s turn our attention to the proposed changes to the Security Rule, which were announced by the U.S. Department of Health and Human Services (HHS) in December, 2024, and how they will affect healthcare organizations. 

Mandatory Encryption for All ePHI Transmission

The proposed updates require end-to-end encryption for emails, messages, and data transfers involving ePHI, making all implementation specifications required with specific, limited exceptions. This means that patient data must be encrypted in transit, i.e., from one place to another (when collected in a secure form, sent in an email, etc.), and in storage, i.e., where it will reside. 

To accommodate these changes, many healthcare organizations will need to upgrade to HIPAA-compliant email solutions, for their outreach requirements, as well as encrypted databases to store the ePHI in their care.

Expanded MFA Requirements

Healthcare providers must implement Multi-Factor Authentication (MFA) for all personnel with access to ePHI. MFA moves beyond usernames and passwords, requiring users to prove their identity in more than one way. 

This could include:

  • One-time passwords (OTPs) via email, an app, or a physical security dongle (e.g., an RSA token)
  • Access cards or Fobbs
  • Biometric identification, such as retina scans, fingerprints, or voice recognition. 

This proposed rule change addresses increasing risks from phishing and other credential-based attacks, in which malicious actors acquire employee login details to access ePHI.

Stronger Risk Management and Third-Party Security Controls

Healthcare organizations must conduct more frequent risk assessments to identify, categorize, and mitigate threats to ePHI. A considerable part of this is implementing stricter security controls for business associates who have access to the healthcare company’s ePHI. 

A business associate could be a software vendor with which an organization processes patient data, or it could be a supplier or partner that requires access to ePHI to fulfill its operational duties. In light of this, one of the proposed changes to the HIPAA security rule is that vendor security audits will become more mandatory rather than optional.

New Incident Response (IR) and Breach Reporting Rules

The new rule changes emphasize stricter breach notification timelines for healthcare entities and the business associates that handle ePHI on their behalf. This means that healthcare companies are obligated to inform affected parties of a data breach as soon as possible. 

For healthcare companies, this means devising, or strengthening, continuous monitoring protocols, so their security teams become aware of suspicious activity as as soon as possible and can accurately communicate their containment efforts and take the neccessary actions to mitigate damages. 

Preparing For The Changes to the HIPAA Security Rule: Next Steps for Healthcare Organizations 

As the proposed changes to the HIPAA Security Rule move forward, and are likely to go into effect by the end of this year, healthcare organizations can prepare by:

Conducting frequent risk assessments to pinpoint vulnerabilities to the ePHI in IT ecosystems. This should be done annually, at least – or when changes are made to IT infrastructure that may affect ePHI.

Evaluating existing email and communication platforms to ensure compliance with encryption and authentication requirements, especially under the newly proposed security rule and its requirements.

Hardening your organization’s cybersecurity posture by considering the implementation of network segmentation, zero-trust security principles, and data loss protection (DLP) protocols.

Strengthening vendor risk management to ensure third-party service providers meet HIPAA compliance standards and that you have a Business Associate Agreement in place. 

How the Proposed Changes to the HIPAA Security Rule Affect Healthcare Communications and Email Security

One of the most significant implications of the proposed changes to the Security Rule is the heightened focus on secure email communications involving ePHI. Key takeaways for secure healthcare email include:

  • Encryption is now essential: healthcare organizations relying on unencrypted email delivery platforms to communicate with patients will need to switch to secure, HIPAA-compliant email solutions with the appropriate encryption capabilities. 
  • Email providers must meet stronger compliance standards: if your current email service provider doesn’t support automatic encryption, for instance, it may be non-compliant under the new rule.
  • Stronger authentication for email access: healthcare professionals sending or receiving ePHI via email must implement MFA and similar, robust access control protocols.

With email communication being a key part of patient outreach and engagement, it’s vital for healthcare companies to identify and address security gaps in their IT infrastructure, and prepare for the coming changes to the HIPAA security rule.   

Changes to the HIPAA Security Rule: Final Thoughts

The HIPAA Security Rule remains the foundation for protecting ePHI within healthcare organizations. The proposed updates to the Security Rule reflect the growing need for stronger cybersecurity controls in healthcare. The stark reality is that patient data is, and always will be, sensitive and, as such, will always be a valuable target for cybercriminals. 

In light of the persistent and growing threat to ePHI, healthcare organizations that fail to proactively address the requirements brought forth by the proposed changes to the HIPAA Security Rule risk data breaches, financial penalties and other punitive action. 

If you have questions about HIPAA compliant secure email, encryption, or how the coming changes to the Security Rule will impact your healthcare communications, contact LuxSci today for expert guidance.

How to Make Google Workspace HIPAA Compliant

How to Make Google Workspace HIPAA Compliant

Healthcare organizations can make Google Workspace HIPAA compliant by completing a Business Associate Agreement with Google, configuring advanced security settings, and training staff on proper data handling. Knowing how to make Google Workspace HIPAA compliant means understanding that compliance depends on both technology and human oversight. When these elements are managed carefully, Google Workspace can be used to handle Protected Health Information securely while maintaining efficiency and accessibility for healthcare teams.

The compliance framework

The process of learning how to make Google Workspace HIPAA compliant begins with recognizing that Google provides the infrastructure, but the healthcare organization is responsible for compliance. The HIPAA Privacy and Security Rules require administrative, physical, and technical safeguards that must be implemented through documented policies, technical configuration, and ongoing oversight. Google Workspace, when managed under the right plan, offers encryption, access management, and detailed audit logs. To make Google Workspace HIPAA compliant, administrators must use the business version, not free Gmail accounts, because only paid Workspace plans allow for proper control and a Business Associate Agreement. Documented internal policies should define how messages, files, and calendars containing patient data are stored and monitored. Establishing this structure early makes every later compliance step easier to maintain.

The Importance of the Business Associate Agreement

A Business Associate Agreement (BAA) is an unskippable step in how to make Google Workspace HIPAA compliant. Without it, compliance cannot be achieved regardless of system configuration. This legal contract specifies how Google protects healthcare data, reports incidents, and assists with investigations. The BAA covers key Workspace tools such as Gmail, Drive, Calendar, and Docs but excludes consumer products like YouTube and certain AI-based features. Administrators should disable any unsupported tools to prevent accidental data exposure. Reviewing and maintaining this agreement is essential to keeping Google Workspace HIPAA compliant as Google updates or expands its services. Many healthcare organizations include the BAA in their annual compliance review to confirm it still reflects current practices and security requirements.

Configuring strong security and access controls

Knowing how to make Google Workspace HIPAA compliant requires more than signing documents. It demands careful configuration of security controls that align with HIPAA’s technical safeguard requirements. Encryption should be enforced for all email traffic, and administrators commonly require two-step verification to strengthen account security and meet HIPAA access-control expectations. Device management policies can prevent unapproved computers or phones from connecting to accounts that contain Protected Health Information. Access privileges should be based on job roles so that staff only view the data they need to perform their duties. Audit logs can record sign-ins, file access, and configuration changes, giving compliance officers a clear view of user activity when logs are regularly reviewed. Each of these steps contributes to a Google Workspace HIPAA compliant environment that protects against both external threats and internal misuse.

Maintaining compliance through user awareness and training

Even the most secure configuration cannot replace good judgment. A key part of how to make Google Workspace HIPAA compliant is ensuring that every staff member understands their responsibility when handling patient information. Training should explain how to identify Protected Health Information, when and how encryption is used to protect it, and how to report security incidents. Consistent reminders help prevent accidental sharing or unauthorized forwarding of sensitive messages. Regular audits of user activity can identify risks such as unused accounts, weak passwords, or improper storage of files. By reinforcing awareness and accountability, organizations maintain their Google Workspace HIPAA compliant status while reducing the risk of human error that can lead to violations.

Compliance is not a static condition but a continuous process. Administrators who understand how to make Google Workspace HIPAA compliant know that monitoring and documentation are required to sustain it. Google Workspace offers audit reports, security dashboards, and alerts that track sign-ins and encryption status. Reviewing these reports ensures that no settings are altered without authorization and that user activity remains within policy limits. Keeping written records of policy updates, staff training, and audit results helps demonstrate compliance during inspections. These records also create accountability and give leadership confidence that the system continues to operate within HIPAA standards. With diligent monitoring, a Google Workspace HIPAA compliant setup can stay reliable even as teams and technologies evolve.

A lasting culture of compliance

Organizations that learn how to make Google Workspace HIPAA compliant build more than a secure system—they create a sustainable culture of responsibility. Google Workspace allows healthcare professionals to collaborate, communicate, and share resources efficiently while safeguarding patient data. Maintaining this balance requires consistent review of settings, updates, and employee practices. As new regulations appear and technology develops, compliance officers should revisit each requirement to ensure ongoing protection. A well-managed, Google Workspace HIPAA compliant configuration supports both privacy and productivity, proving that regulatory compliance and convenience can coexist when oversight and education remain priorities.

HIPAA compliant Email

HIPAA Compliant Email Use Cases for Health Plan Administrators and Insurance Providers

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.