LuxSci Enhances API Authentication for Easier, More Flexible Integrations with EHRs, CDPs and RCM Platforms

Company Announcements, New Feature Announcements
Erik Kangas
April 7, 2025

Today, we’re pleased to announce that LuxSci just made it even easier to leverage its powerful high volume email API with the healthcare platforms you rely on most. Whether you’re connecting with an EHR system, Customer Data Platform (CDP), Revenue Capital Management (RCM) platform—or even your contact center or unified communications suite—the new LuxSci API authentication options unlock the flexibility you need to scale and move fast.

In healthcare, connected patient journeys anchored in secure, personalized communications are driving increased engagement and better outcomes for patients and companies—all at a lower cost. From sending secure high-volume transactional emails to targeted marketing and educational communications, your systems and platforms need to talk to each other without friction to achieve the best results. LuxSci’s new API updates make that possible, securely.

What’s New in This Update

Support for OAuth 2.0, API Key, and Basic authentication methods.
Published API YAML specs and SwaggerHub integration for instant testing.
Enhanced multi-factor authentication (MFA) protection with one-time-use codes.

Overview of the LuxSci API

The LuxSci API is built with healthcare IT, security and developer teams in mind. It’s RESTful, secure, and designed for high volume email workflows.

Using industry standards like HTTPS, JSON, and TLS 1.2+, LuxSci’s API delivers fast and reliable integration and communication. Whether you’re sending appointment reminders, test results, preventative care communications, explanation of benefits (EoBs), or new product offers, your messages go out quickly and securely, with best-in-class email deliverability rates of 98% or more.

Designed for Compliance and Performance

LuxSci is HIPAA-compliant and HITRUST Certified, ensuring your healthcare communications stay within the bounds of regulatory compliance, keeping patient and company data secure—even as your email sending volume scales into the millions.

Authentication Gets a Major Upgrade

With the latest API release, LuxSci now supports three industry-standard authentication methods—alongside its proprietary LuxSci Secure option.

Let’s break them down:

OAuth 2.0 – The modern standard. Secure, flexible, and ideal for enterprise-scale integrations.
API Key – Simple and efficient. Ideal for server-to-server use when convenience matters most.
Basic Authentication – Straightforward and widely supported. Great for internal systems and quick testing.

Still Available and Highly Recommended: LuxSci Secure Authentication

For those who want the tightest possible control over API sessions—including HMAC signatures and session revocation—LuxSci Secure authentication remains the best option for customers.

Now, let’s take a closer look at how each of the new authentication methods work:

OAuth 2.0: A Standards-Based Approach

OAuth 2.0 gives you a robust framework to handle both account-level and user-level integrations.

Account-Level Authentication (Client Credentials Flow)

Perfect for system-level access—including EHR, CDP or RCM platform integrations where user context isn’t needed.

User-Level Authentication (Resource Owner Password Credentials Flow)

This method allows API access on behalf of individual users—great for patient portals or provider tools.

Security, Flexibility, and Simplicity Combined

Tokens expire after a default of 15 minutes, ensuring sessions aren’t left open indefinitely. Bonus: No message body signing is required, making integration quick and painless.

API Key: Simple and Straightforward

API Key authentication is as easy as including your credentials in a custom header. No session to manage, no extra handshake steps.

How It Works:

You send the HTTP header

X-API-Key: client_id:client_secret

With each request. That’s it.

Ideal Use Cases

Server-to-server automation
Internal dashboards
Data exports from analytics platforms

Basic Authentication: Familiar and Easy

Basic Auth is a time-tested option. Just Base64 encode your API credentials, include them in an HTTP header, and go.

While not as bulletproof as OAuth or LuxSci Secure, API Key and Basic Auth work fine for less sensitive data or development environments.

Easy Access to YAML Specs and SwaggerHub for API Testing

LuxSci has also published detailed YAML API specifications, making it easier for developers and IT teams to access testing interfaces.

You can find more information on our LuxSci API page.

Improved MFA and Easier Access to Testing Tools

As part of today’s announcement, LuxSci also rolled out new, smarter Multi-Factor Authentication (MFA) for enhanced web interface login protection.

LuxSci now ensures that each MFA code can be used only once. So, even if a hacker captures your password and MFA code, they are useless for conducting new login sessions. This update helps protect against automated phishing, spoofing, and fake login pages.

Why Healthcare Leaders Trust LuxSci

Best-In-Class Email Deliverability Rates of 98%

We don’t just send your emails—we get them delivered. Our 98%+ deliverability rate is among the highest in the industry, especially for sensitive healthcare data and communications.

HIPAA Compliance and HITRUST Certification

LuxSci checks every box when it comes to data privacy and protection. Trust your messages are safe, every step of the way.

Secure Communication at Scale

From a few thousand appointment reminders to millions of outbound secure emails—LuxSci scales with your business. Today, we work with some of the largest players in the healthcare industry, including Athenahealth, 1800 Contacts, US Healthconnect, Lucerna Health and Eurofins.

FAQs

Q1: What’s the most secure authentication method to use with LuxSci?

A: LuxSci Secure authentication offers the highest security with message signing and session revocation. For more information, visit our API Mechanics page.

Q2: Can I use OAuth 2.0 with user-level access?

A: Yes! Use the Resource Owner Password Credentials Flow (ROPC) to authenticate individual users.

Q3: Where can I find the SwaggerHub API testing tools?

A: LuxSci has published YAML specifications for SwaggerHub. Visit the LuxSci API page for more information.

Q4: How does LuxSci ensure HIPAA compliance in its API?

A: Through encryption, access controls, auditing, and industry certifications like HITRUST.

