LuxSci

LuxSci Welcomes Enterprise Software Executive Mark Leonard as New CEO

Mark Leonard LuxSci CEO

LuxSci is pleased to announce the appointment of Mark Leonard as CEO to fuel the company’s next phase of growth. Founder Erik Kangas continues as CTO to focus on product innovation and expansion.

Mark brings more than two decades of enterprise software experience to LuxSci, selling to both technical buyers and business users. He’s led sales, customer success and marketing teams at high-growth start-ups and scale-ups with a proven track record of success, including AI solution providers Cogito and Interactions, and insurance software provider Enservio. Mark’s unique executive leadership experience includes roles as Chief Revenue Officer, Executive Vice President of Customer Success and Chief Marketing Officer, bringing hands-on, real-world expertise in the full range of go-to-market activities to LuxSci.

“LuxSci has built an enterprise-class product and has established a leadership position in the market through sheer determination and an unmatched commitment to its customers’ success,” said Leonard. “I’m honored to join the team as we embark on LuxSci’s next phase of growth, and I want to especially thank founders Erik Kangas and Jeanne Fama, as well as Daan Visscher and the team over at Main Capital Partners, for this incredible opportunity.”

Mark Leonard LuxSci CEO

“It’s an exciting time! The addition of Mark to the LuxSci team marks an important milestone in the LuxSci journey, supporting our aspirations to be the leader in secure healthcare communications,” said Kangas. “We’re now positioned better than ever to understand our customers and the needs of the market to deliver solutions that make a real difference in today’s healthcare experience – from patients to providers, payers and suppliers.”

LuxSci in November received a majority investment from Main Capital Partners, one of Europe’s largest private equity firms. Main recently secured €2.44B in commitments for its latest fund, bringing its total assets under management to approximately €6B. With the financial strength and backing of Main, LuxSci has direct access to the firm’s market intelligence and performance excellence teams for data & research, best practices on go-to-market strategies, technology, financing and M&A – strongly positioning the company for continued innovation and future growth.

Today, LuxSci is used by nearly 2,000 customers for HIPAA-compliant email and marketing solutions across the healthcare industry, including Athena Health, 1800 Contacts, Delta Dental, Beth Israel Lahey Health, Hinge Health, and Rotech Healthcare.

Picture of LuxSci

LuxSci

Get in touch

Find The Best Solution For Your Organization

Talk To An Expert & Get A Quote




A member of our staff will reach out to you

Get Your Free E-Book!

LuxSci High Email Deliverability Best Practices Paper

What you’ll learn:

Related Posts

LuxSci G2 2026

LuxSci Earns 19 G2 Spring 2026 Badges

LuxSci continues its strong performance in the G2 Spring 2026 Reports, earning 19 badges that reflect real customer satisfaction and consistent product excellence across multiple areas, including email encryption, HIPAA compliant messaging, email security and email gateways.

G2: A Highly Reputable Peer Review Platformn

In a crowded software landscape, it’s easy for bold claims to blur together. That’s where G2 stands apart. Its rankings are based entirely on verified user feedback, giving buyers a clearer picture of how solutions actually perform in day-to-day use, not just how they’re marketed.

For Spring 2026, LuxSci earned recognition across multiple categories, including Leader, Best Customer Support, and Best ROI. Together, these awards show that LuxSci delivers leading technology and a best-in-class customer experience.

What the Badges Represent

Each G2 badge reflects direct input from customers using LuxSci in real-world environments. These evaluations cover usability, onboarding, support responsiveness, and long-term value. LuxSci’s Spring 2026 badges span leadership, customer satisfaction, ROI, and ease of implementation, demonstrating consistent strength across the full customer lifecycle.

Leader Badge: Market Leadership Validated

The Leader badge is awarded to companies with high customer satisfaction and strong market presence. LuxSci’s placement reflects reliable performance, strong security, and continued trust from organizations operating in highly regulated environments like healthcare.

Best Customer Support: A Standout Strength

In secure healthcare communications, timely and accurate support is essential. Issues must be resolved quickly to avoid operational or compliance risks. Customers consistently highlight LuxSci’s fast response times, deep expertise, and a hands-on approach, showing that our technology and our people deliver meaningful, real-world solutions.

Best ROI: Proven Business Value

ROI includes reduced compliance risk, improved efficiency, and scalable operations, not just cost. Customers report measurable benefits from LuxSci’s reliability, built-in compliance, and streamlined workflows, leading to strong long-term value and a solution that keeps you ahead of security and compliance risks.

