Intro
In this example we're building a Heart failure care flow. Heart failure can be ongoing (chronic), or it may start suddenly (acute). When deciding on the care flow structure we need to keep in mind for who and when we start up a Heart failure care flow.
In this example, we'll include (who) all patients formally diagnosed with heart failure by a physician in the post-acute phase (when) upon date of diagnosis. Our care flow will allow to monitor the patient remotely and consequently perform care team intervention as necessary.
Step 1: define your care flow elements in time
Define your unique content and at which moment in your care flow timeline this needs to happen, i.e. against what time reference and in which order.
→ We define 4 individual tracks with unique content.
Track | Elements | Activation Timeline after care flow start (in sequence 👇 ) |
Program Intro + Heart Failure Symptom assessment | In-app messaging + Questionnaire | Day 1 |
Medication Compliance | Questionnaire | Day 2 |
Pain Assessment | Questionnaire | Day 4 |
Women’s Health | Questionnaire | Day 10 |
Step 2: define your repetitive components
Then define your repetitive components, these are your candidates to split off in a separate track and associate the right track triggers with.
→ You'll see we now split 'Program intro' from 'HF symptom assessment' to allow running the latter in a loop although both occur on Day 1. We introduce another track, we now have a care flow with 5 tracks.
Track | Activation Timeline | Frequency |
Program Intro | Day 1 | Once |
HF Symptom assessment | Day 1 | Daily |
Medication Compliance | Day 2 | Every 4 days |
Pain Assessment | Day 4 | Every 7 days |
Women’s Health | Day 10 | Once |
Step 3: build alerts & reminders
Account for "reality" by building out explicit alerts and reminders in case of urgency or inactivity.
→ In this example, to ensure high daily patient engagement we choose to not send email/SMS reminders but instead will go for high-touch and call the patient personally by a healthcare professional. We now have a care flow with 6 tracks.
Track | Activation Timeline | Frequency |
Program Intro | Day 1 | Once |
HF Symptom assessment | Day 1 | Daily |
Call from the Care team | Day 1 | Daily |
Medication Compliance | Day 2 | Every 4 days |
Pain Assessment | Day 4 | Every 7 days |
Women’s Health | Day 10 | Once |
Translating this structure to an Awell functioning flow
Creating a care flow that delivers on the requirements above may seem a daunting task, yet this is where Awell Studio shines in the ability to deliver flexible and complex care flows.
We define our amount and type of track triggers as depicted in the table below.
A word of explanation about the choices we make:
We install 2 track triggers when dealing with repetitive content
We set the first trigger to run the track initially at the right time
We set the second trigger to run upon completion of its own track (= loop)
We install timing delays that meet dual requirements, which is a) initial activation b) the loop frequency:
Medication compliance is presented on Day 2 initially (ref. "After a delay of 1 day")
Medication compliance is presented every 4 days consecutively (by defining the lag between step completion and track completion, ref. "After a delay of 3 days")
We install dependencies between tracks when we have a specific order
✔️ Heart failure symptom assessment could have started "When care flow starts", yet we deem it important the patient first receives the 'Program intro' before continuing with the symptom assessment
❌We want the care team to call the patient regardless of completing the HF symptom assessment and therefore do not install the dependency between these two tracks
Track | Activation Timeline + frequency | Amount of Track triggers | Track trigger |
Program Intro | Day 1 + Once | 1 | When Care flow starts |
HF Symptom assessment | Day 1 + Daily | 2 | When track 'Program Intro' is completed + When track 'HF symptom' is completed (= loop) |
Call from the Care team | Day 1 + Daily | 2 | When Care flow starts + When track 'Call from Care team' is completed (= loop) |
Medication Compliance | Day 2 + Every 4 days | 2 | When Care flow starts + When track 'Medication compliance' is completed (= loop) |
Pain Assessment | Day 4 + Every 7 days | 2 | When Care flow starts + When track 'Pain assessment' is completed (= loop) |
Women’s Health | Day 10 + Once | 1 | When Care flow starts |
Next steps in an integration context
You have now defined:
The trigger for Care flow start
The sequence of activities for each stakeholder
Depending on the integration of your choice and context of the care flow, you may still need to install the right activities to push and pull in data from/to the care flow:
Define the necessary business logic to run the sequence of activities
e.g. date of appointment
e.g. eligibility rules for signing up
Decide where the business logic resides for each activity
e.g. provide inputs along with Care flow start through baseline data points
e.g. provide inputs at runtime through form activities to halt Care flow progress and wait for the input to be available and passed on through the API
e.g. update baseline data points at run time