Erik Kangas

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

Get in touch

Find The Best Solution For Your Organization

Talk To An Expert & Get A Quote

First Name

Last Name

Work Email

Phone

Company

Type of Inquiry

Company Size

Message (optional)

Acceptance

I consent to be contacted by LuxSci for this inquiry and other relevant content, products, and services. You may unsubscribe from these communications at any time. We're committed to your privacy. For more information, check out our Privacy Policy.

A member of our staff will reach out to you

Search

Get Your Free E-Book!

LuxSci High Email Deliverability Best Practices Paper

What you’ll learn:

Is OCR Already Enforcing Email Encryption Under the New HIPAA Security Rule?

May 12, 2026
Pete Wermter

Healthcare organizations waiting for the final HIPAA Security Rule updates before improving email encryption and security may already be behind.

While the proposed changes to the HIPAA Security Rule are expected to be finalized in May, the direction from the U.S. Department of Health and Human Services Office for Civil Rights (OCR) is becoming increasingly clear. Across investigations, settlements, and enforcement actions, OCR continues emphasizing stronger technical safeguards, encryption, documented security programs, multi-factor authentication (MFA), risk analysis, and proactive cybersecurity operations.

For healthcare organizations, one area stands directly in the middle of all of these priorities: email.

Email remains a primary communication channel in healthcare — and one of the industry’s largest security vulnerabilities. From unauthorized PHI exposure to phishing attacks and ransomware delivery to account compromise, email continues to be at the center of healthcare cybersecurity incidents.

So, are the proposed HIPAA Security Rule changes hypothetical future guidance or a preview of OCR’s future enforcement expectations?

For healthcare email security, the implications are significant.

Email = Healthcare Cybersecurity Risk

Healthcare organizations rely on email for critical communications and healthcare workflows, including:

Patient communications
Care coordination
Claims and billing notifications
Marketing and engagement
Internal collaboration
Third-party vendor communications
Delivery of sensitive PHI

At the same time, attackers continue targeting email systems because they remain one of the easiest entry points into healthcare environments.

Insecure email workflows create unnecessary exposure of protected health information. Phishing campaigns are becoming more sophisticated. Credential theft attacks are bypassing traditional MFA methods. And business email compromise (BEC) attacks continue rising.

Recent OCR enforcement actions increasingly reflect these realities.

Organizations are being evaluated not simply on whether a breach occurred, but whether they implemented reasonable safeguards beforehand, including encryption, authentication controls, monitoring, access management, and documented risk mitigation processes.

For email systems specifically, that means healthcare organizations should expect increased scrutiny around:

Email encryption enforcement
MFA deployment
Audit logging and retention
Conditional access policies
Vendor security controls
Secure email delivery best practices
Segmentation and infrastructure isolation
Ongoing patch and vulnerability management

In many ways, email infrastructure is becoming a visible test of an organization’s overall cybersecurity posture.

Email Encryption Is Moving From Addressable to Required

Historically, healthcare organizations often interpreted HIPAA email encryption requirements with flexibility because encryption was technically categorized as an “addressable” safeguard under the Security Rule. But, OCR enforcement and broader cybersecurity realities are changing that interpretation rapidly.

Today, failing to encrypt sensitive healthcare communications increasingly creates both security and regulatory risk. The proposed Security Rule updates place even greater emphasis on encryption and technical safeguards. At the same time, OCR investigations continue examining whether organizations properly protected PHI in transit and at rest.

For healthcare email specifically, this creates several growing expectations:

Email encryption should be automated wherever possible
Human error should not determine whether PHI is protected
Organizations should maintain documented encryption policies
Secure delivery methods should adapt dynamically to recipient capabilities
Audit trails should demonstrate how messages were secured

At LuxSci, we have long believed that encryption should operate as a strategic layer of healthcare communications infrastructure, not as a manual user decision.

Our SecureLine email encryption technology automatically applies appropriate encryption methods based on organizational policies and delivery requirements, helping reduce the risks associated with human error while maintaining usability, deliverability and compliance. As enforcement expectations rise, this type of automated security enforcement is becoming increasingly important.

Traditional MFA May No Longer Be Enough

Another major shift emerging from both OCR enforcement trends and the proposed rule updates is the growing importance of stronger authentication models.

Healthcare organizations have historically viewed MFA deployment as sufficient protection. But attackers have adapted quickly.

MFA bypass attacks, token theft, session hijacking, and consent phishing campaigns are increasingly targeting healthcare users. As a result, regulators and cybersecurity experts are placing greater emphasis on phishing-resistant authentication approaches and contextual access controls.

For email environments, organizations should increasingly evaluate:

Whether MFA methods are resistant to phishing attacks
Conditional access policies based on device, location, and behavior
Account monitoring and anomaly detection
Administrative access protections
Session management controls
Logging and authentication auditing

The broader message is clear: healthcare organizations need authentication strategies designed for today’s threat landscape, not yesterday’s compliance checklist.

OCR Wants Proof, Not Just Policies

One of the clearest trends emerging from recent OCR activity is the increasing importance of documentation and operational evidence. Healthcare organizations must increasingly demonstrate not only that safeguards exist, but that they are consistently enforced, monitored, tested, and maintained over time.

For email systems, organizations should be prepared to demonstrate:

Email encryption policies
MFA enforcement records
Audit logs and message tracking
Vendor security documentation
Risk assessments involving email infrastructure
Patch management procedures
Employee security awareness training
Incident response procedures for email-based threats

This represents a broader shift in healthcare cybersecurity expectations.

The question is no longer: “Do you have email security controls?”

The question is increasingly: “Can you prove they are operationally effective?”

