Asking the clinician mid-run
Pause a running Rhazes workflow to ask the clinician a question, then resume from that step, so automation stops when it does not know.
Updated
What it does
An Ask step stops the run and puts a question to you. The workflow waits, and continues from that step once you answer.
Why a workflow should ask
Automation should stop when it does not know, rather than guess. An Ask step is how you put judgement back into a sequence at exactly the point it is needed, instead of either abandoning automation or letting it invent something.
Ask only for what is missing
The pattern worth copying is asking for the gap, not the whole form. If earlier steps already found the patient's name and date of birth, the step should ask only for what they did not find.
A workflow that makes you retype what it already has is one you will stop using, and you can build the question from what earlier steps produced. See Passing values between steps.
While it waits
A run waiting on you is held, not failed. It shows as waiting for input and stays that way until you answer it.
A waiting run can also be cancelled if it is no longer relevant, which is the right move when a run has been sitting waiting since last week. See Following a Rhazes workflow run.
Ask steps and schedules
A scheduled workflow containing an Ask step will stop and wait for a person. That is fine when you check your runs, and a problem when you assumed it was fully unattended.
If a workflow genuinely has to complete without anyone present, either give the Ask step a path that does not need it, or handle the missing information with a Branch instead.