What This Means for LuxSci Customers

These awards show LuxSci’s ability to serve organizations of varying sizes, from mid-market to enterprise. All reviews are from verified users, ensuring authenticity and transparency. Customers consistently mention reliability, security, and responsive support, along with overall peace of mind. The recognitions validate LuxSci’s ability to deliver secure, dependable communication solutions backed by strong support, including HIPAA compliant email, marketing and forms.

LuxSci’s 10 G2 Spring 2026 badges—including Leader, Best Customer Support, and Best ROI—demonstrate consistent excellence across performance, usability, and customer satisfaction. These results reinforce its position as a trusted provider in secure communications.

LuxSci MFA

Traditional MFA No Longer Qualifies as “Reasonable” Security

For years, multi-factor authentication (MFA) was considered one of the most effective ways to protect sensitive systems. By requiring a second verification step, such as a text message code or push notification, organizations could significantly reduce the risk of compromised passwords.

But the threat landscape has changed.

Today, attackers routinely bypass traditional MFA using techniques such as MFA evasion, token replay attacks, and consent phishing. These methods are no longer rare or highly sophisticated. They are widely used, automated, and increasingly effective.

As a result, regulators, auditors, and security frameworks are raising expectations for authentication security. For healthcare organizations in particular, traditional MFA alone may no longer satisfy the HIPAA requirement to implement “reasonable and appropriate safeguards.”

In the near future, email systems that rely only on basic MFA, without conditional access or phishing-resistant authentication, may increasingly be viewed as security gaps during risk assessments.

Why Traditional MFA Is No Longer Enough

Traditional MFA still improves security compared to passwords alone. However, many common MFA methods were designed before today’s phishing techniques and cloud authentication attacks became widespread.

Common MFA methods include:

  • SMS verification codes
  • Email-based authentication codes
  • Push notifications to mobile apps

While these mechanisms add friction for attackers, they can still be intercepted or manipulated during sophisticated phishing attacks. Because modern attackers now target authentication workflows directly, organizations relying solely on traditional MFA may be more vulnerable than they realize.

How Attackers Bypass MFA Today

Cybercriminals increasingly rely on tools that capture credentials and authentication tokens during login sessions. Three attack techniques are now especially common.

  • MFA Evasion and Phishing Proxies – Attackers frequently deploy adversary-in-the-middle phishing kits that sit between the user and the real login service. When users enter their credentials and MFA code on a phishing page, the attacker forwards the information to the legitimate site and captures the authentication session. The user successfully logs in—but the attacker gains access as well. If attackers capture those tokens, they can reuse them to access the account directly.
  • Token Replay Attacks – After successful authentication, systems typically issue session tokens that allow users to remain logged in without repeated MFA prompts. This technique has been widely observed in attacks targeting cloud email platforms such as Microsoft 365, allowing attackers to access email data even when MFA is enabled.
  • Consent Phishing – Consent phishing bypasses MFA entirely. Instead of stealing passwords, attackers trick users into granting permissions to malicious applications that request access to their mailbox or files. If users approve the request, the attacker’s application receives persistent access to the account through APIs—often without triggering security alerts.

Why Email Authentication Matters Most in Healthcare

Email remains one of the most critical systems in healthcare organizations. It supports patient communication, internal collaboration, and the exchange of sensitive information. Unfortunately, it is also the most frequently targeted entry point for cyberattacks.

Once attackers gain access to an email account, they can:

  • Impersonate healthcare staff
  • Launch internal phishing attacks
  • Access sensitive patient communications
  • Extract protected health information (PHI)

Because of this, email authentication controls are becoming a major focus for security teams and compliance auditors alike.

Evolving Regulatory Expectations

HIPAA does not prescribe specific technologies, but it requires organizations to implement safeguards that are “reasonable and appropriate” based on risk. As new attack methods emerge, the definition of reasonable security evolves.

Today, many security frameworks and regulatory bodies are emphasizing stronger identity protections, including:

  • Phishing-resistant authentication
  • Conditional access policies
  • Monitoring for suspicious login behavior
  • Controls for third-party application permissions

Organizations that rely solely on basic MFA may increasingly struggle to demonstrate that their authentication protections are sufficient.

The Shift Toward Phishing-Resistant Authentication