Healthcare Organizations Need a New Email Security Strategy

The healthcare industry is entering a new phase of cybersecurity enforcement.

OCR’s direction is becoming increasingly clear: organizations are expected to proactively secure systems handling PHI using modern, documented, and continuously maintained safeguards. For email security specifically, that means organizations should stop treating encryption, MFA, and secure communications as optional compliance requirements. Instead, they should view secure email infrastructure as a strategic component of enterprise cybersecurity and patient trust.

At LuxSci, we help healthcare organizations modernize secure communications with HIPAA compliant email infrastructure designed specifically for healthcare environments, including flexible encryption, secure delivery, auditability, high deliverability, access controls, and dedicated infrastructure options.

The proposed HIPAA Security Rule updates may not yet be final. But, OCR is already signaling where healthcare cybersecurity enforcement is headed next. For organizations relying on email to communicate with patients, members, customers, and partners, the time to examine your secure email infrastructure is now.

Connect with our experts to learn more using the form at the top of this page!

LuxSci Launches Enterprise-Grade HIPAA Compliant Email Security for Mid-Sized Healthcare Organizations

May 5, 2026
Pete Wermter

New right-sized offering brings advanced encryption, easy API integration, and HITRUST-certified compliance to the most underserved segment in healthcare email — with pricing starting at $99/month

CAMBRIDGE, MA — May 5, 2026 — LuxSci, a leading provider of HIPAA compliant secure healthcare communications, today announced the launch of LuxSci Secure High Volume Email for mid-sized healthcare organizations, the industry’s trusted HIPPA-compliant email solution now packaged and priced for mid-size healthcare organizations. Regional health systems, health plans, specialty group practices, urgent care networks, and multi-site regional providers can now access LuxSci’s enterprise-grade email security and encryption infrastructure at published, volume-based pricing — with no custom quote required.

LuxSci Secure High Volume Email for mid-sized healthcare organizations delivers the same HITRUST CSF r2-certified email security and flexible encryption capabilities that power communications for some of the largest healthcare organizations in the industry, including Athenahealth, 1-800 Contacts, Hinge Health and Eurofins. The new LuxSci mid-sized offer is tiered and priced for organizations with email sending volumes of between 300 and 99,000 emails per month.

LuxSci Secure High Volume Email is built on the company’s proprietary SecureLine™ encryption technology, which automatically selects the optimal email encryption method — TLS, secure portal fallback, PGP, or S/MIME — on a per-recipient basis at the time of delivery, with no action required from senders or recipients. This intelligent, adaptive encryption method goes significantly beyond TLS-only or portal fallback models offered by basic platforms, giving mid-market healthcare organizations the flexibility and cybersecurity depth they need as HIPAA regulations tighten and email threats continue to get more sophisticated.

Key capabilities include:

Automatic email encryption via SecureLine™ — encrypt every email and its content, including Protected Health Information (PHI), with per-recipient adaptive encryption across TLS, portal fallback, PGP, and S/MIME.
Advanced REST API with webhooks for dataflows into your systems — supports unlimited messages/hour with failover, queuing, plus webhooks can push email engagement data back to EHRs, CRMs, RCM and customer data platforms.
Comprehensive audit logging and reporting — message-level tracking, delivery status, engagement reporting, and downloadable reports for compliance officers.
HITRUST CSF r2 certification, BAA, GDPR-compliant, and US-EU Privacy Framework agreement all included.
Microsoft 365 and Google Workspace overlay — use LuxSci’s Secure Email Gateway add-on to integrate directly with existing M365 or Google Workspace environments, adding HIPAA-compliant encryption without migration or user retraining.
HIPAA-compliant patient engagement — secure outbound email campaigns with PHI-powered hyper-segmentation, automated workflows, and personalized emails for marketing campaigns, proactive patient communications, appointment reminders, care gap outreach, new plan enrollments, healthcare education, and more — with LuxSci Secure Marketing add-on.

New Published LuxSci Pricing

LuxSci Secure High Volume Emai for mid-sized healthcare organizations features published pricing based on monthly sending volume:

Monthly Send Volume	Monthly Price
300 to 9,999 emails/month	$99/month
10,000 – 29,999 emails/month	$199/month
30,000 – 49,999 emails/month	$299/month
50,000 – 99,999 emails/month	$399/month
100,000+ emails/month	Custom

“Mid-size healthcare organizations have been underserved for too long, forced to choose between inadequate email security tools that weren’t built for healthcare and HIPAA compliance and enterprise level solutions that felt too big or too complex,” said Mark Leanord, CEO of LuxSci. “Our new secure email packaging for mid-sized organizations changes that. We’re making the same encryption depth, ease of integration into EHRs, CRMs and other systems, and compliance rigor that powers our largest customers accessible for mid-sized organizations to easily evaluate and buy.”

Timing and Market Context

The launch comes at a critical moment for mid-size healthcare organizations. The HHS HIPAA Security Rule overhaul, expected to finalize in mid-2026, is anticipated to mandate email encryption as a required safeguard, elevating email security from addressable best practice to a regulatory requirement for thousands of organizations that have not yet upgraded their email security and compliance posture. LuxSci secure email is designed to meet these requirements, backed by HITRUST CSF r2 certification and the company’s 20-year track record in secure healthcare communications.

Availability

LuxSci Secure Email for mid-sized healthcare organizations is available immediately. Pricing and product details are published here.

Users can contact LuxSci to set up a call or DEMO.

About LuxSci

