Skip to content

Latest commit

 

History

History
29 lines (17 loc) · 1.62 KB

overview-trigger-care-flows.mdx

File metadata and controls

29 lines (17 loc) · 1.62 KB
title description
Overview
Learn about the various ways to trigger care flows in Awell

Keep in mind that you are not restricted to using just one type of trigger. Each trigger is designed for specific use cases, so you can use a variety of triggers for your care flows in Awell.

Prerequisites

Regardless of the method used to trigger care flows in Awell, there are two fundamental principles to keep in mind.

Create a patient first

In Awell, each care flow is linked to a patient. This means a patient needs to be created before starting a care flow. However, Awell’s system is flexible in the data you need to provide for patients; we can even support anonymous patients (no PHI).

We do recommend populating the patient_code field in the patient profile. The value you input here is your internal ID for the patient, which facilitates matching a patient in Awell with one in your system.

Data required at care flow start

It’s important to consider what data will be needed to start a care flow. There are two categories of data to consider:

  1. Data about the patient (see above)
  2. Data needed for the care flow logic: this includes information essential for assessing conditions and determining timings within the care flow. For instance, in pre-surgery care flows, usually the type and date of surgery is provided. These data points are then utilized within the care flow's configuration to ensure timely message delivery and relevant surgery information.

Comparing trigger types

You can learn more about each trigger type on their corresponding pages (see "Trigger types").