To address the weaknesses of traditional MFA, many organizations are adopting phishing-resistant authentication technologies, which can be enabled with tools like Duo and Okta. These solutions rely on cryptographic authentication tied to trusted devices, which prevents attackers from capturing or replaying login credentials.

Examples include:

  • Hardware security keys
  • Passkeys
  • Certificate-based authentication

Because authentication is tied to both the device and the legitimate website domain, these technologies significantly reduce the success rate of phishing attacks.

Why Conditional Access Is Becoming Essential

Conditional access adds another layer of protection by evaluating context and risk before granting access. Instead of treating every login the same, conditional access policies analyze signals such as:

  • Device security status
  • Geographic location
  • Network reputation
  • User behavior patterns

If something appears unusual, such as a login from a new country, the system can require stronger authentication or block the attempt altogether. This risk-based approach to authentication helps prevent many account compromise scenarios.

The Future of HIPAA Risk Assessments

As authentication threats evolve, healthcare security assessments are increasingly focusing on identity protection maturity. Organizations may begin seeing findings related to:

  • Weak or outdated MFA methods
  • Lack of conditional access policies
  • Insufficient monitoring of login activity
  • Unrestricted third-party application permissions

In particular, email systems without advanced authentication protections may be flagged as high-risk vulnerabilities, especially when PHI is accessible.

LuxSci’s Modern Approach to MFA

Modern threats require more than a simple second login factor. LuxSci approaches authentication security with layered identity protection designed specifically for healthcare environments.

Instead of relying solely on basic MFA methods like SMS codes or email verification, LuxSci supports stronger authentication controls and policies that align with evolving security expectations. These protections can include:

  • Strong multi-factor authentication options
  • Monitoring for unusual login behavior
  • Enhanced identity verification mechanisms

By combining multiple security layers within its HIPAA-compliant secure communications email and marketing solutions, LuxSci helps healthcare organizations protect sensitive email communications while maintaining usability for providers, health plan administrators, payment providers, and patient engagement teams.

Conclusion

Multi-factor authentication remains an important security control—but not all MFA is created equal. Attack techniques such as phishing proxies, token replay, and consent phishing have demonstrated that traditional MFA methods can be bypassed. As a result, regulators and auditors are increasingly expecting stronger identity protections.

For healthcare organizations that rely heavily on email communications, the implications are significant. Weak authentication controls can expose sensitive patient data and may soon appear as high-risk findings during HIPAA risk assessments. The organizations best positioned for the future will be those that modernize authentication strategies now, moving toward phishing-resistant methods, conditional access policies, and layered identity protection.

Reach out to LuxSci today to learn how HIPAA compliant email can support both your organization’s engagement and cybersecurity needs.


FAQs

1. What is traditional MFA?

Traditional MFA refers to authentication methods that require a second verification step, typically SMS codes, email codes, or push notifications.

2. Why can attackers bypass MFA today?

Modern phishing tools can intercept authentication sessions or steal login tokens, allowing attackers to access accounts even when MFA is enabled.

3. What is phishing-resistant authentication?

Phishing-resistant authentication uses cryptographic methods tied to trusted devices, preventing attackers from capturing login credentials.

4. Why is email security especially important for healthcare organizations?

Email systems often contain patient communications and sensitive information, making them a common target for cyberattacks.

5. How can organizations improve authentication security?

Organizations can strengthen identity security by adopting phishing-resistant authentication methods, implementing conditional access policies, and monitoring login activity.

LuxSci Automated Email Encryption

Encryption Optional Email Will Fail Audits in 2026 and Beyond

For years, healthcare organizations have relied on click-to-encrypt email workflows and secure portals as a practical compromise between usability and compliance. Or in some cases, they simply thought most of their emails did not need to be compliant. In regulated industries where data security and privacy are paramount, this approach was still considered “good enough.”

That era is ending.

As we progress into 2026 and beyond, regulators, auditors, and cyber insurers are sending a clear and consistent message: encryption that depends on human choice is no longer acceptable. It’s already happening. Encryption optional email isn’t merely raising concerns, it’s failing audits outright.

An Email Threat Landscape That’s Changing Faster Than Email Habits

Historically, email encryption was treated as a best practice rather than a hard requirement. If an organization could demonstrate that encryption tools existed and that employees had access to them, auditors were often satisfied. The box was checked, everybody moved on.