LuxSci is a leading provider of secure healthcare communications solutions for the healthcare industry. The company offers secure email, marketing, forms and hosting, delivering HIPAA‑compliant communication solutions that enable organizations to safely manage and transmit sensitive data, including protected health information (PHI). Founded in 1999 and recently merged with digital care and telehealth provider Ovia Health, LuxSci serves more than 2,000 customers across healthcare verticals, including providers, payers, suppliers, and healthcare retail, home care providers, and healthcare systems, as well as organizations operating in other highly regulated industries. LuxSci is HITRUST‑certified with current customers including Athenahealth, 1800 Contacts, Lucerna Health, Eurofins, and Rotech Healthcare, among others.

###

Media Contact:
Pete Wermter, CMO

pwermter@luxsci.com

Patient Engagement ROI: The Business Case for Secure Email in Healthcare

April 28, 2026
Pete Wermter

Every IT investment in healthcare today is being evaluated through a sharper lens.

Budgets are tighter. Expectations are higher. AI is the shiny object. Across healthcare organizations, leadership is asking the same question: how does this investment drive measurable results?

That’s where Patient Engagement ROI comes in, and where many traditional approaches fall short.

The Hidden Cost of Ineffective Communication

Patient engagement isn’t just a healthcare priority. It’s a financial one.

Missed appointments, gaps in care, and low response rates all translate directly into increased costs, operational inefficiencies, and a poor patient experience. Yet many organizations still rely on fragmented, manual, or non-personalized communication strategies.

Why?

For many, it’s because of uncertainty around HIPAA compliance, and what’s allowed and not allowed. Too often, healthcare IT and marketing teams avoid using valuable patient data to avoid security and compliance risks, especially over the email channel. The result is often generic outreach that fails to connect, and fails to deliver meaningful results, such as better health outcomes, fewer missed appointments, and increased sales.

How Secure Email Delivers ROI in Healthcare

Among all healthcare IT investments, secure email stands out for one reason: it directly impacts both patient engagement and staff and process efficiency.

With the right HIPAA-compliant marketing automation platform, secure email enables organizations to:

Deliver personalized, relevant messages using PHI data in their emails
Automate outreach at scale with triggered, engagement-driven campaigns
Improve patient response rates and adherence for better outcomes
Reduce manual workload across teams for greater productivity

This is where patient engagement ROI becomes tangible.

Instead of one-size-fits-all messaging, organizations can connect with patients based on unique needs and health conditions, such as appointments, care plans, preventative care reminders, new product needs, and more. And because it’s automated, these improvements scale without adding to workloads.

Turning Compliance into Better Outcomes and Growth

HIPAA is often viewed as a constraint. In reality, it’s an opportunity. If you have the right tools.

At LuxSci, we focus exclusively on secure healthcare communications, helping organizations safely unlock the value of their data and communications. Our solutions are designed to remove the friction between compliance and communication, so you don’t have to choose between security and growth.

With capabilities like flexible encryption, advanced segmentation, and high-volume delivery, secure email marketing becomes more than a safeguard, it becomes a growth driver.

And with industry-leading security performance and recognition, organizations can trust that their communications are protected at every level with LuxSci.

Scaling Patient Engagement ROI with Automation

The real power of secure email comes when it’s combined with automated healthcare workflows.

HIPAA compliant marketing automation allows you to build multi-step, data-driven patient journeys that run continuously in the background, taking adaptive steps based on each individual’s email engagement activity. This can include:

Appointment reminders that reduce no-shows
Follow-up communications that improve outcomes
Preventative care outreach for check-ups, annual test and care reminders
New product offers, upgrades and promotions
Educational email campaigns that drive long-term engagement and better health

Each interaction is an opportunity to improve both patient experience and your financial performance. Over time, these incremental gains compound, resulting in significantly higher patient engagement that delivers real value to your business.

Why Act Now?

Healthcare organizations can no longer afford IT investments that don’t deliver clear, measurable value. Secure email, powered by HIPAA compliant marketing automation, offers one of the most direct paths to improving engagement, efficiency, and outcomes, all while maintaining the highest standards of security.

Ready to see how LuxSci secure email can transform your patient engagement into real ROI?

Connect with us today or book a demo to explore how HITRUST-certified, HIPAA-compliant marketing automation can work for your organization.

What Is B2B Marketing in Healthcare?

April 27, 2026
Erik Kangas

B2B marketing in healthcare describes the promotion of products and services to healthcare businesses rather than to patients or the public. The audience can include provider groups, payers, laboratories, medical suppliers, health technology firms, and service companies working across the sector. The work calls for a more measured approach than many other business categories because buying decisions tend to involve several stakeholders, internal review, and close attention to data handling, workflow impact, and commercial fit. Good execution depends on clear communication, useful content, and a strong sense of how healthcare organizations evaluate change.

Why healthcare buying requires a different approach

Healthcare companies rarely move through a buying process in a straight line. One person may open the conversation, though several others can influence whether it goes any further. Finance may want a clearer commercial case. Operations may focus on staffing, efficiency, and implementation pressure. IT may look at access, system fit, and data management. Compliance teams may review privacy implications or contractual language. B2B marketing in healthcare works better when the writing reflects those realities early. Buyers are looking for material that helps them assess risk, discuss options internally, and move forward with fewer unanswered questions.

A Difference in stakeholder priorities

A single account can contain several audiences at once. That is part of what makes this area demanding. A hospital operations leader may care about throughput and day to day workflow. A payer executive may be more interested in administrative efficiency or review times. A supplier may focus on coordination, ordering processes, or communication across partner relationships. Content becomes stronger when it takes those different perspectives seriously. The message does not need to become overly technical. It needs enough accuracy and relevance for each reader to feel that the company understands the conditions attached to their role.

Why credibility matters in every channel

