As today’s healthcare patients demand more personalized and efficient care, secure communication tools have become a requirement for modern multi-touch engagement. With increasingly tech-savvy patients and customers, today’s providers, payers and suppliers are turning to secure texting apps for healthcare to open up new communications channels, enhance engagement, and improve overall health outcomes.
Sounds great, right? Well, secure text must not only be efficient, but also secure and compliant with strict regulations, including HIPAA (Health Insurance Portability and Accountability Act).
In this blog post, we’ll explore how secure texting can make healthcare more efficient, adding a new and commonly used channel to better connect with your patients and customers—and we’ll provide some useful tips for companies looking to bring secure text into their healthcare engagement strategies.
The Value of Secure Texting Apps for Healthcare
Healthcare providers, payers and suppliers often face the challenge of quickly sharing critical information with patients and customers, all while maintaining data privacy and securing protected health information (PHI). Traditional texting and SMS methods are inherently insecure, leaving sensitive health information vulnerable to breaches. Text messages have a number of widely known security vulnerabilities, including issues with confidentiality, only optional encryption, and inadequate authentication.
In healthcare, a data breach isn’t just a technical issue—it can lead to severe consequences, including legal penalties and the loss of patient trust, as well as harming your brand and future business. Secure texting ensures compliance with HIPAA regulations, protecting patient data and safeguarding healthcare organizations and companies from fines.
HIPAA Compliance Considerations for Secure Texting
One of the key concerns when implementing secure texting in healthcare is HIPAA compliance. HIPAA mandates strict guidelines for the handling, transmission, and storage of Protected Health Information (PHI). Any communication containing PHI must be encrypted, auditable, and only accessible by authorized users. Here are some HIPAA compliance factors to consider:
End-to-End Encryption: Ensure that your secure texting app offers end-to-end encryption. This means that the email service provider (ESP) encrypts and transmits data using the TLS security protocol, securely stores data at rest, and data is never kept on a recipient’s device, preventing interception and access by unauthorized parties.
Audit Controls: HIPAA requires organizations to maintain an audit trail of all communications. Your secure texting solution should provide a record of when messages are sent, delivered, and read, as well as details on who accessed the information.
Access Controls: Only authorized personnel should have access to sensitive patient data or PHI. Secure texting apps for healthcare should offer user authentication features such as PINs, biometrics, or two-factor authentication to ensure the identity of the user. The safest approach is to not include PHI in your text message at all, but rather direct users to a secure communications platform via text message.
Remote Wipe Functionality: In the event that a device is lost or stolen, healthcare providers must be able to remotely wipe PHI from the device to prevent unauthorized access, if needed.
Tips for Implementing Secure Texting in Healthcare
If you’re a healthcare organization considering secure texting apps, here are some practical tips to ensure a smooth implementation:
Choose the Right Platform: Not all secure texting apps are created equal. Look for platforms that are specifically designed for healthcare, as they are more likely to include features designed for HIPAA compliance. LuxSci Secure Text, for example, is built for healthcare environments, with encryption, audit trails, and other compliance tools integrated into the solution.
Train Your Staff: Technology is only as secure as the people using it. Ensure that all staff members who will use the secure texting app are trained on best practices for handling PHI and following compliance protocols. Regular training sessions and refresher courses are a must to keep everyone up to date with the latest rules and regulations.
Encourage Patient and Customer Adoption: Secure texting is a powerful tool for patient and customer engagement. Inform patients about the benefits of secure messaging and how it protects their privacy. Offer your patients and customers—especially those less likely to respond to other channels—the option to receive text messages as part of a multi-channel or omnichannel engagement approach.
Integrate with Existing Systems: A seamless workflow is crucial for the success of any new technology. Ensure that your secure texting solution can integrate with your existing Electronic Health Records (EHR) system, CDP platform, and other healthcare engagement channels and portals, so communication between providers, payers, suppliers and patients is not siloed.
Monitor and Review: After implementing secure texting, regularly review its usage and ensure compliance protocols are being followed. Monitor audit logs and address any potential security concerns promptly. Continuous improvement is key to maintaining both security and efficiency.
Improving Personalization and Engagement with Secure Texting
Beyond compliance and data protection, secure texting apps for healthcare can significantly enhance patient engagement and improve the overall healthcare experience. In fact, personalized, timely communication has been shown to improve health outcomes and boost patient satisfaction. Here’s how:
Appointment Reminders and Care Management: Send patients personalized appointment reminders, medication prompts, or follow-up instructions, reducing no-shows and improving adherence to treatment plans. For instance, sending a patient a personalized text reminder for their diabetes check-up or alerting them to the results of medical tests can improve and accelerate care management.
Product Offers, Renewals and Upgrades: Secure messaging enables healthcare providers and suppliers to reach out to patients and customers to remind them about a prescription renewal, to upgrade or offer a new product, or to drive plan renewals and new services.
Patient Education: Use secure texting to alert patients that new educational materials, such as care instructions, post-surgery protocols, or health tips tailored to the patient’s specific condition, are available. This not only empowers patients with more information but improves outcomes with better adherence to treatment plans and ongong care needs.
How LuxSci’s Secure Text Works
LuxSci Secure Text transmits its data with TLS protection, stores its information with 256-bit AES, and data is never kept on the recipient’s device. Recipients use password-based authentication to access the information and messages are securely stored in LuxSci’s databases and dedicated secure infrastructure.
LuxSci’s Secure Text does not require the sender to install or use any new applications. Leveraging LuxSci’s SecureLine encryption service, the sender:
Writes their message in either LuxSci’s WebMail email app or their preferred email program, including Google Workspace or Microsoft 365.
In the address field, the sender enters a special email address that is based the recipient’s phone number. For example, an address of 2114367789@secure.text would send the message to a US recipient whose number is 211-436-7789. Once the sender is finished, they hit the send button.
The recipient will receive a normal SMS that tells them a secure message is waiting for them. The message contains a link, which opens up their phone’s web browser:
If they have recently viewed another Secure Text message, the new message will immediately be displayed.
If the recipient has used Secure Text to view messages at an earlier date, they will need to enter their password before they can view the message.
If this is the recipient’s first Secure Text message, they will need to set up a password before they can view the message.
With LuxSci, you do not include PHI in your text messages, helping to ensure the privacy and protection of patient and customer data at all times, and eliminating the inherent security risks of text and SMS messages.
Learn More About Secure Texting Apps for Healthcare
Today’s secure texting solutions are expanding the ways healthcare organizations communicate with patients and customers. With the right solution, you can ensure compliance with regulations like HIPAA, while enhancing personalization, engagement, and health outcomes. Secure texting can improve the end-to-end healthcare journey and create a more efficient, patient-centered healthcare experience.
Are you ready to improve your patient engagement with secure text, while maintaining HIPAA compliance and securing PHI data?
Contact us today to learn more about secure texting apps, healthcare-specific use cases, and how you can implement new secure communication channels to achieve better outcomes and grow your business.
Secure email is not the same as “email with encryption turned on.” True secure email requires enforced automated encryption, a signed BAA, access controls, audit logs, and documented processes — not just a feature toggle.
Standard email platforms like Gmail and Microsoft 365 rely on opportunistic TLS by default, which can silently fall back to unencrypted delivery if the recipient’s server doesn’t support encryption.
HIPAA’s encryption safe harbor means a misdirected but properly encrypted email is a non-event. The same email sent unencrypted is a presumed breach unless a risk assessment shows otherwise.
A signed Business Associate Agreement (BAA) with your email provider is non-negotiable — without one, you cannot legally send or store PHI through that provider.
The proposed 2025 HIPAA Security Rule update, planned for finalization in 2027, would make encryption of ePHI in transit and at rest a mandatory requirement rather than “addressable,” raising the stakes for organizations still relying on opportunistic TLS.
Best for: Healthcare IT Directors, Compliance Officers, Privacy Officers, and Marketing Managers at provider, payer, and supplier organizations that handle protected health information (PHI).
In healthcare IT, the term “secure email” gets thrown around loosely. Vendors slap the label on anything with a padlock icon, and internal teams often assume that because their provider offers TLS, they’re covered. They’re not, and the gap between what’s assumed and what’s actually required is where data breaches occur and HIPAA violations happen.
This guide breaks down exactly what secure email means from a technical and regulatory standpoint, why the email platform your staff uses every day probably isn’t compliant out of the box, and what to look for when evaluating a provider that needs to protect PHI at scale. If you want the full picture of what compliance requires beyond email specifically, our HIPAA Compliance Checklist is a useful companion read.
What Is Secure Email?
Secure email refers to an email system that protects the confidentiality, integrity, and availability of message content — specifically PHI — through a combination of technical safeguards and contractual protections. It’s not a single feature. It’s a stack of controls working together.
At minimum, secure email in a healthcare context includes:
Enforced encryption in transit, so messages can’t fall back to plaintext delivery
Encryption at rest, so stored messages remain protected on the server
Authentication protocols (SPF, DKIM, DMARC) that prevent spoofing and impersonation
Access controls and audit logs that track who accessed what, and when
A signed Business Associate Agreement (BAA) with the email provider
The distinction that trips up most organizations is this: encryption is a component of secure email, not the whole picture. A provider can offer encryption and still fail to meet HIPAA requirements if that encryption isn’t enforced, if there’s no BAA in place, or if audit logging doesn’t exist. Secure email is the combination of all these pieces functioning as a system, which is why it needs to be evaluated holistically rather than checked off feature by feature.
For healthcare provider, payer, and supplier organizations, this matters because email remains one of the highest-volume channels for PHI exposure, from clinical referrals to patient billing statements to routine staff communication. Getting the definition right is the first step toward closing the compliance gap.
Why Standard Email Is Not HIPAA-Compliant
Many healthcare organizations run on Gmail (Google Workspace) or Microsoft 365, and most assume they’re protected because encryption exists somewhere in the stack. That assumption is the single most common — and most dangerous — misconception in healthcare email security.
Here’s the problem: standard email services use opportunistic TLS by default. TLS is attempted between mail servers, but if the receiving server doesn’t support it, the message is delivered anyway — unencrypted, in plaintext. Neither the sender nor the recipient typically sees a warning. The email just goes through.
This isn’t a hypothetical edge case. IT professionals managing healthcare email infrastructure have flagged this exact issue directly: opportunistic TLS is often enabled by default and creates a false sense of security, since it offers no guarantee that a given message, including one containing PHI, won’t be transmitted in plaintext if the recipient’s mail server doesn’t support encryption. Organizations assume they’re protected simply because TLS is technically “on,” without realizing it isn’t enforced.
That gap has real consequences under HIPAA. The Security Rule currently treats transmission encryption as an “addressable” safeguard, meaning covered entities can, in theory, implement an equivalent alternative measure instead. In practice, regulators and auditors from the Office for Civil Rights (OCR) expect enforced encryption as the standard of care. “Addressable” has never meant optional — it means an organization needs a documented, defensible reason if it isn’t doing enforced encryption, and few reasons hold up under scrutiny. Finally, under OCR’s proposed changes to the HIPAA Security Rule for ePHI, scheduled for final publication in July 2027, email encryption moves from addressable to mandatory.
Beyond the encryption gap, standard consumer and even most business email plans typically lack:
A BAA that’s actually offered and signed (available on some enterprise tiers, but not automatic)
Audit logging sufficient to meet HIPAA Security Rule requirements
Built-in encryption at rest guarantees for stored messages
None of this means Gmail or Microsoft 365 are inherently insecure products. It means their default configuration is built for general business use, not for an environment where every misrouted or intercepted message carries breach notification liability. Making either platform HIPAA-appropriate requires layering on additional tools, policies, and critically, a provider relationship that includes a signed BAA covering the exact services in use.
The Technical Components of Secure Email
Secure email is built upon five technical layers. Understanding each one, and where it fails in standard email, clarifies exactly what a compliant solution needs to deliver.
Encryption in Transit (TLS)
Transport Layer Security (TLS) encrypts the connection between mail servers as a message travels from sender to recipient. There are two flavors, and the difference between them is the crux of most healthcare email compliance failures:
Opportunistic TLS attempts an encrypted connection but falls back to unencrypted delivery if the receiving server doesn’t support it. This is the default across most consumer and business email platforms.
Enforced TLS requires an encrypted connection for delivery to succeed. If encryption can’t be established, the message fails to send rather than going out in plaintext, or a link to secure portal can be sent to securely access the information.
HIPAA’s Security Rule lists encryption as addressable, but enforced TLS has become the de facto standard that auditors and OCR expect from covered entities and business associates handling PHI over email. As one healthcare IT professional put it while debating this exact tradeoff internally: the goal is to require TLS for all outbound email and then document the remaining controls around it, treating enforced TLS as the technical baseline, with policy and process built on top.
Encryption at Rest
Transit encryption only protects a message while it’s moving. Once it lands on a mail server — sender’s outbox, recipient’s inbox, backups, archives — it needs to remain encrypted in storage. This is encryption at rest, and it’s where many organizations underestimate their exposure.
Encryption in transit alone offers zero control over a message after it’s been delivered. If the destination server isn’t itself encrypting stored data, or if a backup snapshot is taken without encryption, PHI sitting in an inbox is exposed regardless of how securely it arrived. HIPAA’s Security Rule requires safeguards for ePHI both in transit and at rest, a compliant secure email provider needs to guarantee both, not just one.
End-to-End Encryption (S/MIME, PGP)
End-to-end encryption (E2EE) encrypts message content itself, not just the connection it travels over — meaning even the email provider can’t read the content. Two standards dominate here:
S/MIME uses certificate-based encryption and is common in enterprise environments, such as healthcare, particularly where organizations already manage a public key infrastructure.
PGP (Pretty Good Privacy) uses a public/private key model and is more common in technical or security-conscious communities, though it’s less frequently deployed at scale in healthcare due to key management complexity.
E2EE isn’t a baseline requirement for every PHI-containing email, enforced TLS plus encryption at rest satisfies most use cases. But it becomes necessary for especially sensitive communications, cross-organization data sharing where you don’t control the recipient’s infrastructure, or when a business associate agreement specifically requires it.
Authentication (SPF, DKIM, DMARC)
These three protocols work together to prevent domain spoofing and email impersonation, a growing attack vector against healthcare organizations specifically, given how often phishing campaigns impersonate providers, payers, or patients.
SPF (Sender Policy Framework) specifies which mail servers are authorized to send email on behalf of a domain.
DKIM (DomainKeys Identified Mail) adds a cryptographic signature verifying a message wasn’t altered in transit.
DMARC (Domain-based Message Authentication, Reporting & Conformance) tells receiving servers what to do when SPF or DKIM checks fail, and provides reporting visibility.
Without these configured correctly, an organization’s domain can be spoofed to send convincing phishing emails to patients or staff, creating a security failure that compounds the compliance risk of email interception.
Digital Signatures
Digital signatures verify sender identity and confirm a message hasn’t been tampered with between sending and receipt. Paired with encryption, they close the loop on message integrity, confirming not just that content was protected, but that it came from who it claims to have come from and arrived unaltered.
Standard Email vs. Secure Email: Feature Comparison
Feature
Standard Email
Secure Email (HIPAA-Compliant)
Encryption in Transit
Opportunistic TLS — attempted but not enforced
Enforced TLS — connection fails if encryption unavailable, can include delivery via secure portal option
Encryption at Rest
Not guaranteed; provider-dependent
Required — server-side encryption of stored messages
End-to-End Encryption
Not available
Supported via S/MIME and/or PGP
Digital Signatures
Not available
Included — verifies sender identity and message integrity
Authentication (SPF / DKIM / DMARC)
Optional, rarely enforced
Required — spoofing and impersonation protection
Business Associate Agreement (BAA)
Not provided on standard plans
Required — must be signed before sending PHI
Audit Logs
Basic or none
Full audit trail — required under HIPAA Security Rule
Access Controls
Basic password only
Role-based access, MFA, admin controls
Misdirected Email
Reportable HIPAA breach
Non-reportable if properly encrypted (safe harbor)
HIPAA Compliant by Default
No
Yes
What Makes Email HIPAA-Compliant Specifically
Technical safeguards alone don’t make email HIPAA-compliant. Compliance is a combination of technology, contracts, and documented processes — all four need to be in place simultaneously. This includes:
A signed BAA with your email provider – Any vendor that transmits, processes, or stores PHI on your behalf is a business associate under HIPAA, and business associates are legally required to sign a BAA before handling that data. Email providers have persistent access to ePHI — even end-to-end encrypted messages pass through their infrastructure at some point — which makes this requirement absolute, not situational. If a provider won’t sign a BAA, using them to send or store PHI isn’t a compliance risk you can mitigate; it’s a violation from the start.
Encryption as an addressable safeguard – Under 45 CFR §164.312(e)(2)(ii), the HIPAA Security Rule lists encryption of ePHI in transit as “addressable” rather than strictly “required.” In practice, this doesn’t mean optional, it means an organization must implement it, or document and justify an equivalent alternative safeguard. Enforced encryption has become the expected standard, and with the newly proposed HIPAA Security Rule planned for July 2027 publication, NPRM would formalize that expectation by making encryption of ePHI in transit and at rest mandatory rather than addressable. Organizations still relying on opportunistic TLS as their “equivalent alternative” should treat this as a closing window.
Access controls and audit logs – HIPAA requires the ability to track who accessed PHI, when, and what they did with it. This means role-based access permissions, multi-factor authentication, and a complete, retained audit trail — not just for compliance reporting, but for identifying and responding to incidents quickly.
The encryption safe harbor – This is one of the most consequential, and most underused, provisions in HIPAA. If PHI is sent via properly encrypted email and ends up misdirected to the wrong recipient, it is not a reportable breach under the Breach Notification Rule, because the encrypted content is considered unreadable and therefore not “unsecured PHI.” The exact same misdirection with unencrypted email is a reportable breach, triggering notification obligations to the individual and to HHS/OCR. Encryption isn’t just a security best practice here, it’s the line between a non-event and a formal breach investigation.
HITRUST certification as a trust signal – When evaluating vendors, HITRUST CSF certification is a strong external indicator that a provider’s security controls have been independently assessed against a recognized healthcare-specific framework. It’s not a HIPAA requirement in itself, but it meaningfully reduces the diligence burden on your side when vetting a provider.
Types of Healthcare Email That Must Be Secure
Not all internal debate here is about “should we secure email” — it’s about scope. Which specific email flows actually carry PHI, and therefore need to run through a compliant channel? In practice, the answer is broader than most teams initially assume.
The common thread: if a message references anything that could identify a patient in connection with health information — a name next to a diagnosis, an account number tied to a service date, an annual test reminder — it needs to move through a secure channel, regardless of whether it’s clinical, financial, or administrative in nature.
How to Evaluate a Secure Email Provider for Healthcare
Vendor evaluation in this category tends to go one of two ways: teams either take a provider’s “HIPAA-compliant” label at face value, or they get buried in RFP questions without knowing which answers actually matter. Ask these key questiosn to focus the evaluation on what’s operationally and legally significant.
“Does the provider sign a BAA? This is the first filter, not the last. If a vendor won’t sign a BAA — or offers a heavily limited one — everything else is irrelevant. Some organizations go a step further and negotiate indemnity or make-whole clauses into the BAA itself, seeking financial protection beyond the baseline liability allocation.
What encryption methods are supported? Confirm specifically whether the provider offers TLS only, or also supports S/MIME and/or PGP for end-to-end encryption where needed. TLS-only coverage is sufficient for most standard PHI communication; organizations with cross-border data sharing or especially sensitive use cases may need E2EE options available.
Is encryption enforced or opportunistic? This is the single most important technical question to ask directly, in those terms. A vendor that describes its encryption vaguely, without distinguishing enforced from opportunistic delivery, hasn’t answered the question. Push for specifics.
How are large attachments handled? Lab results, imaging files, and clinical documents often exceed standard attachment size limits. Confirm the provider has a secure, compliant method for large file transfer that doesn’t force users onto an unencrypted workaround.
What audit logging and reporting capabilities exist? You need visibility into delivery, access, and any failed encryption attempts, not just a generic sent/received log. Ask whether logs are retained for a period consistent with your organization’s HIPAA documentation requirements.
Do they support high-volume transactional email? Appointment reminders, billing notices, and patient communications at scale require infrastructure built for volume without sacrificing per-message compliance. Confirm the provider’s platform is built for this your specific pattern, not just person-to-person messaging.
Is the platform US-based with US data residency? For many healthcare organizations, where data physically resides — and under which jurisdiction — is a material factor in vendor risk assessment, particularly for payers and larger provider organizations with strict data governance policies.”
One operational factor worth weighing alongside these questions: secure email portals — the kind that require recipients to click through to a separate web page to read a message — solve the encryption problem but often create a real adoption problem. IT teams have reported a direct conflict between phishing-awareness training and portal-based workflows: staff and patients trained not to click suspicious links in emails are, understandably, reluctant to click the “secure link” a portal email contains. This is a legitimate reason many organizations increasingly prefer platforms that enforce encryption transparently in the background — like LuxSci’s SecureLine encryption technology — rather than routing every message through a separate portal experience.
Secure Email Checklist for Healthcare Organizations
Every safeguard covered in this guide comes down to a handful of concrete, verifiable actions. Use the checklist below as a working reference for what needs to be in place across your legal agreements, technical controls, and internal processes. This is not a one-time setup task, but something worth revisiting as your email volume, vendors, and regulations evolve. Share it across your compliance and IT teams as a starting point for an internal audit.
Legal and Contractual – BAA signed with email provider and all third-party vendors handling PHI.
Encryption – Forced TLS, not opportunistic only for emails in transit and all stored data encrypted with AES-256 bit encryption.
Access and Audit – Unique user IDs, role-based access, and login monitoring with advanced MFA enabled for all email accounts; audit logs active and maintained.
People and Processes – Staff trained in PHI handling, established breach response plan, annual email security policy review.
What Should I Do Now?
Secure email isn’t a single setting you switch on — it’s a combination of enforced encryption, a signed BAA, access controls, and documented process working together. Get any one piece wrong, and the rest doesn’t hold up under an OCR audit or a breach investigation.
If your organization is still relying on opportunistic TLS, an unsigned or incomplete BAA, or a patchwork of workarounds to move PHI through email, now is the time to close that gap, especially with the proposed 2025 HIPAA Security Rule update poised to make encryption a mandatory requirement rather than an addressable one in 2027.
Below are three ways you can continue your journey to securing your healthcare email:
Email can be HIPAA compliant, but only when the right safeguards are in place — enforced encryption, a signed BAA with your email provider, access controls, audit logs, and staff training on PHI handling. Standard email without these safeguards is not compliant.
2. Do I need to sign a BAA with my email provider?
Yes. Email providers have persistent access to ePHI — even encrypted messages pass through their servers — making them Business Associates under HIPAA. A signed BAA is required. If your provider won’t sign one, you cannot legally use them to send or store PHI.
3. What is the difference between opportunistic TLS and enforced TLS — and which does HIPAA require?
Opportunistic TLS attempts encryption but falls back to plaintext if the recipient’s server doesn’t support it. Enforced TLS stops delivery rather than sending unencrypted. HIPAA’s Security Rule treats transmission encryption as an addressable specification, in practice, enforced TLS is the standard auditors and OCR expect. The proposed 2025 HIPAA Security Rule NPRM would make encryption of ePHI in transit a mandatory requirement in 2027.
4. What happens if I send PHI in an unencrypted email?
It is an impermissible disclosure under HIPAA’s Privacy Rule and triggers the Breach Notification Rule, requiring you to notify the individual and HHS/OCR within 60 days. Penalties range from $100 to $50,000 per violation. Had the email been properly encrypted, the same incident would qualify for HIPAA’s encryption safe harbor, meaning no notification required.
5. Is Gmail or Microsoft 365 HIPAA compliant for sending patient emails?
Neither is compliant in their default configuration. Both use opportunistic TLS, meaning PHI can be sent in plaintext if the recipient’s server doesn’t support encryption. A signed BAA is available on enterprise plans but doesn’t close the technical gap alone. A purpose-built HIPAA-compliant email platform is the reliable solution.
If you’ve been waiting for the final word on the new HIPAA Security Rule before you touch your email encryption strategy, you now have an official reason to keep waiting.
Our advice: Don’t do it.
What is the new HIPAA Security Rule for ePHI?
The Department of Health and Human Services’ Office for Civil Rights had targeted May 2026 for a final rule implementing the most significant update to the HIPAA Security Rule in over two decades. The proposal eliminates the “addressable” standard and makes encryption of ePHI in transit and at rest mandatory for every covered entity and business associate. That deadline came and went quietly. Now we know why: an updated federal regulatory agenda shows OCR’s timeline has moved to July 2027, with the rule-making downgraded from “final rule stage” to “long-term action.” OCR is still working through more than 4,700 public comments on the January 2025 proposal.
For an industry that had been expecting a tighter deadline, a year-plus delay is the kind of news that invites a collective exhale — and a shelved project plan. At LuxSci, we think that would be a mistake, for three reasons:
The current rule already requires you to address encryption. “Addressable” was never “optional.” It has always meant you must implement the safeguard, implement an equivalent alternative, or document in writing why neither is reasonable for your organization. Most healthcare organizations have never done that documentation rigorously, and OCR’s existing enforcement authority applies today, not in 2027.
Breach costs haven’t waited for the rule.IBM’s 2025 Cost of a Data Breach Report puts the average healthcare breach at $7.42 million, still the highest of any industry. At the same time, email remains the number one attack vector into healthcare organizations. None of that risk is paused by a regulatory delay.
Delay is not withdrawal.OCR has not signaled it’s abandoning the encryption mandate, only that it’s taking longer to finalize it. Organizations that build now toward the standard already proposed will be ahead (and more secure) regardless of exactly when, or in what final form, the rule lands. Organizations that wait risk a compressed scramble once it does.
What should healthcare IT and compliance leaders actually do with this news?
Reevaluate your ePHI security posture, recalibrate its urgency, and use the extra runway to do the job right, instead of racing against a deadline. This includes:
Getting a real inventory of where ePHI moves by email today, inbound and outbound, and where encryption is inconsistent or absent.
Closing the documentation gap on “addressable” now, while you have time to do it well rather than defensively.
Pushing your email vendor for concrete answers on encryption standards, MFA enforcement, audit logging, and breach notification — the same technical controls the proposed rule would make mandatory.
Building (or updating) a written, enforcement-ready posture: policies, vendor agreements, certifications and verifications, test results, and training records that would hold up under an OCR investigation today, not just in a future compliance deadline.
Get LuxSci’s new Definitive Guide on the new HIPAA Security Rule
From Addressable to Mandatory: Email Encryption Under the New HIPAA Security Rule provides the latest update on the rule, what it means for healthcare email encryption, and what you can do now to properly prepare for what’s coming in 2027. The guide also includes an interactive scorecard that lets you evaluate your current email set up and vendor across seven security and compliance dimensions in under two minutes, no email address required.
If you want a second set of eyes on where your organization stands, our team offers a free 30-minute compliance assessment of your current email environment against the proposed rule’s requirements.
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.
The Health Insurance Portability and Accountability Act (HIPAA) is a complicated law that defines the standards for the secure collection, transmission, and storage of protected health information (PHI). When information is stored or exchanged electronically, the HIPAA Security and Privacy Rules require covered entities, i.e., organizations that handle PHI, to safeguard its integrity and confidentiality.
One of the most common ways that PHI is shared electronically is via email, so understanding HIPAA email rules is essential for achieving compliance and protecting sensitive data.
The HIPAA Email Security Rule
It’s important to note that HIPAA does not require the use of any specific technology or vendor to meet its requirements. Generally speaking, the Security Rule requirements for email fall into four categories:
Organizational requirements state the specific functions a covered entity must perform, including implementing policies, procedures and obligations concerning business associate agreements (BAAs).
Administrative requirements relate to employee training, professional development, and management of PHI.
Physical safeguards encompass the security of computer systems, servers, and networks, access to the facility and workstations, data backup and storage, and the destruction of obsolete data and HIPAA email archiving.
Technical safeguards ensure the security of email data transmitted over an open electronic network and the storage of that data.
Let’s move on to discussing some of the main requirements that apply to email and the steps you need to take to secure email accounts that transmit and store PHI.
HIPAA Email Rules: Compliance Checklist
While encryption gets most of the spotlight during discussions on email security, the HIPAA email rules, in contrast, cover a range of behaviors, controls, and services that work together to address eight key areas:
Access
Encryption
Backups and Archival
Defense
Authorization
Reporting
Reviews and Policies
Vendor Management
Let’s look at each aspect of HIPPA’s email rules in greater detail.
1. Access
Access controls help safeguard access to your email accounts and messages. Implementing access controls is essential to keep out unauthorized users and secure your data, with key steps including:
Using strong passwords that cannot be easily guessed or memorized – and changing them frequently, e.g. every 30 days.
Creating different passwords for different sites and applications.
Enabling multi-factor authentication (MFA).
Securing connections to your email service provider using TLS and a VPN.
Blocking unencrypted connections.
Pre-emptively installing software that remotely wipes sensitive email off your mobile device when it is stolen or misplaced.
Logging off from your system when it is not in use and when employees are away from workstations.
Emphasizing opt-out email encryption to minimize breaches resulting from human error.
2. Encryption
Email is inherently insecure and at risk of being read, stolen, intercepted, modified, and forged (repudiated). Covered entities should go beyond the technical safeguards of the HIPAA Security Rule and take steps that exceed what is required to futureproof their communications. Email encryption features to adopt include the following:
The ability to send secure messages to anyone with any email address.
The ability to receive secure messages from anyone.
Implementing measures to prevent the insecure transmission of sensitive data via email.
Exploring message retraction features to retrieve email messages sent to the wrong address.
Avoiding opt-in encryption to satisfy HIPAA Omnibus Rule.
3. Backups and Archival
HIPAA email rules require copies of messages containing PHI to be retained for at least six years. In light of this, organizations must consider the following:
How are email folders backed up?
Are there at least two different backups at two different geographical locations? Additionally, the processes updating these backups should be independent of each other as a measure against backup system failures.
Have you maintained separate, permanent, and searchable archives? While the emails should be tamper-proof, with no way to delete or edit them, they should be easily retrievable to facilitate discovery, comply with audit requests, and support business-critical scenarios.
4. Defense
Cyber threats against healthcare organizations are continually on the increase. Some may be surprised to learn that HIPAA compliant email rules mandate that organizations take steps to defend against possible malicious actors. With this in mind, consider implementing the following technologies:
Server-side inbound email malware and anti-virus scanning to detect phishing messages and malicious links.
Showing the sender’s email address by default on received messages.
Email filtering software to detect fraudulent messages and ensure it uses Sender Policy Framework (SPF), DomainKeys Identified Mail (DKIM), and Domain-based Message Authentication, Reporting and Conformance (DMARC) information to classify messages.
Scanning outbound email.
Scanning workstations for malware, i.e., viruses, ransomware, etc.
Using plain text previews of your messages.
5. Authorization
A critical aspect of HIPAA’s email rules is ensuring that cybercriminals cannot impersonate your company or employees. Configuring your domains with SPF and DKIM is essential to verify your identity as an authorized sender of mail from your domains. Also, ensure that users cannot send messages through your email servers without authentication and encryption.
6. Reporting
Setting accountability standards for email security is essential to establishing and strengthening your HIPAA compliance posture. Important steps to take include:
Creating login audit trails.
Receiving login failure and success alerts.
Auto-blocking known attackers.
Maintaining a log of all sent messages.
7. Reviews and Policies
Humans are the greatest vulnerability to any security and compliance plan, so creating policies and procedures that focus on plugging vulnerabilities and preventing human errors is essential. Strategies for reducing risk include:
Inviting independent third parties to review your email policies and user settings. Fresh, unbiased eyes can discover existing issues quickly.
Preventing devices that connect to sensitive email accounts from connecting to public WiFi networks.
Creating email policies prohibiting users from clicking on links or opening attachments that are not expected or requested.
8. Vendor Management
Most companies do not manage their email in-house, so it’s crucial to thoroughly research and vet whoever will be responsible for your email services. Perform an annual review of your email security and stay on top of emerging cybersecurity threats to take proactive action and for continued compliance with HIPAA email rules.
LuxSci’s secure high-volume email and marketing solutions are designed to help healthcare organizations tackle complicated HIPAA email rules and automate the compliance process. Contact us today to learn more about how our industry-leading HIPAA complaint email services can help you better secure your customer PHI and keep you in compliance.
If you work in a busy healthcare practice, administrative tasks can create additional costs and barriers to care. Common communications like appointment reminders, billing statements, and other external messages take a lot of time to create and send. By automating these emails, it’s possible to increase operational efficiency and improve patient outcomes.
What is Email Automation?
Email automation allows organizations to automatically send emails based on pre-determined triggers or behaviors. Receipts, shipping notifications, password resets are all common types of automated transactional emails. The main message content is created in advance. Then, variables are used to insert custom information into the template automatically. Most importantly, the email is sent when a certain action is taken. Many people are familiar with automated emails in the form of receipts. For example, you make an online purchase and a receipt is automatically emailed to you with the exact details of your purchase. Next, we explore some examples for how email automation can increase operational efficiency in the healthcare system.
How Email Automation Works
There are many ways to utilize email automation to streamline patient communications. One example is appointment reminders. This is a good message to automate because:
The message is generally the same for every recipient
Variables can be used to customize the content: the patient’s name and the date/time of their appointment.
There is a clear event to trigger the email (the date of the upcoming appointment).
Let’s look at an example of an appointment reminder email:
An administrator creates a template with the message content and layout. It may read something like: “Hi [patient name], This notice is to remind you of your upcoming appointment with Dr. Smith on [X date] at [X time]. Please call our office at 555-555-5555 if you need to reschedule.”
Next, connect the email program to a patient database, like an EHR or CRM. If properly integrated, it is possible to pull in the correct information to replace the variables (in brackets above) for the email recipient. For example, the if the email was sent to a patient named Jane Doe, the email program would pull in the correct details from her record to read: “Hi Jane Doe, This notice is to remind you of your upcoming appointment with Dr. Smith on May 2, 2022 at 1pm. Please call our office at 555-555-5555 if you need to reschedule.”
Finally, set up a trigger point to instruct the email program under what conditions to send the email. For an appointment reminder, the administrator may choose to send the email one week before the appointment, so the recipient has ample time to respond.
Once the template, variables, and trigger are set up, ongoing attention from office staff is not required. Each day appointment reminder emails will be sent out when the conditions of the trigger are met.
The Benefits of Email Automation
By automating common administrative email communications, it frees up staff time to focus on patients. Many healthcare providers still have staff members call patients to remind them of upcoming appointments. By automating this task, it streamlines operations and frees up staff time to focus on other tasks more directly tied to improving patient health outcomes. Using email (and/or text message) reminders can also help decrease no-show rates and reduce the costs of rescheduling.
Email automation is just one tool that can help streamline administrative workflows, provide cost savings, and improve the health outcomes of patients.
Don’t Forget HIPAA
Automated emails like appointment reminders, billing messages, and test results all contain ePHI and must be protected under HIPAA guidelines. Review our HIPAA guidelines for email and take steps to secure systems before starting to automate and send transactional emails containing ePHI.
Get Started with Email Automation
To get started, there are a few internal questions that need to be answered.
First, identify the data source- do you have a database or EHR that contains the information needed to trigger and personalize email messages? Next, how will these emails be sent? Do you have an email marketing platform with automation capabilities? Finally, how will these messages be secured?
Once these questions are answered, LuxSci’s Secure High Volume Email service can help securely scale your operations. Contact us if you are interested in learning more about automating email workflows for your healthcare practice.
Healthcare marketing compliance involves strict adherence to HIPAA authorization requirements, state privacy regulations, and industry advertising standards when using patient information for promotional purposes. Medical practices must obtain written patient consent before incorporating protected health information into testimonials, case studies, or targeted advertising campaigns, while ensuring all business associate agreements with promotional vendors include appropriate data protection clauses and breach notification procedures.
Medical practices pursue new patient acquisition through promotional activities while protecting existing patient privacy rights. Marketing departments frequently discover that their most compelling promotional ideas involve patient stories, treatment outcomes, or demographic data that require extensive legal review before implementation.
Written Authorization for Healthcare Marketing Compliance
Patient authorization must precede any use of PHI in promotional materials, specifying exactly which information will be disclosed, identifying all recipients of promotional communications, and explaining patient rights to revoke consent. These forms require expiration dates, signature requirements, and plain language descriptions that patients can easily comprehend without legal expertise.
Organizations cannot combine promotional authorization with treatment consent forms or condition medical services on patients agreeing to promotional uses of their information. Patients who decline promotional authorization must receive identical treatment quality and cannot experience discrimination or reduced service levels because of their privacy choices.
State Privacy Laws
California’s Consumer Privacy Act, Texas Medical Records Privacy Act, and other state regulations impose requirements that exceed federal HIPAA standards for promotional activities. Some states require opt-in consent for all promotional communications, while others mandate specific disclosure language or waiting periods before promotional authorization becomes effective.
Multi-state healthcare systems must comply with the most restrictive state requirements across all their operations to avoid violating patient privacy laws. Organizations operating in states with enhanced privacy protections cannot rely solely on healthcare marketing compliance but must incorporate additional state-specific requirements into their promotional practices.
Digital Advertising Platforms
Social media advertising, email promotional platforms, and website analytics tools frequently request access to patient contact information, demographic data, or behavioral tracking that falls under privacy protection laws. Healthcare marketing compliance requires careful evaluation of third-party technology vendors to ensure they provide appropriate business associate agreements and data protection measures.
Retargeting campaigns that track patient website visits or online behavior present particular risks when healthcare organizations use advertising pixels, conversion tracking, or audience segmentation tools. These technologies may inadvertently transmit protected information to advertising networks without proper authorization or contractual protections.
Vendor Management Protects Marketing Activities
Advertising agencies, promotional consultants, and marketing service providers need business associate agreements before accessing any patient information for campaign development or audience analysis. These contracts must specify permitted uses of protected data, establish security requirements, and outline breach notification procedures when privacy violations occur.
Organizations retain full liability for vendor compliance failures, making thorough due diligence essential before selecting promotional partners. Healthcare marketing compliance programs should include vendor auditing procedures, contract review protocols, and performance monitoring systems to ensure privacy protection throughout promotional activities.
Content Creation Within Privacy Protection Guidelines
Patient testimonials, success stories, and case studies require detailed authorization forms that specify exactly how patient information will be used across different promotional channels and time periods. De-identification offers an alternative approach but requires removing all identifying elements according to HIPAA standards, including dates, locations, and demographic details that could reveal patient identity.
Photography and video content featuring patients or their treatment areas need separate consent documentation covering future use, distribution methods, and duration of permission. Healthcare marketing compliance includes behind-the-scenes content, facility tours, and staff interviews that might inadvertently capture patient information in background elements.
Staff Education Prevents Privacy Violations
Marketing personnel, communications staff, and external vendors need education about distinguishing between permissible healthcare communications and restricted promotional activities requiring authorization. Training programs should cover identification of protected information, authorization requirements, and escalation procedures for situations requiring legal review.
Updates cover new promotional channels, technology platforms, and changing regulatory interpretations that affect healthcare marketing compliance standards. Organizations benefit from establishing clear approval workflows for promotional materials and designating privacy personnel to review campaigns before launch.
Enforcement Actions Shape Compliance Priorities
Recent OCR investigations have targeted healthcare organizations using patient information in social media posts, email campaigns, and website content without proper authorization. These enforcement actions show increasing federal attention to promotional activities and willingness to impose financial penalties for privacy violations.
Settlement agreements frequently require organizations to implement comprehensive compliance programs, conduct staff training, and submit to monitoring for extended periods. Healthcare marketing compliance programs that consider these enforcement priorities can minimize violation risks and avoid costly regulatory investigations.
Today, we’re excited to unveil our new website and branding, reflecting the company’s next stage of growth and evolution – as well as our aspirations to bring more clarity to data security and the HIPAA compliance landscape for healthcare communications.
In an era where healthcare is rapidly evolving, personalized engagement and communications are more critical than ever, driving greater participation in today’s healthcare journeys and delivering better outcomes. At the same time, HIPAA compliance and the security of protected health information (PHI) are a constant concern for all healthcare organizations. New regulations and cybersecurity threats pop up almost daily and without warning.
At LuxSci, we believe that you can both protect PHI data and use it to carry out more personalized, more effective, and more inclusive healthcare experiences. Our new website and branding are designed to represent this belief, and to help you make the smartest decisions when it comes to secure healthcare communications and HIPAA compliance.
Personalization: The Key to Better Healthcare Engagement
With new healthcare initiatives aimed at increasing patient participation rapidly emerging, including connected care and value-based care, one-size-fits-all communication strategies are no longer effective. Today, patients and customers increasingly expect personalized, relevant, and timely communications over the channel of their choice – and organizations that can deliver on these expectations will deliver better healthcare outcomes for everyone involved. The problem is that patient portal adoption has been hovering at around 50-60% for years, leaving a large portion of the population out of the health conversation.
Now’s the time for healthcare organizations to take action by adopting a more multi-channel approach to communications – while remaining HIPAA-compliant. LuxSci’s new website highlights our capabilities in helping you protect and leverage PHI data for personalized healthcare engagement across email, text, and marketing channels. By combining secure communication channels with advanced personalization powered by PHI data, we empower healthcare organizations to connect with patients in more meaningful ways across the end-to-end healthcare journey.
A New Look for a New Era
Over the years, LuxSci has been at the forefront of providing secure healthcare communications, establishing itself as a leader in HIPAA-compliant email. We serve some of the healthcare industry’s largest organizations, securely sending hundreds of millions of emails per month for our customers. This includes athenaHealth, Delta Dental, Rotech Healthcare, and 1800 Contacts, to name a few.
The launch of our new website reinforces our strategy to deliver a secure multi-channel healthcare communications suite that includes high volume email, and support for text, marketing and forms – and more in the future. Today, LuxSci’s secure healthcare communications suite includes:
Secure High Volume Email – proven, highly scalable HIPPA-compliant email.
Secure Email Gateway – Automatically encrypt emails sent from Microsoft 365, Google Workspace or on-premises solutions for HIPAA compliance.
Secure Marketing – Easy-to-use HIPAA-compliant email marketing solution for healthcare with advanced segmentation and automation.
Secure Text – Secure access to patient portals and digital platforms via SMS from any device – no application required.
Secure Forms – HIPAA-compliant data collection, including PHI, from patients and customers for improved workflows and business intelligence.
All LuxSci products are HIPAA-compliant and are anchored in the company’s highly flexible and automated SecureLineTM encryption technology. LuxSci’s SecureLineTM technology enables you to set different levels of security based on the needs and goals of your targets, and your business. This includes enabling the right level of security for your HIPPA-compliant communications – and all your communications. The best part: SecureLineTM encryption technology is automated, so your users do not need to take any action to ensure all your communications are secured.
“Personalized communications are more likely to engage patients and customers, leading to better care, improved adherence to treatment plans, more purchases, higher satisfaction rates, and ultimately, improved health outcomes,” said Mark Leonard, CEO at LuxSci. “Our new website and branding underscores our ongoing commitment to empower healthcare organizations with best-in-class security and encryption, stellar customer support, and the power to connect with their patients and customers over the communication channel of their choice.”
Whether you’re a customer, partner, or healthcare professional on the lookout for your next HIPAA-compliant, secure healthcare communications solution, check out the new LuxSci website today. See how personalized healthcare engagement can impact your patients, your customers – and your business.
