🚧

The Messaging Service is currently in beta.

Messaging Service

Introduction

The ZapEHR Messaging Service provides HIPAA-compliant rails for building healthcare messaging workflows. The messaging service is integrated with the ZapEHR FHIR Service so that when you send SMS messages or create Conversations, they are automatically documented in the clinical record.

The Messaging Service has two components:

  • Transactional SMS — Send texts to patients and providers. These are typically appointment reminders, medication reminders, and other automated messages.
  • Conversations — Multi-channel HIPAA-compliant chat rooms. Conversations are a powerful way to build custom workflows that require real-time communication between providers and/or patients. For example, you might create a Conversation for providers using a webapp to discuss a patient's care plan. Or, you might create a Conversation where a provider messages with a patient through a web app, and the patient receives and responds to messages via SMS on their phone.

When to use Transactional SMS vs. Conversations

Transactional SMS is ideal for one-way automated text messages. It is more cost effective (opens in a new tab), and easier to use, since all it takes is one API call to send an SMS.

If you need two-way communications between two or more parties, then Conversations is the feature for you.

🚧  Beta Access

The ZapEHR Messaging Service is being used in production by ZapEHR customers. However, it is still in beta and we are actively working on improving the service. While the service is in beta, before you can use the Messaging Service, we need to enable it for your Project. Send us an email at [email protected] and we'll get you set up.

🚧

The Messaging Service does not yet support FHIR R5 (opens in a new tab).