Lead Source and Conditions
The node that decides who enters the workflow, and the node that branches on a patient attribute
Two nodes make decisions without an agent. The Lead Source decides whether a patient enters the workflow at all. The condition node reads one or two patient attributes and sends the patient one way or the other.
Lead Source
The Lead Source is the workflow's front door. Every workflow needs one, placed first on the canvas. Its rules say which patients enter: a patient is let in only when the source recorded on them equals the Source of one of the rules.
Field | Meaning | Constraint |
|---|---|---|
Rule Name | A label for the rule; it names the rule's output on the canvas | Up to 24 characters |
Source | The patient source the rule accepts, picked from your source list or typed | Typed sources are stored in capitals |
Add Assignment Rule | Adds another rule; each rule accepts one source | One rule exists by default; a delete icon appears on each once there are two |
How the rule is applied:
- The comparison ignores letter case: a patient with source "direct" enters a rule whose Source is DIRECT.
- Any rule may match; a patient needs to match one, not all.
- A patient whose source matches no rule is not entered, whatever triggered the workflow (see Bringing Patients In). Nothing tells the agent; the patient simply does not appear on the board.
- The node shows one output per named rule. Connect your first stage from it and mark that stage as the start node; a new patient always begins at the start node.
Example: patients added at the front desk carry the source DASHBOARD, patients from your website carry WEBSITE. Two rules, "Front desk" with DASHBOARD and "Website" with WEBSITE, let both groups in; a patient imported with the source CAMPAIGN stays out until you add a rule for it.
Set a Condition
The condition node compares a patient attribute with a value and takes the green output when the comparison holds, the red output when it does not.
Field | Meaning | Constraint |
|---|---|---|
Attribute | The patient attribute to test, from the attribute picker | Required for the branch to be evaluated |
Operator | How to compare it | One of the twelve below |
Value | What to compare with; hidden for Is Empty and Is Not Empty | Free text; numbers are compared as numbers |
+ Add Condition | Adds a second condition, joined by AND or OR | At most two conditions; Delete Condition removes the second |
Operators
Operator | The branch holds when |
|---|---|
Greater Than, Less Than | The attribute is above, or below, the value |
Greater Than or Equal To, Less Than or Equal To | The same, allowing equality |
Equal To, Not Equal To | The attribute is, or is not, exactly the value |
Contains, Does Not Contain | The value appears, or does not appear, inside the attribute |
Starts With, Ends With | The attribute begins, or ends, with the value |
Is Empty, Is Not Empty | The attribute has no value, or has one |
- Text comparisons ignore letter case. An attribute that holds a number in text form is compared as a number.
- With two conditions, AND takes the green output only when both hold; OR takes it when either holds. The toggle sits on the second condition and starts at AND.
- A comparison that cannot be evaluated, for example an attribute the patient does not have, takes the red output.
Outputs
Output | Meaning |
|---|---|
Green-bordered | The condition holds |
Red-bordered | It does not hold, or could not be evaluated |
Connect both. A missing connection on the branch that fires ends the workflow for that patient.
Example: a condition on the attribute holding the patient's age, Greater Than or Equal To 35, sends older patients to a stage with an extra counselling call and younger patients straight to the booking stage.
The Node Card
The condition node shows its comparison on the canvas, in the form attribute, operator, value, so you can read the branch without opening it. While parts are missing it shows "No Left Operand", "No Operation Selected" or "No Right Operand" in red.
Last updated on