Healthcare buyers tend to read promotional material carefully. They notice vague claims, inflated language, and unsupported promises very quickly. That is why credibility has to be built into the writing itself. A clean explanation of a business problem can carry real weight. A grounded case example can help a reader picture how a solution would work in practice. Clear language around implementation, support, privacy, or service structure can also help keep the conversation moving. When protected health information enters the picture, HIPAA may become part of the review as well, especially for companies handling regulated data or supporting covered entities and business associates.

Content to support real decisions

The most useful assets in this space are the ones that help buyers think more clearly. An article can frame a problem in a way that supports internal discussion. An email sequence can keep a company visible while review is taking place. A service page can answer practical questions before a meeting is booked. B2B marketing in healthcare gains traction when content has a clear job and a clear reader. That focus usually produces stronger engagement than broad copy built around generic thought leadership language. Buyers respond well to material that respects their time and gives them something worth passing along.

What strong performance looks like

Success in healthcare is rarely captured by surface numbers alone. Traffic and opens may show that content has reached people, though those signals do not say much on their own about buying intent. Better indicators include repeat visits from the same organization, replies from relevant contacts, deeper engagement with security or implementation pages, and growing activity across several stakeholders in one account. Those patterns can tell commercial teams where interest is becoming more serious. B2B marketing in healthcare proves its value when it helps those teams follow up with better timing, better context, and material that fits the next stage of evaluation.

LuxSci vs. Paubox: How to Choose the Right HIPAA-Compliant Email Provider

January 29, 2025
LuxSci

Choosing the right HIPAA-compliant email vendor is crucial for protecting patient data and ensuring compliance with healthcare regulations, including verifying HIPAA compliance and security features, evaluating ease of use and integration capabilities, assessing deliverability and performance, and understanding pricing and scalability. You should also evaluate a vendor’s customer support and company reputation.

The Health Insurance Portability and Accountability Act (HIPAA) details strict guidelines for securing sensitive patient data, including Protected Health Information (PHI). As a result, healthcare providers, payers, and suppliers must use a HIPAA-compliant email provider to abide by regulations designed to safeguard PHI.

With this in mind, this post evaluates two of today’s most popular HIPAA-compliant email providers on the market: LuxSci and Paubox. We’ll compare the two HIPAA-compliant offerings on several criteria, helping you to decide which email provider best fits the needs of your organization.

LuxSci vs. Paubox: Evaluation Criteria

We will evaluate LuxSci vs. Paubox on the following criteria:

Data security and Compliance: how well each email provider safeguards PHI as per HIPAA’s requirements
Performance and Scalability: the platform’s ability to conduct bulk email marketing campaigns, and scale them as a company’s engagement efforts grow.
Infrastructure: if it provides the necessary technical infrastructure, processes and controls to both protect sensitive patient data and support high-volume email marketing campaigns.
Marketing Capabilities: if the platform provides tools for optimizing and refining your communication strategies.
Ease of Use: how steep the learning curve is for each platform.
Other HIPAA-Compliant Products: if the email provider offers complementary features that will aid your patient engagement efforts.

Now that we’ve explained the parameters by which we’ll be comparing the HIPAA compliant email providers, let’s see how LuxSci and Paubox stack up against each other.

LuxSci vs. Paubox: How They Compare

Data Security and Compliance

Both LuxSci and Paubox perform admirably here, with both being fully HIPAA-compliant email providers, offering automated encryption that allows you to include PHI in email communications straight away. Both providers secure email data both in transit and at rest.

Additionally, both are HITRUST certified, which further demonstrates a strong commitment to data privacy and security.

When compared to Paubox, LuxSci has the edge here because it has more comprehensive encryption options. This includes highly flexible encryption: automatically setting the ideal level of security and encryption needs based on the email content, recipient and business process.

Performance and Scalability

While both email providers deliver proven solutions and enable healthcare companies to scale their email marketing campaigns accordingly, LuxSci is the better option for high-volume email marketing campaigns, including bulk sending of hundreds of thousands to millions of emails per month. This is due to the fact that LuxSci specializes in assisting large healthcare organizations with executing high volume email marketing campaigns, including companies like Athenahealth, 1800 Contacts, Eurofins, and Rotech medical equipment. Consequently, LuxSci offers enterprise-grade scalability and has developed robust solutions capable of the high throughput required for enterprise-level patient and customer engagement efforts.

Infrastructure

Additionally, when it comes to other aspects related to infrastructure, LuxSci demonstrates an advantage. Firstly, they offer a dedicated, single tenant infrastructure, as well as secure email hosting, while Paubox does not. Additionally, though Paubox can provide additional options, such as high availability and disaster recovery, their capabilities may not as comprehensive as LuxSci.

Marketing capabilities

Both email delivery platforms possess useful marketing tools, enabling more effective HIPAA-compliant email marketing. This includes automation for streamlining email marketing campaigns and, customization options, so your messages are both more compelling and align with your company’s branding.

LuxSci offers comprehensive reporting capabilities, including real-time monitoring, detailed performance metrics (e.g., deliverability, open and click-through rates, bounced emails, spam complaints, and recipient domain reporting), as well as granular segmentation options.

Ease of use

Paubox has the edge here, being the easier of the two HIPAA-compliant email providers to deploy and for staff to get to ramp up on. Suited for more complex and sophisticated environments, LuxSci offsets this with exemplary customer support honed from decades of facilitating organizations’ HIPAA-compliant email marketing campaigns – especially for this on a large scale.

Other HIPAA-compliant Products

Lastly, when it comes to complementary features, both LuxSci and Paubox offer secure texting functionality, allowing healthcare companies to cater to their patients and customers who prefer to communicate via SMS. And while both email providers feature secure forms for HIPAA-compliant data collection, LuxSci’s forms are capable of handling complex workflows, including multi-step data collection, and providing better customization options.

