Orchestration ontology

Design ontology

Before diving into the Orchestration ontology, we recommend reading our Design ontology to learn more about how care flows are structured when designing them in Awell Studio.

Orchestration ontology

When a care flow is orchestrated, it is translated to a set of activities. So when an action is activated, an activity is created in the Awell System to keep track of its start date, status, completion date, etc. The activity stores a reference to the action, step, and track so we know at all times what action needs to be completed as part of what activity and in what context the activity is created.

We use the concept of activities because, depending on how your care flow is structured, a track or step (and thus the actions in it) might be activated more than once.

Please note that an orchestrated care flow does not only consist of activities related to actions but that there are many other (system) activities as well (eg: track activation/completion, step activation/completion, reminders, ...). You can thus look at activities as a full history log of what has happened in a pathway.

Activities and data points

Where tracks and triggers, steps and transitions, and actions were the main building blocks when designing care flows, the main elements you will engage with when Orchestrating care flows are activities and data points.