Email marketing can be a powerful tool for healthcare organizations, but it requires careful planning and execution because of HIPAA compliance requirements. In this blog post, we will discuss email marketing best practices to help healthcare marketers achieve their goals.
1. Define Your Campaign Goals
The success of any email marketing campaign depends on the goals you want to achieve. However, because healthcare organizations are often not selling products to their patients, marketers can be confused about how to set measurable goals for their campaigns that aren’t tied to revenue generation.
Healthcare marketers want to use email marketing campaigns for various purposes, including patient engagement, education, and retention. Some possible objectives of your campaigns could be:
New patient acquisition
Re-engaging lapsed patients
Spreading awareness about vaccines, treatments, or medical conditions
Increasing treatment or medication adherence
Collecting survey responses or patient-reported outcomes
All of these campaign objectives will correlate with different metrics. Identifying the campaign goal and the corresponding metrics you need to track is critical before selecting the audience and crafting the content.
2. Select Your Audience
Gone are the days of sending giant email blasts to your entire contact list. The best email marketers are creating highly targeted campaigns for specific audiences. Healthcare marketers using patient data in their audience targeting efforts are at an advantage. They can use patient information to create distinct audience segments. Targeting a patient population with common attributes makes it easier to craft a relevant message to drive clear results. For example, marketers can create more relevant campaigns when they can divide their patient population into subgroups based on shared characteristics like diagnoses, risk factors, and demographic data.
3. Personalize Your Content
Once you have clearly defined your goal and your audience, it’s essential to use personalization techniques to craft relevant messaging. Healthcare consumers expect more personalization from their providers and want to receive messages that tie into their past experiences. Generic, irrelevant messaging is more likely to annoy patients than get them to act. Healthcare marketers are lucky to have a wealth of data points to use in their messaging, but they must be aware of patient privacy and take steps to secure their messaging. When you have taken the appropriate steps to secure patient data, including protected health information in email messages is possible. This improves the patient experience and makes it easier for healthcare marketers to achieve their objectives.
4. Use A Clear Call-to-Action
Your emails should include a clear call-to-action (CTA) that encourages your audience to take the desired action. These actions may include scheduling an appointment, downloading a resource, logging into a patient portal, filling out a survey, or contacting your organization. Ensure that your CTA is prominent, stands out from the rest of your content, and ties back to the goal of your campaign. Most importantly, implement appropriate tracking technologies so you can see how many email recipients followed through on the CTA.
Don’t include too many calls to action in one message! Including multiple prompts may confuse the recipient and make it more difficult for your team to understand how the campaign performed.
5. Review Your Data
Finally, it’s essential to monitor your email metrics to evaluate the success of your campaigns. Some key metrics may include open rates, click-through rates, surveys completed, successful logins, appointments scheduled, and other relevant metrics that tie back to your goals. Use this data to refine your email marketing strategy, trigger follow-up campaigns and marketing activity, and optimize future campaigns. Use APIs or webhooks to ensure your email campaign statistics are tied into marketing dashboards to get a holistic view of how your campaigns are performing.
6. Choose an Email Marketing Platform Designed for Healthcare
Finally, to use the tactics recommended above, it’s necessary to use a HIPAA-compliant email marketing platform. Segmenting audiences and personalizing content requires the use of protected health information. Therefore, it must be secured in compliance with HIPAA. You must select a platform that can protect data both at rest and in transit to utilize the power of your data fully.
LuxSci’s HIPAA-compliant Secure Marketing was designed to meet the needs of healthcare marketers and enables the use of PHI at scale. Contact our sales team to learn more about our capabilities and email marketing best practices.
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
Most conversations about HIPAA compliant email eventually land on the same acronym: TLS. It’s the most common encryption method in use, and for good reason — it’s widely supported and relatively simple to enforce. But TLS isn’t the only encryption standard healthcare organizations should understand, and it isn’t always the right tool for securing your email address and message content.
S/MIME is the other name that comes up frequently, especially in healthcare, and usually in the same breath as PGP, along with some confusion about what it actually does differently. This guide breaks down what S/MIME is, how MIME works underneath it, how to configure it, and — just as importantly — when it’s genuinely worth the effort versus when it isn’t, based on both the technical standard and real feedback from the people who’ve actually had to manage it.
If you haven’t yet worked through the basics of what makes email HIPAA compliant in the first place, our HIPAA Compliant Email guide is a useful starting point before diving into a specific encryption standard like this one.
What Is S/MIME?
S/MIME stands for Secure Multipurpose Internet Mail Extensions (also written Secure/Multipurpose Internet Mail Extensions). It’s a security extension of MIME, the original standard introduced in 1992 that first allowed email to carry more than plain text — attachments, formatting, and different character sets. Understanding how MIME works helps explain what S/MIME adds on top: where MIME made richer content possible, S/MIME made that content secure by encrypting it and digitally signing it.
S/MIME’s roots as a security standard go back to the early 2000s, largely through work done by RSA Security, one of the earliest companies focused on computer and network security. Because it’s been around for so long, S/MIME is supported natively by most major email clients, including Outlook and Apple Mail, without requiring third-party software or plugins.
At its core, S/MIME provides three distinct protections for email security:
Encryption — ensures that only the intended recipient, using their private key, can read the email messages sent to them
Sender authentication — verifies the identity of the sender, so the recipient can trust the email actually came from who it claims to be from
Digital signing — confirms the message wasn’t altered in transit, effectively letting you digitally sign each message you send
This combination is what distinguishes S/MIME from encryption methods that only protect the connection a message travels over. S/MIME protects the message itself — a meaningful distinction for any organization handling sensitive data security requirements.
How Does S/MIME Work?
S/MIME is built on Public Key Infrastructure (PKI) and asymmetric encryption — a system that uses two mathematically linked digital certificates instead of one shared password.
Public key — shared openly, used by others to encrypt messages sent to you and to verify your digital signature
Private key — kept secret and secure, used by you to decrypt received messages and sign outgoing ones
When someone sends you an S/MIME-encrypted email, they encrypt it using your public key. Only your corresponding private key can decrypt it, meaning that even if the message is intercepted somewhere along its path, it remains unreadable without that specific private key. This is what people mean when they describe S/MIME as end-to-end encryption: the protection travels with the message itself, not just the connection carrying it.
To configure S/MIME, both the sender and recipient need:
A digital certificate, issued by a trusted certificate authority (CA), tied to their specific email address
That certificate properly installed and configured in their email client
Each other’s public key, exchanged in advance, so encryption and decryption can actually happen
If any one of these pieces is missing on either side, S/MIME simply doesn’t work for that exchange — a limitation that comes up constantly in practitioner discussions, and one worth understanding before you invest time configuring it.
What IT Practitioners Actually Say About This
One useful, if slightly humbling, reality check comes up repeatedly in IT forums when people ask whether they should bother configuring S/MIME: as one systems administrator put it plainly, most people you correspond with have no idea how to verify a digital signature and won’t even notice if one is missing. Emails from your bank or a government tax agency, they pointed out, typically aren’t S/MIME signed at all — a sign of just how limited real-world verification behavior actually is outside of specific technical or regulatory contexts.
Another common thread: several IT professionals candidly noted that email clients like Outlook can create friction by automatically trying to reply with an S/MIME signed message, which can be genuinely annoying for a recipient who has no certificate configured and no way to make sense of the added complexity. Their advice, consistently, boiled down to one clarifying question: it isn’t a question of whether you should configure S/MIME, but whether you actually need it — if none of the people you communicate with require signed email, the added configuration probably isn’t buying you anything meaningful.
That distinction — need versus want — is exactly the lens healthcare organizations should apply too, and it’s the framing this guide uses throughout.
S/MIME vs. TLS vs. PGP: How They’re Different
It’s easy to lump every encryption acronym together, but each one solves a slightly different problem.
Method
What It Protects
Identity Verified Via
Complexity
TLS
The connection between mail servers
Server-level certificates, not individual senders
Low — largely automatic, minimal user setup
S/MIME
The message content itself, end-to-end
Trusted certification authorities issue and vouch for individual certificates
High — requires certificates and key exchange for every sender/recipient pair
PGP
The message content itself, end-to-end
A decentralized “web of trust” — users vouch for each other directly
High — similar certificate/key management burden as S/MIME
TLS encryption – most people interact without realizing it — it’s what protects the connection when your email travels from your server to the recipient’s server. The tradeoff is that TLS only protects the message in transit; once it lands on a mail server, TLS’s job is done.
S/MIME and PGP both aim to close that gap by encrypting email messages themselves, so they remain protected even after delivery. The key difference, as one privacy-focused forum discussion put it well, comes down to how identity is managed: S/MIME farms identity verification out to a trusted certification authority, while PGP requires you to manage that trust relationship yourself. For most healthcare organizations, S/MIME’s centralized CA model is the more practical fit, since it aligns better with how enterprise IT departments already manage digital certificates and existing vendor relationships.
Key Benefits of S/MIME
Genuine end-to-end protection. Because the message itself is encrypted, S/MIME protects data security even if it passes through servers that don’t support encryption.
Built-in sender authentication and message integrity. Digital signatures verify both the identity of the sender and that the message hasn’t been tampered with — a layer TLS alone doesn’t provide.
Broad native support across email clients. Most major email clients support S/MIME out of the box, without requiring a separate plugin.
Flexibility to sign without encrypting. As one practitioner pointed out, you can digitally sign an outgoing message without encrypting it — useful for something like a mailing list, where you want recipients to trust the message came from you, but full encryption isn’t necessary or practical for a broad distribution list.
The Real Tradeoffs of S/MIME
Certificate management is ongoing, not one-time. Every sender and recipient needs a certificate tied to their email address, renewed and reissued as staff change roles or leave. Manageable for a small group; significant admin overhead for a whole organization.
Both parties must be configured correctly. If a recipient lacks a certificate or the sender’s public key, the message bounces or fails to send encrypted — some systems fall back to TLS, but only if configured to do so.
Most recipients can’t verify it anyway. IT practitioners consistently note that outside specific business or regulatory contexts, recipients have no practical way to check a digital signature — and default behaviors like auto-signed replies can just create friction.
It doesn’t scale to high-volume email. S/MIME suits direct correspondence between known parties, not appointment reminders, billing notices, or large mailing lists.
It can conflict with malware scanning. End-to-end encryption blocks gateway-level inspection, so scanning has to happen at the endpoint instead.
How to Configure S/MIME?
For Individuals
Obtain an S/MIME certificate from a trusted certificate authority. Certificates come in different validation levels — Basic (validates only the email address), Individual Validation (confirms personal identity), Organization Validation (confirms the business’s legitimacy), or Sponsor validation (combining both).
Install the certificate in your email client — most major email clients, including Outlook and Apple Mail, support this natively.
Configure the client to use the certificate for both encrypting outgoing messages and verifying signatures on incoming ones.
Exchange public keys with anyone you intend to correspond with securely — typically by sending them a signed (but not necessarily encrypted) email first, which shares your public key automatically.
For Organizations
Determine the validation level your organization actually needs. Higher validation levels provide stronger identity assurance but involve more verification steps and cost.
Use centralized tools to manage the certificate lifecycle. Protocols like LDAP or endpoint management platforms (such as Microsoft Intune) can significantly reduce the manual burden of distributing and renewing digital certificates at scale.
Distribute certificates and provide clear installation guidance to every employee who needs S/MIME — this is often where organizations underestimate the support burden, particularly for less technical staff.
Set clear policies on when S/MIME is required versus when other encryption methods, like enforced TLS, are sufficient. Treating S/MIME as a blanket requirement across an entire organization typically creates more friction than protection, echoing exactly what practitioners report when they configure it without a clear need.
When Does S/MIME Actually Make Sense?
Given its administrative overhead — and the recurring, practical feedback from people who’ve actually configured it — S/MIME is best reserved for specific, high-sensitivity use cases rather than applied indiscriminately:
Clinician-to-clinician communication involving particularly sensitive diagnoses or treatment details, where both parties are known and willing to maintain certificates
Cross-organization referrals where a small, defined group of specialists regularly exchanges detailed patient information and can reasonably manage the certificate relationship
Legal, compliance, or executive correspondence where verifying the sender’s identity and confirming message integrity outweighs the setup cost
For everything else — appointment reminders, billing communications, marketing outreach, or high-volume patient correspondence — enforced TLS or a managed encryption platform that automatically selects the right method per recipient is almost always the more practical choice. This mirrors exactly what experienced IT practitioners consistently conclude on their own: it’s not about whether S/MIME can work, it’s about whether your specific communication actually needs it.
A Simpler Path: Automated, Per-Recipient Encryption
The tradeoff most organizations run into with S/MIME isn’t whether it works — it’s whether staff can reliably manage digital certificates for every relevant contact without errors slipping through, and without creating the kind of recipient friction practitioners describe so consistently.
Rather than requiring every sender and recipient to individually configure S/MIME, some HIPAA compliant email platforms automatically select the appropriate encryption method per recipient — TLS when it’s sufficient, a secure portal when the recipient’s system doesn’t support TLS, and PGP or S/MIME when the situation calls for genuine end-to-end protection and sender verification. This removes the burden of manually deciding — and manually maintaining certificates — from individual staff members, while still making S/MIME available for the specific cases where it’s the right tool.
What Should I Do Now? (revised with target-keyword anchor text)
S/MIME is a legitimate, well-established way to secure your email and verify the sender — but understanding when to use it, and when a simpler method is more appropriate, matters just as much as knowing how to configure it. Most healthcare organizations don’t need S/MIME everywhere; they need the right encryption method applied automatically, based on the situation.
Here’s where to go next:
Learn more about HIPAA compliant email encryption to see how encryption standards like S/MIME fit into a broader compliance strategy.
Explore Secure High Volume Email to see how automatic, per-recipient encryption — including S/MIME and PGP where appropriate — removes the manual certificate management burden from your staff.
Talk to a LuxSci expert if you’re evaluating which encryption approach fits your organization’s specific mix of high-sensitivity and high-volume email.
FAQs
1. Is S/MIME better than TLS for email security?
Neither is universally better — they solve different problems. TLS protects the connection a message travels over and suits high-volume, everyday email. S/MIME protects the message content itself, end-to-end, and suits specific, high-sensitivity communications between known parties who can manage digital certificates.
2. What happens if I send an S/MIME encrypted email to someone who doesn’t support it?
The message typically won’t deliver as encrypted, and depending on how the sending system is configured, it may bounce back to the sender or automatically fall back to TLS.
3. Do I need a separate digital certificate for every email address, or just one for my organization?
Each individual email address needs its own certificate issued by a certificate authority. A single organizational certificate doesn’t cover every employee — certificates are tied to specific addresses, not the organization as a whole.
4. Can I digitally sign an email without encrypting it?
Yes. Signing confirms the identity of the sender and that the message wasn’t altered, without requiring the recipient to have a certificate of their own. This is useful for situations like mailing lists, where full encryption isn’t practical but sender verification still adds value.
5. Is S/MIME a good fit for HIPAA compliant marketing emails?
Generally, no. S/MIME’s certificate and key exchange requirements don’t scale well to high-volume or one-to-many communication like marketing campaigns. Enforced TLS or a platform that manages encryption automatically per recipient is typically the better fit for that use case.
Few terms in healthcare get thrown around as loosely as “HIPAA violation.” It gets invoked when a nurse mentions a patient’s diagnosis to a friend outside of work, when a technician talks about a well-known patient who came through the clinic, or when a physician casually brings up a person’s rare diagnosos at a backyard barbecue — situations that sound like violations but often have nothing to do with the actual law. That confusion isn’t just an oversight, but rather, it points to a gap in understanding what HIPAA covers, who it applies to, and what genuinely puts an organization at risk.
For health care providers, compliance officers and IT professionals, the stakes behind that confusion are anything but casual. The Department of Health and Human Services (HHS) Office for Civil Rights (OCR) has issued settlements ranging from a few thousand dollars to over $16 million for the same underlying failures, such as a missed risk assessment, an unencrypted laptop, a chart accessed by the wrong person. This guide breaks down what actually constitutes a HIPAA violation, the most common ways organizations end up on OCR’s radar, what genuinely falls outside HIPAA’s scope, and what to do if you’re managing risk or responding to an incident right now.
If your organization handles PHI over email — one of the highest-risk channels for exactly this kind of violation — our HIPAA Compliant Email guide is a useful next read once you’ve worked through this one.
What Is a HIPAA Violation?
A HIPAA violation occurs when a covered entity, business associate, or a member of either’s workforce fails to comply with a standard set out in the HIPAA Privacy Rule, Security Rule, or Breach Notification Rule — or fails to follow an internal policy implemented to support HIPAA compliance.
That definition matters because it draws a hard boundary around who can actually commit one. HIPAA applies to:
Covered entities — healthcare providers, health plans, healthcare suppliers, payers, and healthcare clearinghouses
Business associates — vendors and contractors that create, receive, maintain, or transmit protected health information (PHI) on a covered entity’s behalf
Workforce members — employees, volunteers, and contractors of either of the above
HIPAA does not apply to private individuals acting outside of a covered role — a distinction that trips up far more people than you’d expect, and one we’ll come back to later in this guide.
The Health Insurance Portability and Accountability Act (HIPAA) was designed to protect the confidentiality of medical records and patient data while still allowing healthcare organizations to function and share information when appropriate. A violation happens when that balance breaks down — when PHI is accessed, used, or disclosed in a way the law doesn’t permit, or when required safeguards simply aren’t in place.
The Three HIPAA Rules a Violation Can Break
Every HIPAA violation traces back to one (or more) of three core rules. Understanding which rule is in play helps clarify what actually went wrong — and what needs to be fixed.
Rule
What It Governs
Example Violation
Privacy Rule
Who can access, use, and disclose PHI, and under what circumstances
Sharing a patient’s diagnosis with someone outside their care team without authorization
Security Rule
Administrative, physical, and technical safeguards for electronic PHI (ePHI)
Failing to encrypt emails in transit or a laptop that stores patient information
Breach Notification Rule
Requirements for notifying affected individuals and HHS after a breach of unsecured PHI
Missing the 60-day deadline to notify patients after a data breach
Most real-world violations involve more than one rule at once, such as a stolen, unencrypted laptop is a Security Rule failure that can also trigger Breach Notification Rule obligations. Keeping the three rules distinct in your own documentation, though, makes it much easier to identify exactly where a gap exists.
Most Common Types of HIPAA Violations
These are the violation categories that show up most often in OCR settlements, and the ones every provider, payer, and supplier organization should actively guard against.
Unauthorized Access / Snooping
This is the violation most people have actually heard about, usually because of a celebrity or high-profile patient case that made headlines. A staff member accesses a patient’s medical record without a legitimate, job-related reason — often out of curiosity, not malice — and it still counts as a serious violation.
What’s easy to miss here: the violation is about the access itself, not just what happens to the information afterward. Looking at a chart you have no clinical reason to view is a violation the moment it happens, even if you never repeat, share, or act on what you saw. Hospitals take this seriously enough to flag high-profile patient charts automatically and audit access in real time — which is exactly why staff who snoop tend to get caught quickly, and why termination is the near-universal outcome when they do.
A useful way to think about it: the sensitivity of the underlying information isn’t what determines whether accessing it was a violation — the authorization to access it through that specific system is and if a job role requires it. Pulling PHI through a restricted system without a legitimate reason is a violation even in cases where the same information might, in theory, be available through some other, non-restricted channel. Improper access through the wrong door is still improper access.
Example: Dr. Huping Zhou was sentenced to four months in federal prison after accessing celebrity medical records 323 times with no legitimate reason. UCLA Health System was separately fined $865,000 related to similar unauthorized access incidents.
Failure to Conduct a Risk Analysis
The Security Rule requires covered entities and business associates to conduct an organization-wide risk analysis identifying vulnerabilities to the confidentiality, integrity, and availability of ePHI. Skipping this step — or doing a superficial version of it — is one of the single most commonly cited failures in OCR settlements, because it’s foundational: nearly every other safeguard depends on knowing where your actual risks are.
Example: Premera Blue Cross paid $6,850,000, and Excellus Health Plan paid $5,100,000, both tied in part to failures to conduct adequate risk analyses before major breaches occurred.
Insufficient Access Controls
Access controls determine who can view or modify ePHI, and they need to be granular enough that staff can only access the minimum information necessary for their role. When access controls are too loose, such as shared logins, no role-based restrictions, no automatic logoff, organizations lose the ability to actually enforce the “minimum necessary” standard HIPAA requires.
Example: Anthem Inc. paid $16,000,000, the largest HIPAA settlement to date, following a breach connected in part to access control failures affecting nearly 79 million individuals.
Failure to Encrypt ePHI on Portable Devices
Laptops, phones, and USB drives leave the building. When they’re lost or stolen without encryption, an isolated incident becomes a reportable breach — because unencrypted PHI on a missing device is, by definition, unsecured PHI.
Example: Children’s Medical Center of Dallas paid $3.2 million after multiple incidents involving lost, unencrypted mobile devices containing ePHI.
Missing or Incomplete Business Associate Agreements
Any vendor that creates, receives, maintains, or transmits PHI on a covered entity’s behalf — from a billing company to an email provider — is a business associate under HIPAA, and business associates are legally required to sign a Business Associate Agreement (BAA) before handling that data. Skipping this step, or using a vendor without one, is a violation regardless of whether anything actually goes wrong with the data itself.
Example: North Memorial Health Care of Minnesota paid $1.55 million after failing to enter into a BAA with a business associate that later experienced a breach.
Impermissible Disclosures of PHI
This category covers PHI shared with someone who wasn’t authorized to receive it — a press release naming a patient, a social media post, filming patients without consent, or telling family or coworkers more than they’re entitled to know.
Example: New York Presbyterian Hospital paid $2,200,000 after filming patients for a documentary without proper consent.
Improper Disposal of PHI
Paper records tossed in regular trash instead of being shredded, or old hard drives discarded without being wiped, both count as impermissible disclosures — PHI doesn’t stop being protected just because someone’s done using it.
Example: Parkview Health paid $800,000 after leaving patient medical records unattended in a driveway during a records transfer.
Exceeding Breach Notification Deadlines
Once a breach of unsecured PHI is discovered, the Breach Notification Rule sets a hard 60-day deadline to notify affected individuals (and HHS, for breaches involving 500+ records). Missing that window turns a bad situation into a compounding one.
Example: Presence Health paid $475,000 for failing to notify affected individuals within the required timeframe following a breach.
Denying Patient Access to Records
Patients have a right to access their own medical records, generally within 30 days of a request, without excessive fees or unreasonable barriers. Denying or delaying that access is one of the more consistently enforced violation categories in recent years.
Example: Cignet Health of Prince George’s County paid $4,300,000 for denying 41 patients access to their own medical records.
Every one of these categories comes back to the same underlying question: does your organization actually have documented, enforced processes for who can touch PHI, how it’s protected, and what happens when something goes wrong? If email is part of that picture — and for nearly every healthcare organization, it is — our HIPAA Compliance Checklist walks through exactly what needs to be in place.
What Is Not a HIPAA Violation (Common Misconceptions)
HIPAA gets invoked constantly in situations it has nothing to do with — and clearing up that confusion matters, because it helps healthcare professionals, IT and compliance teams focus their actual attention where it belongs.
A family member discussing your health isn’t a HIPAA violation. HIPAA governs covered entities, business associates, and their workforces — not private individuals speaking in a personal capacity. Your mother telling a relative about your diagnosis might be a breach of your trust, but it’s not a HIPAA violation, because she isn’t bound by HIPAA in the first place.
Confusing HIPAA with FERPA or the ADA is common, and usually incorrect. Educational records fall under FERPA (the Family Educational Rights and Privacy Act), not HIPAA — a teacher discussing a student’s grades or attendance isn’t a HIPAA issue. Similarly, questions about a disability accommodation, like a mask exemption or a service animal, generally fall under the Americans with Disabilities Act (ADA), not HIPAA.
Asking about someone’s health isn’t the same as disclosing it. HIPAA restricts what covered entities and their workforces can disclose, it doesn’t restrict what any individual, including a coworker, cashier, or stranger, can ask. Someone asking why you’re wearing a mask or requesting proof of a medical condition might be inappropriate or even illegal under a different law, but it isn’t itself a HIPAA violation.
Vague references aren’t the same as identifiable disclosures. HIPAA violations require that protected health information (PHI) be tied to an identifiable individual. Referring to “a patient” or “a young adult male” in casual conversation is too vague to trigger a violation. Naming a specific person — “my patient, Mike, who lives on Oak Street” — alongside health information crosses that line.
A simple way to keep the distinction clear:
A nurse telling friends a specific patient’s name, date of birth, and diagnosis → HIPAA violation.
A pharmacist telling a customer their prescription refill is delayed → not a HIPAA violation.
The line isn’t about whether something feels private. It’s about whether protected health information tied to an identifiable person was disclosed by someone bound by HIPAA in the first place.
HIPAA Violation Penalties: The 4-Tier Structure
OCR calculates civil penalties based on the violator’s level of culpability, not just the severity of the incident. Understanding which tier applies matters, because the same underlying mistake can result in wildly different consequences depending on whether it was a one-off oversight or a known, ignored risk.
Tier
Culpability Level
Fine Range (Per Violation)
Annual Cap
Example Scenario
Tier 1
No Knowledge
$100 – $50,000
$25,000
The organization could not have reasonably known about the violation
Tier 2
Reasonable Cause
$1,000 – $50,000
$100,000
The organization should have known, but the violation wasn’t due to willful neglect
Tier 3
Willful Neglect (Corrected)
$10,000 – $50,000
$250,000
Willful neglect occurred, but the issue was corrected within 30 days
Tier 4
Willful Neglect (Not Corrected)
$50,000 (fixed)
$1.5 million+
Willful neglect occurred and was not corrected in time
Penalty amounts are periodically adjusted for inflation, and current maximum penalties can exceed $2 million annually per violation category — figures worth confirming against HHS’s current published rates before citing specific numbers internally.
Criminal penalties sit outside this civil tier structure entirely. Knowing or willful violations can result in criminal fines ranging from $50,000 to $250,000, plus up to 10 years in prison for the most serious offenses — typically reserved for cases involving intent to sell, transfer, or use PHI for personal gain or malicious harm.
How Are HIPAA Violations Discovered?
Violations don’t usually surface because someone confesses. They’re found through a handful of consistent channels:
Audit logs and automated access-flagging. Most modern EHR systems automatically flag unusual access patterns — a chart accessed by someone outside the care team, or a spike in access to a high-profile patient’s record. This is precisely how most unauthorized-access violations come to light; systems are built to catch exactly this pattern.
Patient complaints. Patients can, and do, file complaints directly with HHS when they believe their information was mishandled.
Breach self-reporting. Covered entities and business associates are required to self-report breaches meeting certain thresholds.
OCR compliance audits. HHS periodically conducts proactive audits of covered entities and business associates, independent of any specific complaint or breach.
One nuance worth understanding: not every violation escalates the same way. A single, isolated mistake, such as an email sent to the wrong recipient or a chart accidentally opened, is often handled through internal correction and documentation. A repeated pattern of the same behavior is a different story entirely, and is far more likely to become something an organization is required to report to HHS. This is one of the most important distinctions for healthcare organizations and compliance teams to build into internal escalation policies: document every incident, but treat repetition as a signal that internal correction alone is no longer sufficient.
How to Report a HIPAA Violation
If you’re a patient, employee, or compliance officer who has identified a potential violation, there are two established paths ti report a violation, and they aren’t mutually exclusive.
Step 1: Report it to the employer or covered entity directly. Most healthcare organizations have an internal compliance officer or reporting process specifically for this purpose. Internal reporting is often the fastest way to get a genuine mistake corrected before it escalates.
Step 2: File a complaint with HHS’s Office for Civil Rights. If internal reporting isn’t appropriate, isn’t effective, or the violation is serious enough to warrant it, complaints can be filed directly through HHS’s official complaint portal. Complaints generally must be filed within 180 days of when the violation was discovered, though extensions are sometimes granted for good cause.
A few practical notes:
Anonymous reporting is possible, but limited. OCR accepts anonymous complaints, but the lack of contact information can restrict how thoroughly they’re able to investigate.
Retaliation against someone who reports in good faith is itself prohibited under HIPAA.
Not every complaint results in a formal investigation — OCR reviews each complaint to determine whether it falls within HIPAA’s scope before proceeding.
How to Avoid HIPAA Violations & Fines
For Organizations
Conduct — and document — a genuine risk assessment. This isn’t a one-time checkbox; risk assessments should be revisited whenever systems, vendors, or workflows change.
Sign a BAA with every vendor that touches PHI, including email, billing, and IT service providers — no exceptions.
Implement role-based access controls so staff can only access the minimum PHI necessary for their specific role.
Encrypt ePHI in transit and at rest, especially on portable devices and email, where enforced encryption remains one of the most consistently under-implemented safeguards.
Train staff regularly, not just at onboarding. A single training session at hire rarely holds up against years of evolving risk.
For Individual Staff Members
Only access patient records tied to a legitimate, job-related reason — never out of curiosity, even for patients you know personally.
Never discuss identifiable patient information outside of your care team, including with family, friends, or on social media.
Report suspected violations, including your own mistakes, immediately rather than waiting to see if anyone notices.
Treat every device and email containing PHI as if it could be lost, stolen, or misdirected tomorrow, because eventually, statistically, one will be.
Since email remains one of the highest-volume channels for exactly this kind of accidental exposure, secure, HIPPA compliant solutions, such as LuxSci’s SecureLine encryption technology, are built specifically to remove the guesswork — enforcing encryption automatically rather than relying on staff to remember to apply it correctly every time.
HIPAA vs. State Privacy Laws
HIPAA sets a federal floor, not a ceiling. States are free to enact privacy laws that are stricter than HIPAA, and when they do, the stricter standard generally governs. This matters for multi-state healthcare organizations especially, such as a provider, payer, or supplier operating across state lines may need to comply with HIPAA everywhere, plus additional, more stringent requirements in specific states.
This guide focuses on federal HIPAA requirements, but compliance officers should treat HIPAA as the baseline, not the finish line, when evaluating their organization’s full regulatory exposure.
What Should I Do Now?
Understanding what counts as a HIPAA violation is the first step. Actually closing the gaps that lead to one is the harder, ongoing work — and email is one of the most common places that work quietly falls through the cracks.
Here are three ways to keep moving forward:
Read our HIPAA Compliant Email guide to understand exactly what makes an email platform compliant — and where standard email tools like Gmail and Microsoft 365 fall short.
Work through our HIPAA Compliance Checklist to audit your organization’s current safeguards against what HIPAA actually requires.
Explore LuxSci’s SecureLine encryption technology to see how enforced encryption and a signed BAA work together to close the exact gaps that show up most often in OCR settlements.
The most common violations include unauthorized access to patient records, failure to conduct a risk analysis, insufficient access controls, failure to encrypt ePHI on portable devices, missing Business Associate Agreements, impermissible disclosures of PHI, improper disposal of records, and exceeding breach notification deadlines.
2. What’s the difference between a HIPAA violation and a FERPA or ADA issue?
HIPAA governs protected health information handled by covered entities and business associates in healthcare settings. FERPA governs education records, and the ADA governs disability discrimination and accommodation. A teacher discussing grades falls under FERPA, not HIPAA. A question about a disability accommodation typically falls under the ADA, not HIPAA.
3. How do I report a HIPAA violation?
Report it directly to the employer or covered entity first, if appropriate. If that isn’t effective or the violation is serious, file a complaint with HHS’s Office for Civil Rights within 180 days of discovering the violation, using the official HHS complaint portal.
4. Can I sue someone for violating HIPAA?
No. HIPAA does not provide a private right of action, meaning individuals cannot sue directly under HIPAA. Patients can file a complaint with HHS/OCR, and in some cases may have separate legal remedies under state privacy or negligence laws.
5. Is looking up a patient’s chart without a work reason a HIPAA violation, even if I don’t share the information?
Yes. Accessing a patient’s record without a legitimate, job-related reason is a violation the moment it happens — it doesn’t require sharing, saving, or acting on the information afterward. This is one of the most consistently enforced categories, particularly for high-profile or celebrity patients whose charts are routinely audited.
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.
A HIPAA secure email is a specialized communication system that protects protected health information during electronic transmission through encryption, access controls, audit logging, and other security features required for regulatory compliance. HIPAA secure email platforms enable healthcare organizations to send sensitive patient information while meeting privacy and security standards established by federal healthcare regulations. Healthcare providers, payers, and suppliers use HIPAA secure email to communicate with patients, business partners, and other healthcare organizations without risking privacy violations or security breaches. Understanding what makes HIPAA secure email different from standard email helps organizations select appropriate communication tools and maintain compliance with healthcare privacy regulations.
Core Security Features of HIPAA Secure Email
HIPAA secure email systems include end-to-end encryption that transforms readable messages into coded format during transmission and storage. This encryption ensures that only authorized recipients with proper decryption keys can access message content and attachments. Transport Layer Security protocols protect email communications during transmission between servers, while message-level encryption secures content even when stored on email servers. Multi-factor authentication verifies user identities before granting access to email systems, requiring additional verification beyond standard passwords. Access controls limit which users can send emails to external recipients and specify what types of information can be included in different message categories. Automatic session timeouts prevent unauthorized access when users leave workstations unattended, while secure password requirements protect user accounts from unauthorized access.
Administrative Controls and User Management
HIPAA secure email platforms provide centralized administration tools that allow IT teams to manage user accounts, configure security policies, and monitor compliance across the organization. Role-based permissions ensure that staff members can only access email functions appropriate to their job responsibilities and organizational roles. User provisioning and deprovisioning processes control access to email systems when staff members join or leave the organization. Policy enforcement mechanisms automatically apply security settings based on message content, recipient types, and organizational rules. Administrative dashboards provide real-time visibility into email security metrics, user activity patterns, and potential policy violations. Centralized logging captures all administrative activities, creating audit trails that demonstrate compliance with regulatory requirements and organizational policies.
Audit and Compliance Tracking Capabilities
Comprehensive audit logging tracks all activities within HIPAA secure email systems, creating detailed records of message transmission, recipient access, and user behavior patterns. These logs include information about who sent messages, when they were transmitted, what attachments were included, and how recipients accessed the content. Audit trails help organizations demonstrate compliance during regulatory reviews and investigate potential security incidents. Log retention policies ensure that audit information remains available for required periods while protecting stored data from unauthorized modification or deletion. Automated reporting features generate compliance reports and alert administrators to unusual email patterns or potential security concerns. Regular audit log reviews help identify training needs and process improvements for email security practices across the organization.
Integration with Healthcare Systems and Workflows
HIPAA secure email solutions integrate with electronic health record systems, practice management platforms, and other healthcare applications to streamline communication workflows. These integrations allow users to send secure messages directly from patient records or billing systems without switching between multiple applications. Automated triggers generate secure email notifications for appointment reminders, lab results, billing communications, and other routine patient interactions. Application programming interfaces enable custom integrations with specialized healthcare software used by different types of organizations. Single sign-on capabilities allow users to access email functions using their existing healthcare system credentials, reducing password management burden and improving user experience. Integration features help maintain productivity while ensuring that all communications involving protected health information remain secure.
Patient Communication and External Messaging
HIPAA secure email platforms include patient portal functionality that enables secure two-way communication between healthcare organizations and their patients. Patients can access secure portals to read messages, respond to communications, and download documents without requiring special software installations. Portal notifications alert patients when new messages arrive while maintaining privacy protections throughout the communication process. External messaging capabilities allow secure communication with business partners, referring physicians, and other healthcare organizations that may use different email systems. Message delivery confirmation and read receipts provide verification that important communications reached intended recipients and were accessed appropriately. Secure message forwarding ensures that communications can be shared with authorized parties while maintaining encryption and audit trail integrity.
Implementation and Deployment Considerations
Healthcare organizations implementing HIPAA secure email need to consider data migration from existing email systems, staff training requirements, and integration with current technology infrastructure. Planning processes should include security risk assessments, workflow analysis, and stakeholder input to ensure selected solutions meet organizational communication needs. Pilot deployments allow organizations to test functionality and identify potential issues before full implementation across all departments. Change management strategies help staff adapt to new email security procedures and software interfaces while maintaining productivity and patient care quality. Technical support during implementation ensures that integration challenges are resolved quickly and security configurations meet organizational requirements. Post-deployment monitoring verifies that HIPAA secure email systems perform as expected and continue meeting compliance obligations as organizational needs change over time.
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.
HIPAA for explanation of benefits statements includes privacy protections, disclosure limitations, and patient access rights that healthcare providers, payers, and suppliers need to understand when handling these documents. These requirements govern how explanation of benefits forms can be shared, stored, and transmitted while protecting patient information. Healthcare organizations processing explanation of benefits communications encounter specific HIPAA obligations that affect billing workflows, patient communications, and third-party interactions.
Privacy Protections in Explanation of Benefits Communications
HIPAA for explanation of benefits statements requires health plans to protect patient information contained within these documents. Explanation of benefits forms contain protected health information including patient names, dates of service, provider details, and treatment codes that qualify for privacy protections under HIPAA regulations. Health insurers processing explanation of benefits must implement safeguards to prevent unauthorized access, use, or disclosure of this information during document creation, transmission, and storage processes. The privacy protections extend to electronic and paper-based explanation of benefits communications. Health plans sending explanation of benefits via email need encryption or secure patient portals to protect information during transmission. When mailing paper explanation of benefits, insurers must use appropriate addressing and packaging to prevent accidental disclosure to unintended recipients. Correct implementation of these privacy measures prevents unauthorized access and maintains patient confidentiality.
Patient Access Rights for Explanation of Benefits Documents
Patients have specific rights under HIPAA regarding their explanation of benefits statements, including the right to receive copies, request corrections, and control how these documents are shared. Health plans must provide explanation of benefits to patients within reasonable timeframes and allow patients to designate how they prefer to receive these communications. Patients can request explanation of benefits in specific formats or ask that copies be sent to alternative addresses when medically necessary or for safety reasons. The right to request amendments applies to explanation of benefits when patients identify errors in treatment descriptions, billing codes, or other information contained within these documents. Health plans must have procedures for handling amendment requests and responding to patients within required timeframes. When approved, health plans must accommodate these requests according to HIPAA timelines and notification procedures.
Disclosure Rules for Explanation of Benefits Information
Health plans must follow certain disclosure rules when sharing explanation of benefits information with healthcare providers, patients, and third parties. HIPAA allows disclosure of explanation of benefits information for treatment, payment, and healthcare operations without patient authorization, but requires minimum necessary standards to limit information sharing to what is needed for the specific purpose. Healthcare providers can receive explanation of benefits details related to their patients’ claims processing and payment status as part of routine payment operations. Disclosure to family members or personal representatives requires either patient authorization or demonstration that the person has legal authority to act on the patient’s behalf. Health plans cannot share explanation of benefits information with employers, even when the employer sponsors the health plan, without specific patient authorization or as permitted under limited circumstances outlined in HIPAA regulations. Patient privacy remains protected while enabling health plans to conduct necessary payment and administrative activities.
Electronic Transmission Requirements for Explanation of Benefits
Electronic transmission of explanation of benefits requires compliance with HIPAA security standards to protect patient information during digital communication processes. Health plans using email, patient portals, or other electronic methods to deliver explanation of benefits must implement appropriate safeguards including encryption, access controls, and transmission security measures. These requirements apply whether explanation of benefits are sent as attachments, embedded in secure messages, or accessed through online platforms. The security requirements also cover explanation of benefits data stored in electronic systems, requiring health plans to implement administrative, physical, and technical safeguards to protect this information from unauthorized access or disclosure. Audit controls help track who accesses explanation of benefits information and when, providing accountability and helping identify potential security incidents. Organizations benefit from conducting periodic reviews to address emerging security challenges and technology updates.
Business Associate Obligations for Explanation of Benefits Processing
Third-party vendors processing explanation of benefits on behalf of health plans operate as business associates under HIPAA and must comply with specific obligations when handling this protected health information. Business associate agreements must outline how vendors will protect explanation of benefits data, limit its use to authorized purposes, and report any security incidents or unauthorized disclosures. These agreements help ensure that outsourced explanation of benefits processing maintains the same privacy and security protections required of health plans. Business associates processing explanation of benefits must implement appropriate safeguards for the information they handle and ensure that any subcontractors also comply with HIPAA requirements. The obligations include limiting access to explanation of benefits information to authorized personnel, providing security training, and maintaining audit logs of information access and use. Proper contract management and oversight ensure that all parties handling explanation of benefits information maintain appropriate privacy standards.
Compliance Monitoring for Explanation of Benefits Practices
Healthcare organizations need to consistently assess their explanation of benefits practices to ensure continued HIPAA compliance. Conducting audits also helps to identify potential gaps in privacy protections, disclosure practices, or security measures that could lead to violations. Training programs help staff understand their responsibilities when handling explanation of benefits information and keep them updated on regulatory changes that affect these communications. Incident response procedures specifically address explanation of benefits-related security breaches or privacy violations, including notification requirements and remediation steps. Documentation of explanation of benefits practices, policies, and training helps demonstrate compliance efforts during regulatory reviews or investigations. Consistent monitoring and documentation create a foundation for sustainable HIPAA compliance across all explanation of benefits operations..
As the healthcare industry grows increasingly competitive, personalized engagement has become a key differentiator for companies aiming to better connect with their patients and customers.
However, effective personalization requires more than loosely matching a patient to a product or service based on a handful of dubious demographic data points – or a message carefully crafted to assume familiarity. Instead, successful personalized patient engagement requires using data from your Customer Data Platforms (CDPs), Electronic Health Records (EHR) systems, and Revenue Collection Platforms (RCPs) in combination with a secure communications solutions to target and tailor your messages like never before.
To help you get there, this post explores core strategies for leveraging PHI in patient engagement, as well as the benefits of integrating secure communications like HIPAA-compliant email with your CDPs, RCPs, and EHR systems. Whether you’re a healthcare provider, payer or supplier, these strategies will help you develop a data-driven approach to patient engagement that sets your brand apart, builds trust, and boosts customer loyalty and satisfaction.
Why Personalized Engagement Makes a Difference
Ultimately, personalized patient or customer engagement is vital because it strengthens relationships, fosters trust, and encourages proactive healthcare behaviors and decision-making. By taking the extra time to craft your communications to resonate with the recipient’s particular healthcare needs and pain points – and securely including it in our messages – makes your targets more likely to engage with you, now and in the future. This results in an individual becoming a more active participant in their healthcare journey: engaging in more self-education, listening to advice (e.g., screening recommendations), adhering to treatments, trying new products, and, ultimately, enjoying better health outcomes overall.
However, to reap these benefits, healthcare organizations must navigate the complexities of securely handling PHI and integrating it across communication systems and data platforms to facilitate personalized and HIPAA-compliant interactions.
Three Core Strategies for Personalized Engagement Across the Healthcare Journey
Let’s look at three essential engagement strategies that will help you achieve better results by leveraging PHI in your communications, including:
Here are a few examples of how healthcare providers can employ PHI-driven personalization to increase patient engagement, using the email channel:
Reminders for Preventive Care: by segmenting patients by their risk factors and medical history, providers can send customized email reminders for preventative screenings, vaccinations, or check-ups.
Post-Treatment Follow-ups: sending patients customized follow-ups after treatment or surgery improves adherence to prescribed care plans. Providers can automate reminders, follow-up surveys, or educational materials specific to the patient’s condition, increasing engagement, and overall awareness of their health journey, and, subsequently, health outcomes.
Mental Health and Chronic Care Management: the management of both mental health and chronic disease conditions favor a high-touch, personalized approach. PHI-driven engagement enables healthcare providers to send the most appropriate regular check-ins, support resources, and reminders to reach a patient population that can fall through the cracks of outreach efforts.
2. Payer-Focused Strategies: Supporting Long-Term Health
Payers, such as health insurers, can leverage PHI for tailored member engagement that aligns with value-based care objectives, including:
Engage Members Via Their Preferred Channels: sending people information through their preferred channels, such as email, text, or phone, greatly improves the chances that they receive it and act upon it. This better ensures they receive important details, such as policy details and benefits, that will assist them on their healthcare journey, leading to higher levels of satisfaction with their coverage and more business and renewals for your company. You can gain greater insight into this in our article on How to Improve Patient Engagement with Secure Communications.
Strengthened Member Loyalty: the more that customer feel that their payer understands their unique health concerns and needs, the greater their sense of loyalty towards them. Personalized interactions increase trust and member or customer satisfaction, resulting in long-term relationships.
Proactive Retention Strategies: by analyzing customer data, payers can identify those at risk of not renewing their healthcare coverage and implement targeted communications to retain them. Personalized outreach, such as email reminders about plan benefits or assistance with the renewal process, can effectively encourage members to continue their coverage.
3. Supplier Strategies: Enhancing Customer Support and Education
Healthcare suppliers, such as medical device manufacturers and pharmaceutical companies, can harness PHI to educate customers on the benefits of their products and services for upsell and cross-sell, in addition to offering exceptional support, training and aftercare following their purchase.
Tailored Customer Education: with PHI, healthcare suppliers can provide condition-specific educational resources that will help customers better understand how their offerings support their health. In many cases, this will be much-welcomed information, resulting in increased brand awareness, trusted relationships, and, ultimately, better health outcomes.
Personalized Adherence Programs: sending personalized reminders, or an offer of support, boosts the chances of compliance with medication or device usage instructions – both increasing their efficacy and reducing the risks that accompany their misuse. Additionally, automating emails for these follow-ups, as part of a comprehensive customer onboarding process, streamlines this process and ensures the most valuable customer experience.
Equipment Renewals or Upgrades: proactively sending customers emails and messages on new or updated products and services can lead to increased conversions and sales, by simple virtue of the fact you’re telling your customer base about them. All customers who have seen improvements in their quality of life from your products or services will be interested to hear about improvements or additions to your offerings – so seize this prime opportunity to engage with them.
The Power of Data Integration
To maximize personalization, healthcare organizations can leverage PHI across the different systems within their IT ecosystems and create unified data profiles that drive better engagement. Integrating data from Customer Data Platforms (CDPs), Electronic Health Records (EHR) systems, and Revenue Collection Platforms (RCPs), and securely using it in communications, such as email campaigns, is a critical component of meaningful engagement and increases your ability to reach your targets. Here’s how it helps:
CDPs aggregate data from multiple channels to provide a comprehensive, centralized view of each patient or customer. By integrating PHI and other behavioral data in a CDP, healthcare organizations can better understand patient needs, preferences, and history, resulting in more precise, data-driven engagement.
EHRs boast a wealth of patient data that can be used to personalize engagement down to an individual level. By securely integrating EHR data, healthcare providers can tailor communications to reflect each patient’s unique medical history and current care plan, making successful engagement far more likely.
RCPs are essential for understanding the financial side of patient engagement. When combined with clinical and behavioral data, RCPs provide insights into a patient’s financial interactions with the healthcare system, allowing organizations to personalize payment reminders, financial assistance programs, and other revenue cycle communications. With this being one of the more contentious and stressful parts of the healthcare journey for many patients, securely communicating PHI as part of your RCP strategy can have a considerable positive impact on patient satisfaction, as well as reducing billing cycle times and their resulting admin.
By uniting data from these platforms, and other applications where critical data resides, healthcare organizations gain a comprehensive view of each patient, enabling highly-personalized interactions that improve outcomes and increase trust over time.
As healthcare provider, payers and suppliers expand their use of PHI for more effective personalization, securing sensitive patient data becomes increasingly crucial. When employing the personalized engagement strategies detailed in this post, it’s essential to ensure all PHI is handled securely, if you don’t want to incur the consequences of falling out of HIPAA compliance.
LuxSci offers a suite of HIPAA-compliant, secure communication solutions designed to facilitate secure, personalized patient and customer engagement, while providing the necessary foundation to effectively use PHI in your emails. Our solutions enable healthcare organizations to optimize data integration from CDPs, EHRs, and RCPs to better personalize engagement and deliver better results. This includes:
Secure Email: protects PHI with automated, flexible encryption options that exceed HIPAA compliance requirements. This allows for high-volume, personalized email outreach without compromising privacy.
Secure Marketing: especially designed for HIPAA-compliant campaigns, LuxSci’s Secure Marketing solution boasts advanced email functionality including segmentation, automation, and deep email reporting tools, enabling impactful engagement at scale.
Secure Text: connect with patients over mobile devices by enabling access to PHI and other sensitive information via regular SMS text messages – with no installation of new applications required.
Secure Forms: LuxSci’s Secure Forms tool ensures that organizations can safely collect and process PHI, enabling seamless data capture for personalized engagement.
Interested in discovering how LuxSci’s secure healthcare communications services can help you leverage PHI for highly more personalized patient engagement?
Contact us to learn more about our products and pricing, and to schedule your free demo!