Today, the questions auditors ask are fundamentally different. Instead of asking whether encryption is available, they are asking whether sensitive data can ever leave the organization unencrypted. If the answer is yes, even in rare cases, or even accidentally, that’s no longer viewed as an acceptable gap. It’s viewed as inadequate control.

Why 2026 Is a Tipping Point for Email Security

Several forces are converging here in 2026 that make optional encryption increasingly untenable. Regulatory scrutiny around PHI and PII exposure continues to intensify. Breach costs and litigation are rising, with email remaining one of the most common vectors for data exposure and breaches. AI is also changing the game for cybercriminals, and attacks will continue to increase and be more sophisticated. As a result, cyber insurers are tightening underwriting requirements and demanding stronger, more predictable controls.

At the same time, email user behavior is unpredictable and inconsistent, which is a non-starter for data security in today’s world.

Taken together, these trends and behaviors point to a single requirement: email security controls must be automated. They must be enforced by systems, not dependent on employee memory, judgment, or good intentions.

The Reality of “Encryption Optional” in Practice

On paper, optional encryption can sound reasonable. In practice, it creates gaps large enough to open you up to a breach.

Secure portals are a good example. They require recipients to click a link, authenticate, and access content in a controlled environment. While this protects data in transit, and is a better approach than no security at all, it also introduces friction. And people don’t like friction. Senders forget to use the portal. Recipients ask for “just a quick email instead.” Shortcuts are taken to save time. And every shortcut becomes a risk.

Click-to-encrypt systems suffer from a similar problem. They rely on users to correctly identify sensitive data and remember to take action. But people often misclassify information, forget to click the button, or assume someone else has already secured the message. From an auditor’s perspective, this isn’t a training failure. It’s a set-up and control failure.

Email Security Defaults Are the New Normal

The latest message from regulators, auditors, and insurers is clear. If encryption is optional, data vulnerabilities become inevitable.

What can you do?

Below is a quick email security checklist to help you get started. Cyber insurers may require or recommend the following safeguards during the underwriting process, such as:

  • Multi-factor authentication (MFA)
  • Endpoint protection
  • Encrypted backups
  • Incident response planning
  • Encryption protocols for sensitive data in transit and at rest, including PHI in emails

In 2026 and beyond, healthcare organizations and regulated industries will be judged not by what they allow, but by what they prevent. Automated, encrypted email is the new. normal.

Want to learn more about LuxSci HIPAA compliant email? Reach out today.

LuxSci Oiva Health

LuxSci and Oiva Health Combine to Form Transatlantic Healthcare Communications Group

Boston & Helsinki, February 12, 2026 – LuxSci, a provider of secure healthcare communications solutions in the United States, and Oiva Health, a Nordic provider of Digital Care solutions in social and healthcare services, today announced that the companies are joining forces. Backed by Main Capital Partners (“Main”), the combination brings together two complementary platforms and teams, forming a strong transatlantic software group focused on secure healthcare communications.

Founded in 1999, LuxSci is a U.S. provider of HIPAA‑compliant, secure email, marketing, and forms solutions. Its application and infrastructure software enable organizations to securely deliver personalized, sensitive data at scale to support a broad range of healthcare communications and workflows including care coordination, benefits and payments, marketing, wellness communications, after care and ongoing care. Certified by HITRUST for the highest levels of data security, LuxSci serves dozens of healthcare enterprises and hundreds of mid‑market organizations.

Founded in 2010, Oiva Health is a provider of digital care and communications solutions in the Nordics. Headquartered in Finland, with additional offices in Denmark, Norway, and Sweden, Oiva Health offers digital care and digital clinic solutions – including digital visits, secure messaging, online scheduling and appointments, and caregiver communications – serving the long-term care, especially elderly care, and occupational healthcare verticals. The company employs approximately 60 people and has recently expanded across the Nordic region, with a growing presence in Norway and Sweden.

The combination of LuxSci and Oiva Health creates a larger, cross Atlantic group with complementary solutions, serving the U.S. and European markets. Together, the companies offer healthcare providers, payers, and suppliers a comprehensive suite of tools to communicate securely and compliantly, spanning communications, workflows, and virtual care delivery.

Daan Visscher, Partner and Co-Head North America at Main, commented: “We are pleased to announce this cross Atlantic transaction, creating an internationally active secure communications player within the healthcare and home care space. The combined product suite enables healthcare organizations to drive much needed efficiency gains in healthcare provision addressing a global trend of rising costs, aging population, and increasing pressure on resources needed to provide high-quality care.”

