Every Automation is built from three building blocks: a Trigger (the event that starts it), optional Conditions (rules that must be met), and one or more Actions (what happens as a result). Understanding each piece helps you build Automations that run exactly when and how you need them.
Triggers
A Trigger is the event that kicks off an Automation. Every Automation must have exactly one Trigger.
Available Triggers
Patient Check In fires when a patient is checked in for a visit
Patient Check Out fires when a patient is checked out of a visit
Completed Treatment fires when a treatment is added and then marked complete (treatments left incomplete will not trigger this)
Dispensed Prescription fires when a prescription is dispensed
Note: Only one Trigger can be used per Automation. If you need to act on multiple events, create a separate Automation for each. |
Conditions
Conditions are optional rules that must all be met before the Action fires. You can add multiple Conditions to a single Automation—if you do, every Condition must be satisfied. Conditions are grouped into three categories.
Patient Conditions
Patient Alert — include or exclude patients who have a specific Patient Alert (e.g., Caution, Aggressive). Multiple alerts can be selected.
Deceased Status — include or exclude patients marked as deceased.
PIMS ID — match or exclude a specific patient by their exact PIMS ID. One ID per Condition; partial IDs are not accepted.
Product Conditions
Invoice Tags — include or exclude products with a specific Invoice Tag (e.g., Surgery). Multiple tags can be selected.
Name — include or exclude products whose name contains or does not contain specific text. This field is case sensitive.
PIMS ID — match or exclude a specific product by its exact PIMS ID. One ID per Condition.
Visit Conditions
Alerts — include or exclude visits where the patient has a specific Visit Alert (e.g., a Belongings note). Multiple alerts can be selected.
Reason — include or exclude visits whose Reason for Visit contains specific text. This field is case sensitive.
Service — include or exclude visits tied to a specific Service (e.g., Neurology). One Service per Condition.
Status — include or exclude patients who were placed on a specific Status Board (Outpatient, Inpatient, Boarding, or OTW) during the visit.
Note: Not all Conditions are available for every Trigger. Visit Conditions cannot be used with a Dispensed Prescription trigger, and Product Conditions cannot be used with Patient Check In or Check Out triggers. |
Actions
Actions are what the Automation does once a Trigger fires (and any Conditions are met). You can add multiple Actions to a single Automation.
Available Actions
Send Comm Log Message — creates a Comm Log entry and sends an email to the Primary Contact and/or Referrers. The subject and message are fully customizable and support snippets. Requires a valid email address on the client's account.
Send Comm Log with Handouts — emails the Primary Contact with PDF drug handouts attached for a dispensed prescription. All handouts linked to the prescription's monograph are included. The subject and message are customizable and support snippets. This action sends to the Primary Contact only.
Create Task — creates and assigns a task to a specific user or group. An optional Due Duration field sets when the task is due (in hours) after the Automation fires.
Create Document from Template — generates a document from a template. If the Automation is tied to a visit, the document is added to that visit; otherwise, it is added to the patient's chart in the Non-Visit section.
Tip: Conditions are entirely optional. A simple Trigger → Action Automation with no Conditions will fire for every instance of that Trigger—useful for broad, catch-all workflows. |
Frequently asked questions
Can I add more than one Condition to an Automation?
Yes. You can add multiple Conditions, but all of them must be met for the Action to fire. For example, if you add a Reason for Visit condition of "Surgery" and a Patient Alert condition of "Aggressive," the Automation will only run for aggressive surgery patients—not one or the other.
Are the Name and Reason fields case sensitive?
Yes. The Product Name and Reason for Visit Condition fields are case sensitive. Make sure the text you enter matches exactly what appears in the app (for example, "In-House" vs. "In-house" will produce different results).
Can I use Visit Conditions with a Dispensed Prescription trigger?
No. Visit Conditions are only available for Triggers that are visit-based (Patient Check In, Check Out, and Completed Treatment). Similarly, Product Conditions are not available for Patient Check In or Check Out triggers.
Can I use the Send Comm Log action if a client doesn’t have an email address on file?
No. The Send Comm Log Message action requires a valid email address on the client’s account. If no email is on file, the Automation will not be able to deliver the message.
What happens if I add multiple Actions?
All Actions in an Automation will fire when the Trigger (and any Conditions) are met. For example, you could send a Comm Log message and create a follow-up Task at the same time.
Submit feedback
Have ideas about Automations? In the in-app chat, select Ask a Question → I Have a Product Idea. All feedback goes directly to the Product and Engineering teams.
Still need help?
Contact support via live chat or email: [email protected].