Additionally, both provide capabilities for secure file sharing. LuxSci’s secure file sharing encrypts files at rest and in transit, allowing for granular access controls and helping ensure that only those within your company who must handle PHI have the appropriate access permissions. This is yet another safeguard against the exposure of PHI, whether accidentally, through identity theft (e.g., session-hijacking by a cybercriminal), or even corporate espionage.

Get Your Copy of LuxSci’s Vendor Comparison Guide

While this post focuses on comparing LuxSci and Paubox, we have created a complete Vendor Comparison Guide, which compares 12 email providers and is packed full of essential information on HIPAA-compliant communication and how to choose the best healthcare email solution for your organization.

You can grab your copy here, and don’t hesitate to contact us to explore your options for HIPAA-compliant email further.

What Are HIPAA Compliant Hosting Requirements?

June 2, 2025
Erik Kangas

HIPAA compliant hosting requirements include administrative policies for workforce training and access management, physical controls for data center security and equipment protection, and information protections for data encryption, access controls, and audit logging. Healthcare organizations using hosting services must ensure providers implement appropriate business associate agreements, security measures, and compliance documentation that meet Privacy and Security Rule obligations for protecting electronic PHI. Healthcare organizations increasingly rely on cloud hosting and managed services to support their operations while reducing internal IT infrastructure costs. Outsourcing hosting responsibilities does not eliminate HIPAA compliant hosting requirements, requiring careful vendor selection and ongoing oversight.

Administrative Protection Standards

Workforce training requirements mandate that hosting providers educate their personnel about HIPAA obligations and PHI handling procedures. All staff with potential access to healthcare client data must understand privacy requirements and security protocols before gaining system access. Access management procedures ensure that hosting provider personnel receive appropriate permissions based on their job responsibilities and healthcare client needs. Role-based access controls limit employee exposure to PHI while enabling necessary system administration and support activities. Security officer designation requires hosting providers to appoint qualified individuals responsible for developing and implementing security policies that protect healthcare client data. Officers must have appropriate authority and expertise to ensure comprehensive compliance across hosting operations.

Infrastructure & HIPAA Compliant Hosting Requirements

Data center security controls must protect servers and network equipment from unauthorized physical access through multiple layers of security including perimeter controls, biometric access systems, and surveillance monitoring. These protections help prevent unauthorized individuals from accessing systems containing PHI. Equipment disposal procedures ensure that storage devices and servers containing healthcare client data receive appropriate destruction when they reach end of life. Hosting providers must implement certified data destruction methods that prevent PHI recovery from disposed equipment. Environmental protections including fire suppression, climate control, and power management help ensure that healthcare client data remains available and protected from physical threats. Systems of this nature support business continuity while maintaining data integrity and accessibility.

Control Measures for HIPAA Compliant Hosting Requirements

User authentication systems verify the identity of individuals accessing hosting infrastructure before granting permissions to view or modify healthcare client data. Multi-factor authentication provides additional security layers for privileged access to systems containing PHI. Unique user identification ensures that hosting provider activities can be traced to specific individuals through comprehensive account management and monitoring systems. These controls support accountability and enable investigation of potential security incidents involving healthcare client data. Emergency access procedures provide alternative authentication methods when normal access controls might delay urgent system maintenance or security response activities. These procedures must include enhanced monitoring and documentation requirements to maintain security while enabling necessary operations.

Audit Controls and Activity Monitoring

Comprehensive logging systems capture detailed records of all activities affecting healthcare client data including user access, system modifications, and data transfers. These logs must be protected from unauthorized modification and preserved for appropriate periods to support compliance demonstrations. Regular log analysis helps hosting providers identify unusual activity patterns that might indicate security threats or compliance violations. Automated monitoring tools can detect suspicious behavior and alert security personnel to potential incidents requiring investigation. Audit trail preservation ensures that activity records remain available for compliance reviews and incident investigations throughout required retention periods. Hosting providers must maintain secure log storage while providing healthcare clients with access to relevant audit information.

Data Integrity and Transmission Security

Encryption implementation protects healthcare client data during storage and transmission through approved cryptographic methods and key management practices. Hosting providers must maintain current encryption standards while ensuring that decryption capabilities remain available for legitimate access needs. Data validation procedures verify that healthcare client information maintains accuracy and completeness throughout processing and storage activities. These procedures help detect unauthorized modifications or corruption that could compromise data integrity or patient care. Backup and recovery systems maintain additional copies of healthcare client data while preserving security protections and access controls. Frequent testing ensures that backup systems function properly and can restore data without compromising compliance requirements.

Network Security and Communication Controls

Firewall configuration creates secure network boundaries that control traffic between healthcare client systems and external networks. These controls help prevent unauthorized access while enabling necessary communication for healthcare operations and patient care. Intrusion detection systems monitor network traffic for potential security threats and unauthorized access attempts involving healthcare client data. Automated alerting helps hosting providers respond quickly to potential incidents while maintaining comprehensive security coverage. Secure communication channels protect data transmission between healthcare clients and hosting infrastructure through encrypted connections and authenticated access methods. These channels help ensure that PHI remains protected during transfer and remote access activities.

Business Associate Agreement Obligations

Contractual requirements establish hosting provider responsibilities for PHI protection including specific security measures, incident response procedures, and compliance monitoring activities. These agreements must address all applicable HIPAA compliant hosting requirements while defining clear performance expectations. Liability allocation between healthcare organizations and hosting providers depends on their respective roles in PHI protection and which party controls different aspects of data security. Clear contractual provisions help define responsibility for various compliance obligations and potential violations. Termination procedures address how healthcare client data is handled when hosting relationships end including data return, destruction, or transfer requirements.