Mark Leonard, CEO of LuxSci, said, “We are thrilled to join forces with Oiva Health and believe that together we can truly make a difference in healthcare coordination, access, and delivery. We see an exciting path forward with our customers benefiting from an end-to-end, secure and compliant approach to optimizing both healthcare communications and today’s frontline workers, which we need now more than ever.”

Juhana Ojala, CEO at Oiva Health, concluded, “We look forward to this new chapter together with LuxSci. We are very excited about the strong alignment between our solutions, which especially strongly positions us to expand our flagship Digital Care offering to the high-potential U.S. care market – from care coordination to care delivery to in-home and institutional care.”

Nothing contained in this Press Release is intended to project, predict, guarantee, or forecast the future performance of any investment. This Press Release is for information purposes only and is not investment advice or an offer to buy or sell any securities or to invest in any funds or other investment vehicles managed by Main Capital Partners or any other person.

[END OF MESSAGE]

About LuxSci

LuxSci is a U.S.-based 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. Founded in 1999, LuxSci serves more than 1,900 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 example clients being Athenahealth, 1800 Contacts, Lucerna Health, Eurofins, and Rotech Healthcare, among others.

About Oiva Health

Oiva Health is a Digital Care provider in the Nordics, offering a comprehensive Digital Platform for integrated health and care services to digitalize primary healthcare, social care, hospital healthcare and long-term care services. The company was founded in 2010 and currently employs approximately 60 people in Finland, Denmark, Norway, and Sweden serving domestic municipalities, customers and partners, such as City of Helsinki, Keski-Suomi Welfare Region, Länsi-Uusimaa Welfare Region in Finland, and Viborg municipality in Denmark with its Digital Care platform. Annually over 5 million customer contacts are handled digitally through Oiva Health’s Digital Care and Digital Clinic platforms.  

About Main Capital Partners

Main Capital Partners is a software investor managing private equity funds active in the Benelux, DACH, the Nordics, France, and the United States with approximately EUR 7 billion in assets under management. Main has over 20 years of experience in strengthening software companies and works closely with the management teams across its portfolio as a strategic partner to achieve profitable growth and create larger outstanding software groups. Main has approximately 95 employees operating out of its offices in The Hague, Düsseldorf, Stockholm, Antwerp, Paris, and an affiliate office in Boston. Main maintains an active portfolio of over 50 software companies. The underlying portfolio employs approximately 15,000 employees. Through its Main Social Institute, Main supports students with grants and scholarships to study IT and Computer Science at Technical Universities and Universities of Applied Sciences.

The sender of this press release is Main Capital Partners.

For more information, please contact:

Main Capital Partners
Sophia Hengelbrok (PR & Communications Specialist)

sophia.hengelbrok@main.nl

+ 31 6 53 70 76 86

You Might Also Like

HIPAA Email Retention Policy

What Should a HIPAA Email Retention Policy Include?

A HIPAA email retention policy should include classification procedures for different email types, retention schedules based on content and legal requirements, secure storage and disposal methods, access controls for archived communications, and compliance monitoring procedures. The policy must address both HIPAA documentation requirements and broader legal obligations while providing clear guidance for staff implementation and ongoing management. Healthcare organizations need comprehensive retention policies that address complex regulatory landscapes without creating unnecessary administrative burden. Well-designed policies help ensure compliance while managing storage costs and supporting operational efficiency across the organization.

Email Classification and Categorization Guidelines

Content-based categories help staff identify appropriate retention periods by distinguishing between patient care communications, administrative messages, and marketing materials. Each category should have clear examples and decision criteria to ensure consistent application. PHI identification procedures enable staff to recognize when email communications contain protected health information requiring special handling and extended retention periods. These procedures should address obvious PHI like patient names as well as indirect identifiers that could reveal patient information. Business purpose classification distinguishes between emails supporting patient treatment, healthcare operations, payment activities, and other organizational functions. Different business purposes may trigger different retention requirements under various regulatory programs.

Retention Schedule Specifications

Minimum retention periods should reflect the longest applicable requirement from HIPAA email retention policy, state medical record laws, federal programs, and organizational needs. The policy should clearly state these periods for each email category and explain the basis for each requirement. Maximum retention limits help organizations manage storage costs and reduce litigation exposure by establishing when emails should be destroyed unless legal holds or other special circumstances require continued preservation. These limits should balance compliance needs with practical considerations. Exception procedures provide guidance for situations requiring deviation from standard retention schedules such as litigation holds, ongoing investigations, or patient access requests. These procedures should specify approval processes and documentation requirements for exceptions.

