All Collections
Awell Studio
Best practices
Care flow design
Monolithic vs Modular care flow design
Monolithic vs Modular care flow design

Define your track level

Sanne Willekens avatar
Written by Sanne Willekens
Updated over a week ago

One of the questions we receive most often, related to care flow building, is how to best build out relationships between actions or what are meaningful ways to tie things together, how to split care flows into tracks or how to split your business into care flows.

When digging into your context, you will typically uncover a variety of use cases and ways things are currently done and appreciated - so the short answer is: it depends.

Yet, at Awell we Give and expect a lot - so we have a more elaborate answer in store for you based on our years of experience in care flow building.

Start small, launch early

One of the principles closest to our heart, is "Start small, launch early". Care flows are vehicles to drive continuous improvement of care processes. What you envision and design in Awell Studio, may not necessarily work in practice - when reality kicks in.

We therefore advice you to take incremental steps in delivering more care activities and expanding your care flows. You'll get to learn what works best for your organization and patients, and how you'd like to structurally improve your care flows.

Split your care flow into tracks by it's intended use

The heading πŸ‘† is quite a mouthful, yet we advise you to start by analyzing your care flow and define it's individual components by what they do and how they're used.

You'll avoid building a lot of repetition in your flow and steer away from a monolithic and hard to maintain design.

We recommend you to start modular by working out the functional pieces of your flow to then set the right tracks and track triggers:

  1. 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.

  2. Then define your repetitive components, these are your candidates to split off in a separate track and associate the right track triggers with

  3. Account for "reality" by building out explicit alerts and reminders in case of urgency or inactivity

Use case examples orchestrated with Awell

Did this answer your question?