Compliance Monitoring and Vendor Oversight

Risk assessment procedures help healthcare organizations evaluate hosting provider security practices and identify potential vulnerabilities that could compromise PHI protection. These assessments should be conducted regularly and documented to demonstrate due diligence in vendor oversight. Performance monitoring tracks hosting provider compliance with contractual obligations and HIPAA requirements through security audits, incident reviews, and service level assessments. Healthcare organizations must maintain ongoing oversight rather than relying solely on initial vendor evaluations. Documentation requirements ensure that hosting providers maintain records demonstrating their compliance efforts including policies, training materials, audit results, and incident reports. Well kept records support healthcare client compliance demonstrations and regulatory reviews when requested.

Are Replies to Encrypted Emails also Secure?

December 26, 2023
LuxSci

Sending HIPAA-compliant emails is easy when you use an encryption solution like LuxSci. But what happens when someone replies to an encrypted message? Are the replies also secure? This is primarily a concern when using SMTP TLS as a secure means of email delivery.

This article will explain how messages are sent securely, how replies behave, and whether they are secure and compliant. At the end, we provide some recommendations for how to balance security and usability.

(more…)

How to Secure SMTP Email Delivery with TLS

August 29, 2023
Erik Kangas

Secure email sending is a priority for organizations that communicate sensitive data externally. One of the most common ways to send secure emails is with SMTP TLS. TLS stands for Transport Layer Security and is the successor of SSL (Secure Socket Layer). TLS is one of the standard ways that computers on the internet transmit information over an encrypted channel. In general, when one computer connects to another computer and uses TLS, the following happens:

Computer A connects to Computer B (no security)
Computer B says “Hello” (no security)
Computer A says, “Let’s talk securely over TLS” (no security)
Computers A and B agree on how to do this (secure)
The rest of the conversation is encrypted (secure)

In particular:

The conversation is encrypted
Computer A can verify the identity of Computer B (by examining its SSL certificate, which is required for this dialog)
The conversation cannot be eavesdropped upon (without Computer A knowing)
A third party cannot modify the conversation
Third parties cannot inject other information into the conversation.

TLS and SSL help make the internet a more secure place. One popular way to use TLS is to secure SMTP to protect the transmission of email messages between servers.

Secure SMTP Email Delivery with TLS

The mechanism and language by which one email server transmits email messages to another email server is called Simple Mail Transport Protocol, or SMTP. For a long time, email servers have had the option of using TLS to transparently encrypt the message transmission from one server to another.

When available, using TLS with SMTP ensures the message contents are secured during transmission between the servers. Unfortunately, not all servers support TLS! Many email providers, especially free or public ones, have historically not supported TLS. Thankfully, the trend is shifting. LuxSci found that most providers now support TLS- approximately 85% of domains tested as of July 2022.

Using TLS requires that the server administrators:

purchase SSL certificates
configure the email servers to use them (and keep these configurations updated)
allocate additional computational resources on the email servers involved.

For TLS transmission to be used, the destination email server must offer support for TLS, and the sending computer or server must be configured to use TLS connections when possible.

The sending computer or server could be configured for:

No TLS: never use it.
Opportunistic TLS: use it if available; if not, send it insecurely.
Forced TLS: use TLS or do not deliver the email at all.

How Secure is Email Delivery over SMTP TLS?

TLS protects the transmission of the email message contents. It does nothing to protect the security of the message before it is sent or after it arrives at its destination. For that, other encryption mechanisms may be used, such as PGP, S/MIME, or storage in a secure portal.

For sending sensitive information to customers, transmission security is the minimum standard for compliance with healthcare and financial regulations. TLS is appropriate to meet most compliance requirements and offers an excellent alternative to more robust and less user-friendly encryption methods (like PGP and S/MIME).

There are different versions of TLS- 1.0 and 1.1 use older ciphers and are not as secure, while TLS 1.2 and 1.3 use newer ciphers and are more secure. When an email is sent, the level of TLS used is as secure as can be negotiated between the sending and receiving servers. If they both support strong encryption (like AES 256), then that will be used. If not, a weaker grade of encryption may be used. The sending and receiving servers can choose the types of encryption they will support. If there is no overlap in what they support, then TLS will fail (this is rare).

What About Replies to Secure Messages?

Let’s say you send a message to someone that is securely delivered to their inbox over TLS. Then, that person replies to you. Will that reply be secure? This may be important if you are communicating sensitive information. The reply will use TLS only if:

The recipient’s servers support TLS for outbound email (there is no way to test this externally).
The mail servers (where the “From” or “Reply” email address is hosted) support TLS for inbound email.
Both servers support overlapping TLS ciphers and protocols and can agree on a mutually acceptable means of encryption.

Unless familiar with the providers in question, it cannot be assumed that replies will use TLS. So, what should you do? Ultimately, it depends on what compliance standards you must meet, the level of risk you are willing to accept, and the types of communications you send. There are two general approaches to this question:

Conservative. If replies must be secure in all cases, assuming TLS will be used is unreasonable. In this case, a more secure method should be used to encrypt the messages in transit and store them upon arrival. The recipient must log in to a secure portal to view the message and reply securely. Alternatively, PGP or S/MIME could be used for additional security.
Aggressive. In some compliance situations like HIPAA, healthcare providers must ensure that ePHI is sent securely to patients. However, patients are not beholden to HIPAA and can send their information insecurely to anyone they want. If the patient’s reply is insecure, that could be okay. For these reasons, and because using TLS for email security is so easy, many do not worry about the security of email replies. However, this should be a risk factor you consider in an internal security audit. Consider nuanced policies that allow you to send less sensitive messages with TLS while sending more sensitive messages with higher security.

