All Collections
Awell Studio
Awell Platform terminology
Awell Platform terminology

A word of explanation about our lingo

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

Healthcare is complex. We work hard to make complex things simpler. Our language is one of simplicity and unambiguity. In case we dropped the ball or you'd like to hear our interpretation, read our vocabulary to be on par.



Care flow

Care flows in Awell are represented by a set of activities to be performed by the care team and/or the patient to achieve or maintain a desired health state for that patient.

In Awell a care flow consists of the following 4 levels represented top down πŸ‘‡

  • Care flow

  • Track(s)

  • Step(s)

  • Action(s)

Care flows go by many different names, we describe it pretty well over here.


Tracks should be considered as phases of a care flow that can run either sequentially (Diagnosis > Treatment > Follow-up) or in parallel (Daily metrics vs. Monthly appointments).

The amount of tracks and triggers you need depend on your requirements and context such as repetitive components, long-lived care flows, multi-purpose flows, ... Head over to this section to read up on the example use cases.


Steps are presented as containers that hold all actions (forms, messages ...) that happen at a given moment for a given patient group.

Once all of the actions are completed, the orchestration engine will progress to the next step (container) in the care flow.


Actions are the individual elements of a step, that a user interacts with such as forms, messages, ... or system actions that are auto-completed during orchestration such as Calculations, API calls, ...

Actions related to data inputs such as forms, checklists are considered blocking actions.

Data point

Data points are generated throughout the lifespan of a care flow and are related to inputs captured from stakeholders and external systems (e.g. forms, baseline data points, API calls) as well as system generated data (e.g. calculations, step activation/completion times). These data points are available to configure if-this-then-that logic (IFTTT) i.e. set conditions and triggers on transitions & tracks.

The full list of data points, registered in your care flow, is available in the Data catalog tab.

Dynamic Data Variable

Variables are dynamic textual representations, which can be generated from the individual data points captured in the care flow.

Variables can be added via the "/" command in all text editors like messages, API calls, ... and enrich your communication + transfer the information to external systems.

e.g. Hello {Patient_first_name}

e.g. Treatment: {Treatment_selection}


The Preview helps you validate a care flow, by walking through its care delivery activities between care flow to start and end. Its a simulation of the design where you travel through time and can validate the sequence of events and stakeholders part of the full journey.


Via Cases you can simulate the care flow behavior for the different scenario's part of the design. You can validate the work for each care flow branch/condition/patient group to confirm it meets the intended expectations.

Activity feed

The activity feed delivers a chronological log of activities (i.e. message, form, calculation ...) which get orchestrated according to the design in Awell Studio. This feed includes timing delays (based on reference dates e.g. consultation date) and applying if-this-then-that logic (e.g. patient's condition) to create a personalized care flow which you can interact with.

API call

An API, or Application Programming Interface, is a collection of protocols and structures that facilitates communication between two systems. In Awell Studio you can send and fetch data from external systems using the API call action.

Outgoing webhooks

These webhooks are managed on care flow level and allow you to be notified of real-time events happening in the care flow at the defined endpoint of your choice.

You can subscribe to one or multiple events with one webhook.

Incoming webhooks

These webhooks are managed on either extension level associated with a specific 3rd party and care flow, or on organizational level, and trigger the start of a care flow.

Constant Data Variable

Constants are static values defined and managed at care flow level just once, to then re-use in the correct steps and fields of API calls (e.g. URLs, API keys)


A means to capture question and answers from stakeholders. Survey's, questionnaires and feedback forms are collectively called 'Forms' and supported through the Form action.

Visibility logic

You can branch within a form by making use of earlier provided answers. Handle the set of relevant questions per patient group, by toggling on the Visibility logic and setting the right conditions.


Q1: "Biological sex" - present to all

Q2: "Are you pregnant" - present if Q1 = Female

Question library

You can import questions in your form from our library of validated questionnaires. Out-of-the-box, these questionnaires are compatible with their corresponding calculation and are the quickest way to get started with a validated questionnaire & score calculation.

When you have a form created in another tool, you can import this form which you created elsewhere into an Awell form in just a few clicks through a JSON import.


The act of executing a care flow design. After publishing a care flow, you start enrolling patients. From that point onwards, Awell orchestrates all activities for all stakeholders and systems according to its design.


These are all the participants involved in your care flow.

We support a fixed list of stakeholders and recipients. If we missed an important care actor - let us know via the blue chat button at the bottom right of your screen.

Did this answer your question?