Storage and Archive Management Requirements

Security standards for archived emails must maintain the same level of PHI protection as active communications throughout the retention period. The policy should specify encryption requirements, access controls, and monitoring procedures for archived communications. Storage location specifications define where different types of email communications should be preserved including on-premises systems, cloud services, or hybrid approaches. These specifications should address data sovereignty, vendor requirements, and disaster recovery needs. Migration procedures ensure that archived emails remain accessible as technology systems change over time. The policy should address format preservation, system upgrades, and vendor transitions that could affect archived email accessibility.

Access Control and Retrieval Procedures

Authorization requirements define who can access archived email communications and under what circumstances. The policy should establish role-based permissions that limit access to personnel with legitimate business needs while maintaining audit trails. Search and retrieval protocols provide step-by-step procedures for locating archived emails during audits, legal discovery, or patient access requests. These protocols should specify search parameters, documentation requirements, and quality control measures. Emergency access procedures enable retrieval of archived communications during urgent situations when normal approval processes might delay patient care. These procedures should include alternative authorization methods and enhanced audit requirements.

Disposal and Destruction Standards

Secure deletion methods ensure that email content and metadata are completely removed when retention periods expire. The policy should specify approved destruction techniques that prevent unauthorized recovery of PHI from disposed communications. Certification requirements mandate documentation of email destruction activities including dates, methods used, and personnel responsible. These certifications support compliance demonstrations and help track disposal activities across the organization. Media destruction procedures address proper disposal of storage devices containing archived emails when equipment reaches end of life. A HIPAA email retention policy should specify physical destruction or certified wiping procedures that prevent PHI recovery.

Compliance Monitoring and Audit Support

Review schedules establish regular assessment of email retention practices to ensure continued compliance with policy requirements and changing regulations. These reviews should evaluate policy effectiveness, system performance, and staff compliance. Audit preparation procedures provide guidance for responding to regulatory reviews or legal discovery requests involving archived email communications. These procedures should include search protocols, production formats, and timeline management. Performance tracking helps organizations measure their success in meeting retention obligations while identifying areas needing improvement. Key metrics might include retention compliance rates, retrieval response times, and storage cost management.

Staff Training and Implementation Guidance

Training requirements specify education that personnel must receive about email retention obligations and their role in policy implementation. Training should cover classification procedures, retention schedules, and proper handling of archived communications. Implementation timelines provide realistic schedules for deploying new retention policies while allowing adequate time for staff training, system configuration, and process development. These timelines should consider organizational capacity and change management needs. Resource allocation addresses personnel, technology, and financial requirements for effective email retention policy implementation. The policy should specify roles and responsibilities while identifying budget needs for ongoing operations.

Legal and Regulatory Compliance Integration

Regulatory coordination ensures that a HIPAA email retention policy is adhered to, aligning with requirements from state laws, federal programs, and professional licensing boards. The policy should identify all applicable requirements and explain how conflicts are resolved. Legal hold procedures provide immediate preservation capabilities when litigation is anticipated or pending. These procedures should include notification processes, scope determination, and coordination with legal counsel to ensure comprehensive preservation. Update mechanisms ensure that retention policies remain current as regulations change or organizational needs evolve. A HIPAA email retention policy should specify review frequencies, approval processes, and communication procedures for policy modifications.

HIPAA Compliant Marketing

What Is HIPAA Compliant Marketing for Healthcare?

HIPAA compliant marketing for healthcare refers to promotional communications that follow HIPAA Privacy Rule requirements when using or disclosing protected health information (PHI). Healthcare organizations can conduct marketing activities while protecting patient privacy by obtaining proper authorizations, implementing security measures, and ensuring all marketing communications meet regulatory standards for PHI protection. Healthcare marketing has changed dramatically with digital communication channels, yet patient privacy remains paramount. Organizations must balance effective marketing strategies with strict compliance requirements to avoid violations that can result in hefty penalties and damaged reputations.

Understanding Marketing Under HIPAA Regulations

