Growing numbers of healthcare organizations are turning to Customer Data Platforms (CDPs) to consolidate and leverage patient data (or electronic protected health information (ePHI) from electronic health record (EHR) systems, RCM platforms, CRM systems, websites, communications channels, and other various sources.
CDPs enable healthcare providers, payers, and retailers to better understand each patient’s needs, health conditions, treatment schedules, ongoing care, and so on, enabling them to take the right actions, at the right time to improve engagement. This results in more patient participation, enhanced coordination with providers and companies, and, ultimately, improved patient outcomes.
Why Should You Integrate CDPs and Email?
Integrating the functionality of a CDP with a HIPAA compliant email platform, such as LuxSci, empowers you to put your data into action. This includes enabling you to better target your various segments using real-time communications data – such as email opens, clicks and conversions – as well as using PHI in secure messages for greater personalization – all while operating within the bounds of HIPAA (the Health Insurance Portability and Accountability Act) regulations.
With this in mind, this post discusses the benefits of integrating your organization’s CDP solution with a HIPAA compliant email solution. We’ll explore the main benefits and how to integrate the two solutions, as well as several effective strategies for leveraging the valuable PHI stored within your CPD to increase patient and customer engagement.
Benefits of Integrating a CDP with HIPAA Compliant Email
Let’s begin by looking at the main advantages of pairing your CDP with a HIPAA compliant email platform.
Increased Protection of Customer Data
Above all, HIPAA compliant email platforms are specifically designed with the stringent data privacy and security requirements of the healthcare industry in mind. As a result, they contain a range of data security features, including encryption, access control, user authentication, and audit logging, that both better safeguard ePHI from unauthorized access and ensure HIPAA compliance. In short, HIPAA compliant email helps ensure that when valuable and sensitive CDP information is put into use, i.e. using it in patient emails and communications, it’s protected and safe both in transit and at rest.
Avoid the Consequences of HIPAA Violations
By opting for an email provider that meets the security requirements for HIPAA compliance – and better yet, HITRUST certification – your company can better mitigate the risk of data breaches, and the compliance violations that accompany them. The consequences of HIPAA compliance violations include:
Financial penalties: this includes regulatory fines, legal fees and compensation to affected parties, and state-level fines (in certain cases). In the event that compliance officers can prove willful neglect, your company may even face criminal charges, incurring further damage.
Operational disruptions: suffering a security breach requires healthcare organizations to spend time on containment and notifying and reassuring affected parties, as well as taking subsequent mitigation efforts – all of which take time away from running the day-to-day business.
Reputational damage: displaying an inability to safeguard sensitive data will cause patients and customers to lose trust in your organization and move to other providers or suppliers.
Enhanced Personalization in Engagement Efforts
With ongoing uncertainty around HIPAA regulations, healthcare companies are often reluctant to include PHI in their email communications and campaigns, missing opportunities to fully leverage your CDP to create more effective, more relevant messages, targeting highly segmented audiences. Safe in the knowledge that customer data derived from your CDP will be secured by your HIPAA compliant email provider or HIPAA compliant marketing solution, you can confidently include PHI in communications to craft more personalized – and potent – engagement opportunities.
The data aggregated by CDPs can be used to divide, or segment, customers into smaller groups with particular commonalities, such as a health condition like diabetes, or users of a particular type of medical equipment. Healthcare marketers can use the shared needs and problems of each patient or customer segment to drive more effective and targeted campaigns that deliver more opens, clicks, and conversions.
Strategies for Leveraging Customer Data Through CDP and Email Integration
Having a better understanding of the benefits of CDP integration with your email communications, let’s move on to a few of the most effective ways to leverage your customer data through a HIPAA compliant, secure email services provider (ESP).
Segmenting Customers by Health Condition or Risk Profile
The first strategy, as alluded to above, is to use the health-oriented data stored in your CDP to group customers into segments that you can target with highly personalized messaging – using PHI to your advantage. Segmentation could be based on health conditions, such as demographics, location, or by a patient’s lifestyle risk factors, e.g., smokers.
Having defined your segments, you can create personalized email campaigns for each, which are far more likely to drive engagement and actions versus messages designed to appeal to everyone or with limited information. Better still, you can create different email campaigns to fulfill different purposes with automated workflows based on how your patients respond, giving you a range of opportunities to reach out and connect. Using intelligence from your CDP, you can design your email campaigns to:
Educate: send patients and customers educational materials designed to increase their understanding of their state of health and the options available to them for creating the most favorable outcomes.
Offer adherence advice: include information on how to best adhere to a prescribed care or treatment plan, resources on overcoming common challenges, where to go for support, etc.
Provide preventive care tips: help patients who fit a particular risk profile, such as diabetes or heart disease, make better lifestyle choices, with the ultimate aim of avoiding the disease they’re at risk of.
Lifecycle-Based Messaging
This is a variation on the above strategy that segments patients and customers based on how far along they are in their treatment lifecycle, for instance:
Onboarding: messaging that introduces your services, explains how to access care, and covers other preliminary details; this stage is essential for setting expectations and establishing trust with your patients and customers.
Active Treatments: regular check-ins, medication reminders, preparation guides, and educational resources based on their condition or treatment plan; this messaging is designed to support adherence and improve healthcare outcomes.
Follow-Up and Recovery: personalized care instructions, satisfaction surveys, or information about next steps; this shows ongoing support and maintains consistent communication when a patient may be feeling most vulnerable.
Preventive and Long-Term Care: triggering routine screening reminders, vaccine alerts, or wellness tips based on age, history, and risk factors; an integrated CDP and email system can track when patients are due for services and automate communication accordingly.
Re-engagement: sending patients who have been inactive for a while tailored prompts, e.g., “We haven’t seen you in a while…”; this encourages proactivity and helps highlight new services that may be of interest.
Behavior-Triggered Messaging
Integrating your CDP with a HIPAA compliant email platform enables you to automate email delivery and workflows based on a customer’s behavior and engagement patterns. This type of email is enabled by the CDP’s ability to monitor events and behaviors across multiple activities and locations, enabling you to create email campaign strategies and workflows accordingly. This approach allows for a range of timely and relevant engagement opportunities, including:
Missed appointments: sending a message if a patient misses an appointment that encourages them to reschedule and assists them in how to do so.
Periodic checkup reminders: similarly, if a patient is supposed to have regular checkups, follow-up appointments, a recommended health screening, etc., this data can be passed from the CDP to the email client to schedule automated emails that drive up appointment bookings.
Unfilled prescriptions: if a patient hasn’t picked up their prescribed medication, you can automatically trigger an email reminder and automated workflow to get the prescription filled; this information can also be fed back to their healthcare providers if repeated reminders see the prescription remain unfilled.
Patient portal inactivity: if a user hasn’t logged into a portal for a predefined time frame, this can prompt a re-engagement email encouraging them to check messages in their portal, view test results, etc.
Form completion: after inputting data into a web form, an integrated CDP can help facilitate the delivery of a tailored email that offers guidance on next steps or the most relevant products or services based on given answers.
Implement Feedback Loops for Optimized Engagement
Finally, a key benefit of integrating a CDP with a HIPAA compliant email platform is that it enables you to close the loop between engagement and results. By feeding campaign performance data, such as email opens, clicks, conversions, and other key metrics, back into your CDP, you can continuously refine your email outreach strategies to enhance engagement, while developing a more complete data profile of patients and customers.
Put Your CDP into Action with LuxSci Secure Email
Integrating HIPAA compliant communications solutions like LuxSci with your healthcare organization’s CDP empowers you to securely harness your customer data in email communications for consistent, timely, and relevant engagement – for better health outcomes and better business.
To learn more about LuxSci’s suite of secure HIPAA compliant communication solutions and how we seamlessly integrate with leading CDP solutions to improve engagement, contact us today!
Pete Wermter
As a marketing leader with more than 20 years of experience in enterprise software marketing, Pete's career includes a mix of corporate and field marketing roles, stretching from Silicon Valley to the EMEA and APAC regions, with a focus on data protection and optimizing engagement for regulated industries, such as healthcare and financial services.
Pete Wermter — LinkedIn
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.
Ensuring HIPAA compliance for email is crucial for healthcare organizations and their business associates when handling Protected Health Information (PHI). HIPAA regulations require strict safeguards, including access controls, audit logs, integrity protections, and transmission security, to prevent unauthorized access and breaches. Encryption plays a key role in securing PHI during email exchanges, and organizations must establish comprehensive email policies aligned with the HIPAA Privacy Rule. Additionally, some state laws may impose stricter requirements, such as obtaining explicit patient consent before using email for PHI. Understanding these regulations is essential for maintaining compliance, protecting patient data, and avoiding costly penalties.
The Health Insurance Portability and Accountability Act (HIPAA) is a complicated law that sets the standards for collecting, transmitting, and storing protected health information (PHI). When information is stored or exchanged electronically, the HIPAA Security and Privacy Rules require covered entities to safeguard its integrity and confidentiality. One of the most common ways that PHI is shared electronically is via email. Understanding how HIPAA email rules apply is essential to meet HIPAA requirements and protect 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 and procedures and obligations concerning business associate contracts.
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.
Technical safeguards ensure the security of email data transmitted over an open electronic network and the storage of that data.
Below, we discuss 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 Compliance Email Rules
While email encryption gets most of the spotlight during discussions on HIPAA compliant email security, HIPAA regulations for email cover a range of behaviors, controls, and services that work together to address eight key areas.
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. Some key steps to take include:
Using strong passwords that cannot be easily guessed or memorized.
Creating different passwords for different sites and applications.
Using two-factor authentication.
Securing connections to your email service provider using TLS and a VPN.
Blocking unencrypted connections.
Being prepared with 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, eavesdropped on, modified, and forged (repudiated). Covered entities should go beyond the technical safeguards of the HIPAA Security Rule and take steps beyond what is required to futureproof their communications. Some 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 retention rules require copies of messages containing PHI to be retained for at least six years. To address these requirements, organizations must consider the following:
How are email folders backed up?
Are there at least two different backups at two different geographical locations? 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 increasing. Some may be surprised to learn that HIPAA secure email requirements mandate that organizations take steps to defend against possible attackers. To defend against malicious messages, consider implementing the following technologies:
Server-side inbound email malware and anti-virus scanning to detect phishing 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 SPF, DKIM, and DMARC information to classify messages
Scanning outbound email
Scanning workstations for malware and virus
Using plain text previews of your messages
5. Authorization: A crucial aspect of HIPAA secure email requirements is ensuring that bad actors 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 improving your HIPAA compliance posture. Some 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. Create policies and procedures that focus on plugging vulnerabilities and preventing human errors. Some ways to reduce risk include:
Inviting independent third parties to review your email policies and user settings. Fresh, unbiased eyes can weed out issues quickly.
Disallowing the use of public Wi-Fi for devices that connect to your sensitive email.
Creating email policies prohibiting users from clicking on links or opening attachments that are not expected or requested.
8. Vendor Management: Most people do not manage their email in-house. Properly vetting and researching whoever will be responsible for your email services is essential. Perform a yearly review of your email security and stay on top of emerging cybersecurity threats to take proactive action when necessary for sustained HIPAA compliance.
LuxSci’s secure email solutions were designed to help organizations tackle complicated HIPAA email rules. Contact us today to learn more how we can help you secure sensitive data.
Documenting HIPAA Compliance For Email
HIPAA compliant email requires documented proof that privacy and security protocols are being followed. HIPAA email systems must include audit trails, policy records, and incident response documentation that demonstrate appropriate safeguards are in place. Healthcare organizations benefit from clear documentation practices that satisfy regulatory inspectors while supporting daily operations and staff training activities.
Email Policy Documentation and Implementation Records
Healthcare organizations must develop written policies that govern HIPAA email usage according to Privacy Rule and Security Rule standards. Email policies should specify encryption requirements, staff responsibilities for handling patient information, and procedures for responding to security incidents. Policy documents must include implementation dates, responsible staff members, and update procedures when regulations change or organizational needs evolve.
Training records provide evidence that employees understand their HIPAA email obligations and can properly implement security procedures. Documentation should capture completion dates, training topics, assessment scores, and remedial training when staff members fail initial evaluations. Organizations that cannot produce training records struggle to prove employees received instruction appropriate to their job functions and access to patient information.
Business Associate Agreement files cover relationships with email service providers and other vendors handling protected health information. Contract documentation should include security specifications, incident reporting procedures, and audit rights that allow healthcare organizations to verify vendor performance. Without proper agreements, healthcare organizations expose themselves to liability when vendors mishandle patient information.
Risk assessment documentation identifies vulnerabilities in HIPAA email systems and describes corrective measures implemented to address identified problems. Assessment records should include evaluation methods, discovered issues, remediation plans, and verification that fixes have been properly implemented. Many organizations conduct risk assessments but fail to document their findings, making it difficult to track improvements over time.
Audit Trail Management and Log Analysis
HIPAA compliance for email depends on audit logs that track user activities, system access, and message handling throughout email platforms. Audit systems should capture login events, message transmission records, administrative changes, and security alerts that might indicate potential violations. Log protection prevents tampering while ensuring data remains accessible for regulatory review periods.
Monitoring systems can identify unusual email usage patterns that suggest security incidents or policy violations. Alert capabilities should flag failed login attempts, large file transfers, abnormal message volumes, and access from unauthorized locations. Real-time monitoring helps healthcare organizations respond quickly to potential security events before they escalate into breaches.
Log review schedules ensure audit data receives regular examination for potential security incidents or policy violations. Review procedures should specify analysis frequency, responsible personnel, and escalation steps when suspicious activities are discovered. Some entities collect extensive audit data but never review it, missing opportunities to identify security problems early.
Log retention policies balance storage costs with regulatory requirements and potential legal discovery obligations. Retention schedules should consider HIPAA requirements alongside other applicable regulations that might demand longer storage periods.Log data must be destroyed properly when retention periods expire to prevent unauthorized access to historical communications.
Incident Response Documentation and Breach Investigation
HIPAA email incident response procedures must address security events and human errors that might compromise patient information. Response plans should include assessment procedures, containment steps, investigation protocols, and notification requirements for different incident types. Quick response often determines whether a minor security event becomes a reportable breach.
Breach investigation procedures help healthcare organizations determine whether email incidents constitute breaches of unsecured protected health information under HIPAA definitions. Investigation protocols should include evidence collection methods, impact assessments, timeline development, and documentation standards that support internal decisions and potential regulatory reporting. Complex incidents may require external legal and technical expertise.
Notification procedures vary based on incident severity and the type of information potentially compromised. Internal notification processes ensure appropriate personnel are informed about incidents and can participate in response activities. Patient notification requirements create legal obligations that organizations must fulfill within timeframes established by federal regulations.
Corrective action documentation describes measures implemented to prevent similar incidents and demonstrates organizational commitment to improving email security. Action plans should include root cause analysis, remediation steps, implementation timelines, and verification procedures that confirm corrective measures work as intended. Organizations that implement fixes without documenting them may repeat the same mistakes when staff turnover occurs.
Staff Training Documentation and Competency Records
HIPAA email training programs must address technical email operations and regulatory requirements for handling protected health information. Training materials should cover encryption procedures, access controls, incident reporting, and acceptable use policies for email communications. Role-based training ensures different staff groups receive instruction appropriate to their job functions and patient information access levels.
Competency verification procedures help healthcare organizations confirm staff members understand and can properly implement HIPAA email security measures. Verification methods may include written tests, practical demonstrations, and performance monitoring that evaluate staff compliance with email policies. Training programs without competency verification cannot prove that employees actually learned the required information.
Refresher training schedules ensure staff members stay current with evolving threats, policy updates, and new email system features. Training frequency should consider technology change rates, emerging security threats, and organizational policy modifications. Staff members who received training years ago may not remember procedures or may have developed bad habits that compromise security.
Training effectiveness measurement helps healthcare organizations evaluate whether HIPAA email training programs meet learning objectives. Measurement approaches may include before and after assessments, incident rate analysis, and feedback collection that provide insights into training quality. Organizations should adjust training content based on effectiveness data to ensure educational efforts support compliance goals.
System Configuration and Change Control Records
Email system configuration documentation provides detailed records of security settings, access controls, and integration setups that support HIPAA compliance for email. Configuration records should include baseline security settings, approved modifications, and verification procedures that confirm systems maintain appropriate security levels. System administrators need current configuration records to troubleshoot problems and maintain security standards.
Change management procedures ensure modifications to HIPAA email systems receive proper evaluation, testing, and documentation before implementation. Change processes should include security impact assessments, testing protocols, approval workflows, and rollback procedures that minimize risks to email security. Changes made without proper documentation and approval create security vulnerabilities that may not be discovered until a breach occurs.
Version control procedures help healthcare organizations track changes to email system configurations and maintain the ability to restore previous settings when problems occur. Version documentation should include change descriptions, implementation dates, responsible personnel, and verification that modifications function properly. Organizations need version control to understand how their systems evolved and to reverse changes that cause problems.
Patch management procedures ensure email systems receive security updates promptly while maintaining system stability and compliance. Patch processes should include vulnerability assessment, testing protocols, deployment schedules, and verification that updates install correctly. Delayed patching leaves systems vulnerable to known exploits that criminals actively target.
HIPAA Compliant Email Vendor Management and Contract Documentation
Email service provider relationships must include Business Associate Agreements that specify security requirements, compliance obligations, and incident reporting procedures. Contract documentation should cover data handling standards, audit rights, and termination procedures that protect healthcare organizations when vendor relationships end. Regular vendor performance reviews ensure service providers continue meeting contractual obligations.
Vendor compliance verification ensures email service providers maintain their obligations under Business Associate Agreements and healthcare security standards. Verification activities may include security certification reviews, audit report analysis, and compliance documentation that demonstrates ongoing adherence to healthcare privacy requirements. Healthcare organizations that trust vendors without verification may discover compliance failures only after incidents occur.
Service level agreement documentation defines performance expectations, availability targets, and response times for email services and security incidents. Agreement records should include uptime guarantees, incident response procedures, and remediation steps when service levels are not met. Performance tracking helps healthcare organizations evaluate vendor reliability and compliance with contractual commitments.
Vendor communication records document interactions about security updates, policy changes, and compliance requirements that affect email services. Communication logs should include update notifications, compliance discussions, and resolution of security concerns that arise during vendor relationships. Good communication records help resolve disputes and ensure both parties understand their obligations when changes occur.
Healthcare organizations waiting for the final HIPAA Security Rule updates before improving email encryption and security may already be behind.
While the proposed changes to the HIPAA Security Rule are expected to be finalized in May, the direction from the U.S. Department of Health and Human Services Office for Civil Rights (OCR) is becoming increasingly clear. Across investigations, settlements, and enforcement actions, OCR continues emphasizing stronger technical safeguards, encryption, documented security programs, multi-factor authentication (MFA), risk analysis, and proactive cybersecurity operations.
For healthcare organizations, one area stands directly in the middle of all of these priorities: email.
Email remains a primary communication channel in healthcare — and one of the industry’s largest security vulnerabilities. From unauthorized PHI exposure to phishing attacks and ransomware delivery to account compromise, email continues to be at the center of healthcare cybersecurity incidents.
So, are the proposed HIPAA Security Rule changes hypothetical future guidance or a preview of OCR’s future enforcement expectations?
For healthcare email security, the implications are significant.
Email = Healthcare Cybersecurity Risk
Healthcare organizations rely on email for critical communications and healthcare workflows, including:
Patient communications
Care coordination
Claims and billing notifications
Marketing and engagement
Internal collaboration
Third-party vendor communications
Delivery of sensitive PHI
At the same time, attackers continue targeting email systems because they remain one of the easiest entry points into healthcare environments.
Insecure email workflows create unnecessary exposure of protected health information. Phishing campaigns are becoming more sophisticated. Credential theft attacks are bypassing traditional MFA methods. And business email compromise (BEC) attacks continue rising.
Recent OCR enforcement actions increasingly reflect these realities.
Organizations are being evaluated not simply on whether a breach occurred, but whether they implemented reasonable safeguards beforehand, including encryption, authentication controls, monitoring, access management, and documented risk mitigation processes.
For email systems specifically, that means healthcare organizations should expect increased scrutiny around:
Email encryption enforcement
MFA deployment
Audit logging and retention
Conditional access policies
Vendor security controls
Secure email delivery best practices
Segmentation and infrastructure isolation
Ongoing patch and vulnerability management
In many ways, email infrastructure is becoming a visible test of an organization’s overall cybersecurity posture.
Email Encryption Is Moving From Addressable to Required
Historically, healthcare organizations often interpreted HIPAA email encryption requirements with flexibility because encryption was technically categorized as an “addressable” safeguard under the Security Rule. But, OCR enforcement and broader cybersecurity realities are changing that interpretation rapidly.
Today, failing to encrypt sensitive healthcare communications increasingly creates both security and regulatory risk. The proposed Security Rule updates place even greater emphasis on encryption and technical safeguards. At the same time, OCR investigations continue examining whether organizations properly protected PHI in transit and at rest.
For healthcare email specifically, this creates several growing expectations:
Email encryption should be automated wherever possible
Human error should not determine whether PHI is protected
Organizations should maintain documented encryption policies
Secure delivery methods should adapt dynamically to recipient capabilities
Audit trails should demonstrate how messages were secured
At LuxSci, we have long believed that encryption should operate as a strategic layer of healthcare communications infrastructure, not as a manual user decision.
Our SecureLine email encryption technology automatically applies appropriate encryption methods based on organizational policies and delivery requirements, helping reduce the risks associated with human error while maintaining usability, deliverability and compliance. As enforcement expectations rise, this type of automated security enforcement is becoming increasingly important.
Healthcare organizations have historically viewed MFA deployment as sufficient protection. But attackers have adapted quickly.
MFA bypass attacks, token theft, session hijacking, and consent phishing campaigns are increasingly targeting healthcare users. As a result, regulators and cybersecurity experts are placing greater emphasis on phishing-resistant authentication approaches and contextual access controls.
For email environments, organizations should increasingly evaluate:
Whether MFA methods are resistant to phishing attacks
Conditional access policies based on device, location, and behavior
Account monitoring and anomaly detection
Administrative access protections
Session management controls
Logging and authentication auditing
The broader message is clear: healthcare organizations need authentication strategies designed for today’s threat landscape, not yesterday’s compliance checklist.
OCR Wants Proof, Not Just Policies
One of the clearest trends emerging from recent OCR activity is the increasing importance of documentation and operational evidence. Healthcare organizations must increasingly demonstrate not only that safeguards exist, but that they are consistently enforced, monitored, tested, and maintained over time.
For email systems, organizations should be prepared to demonstrate:
Email encryption policies
MFA enforcement records
Audit logs and message tracking
Vendor security documentation
Risk assessments involving email infrastructure
Patch management procedures
Employee security awareness training
Incident response procedures for email-based threats
This represents a broader shift in healthcare cybersecurity expectations.
The question is no longer: “Do you have email security controls?”
The question is increasingly: “Can you prove they are operationally effective?”
Healthcare Organizations Need a New Email Security Strategy
The healthcare industry is entering a new phase of cybersecurity enforcement.
OCR’s direction is becoming increasingly clear: organizations are expected to proactively secure systems handling PHI using modern, documented, and continuously maintained safeguards. For email security specifically, that means organizations should stop treating encryption, MFA, and secure communications as optional compliance requirements. Instead, they should view secure email infrastructure as a strategic component of enterprise cybersecurity and patient trust.
At LuxSci, we help healthcare organizations modernize secure communications with HIPAA compliant email infrastructure designed specifically for healthcare environments, including flexible encryption, secure delivery, auditability, high deliverability, access controls, and dedicated infrastructure options.
The proposed HIPAA Security Rule updates may not yet be final. But, OCR is already signaling where healthcare cybersecurity enforcement is headed next. For organizations relying on email to communicate with patients, members, customers, and partners, the time to examine your secure email infrastructure is now.
Connect with our experts to learn more using the form at the top of this page!
Patient expectations of healthcare providers have dramatically changed in the last decade. The introduction of technology and the widespread adoption of digital communications in other industries have increased the pressure on healthcare providers to provide a comparable experience.
The 2023 Healthcare Consumer Perspectives on Digital Engagement and AI report conducted by Dynata Research found that more patients are adopting digital tools to manage their health and want their providers to provide a consistent experience across all channels. To improve the patient experience, a personalized patient engagement strategy is necessary.
Personalized Patient Engagement Improves the Patient Experience
Healthcare organizations manage so much data that can be used to improve the patient experience. As audience segmentation and personalization techniques have become more common in other industries like e-commerce and personal care, consumers are starting to expect the same experiences from their healthcare providers.
For example, media streaming services make personalized recommendations for new shows based on what you have previously watched. People like these features because it helps them discover new content they may not know about. Likewise, patients are beginning to expect a similar personalized patient engagement experience from their healthcare provider. Suppose a patient wants to control their diabetes diagnosis and communicates with their provider about this at an appointment. Afterward, when they log into the patient portal or receive follow-up information, they expect to receive relevant information that aligns with that provider’s conversation.
Proactive, personalized patient engagement can also drive patients to make the right choices in managing their health. By sending patients the correct information at the right time in the context of their individual health journey, it is easier for them to manage their own health.
Shifting Preferences for Digital Tools Enable Personalized Patient Engagement
As more people are open to incorporating digital tools into their healthcare journeys, it has revealed new patient engagement opportunities. Several reasons led healthcare organizations to embrace digital tools. The coronavirus pandemic kicked off a necessary wave of digital transformation because of the rapid transmission of the disease through close contact. The desire to use these tools has remained strong even after institutions largely reopened in 2021. Patients have also shown no desire to go back to the way things used to be. Digital channels and tools like patient portals, email, medical devices, and mobile applications all make it easier for patients to manage their health on the go.
As patient preferences have shifted to embrace digital channels and technologies, organizations that can implement digital-first personalized patient engagement strategies intelligently are more likely to have satisfied and healthier patients. However, healthcare organizations must strive to provide a consistent experience across both in-person and digital avenues. According to the survey, the number one reason consumers would consider changing their healthcare provider is “complex or confusing experiences.” Poorly implemented and executed patient engagement can negatively impact the patient experience and retention, so it’s essential to be thoughtful in your approach.
How to Personalize the Patient Experience
Traditionally, HIPAA compliance requirements have made it difficult for healthcare providers to utilize protected health information (PHI) in personalized patient engagement efforts. Using PHI in communications is vital to craft messaging relevant to the patient’s health journey. However, when transmitting and storing PHI, HIPAA regulations must be followed to protect patient privacy.
The first step to executing personalized patient engagement involves selecting the right tools. Many traditional digital engagement tools are not designed to meet these stringent encryption and security requirements. By selecting tools that meet HIPAA’s technical requirements (like LuxSci’s Secure Marketing and Secure High Volume Email) and properly training employees, healthcare teams can employ the same segmentation and personalization techniques to reach patients with relevant and consistent communications.
Conclusion
Personalizing patient engagement is one way to improve patient marketing and retention. Contact us today to learn more about improving the patient experience with secure email communications.
For years, multi-factor authentication (MFA) was considered one of the most effective ways to protect sensitive systems. By requiring a second verification step, such as a text message code or push notification, organizations could significantly reduce the risk of compromised passwords.
But the threat landscape has changed.
Today, attackers routinely bypass traditional MFA using techniques such as MFA evasion, token replay attacks, and consent phishing. These methods are no longer rare or highly sophisticated. They are widely used, automated, and increasingly effective.
As a result, regulators, auditors, and security frameworks are raising expectations for authentication security. For healthcare organizations in particular, traditional MFA alone may no longer satisfy the HIPAA requirement to implement “reasonable and appropriate safeguards.”
In the near future, email systems that rely only on basic MFA, without conditional access or phishing-resistant authentication, may increasingly be viewed as security gaps during risk assessments.
Why Traditional MFA Is No Longer Enough
Traditional MFA still improves security compared to passwords alone. However, many common MFA methods were designed before today’s phishing techniques and cloud authentication attacks became widespread.
Common MFA methods include:
SMS verification codes
Email-based authentication codes
Push notifications to mobile apps
While these mechanisms add friction for attackers, they can still be intercepted or manipulated during sophisticated phishing attacks. Because modern attackers now target authentication workflows directly, organizations relying solely on traditional MFA may be more vulnerable than they realize.
How Attackers Bypass MFA Today
Cybercriminals increasingly rely on tools that capture credentials and authentication tokens during login sessions. Three attack techniques are now especially common.
MFA Evasion and Phishing Proxies – Attackers frequently deploy adversary-in-the-middle phishing kits that sit between the user and the real login service. When users enter their credentials and MFA code on a phishing page, the attacker forwards the information to the legitimate site and captures the authentication session. The user successfully logs in—but the attacker gains access as well. If attackers capture those tokens, they can reuse them to access the account directly.
Token Replay Attacks – After successful authentication, systems typically issue session tokens that allow users to remain logged in without repeated MFA prompts. This technique has been widely observed in attacks targeting cloud email platforms such as Microsoft 365, allowing attackers to access email data even when MFA is enabled.
Consent Phishing – Consent phishing bypasses MFA entirely. Instead of stealing passwords, attackers trick users into granting permissions to malicious applications that request access to their mailbox or files. If users approve the request, the attacker’s application receives persistent access to the account through APIs—often without triggering security alerts.
Why Email Authentication Matters Most in Healthcare
Email remains one of the most critical systems in healthcare organizations. It supports patient communication, internal collaboration, and the exchange of sensitive information. Unfortunately, it is also the most frequently targeted entry point for cyberattacks.
Once attackers gain access to an email account, they can:
Impersonate healthcare staff
Launch internal phishing attacks
Access sensitive patient communications
Extract protected health information (PHI)
Because of this, email authentication controls are becoming a major focus for security teams and compliance auditors alike.
Evolving Regulatory Expectations
HIPAA does not prescribe specific technologies, but it requires organizations to implement safeguards that are “reasonable and appropriate” based on risk. As new attack methods emerge, the definition of reasonable security evolves.
Today, many security frameworks and regulatory bodies are emphasizing stronger identity protections, including:
Phishing-resistant authentication
Conditional access policies
Monitoring for suspicious login behavior
Controls for third-party application permissions
Organizations that rely solely on basic MFA may increasingly struggle to demonstrate that their authentication protections are sufficient.
The Shift Toward Phishing-Resistant Authentication
To address the weaknesses of traditional MFA, many organizations are adopting phishing-resistant authentication technologies, which can be enabled with tools like Duo and Okta. These solutions rely on cryptographic authentication tied to trusted devices, which prevents attackers from capturing or replaying login credentials.
Examples include:
Hardware security keys
Passkeys
Certificate-based authentication
Because authentication is tied to both the device and the legitimate website domain, these technologies significantly reduce the success rate of phishing attacks.
Why Conditional Access Is Becoming Essential
Conditional access adds another layer of protection by evaluating context and risk before granting access. Instead of treating every login the same, conditional access policies analyze signals such as:
Device security status
Geographic location
Network reputation
User behavior patterns
If something appears unusual, such as a login from a new country, the system can require stronger authentication or block the attempt altogether. This risk-based approach to authentication helps prevent many account compromise scenarios.
The Future of HIPAA Risk Assessments
As authentication threats evolve, healthcare security assessments are increasingly focusing on identity protection maturity. Organizations may begin seeing findings related to:
Weak or outdated MFA methods
Lack of conditional access policies
Insufficient monitoring of login activity
Unrestricted third-party application permissions
In particular, email systems without advanced authentication protections may be flagged as high-risk vulnerabilities, especially when PHI is accessible.
LuxSci’s Modern Approach to MFA
Modern threats require more than a simple second login factor. LuxSci approaches authentication security with layered identity protection designed specifically for healthcare environments.
Instead of relying solely on basic MFA methods like SMS codes or email verification, LuxSci supports stronger authentication controls and policies that align with evolving security expectations. These protections can include:
Strong multi-factor authentication options
Monitoring for unusual login behavior
Enhanced identity verification mechanisms
By combining multiple security layers within its HIPAA-compliant secure communications email and marketing solutions, LuxSci helps healthcare organizations protect sensitive email communications while maintaining usability for providers, health plan administrators, payment providers, and patient engagement teams.
Conclusion
Multi-factor authentication remains an important security control—but not all MFA is created equal. Attack techniques such as phishing proxies, token replay, and consent phishing have demonstrated that traditional MFA methods can be bypassed. As a result, regulators and auditors are increasingly expecting stronger identity protections.
For healthcare organizations that rely heavily on email communications, the implications are significant. Weak authentication controls can expose sensitive patient data and may soon appear as high-risk findings during HIPAA risk assessments. The organizations best positioned for the future will be those that modernize authentication strategies now, moving toward phishing-resistant methods, conditional access policies, and layered identity protection.
Reach out to LuxSci today to learn how HIPAA compliant email can support both your organization’s engagement and cybersecurity needs.
FAQs
1. What is traditional MFA?
Traditional MFA refers to authentication methods that require a second verification step, typically SMS codes, email codes, or push notifications.
2. Why can attackers bypass MFA today?
Modern phishing tools can intercept authentication sessions or steal login tokens, allowing attackers to access accounts even when MFA is enabled.
3. What is phishing-resistant authentication?
Phishing-resistant authentication uses cryptographic methods tied to trusted devices, preventing attackers from capturing login credentials.
4. Why is email security especially important for healthcare organizations?
Email systems often contain patient communications and sensitive information, making them a common target for cyberattacks.
5. How can organizations improve authentication security?
Organizations can strengthen identity security by adopting phishing-resistant authentication methods, implementing conditional access policies, and monitoring login activity.
