Skip to main content

Triggers

There are six different types of event triggers.

Manual​

A "Manual" event trigger requires a Platform Admin to actively initiate and run the trigger when needed, as it does not operate automatically based on predefined events or conditions.

Scheduled (Recurring)​

A "Scheduled (Recurring)" event trigger is designed to operate on a predefined schedule. Users can select an interval for the event to run automatically at regular intervals without the need for manual initiation. This allows for automated and consistent execution of the trigger based on the chosen schedule.

Recurring triggers include:

  • Timing presets for common schedules
  • Timezone selection (defaults to America/New_York)
  • Resource to Process: choose between the event resource, a Report, or a Segment
  • Send to each patient only once option, so patients who already started the sequence are skipped on later runs

Scheduled (One-Time)​

A "Scheduled (One-Time)" event trigger runs once at a specific date and time. Like recurring triggers, it supports timezone selection and a report or segment audience.

Resource Creation​

A "Resource Creation" event trigger is activated when a new resource is generated or created within the system. This trigger is often configured to respond to the creation of either an observation or a patient.

Within this event trigger, various types of actions are available to be associated with it. In certain cases, it may be advisable to consult with the CareLaunch team to determine the most suitable and effective action to pair with this trigger. Their expertise can help in identifying the best course of action to align with your specific requirements and objectives.

Observation source and value conditions are configured using Event Filter nodes after the trigger, not inside the trigger configuration itself.

Trigger types

Resource Update​

A "Resource Update" event functions in a manner similar to a "Resource Creation" event, with the key distinction being that it triggers when a resource is modified or updated rather than when it is initially created. This event is designed to respond to changes made to existing resources within the system, providing a way to monitor and trigger actions based on updates, ensuring your processes remain synchronized with the latest data.

Trigger types

Resource Delete​

This event is configured to detect when a resource is deleted within the system. It is specifically designed to identify instances when resources are removed or no longer available, providing valuable monitoring and action-triggering capabilities for deletion events.