HIPAA defines marketing as communications that encourage recipients to purchase or use products or services, with certain exceptions for treatment communications and health care operations. The regulation distinguishes between communications that require patient authorization and those that fall under permitted uses without authorization. Face-to-face marketing communications between healthcare providers and patients do not require written authorization under HIPAA rules. Similarly, promotional gifts of nominal value given during these encounters are permitted without further consent. Most other marketing activities involving PHI require explicit patient authorization before implementation.

Healthcare organizations must understand when their communications cross from permissible patient care activities into regulated marketing territory. Educational materials about treatment options generally qualify as health care operations, while promotional emails about cosmetic procedures usually require marketing authorizations.

Authorization Requirements for Healthcare Marketing

Written authorization forms the foundation of HIPAA compliant marketing for healthcare organizations. Patients must provide explicit consent before their PHI can be used for marketing purposes, and these authorizations must meet specific regulatory requirements to remain valid. Authorization forms must clearly describe what PHI will be used or disclosed, the purpose of the marketing activity, and who will receive the information. The form must also explain that patients can revoke authorization at any time and that refusal to authorize marketing communications will not affect their treatment.

Healthcare organizations receiving financial remuneration for marketing activities face stricter authorization requirements. When third parties pay for marketing communications, authorization forms must disclose these financial relationships and explain how patient information will be shared with outside entities.

Permitted Marketing Activities Without Authorization

Certain healthcare communications that might appear to be marketing can proceed without patient authorization under HIPAA. These include communications about the covered entity’s own health-related products or services, or communications for treatment, case management, care coordination, or preventive health programs. For example, hospitals may send newsletters about their own diabetes management programs or wellness initiatives without obtaining individual authorization. However, if the communication involves financial payment from a third party to promote their products or services, patient authorization is required.

Case management and care coordination communications also receive authorization exemptions when they promote health or wellness activities. Healthcare organizations can recommend disease management programs, wellness initiatives, or preventive care services without obtaining separate marketing authorizations.

Technology Solutions for Compliant Email Marketing

Email marketing platforms designed for healthcare must incorporate security features that protect PHI during transmission and storage. These systems encrypt communications, maintain audit logs, and provide controls that help organizations manage patient authorizations and preferences. Segmentation capabilities allow healthcare marketers to target specific patient populations while maintaining privacy protections. Organizations can send diabetes education materials to patients with relevant diagnoses without exposing individual health conditions to unauthorized recipients.

Automated opt-out mechanisms help healthcare organizations respect patient preferences and maintain compliance with both HIPAA and CAN-SPAM requirements. These systems track authorization status and automatically exclude patients who revoke consent from future marketing communications.

Managing Patient Data in Marketing Campaigns

HIPAA compliant marketing for healthcare requires careful handling of patient data throughout campaign development and execution. Organizations must implement policies that limit PHI access to authorized personnel and document all data usage for compliance auditing.Marketing teams need training on HIPAA requirements and access controls that prevent unauthorized PHI disclosure. Role-based permissions ensure that only personnel with legitimate business needs can access patient information for marketing purposes.

Data retention policies must align with HIPAA requirements and organizational needs. Healthcare marketers should establish schedules for deleting PHI when it is no longer needed for marketing activities and maintain documentation of data destruction for compliance records.

Compliance Auditing and Risk Management

Regular compliance audits help healthcare organizations identify potential vulnerabilities in their marketing practices and address issues before they result in violations. These assessments should review authorization procedures, data handling practices, and technology security measures. Risk assessment processes must evaluate both internal marketing activities and third-party vendor relationships. Business associate agreements become necessary when outside marketing companies access PHI, and these contracts must include appropriate safeguards and liability provisions.

Documentation requirements include maintaining records diligently to demonstrate commitment to HIPAA compliant marketing for healthcare activities and their ability to respond appropriately to potential breaches or violations.

LuxSci Secure Email Reporting Statistics

New Reporting Features Go Deeper on Email Deliverability Statistics, Trends and Analysis

We recently rolled out new email reporting features, taking deliverability depth and analysis to new levels. If you’re a current LuxSci customer and haven’t checked them out, now’s the time. If you’re new to LuxSci, learn more below, and don’t hesitate to reach out for more info – or a demo.

LuxSci secure communications solutions have always featured rich reporting on email deliverability, including volumes and percentages for emails:

  • in queue
  • opened
  • clicked
  • failed
  • secured

With our latest release, we made these powerful statistics easier to consume and analyze with an improved user interface for more efficiency and greater ease-of-use. Users can simply select the type of report they’d like and customize it using a range of filtering selections. This is great for diving deeper into your email performance to make adjustments on-the-fly, and to spot trends or opportunities for better engagement that you may have missed before.