What are the Weaknesses of SMTP TLS?

As discussed, SMTP TLS has been around for a long time and has recently seen a great deal of adoption. However, it has some deficiencies compared to other types of email security:

There is no mandatory support for TLS in the email system.
A receiver’s support of the SMTP TLS option can be trivially removed by an active man-in-the-middle because TLS certificates are not actively verified.
Encryption is not used if any aspect of the TLS negotiation is undecipherable/garbled. It is very easy for a man-in-the-middle to inject garbage into the TLS handshake (which is done in clear text) and have the connection downgraded to plain text (opportunistic TLS) or have the connection fail (forced TLS).
Even when SMTP TLS is offered and accepted, the certificate presented during the TLS handshake is usually not checked to see if it is for the expected domain and unexpired. Most MTAs offer self-signed certificates as a pro forma. Thus, in many cases, one has an encrypted channel to an unauthenticated MTA, which can only prevent passive eavesdropping.

The Latest Updates to Secure SMTP TLS

Some solutions help remedy these issues—for example, SMTP Strict Transport Security. SMTP STS enables recipient servers to publish information about their SMTP TLS support in their DNS. This prevents man-in-the-middle downgrades to plain text delivery, ensures more robust TLS protocols are used, and can enable certificate validation.

In addition, users can adopt TLS 1.3. NIST recommends that government agencies develop migration plans to support TLS 1.3 by January 1, 2024. LuxSci supports both SMTP MTA-STS and TLS 1.3.

How Secure SMTP TLS Email Works with LuxSci

Inbound TLS

LuxSci’s inbound email servers support TLS for encrypted inbound email delivery from any sending email provider that also supports that. For selected organizations, LuxSci also locks down its servers to only accept email from them if delivered over TLS.

Outbound Opportunistic TLS

LuxSci’s outbound email servers will always use TLS with any server that claims to support it and with whom we can talk TLS v1.0+ using a strong cipher. The message will not be sent securely if the TLS connection to such a server fails (due to misconfiguration or no security protocols in common). Outbound opportunistic TLS encryption is automatic for all LuxSci customers, even those without SecureLine.

Forced TLS

When Forced TLS is enabled, the message is either dropped or sent with an alternate form of encryption if the recipient’s server does not support TLS. This ensures that messages will never be sent insecurely. Forced TLS is also in place for all LuxSci customers sending to banks and organizations that have requested that we globally enforce TLS to their servers.

Support for strong encryption

LuxSci’s servers will use the strongest encryption supported by the recipient’s email server. LuxSci servers will never employ an encryption cipher that uses less than 128 bits (they will fail to deliver rather than deliver via an excessively weak encryption cipher), and they will never use SSL v2 or SSL v3.

Does LuxSci Have Any Other Special TLS Features?

When using LuxSci SecureLine for outbound email encryption:

SMTP MTA STS: LuxSci’s domains support SMTP MTA STS, and LuxSci’s SecureLine encryption system leverages STS information about recipient domains to improve connection security.
Try TLS: Account administrators can have secure messages “try TLS first” and deliver that way. If TLS is unavailable, the messages would fall back and use more secure options like PGP, S/MIME, or Escrow. Email security is easy, seamless, and automatic when communicating internally or with others who support TLS.
TLS Exclusive: This is a special LuxSci-exclusive TLS sending feature. TLS Exclusive is just like Forced TLS, except that messages that can’t connect over TLS are just dropped. This is ideal for low-importance emails that must still be compliant, like email marketing messages in healthcare. In such cases, the ease of use of TLS is more important than receiving the message.
TLS Only Forwarding: Account administrators can restrict any server-side email forwarding settings in their accounts from allowing forwarding to any email addresses that do not support TLS for email delivery.
Encryption Escalation: Often, TLS is suitable for most messages, but some messages need to be encrypted using something stronger. LuxSci allows users to escalate the encryption from TLS to Escrow with a click (in WebMail) or by entering particular text in the subject line (for messages sent from email programs like Outlook).
Domain Monitoring: When TLS delivery is enabled for SecureLine accounts, messages will never be insecurely sent to domains that purport to be TLS-enabled, i.e., TLS delivery is enforced and no longer “opportunistic.” The system monitors these domains and updates their TLS-compliance status daily.
Double Encryption: Messages sent using SecureLine and PGP or S/MIME will still use Opportunistic TLS whenever possible for message delivery. In these cases, messages are often “double encrypted.” First, they are encrypted with PGP or S/MIME and may be encrypted again during transport using TLS.
No Weak TLS: Unlike many organizations, LuxSci’s TLS support for SMTP and other servers only supports those protocol levels (e.g., TLS v1.0+) and ciphers recommended by NIST for government communications and which are required for HIPAA. So, all communications with LuxSci servers will be over a compliant implementation of TLS.

For customers who can use TLS to meet security or compliance requirements, it enables seamless security and “use of email as usual.” SecureLine with Forced TLS enables clients to take advantage of this level of security whenever possible while automatically falling back to other methods when TLS is unavailable.

Of course, using Forced TLS as the sole method of encryption is optional; if your compliance needs are more substantial, you can turn off TLS-Only delivery or restrict it so that it is used only with specific recipients.

If your email use cases are complicated, LuxSci’s flexibility enables the secure sending of emails to any recipient, regardless of their email service provider’s support for TLS. Contact the LuxSci sales team to learn more about our secure SMTP TLS email sending.