" New Feature Announcements Archives - Page 5 of 18 - LuxSci

Archive for the ‘New Feature Announcements’ Category

The CMS Interoperability and Patient Access Final Rule

Tuesday, December 22nd, 2020

The Centers for Medicare and Medicaid Services (CMS) Interoperability and Patient Access Final Rule is a mouthful, but it’s also an important step for improving how health data is accessed and shared. While the rule may be beneficial in certain ways, it’s not without its risks. It opens up the door for patient data to be shared with third-party app developers outside of the tight confines of HIPAA regulations, which could lead to more breaches of sensitive data.

CMS Interoperability and Patient Access Final Rule

Read the rest of this post »

API Enhancements for DKIM Automation

Wednesday, December 2nd, 2020

DKIM, Domain Keys identified Mail, is a critical component to ensuring good INBOX delivery of email messages for day-to-day email, email marketing, and transactional email.  DKIM digitally signs outbound email so that the message recipients can verify that the messages originated from email servers authorized to send email from the sender.  I.e., it helps recipients identify and discard forged and fraudulent email messages while keeping legitimate ones.

API Enhancements for DKIM

In order to use DKIM with LuxSci, customers need to:

  1. Have LuxSci generate keys for each sending domain
  2. Update the DNS settings for each domain to publish the DKIM public key.

See LuxSci’s Help for our general DKIM setup instructions for more details.  These steps are pretty quick and easy, unless you have a large number of domains that you are sending email from.

To help such customers automate their workflow and manage their domains, LuxSci’s API has been augmented to enable management of DKIM keys for LuxSci customers.  The API now permits:

  1. Creation of new DKIM keys for new domains.
  2. Downloading the DKIM information needed for the DNS configuration.
  3. Deletion of DKIM keys for domains no longer in use.

Together with LuxSci’s other API endpoints, LuxSci customers can automate the addition and deletion of domains, email aliases, users, and now DKIM settings.  LuxSci is committed to continually expanding its API capabilities to enable and support automated workflows and processes.

Connect your Secure Forms to your Secure Marketing

Wednesday, November 11th, 2020

From a marketing and engagement perspective, an extremely common and revenue-driving workflow is to have the contact information of the people who fill out your online forms automatically added to your marketing database. This integration saves time by not requiring manual data entry steps and speeds up your marketing automation processes.

Secure Form to Secure Email Marketing Integration

This automated connection is now available for your LuxSci Secure Forms. After a license upgrade, they can now be automatically integrated with your LuxSci Secure Marketing platform. This integration enables new contacts to be automatically created in your Secure Marketing instance from selected Secure Form posts. You can then leverage Secure Marketing to send automated drip campaigns to these contacts, group mailings, and more.

Read the rest of this post »

CEO Erik Kangas Featured on Total HIPAA Podcasts

Thursday, July 16th, 2020

 

 

Erik recently sat down with our friends at Total HIPAA to discuss a variety of HIPAA topics, including:

The first of the 2-part conversation can be heard here or on a mobile device via Apple Podcasts.

 

 

Email Templates for SMTP and API Secure Email Sending

Wednesday, March 18th, 2020

Server-side email templates that can be utilized when sending email messages through LuxSci’s APIs and LuxSci’s SMTP services are now available.  In particular, users can:

  1. Create and manage up to 100 templates per user through LuxSci’s web site or via API commands.
    1. Templates can not only define the subject and bodies of the messages that use them, they can also control how these messages will be encrypted (or not).
  2. Send messages using templates via API commands or SMTP — so message content can be retrieved from the server-side templates rather than sent with every message
  3. Use dynamic place holders so the template content can be customized on a per-message basis (i.e., like “mail merge”).
  4. Send unique per-message attachments that will be attached to the template-derived messages.

That’s it — templates made simple.