New UI – Email Deliverability Statistics

LuxSci Secure Email Reporting Statistics

Get more granular, ID trends in real time with Split Reporting

As part of this release, we are pleased to introduce our Split Reporting feature, which empowers users to drill down on email deliverability statistics across a range of parameters, including:

  • subject
  • from address
  • recipient domains
  • marketing ID or campaign
  • custom field

For example, users can analyze email deliverability statistics by subject to determine which ones are performing best, by use case to track results by campaign, or to track performance by recipient email domains. With split reporting, users also can analyze email volumes across queued, delivered, opened, failed and clicked parameters, and determine click-through rates (CTR) to measure effectiveness and ROI of campaigns.

New Feature Example – Split Reporting by Recipient Domain

LuxSci Secure Email Split Reporting

If you’d like to learn more, reach out and connect with us today!

 

HIPAA Compliant

Is Google Forms HIPAA Compliant?

Google Forms is not HIPAA compliant by default and cannot be used to collect protected health information (PHI) without additional measures. While Google Workspace can be configured for HIPAA compliance with a signed Business Associate Agreement (BAA), this agreement specifically excludes Google Forms from covered services. Healthcare organizations must use alternative form solutions designed for healthcare data collection to maintain HIPAA compliance.

Understanding HIPAA Requirements for Digital Forms

Digital forms used by healthcare organizations must meet specific security and privacy standards to comply with HIPAA regulations. Any platform collecting patient information needs encryption during transmission, access controls, audit logging, and secure data storage. Forms must include proper patient authorization language and maintain data confidentiality throughout processing. Google’s consumer products, including the standard version of Google Forms, lack many of these required security features. Healthcare providers who collect PHI through non-HIPAA compliant systems risk substantial penalties for HIPAA violations.

Google Workspace and Business Associate Agreements

Google offers a Business Associate Agreement (BAA) for its Google Workspace (formerly G Suite) business customers. This agreement establishes Google as a business associate under HIPAA and defines responsibilities for protecting healthcare information. However, Google explicitly excludes certain services from its BAA coverage, including Google Forms. The BAA typically covers Gmail, Google Calendar, Google Drive, and similar core services when properly configured. Healthcare organizations attempting to use Google Forms for PHI collection, even with a signed BAA, would violate their agreement terms and HIPAA regulations.

Security Limitations of Google Forms

Google Forms lacks several technical safeguards required for handling protected health information. The platform does not provide adequate access controls to limit form data visibility within organizations. Audit trail capabilities for tracking who has viewed or downloaded form responses do not meet HIPAA standards. While Google implements basic transport layer security, the form data storage and transmission methods were not designed for highly regulated healthcare information. The platform also lacks features for obtaining and documenting patient authorization as required under the HIPAA Privacy Rule.

Alternative HIPAA Compliant Form Solutions

Healthcare organizations have various compliant alternatives for collecting patient information electronically. Purpose-built healthcare form platforms include advanced security features like end-to-end encryption, detailed access logging, and healthcare-specific authorizations. These specialized systems integrate with electronic health records and secure messaging systems while maintaining compliance. Many vendors provide HIPAA compliant form solutions with documentation templates for common healthcare scenarios. Organizations can evaluate these alternatives based on factors like cost, ease of use, integration capabilities, and compliance certification.

Implementation Requirements for Compliant Forms

Regardless of the chosen platform, healthcare organizations must implement specific procedures when collecting patient information through electronic forms. Staff training on handling form data securely plays a crucial role in maintaining compliance. Organizations need documented policies for form creation, approval processes, and data retention schedules. Form systems require regular security assessments and updates to address emerging vulnerabilities. Compliance officers should review all form collection processes to ensure they meet current HIPAA requirements and organizational security standards.

Common Misunderstandings About Google Services and HIPAA

Many healthcare organizations misinterpret Google’s BAA coverage, incorrectly assuming all Google services become HIPAA compliant with a signed agreement. This misunderstanding leads to compliance violations when organizations use excluded services like Google Forms for patient information. Another common error involves using personal Google accounts rather than properly configured Google Workspace accounts with appropriate security settings. Organizations sometimes fail to recognize that collecting even basic patient information through non-compliant systems violates HIPAA when that information qualifies as protected health information under the regulations