← All updates
Build automation rules without code, then test them before they run
The problem it solves
Assigning the right content to the right patient at the right moment was manual work, or a bespoke engineering project per practice. Clinics wanted rules they could own: when this appointment type is booked for this doctor, send these forms. And when a rule didn't fire, nobody could say why without an engineer running a database query.
What's included
- A rules engine. Rules match incoming events (appointments, referrals, questionnaire answers, new patients) against conditions and assign Learn, Actions, forms or questionnaires.
- Rules you can edit. Create, change and remove rules in the tooling without engineering help.
- Compound conditions. Combine conditions with AND logic, and use "does not contain" to keep a procedure name from triggering the wrong automation.
- No duplicate assignments. A rule can check whether the task is already on the patient's current episode before assigning it again.
- Test before going live. Run a rule against real data to see what it would have matched, so it's neither too broad nor too narrow.
- See why a patient was or wasn't assigned. Patient-level automation events and a diagnostic tool answer the support question in minutes, not days.