September's headline is Workflows: the step you used to repeat by hand, built once and run whenever you need it.
Workflows: automate a multi-step task
A lot of clinical admin is the same sequence every time: look something up, weigh it against the guideline, write it up, file it somewhere. A Workflow is that sequence, built once and run whenever you need it — on demand, or on a schedule while you're doing something else.
Building one starts as a conversation. Describe what you want done in plain language and Rhazes drafts the workflow for you, asking a few grouped clarifying questions as it goes rather than demanding a complete specification up front. It suggests steps based on what's already on the canvas, and looks up your own templates, tools and guideline libraries by name so you can point at them instead of describing them. You can accept its proposal, or keep refining — nothing is committed until you say so.
The steps are named for clinicians, not engineers. A workflow is a canvas you can see and edit, built from seven kinds of step:
- Start — what the workflow needs from you before it can run.
- Find information — search the web, your reference documents, a chosen clinical guideline library, or a patient's EHR record.
- Think or write — reason over what's been gathered and draft the output.
- Check with me — pause and ask you something, or ask you to confirm before it continues.
- Choose a path — branch, so the workflow does different things depending on what it found.
- Calculate — work out a value from the numbers it has.
- Finish — what happens with the result.
You decide where the result lands. A finished workflow can show it to you in chat, create a document as PDF, Word or text, fill one of your own PDF forms, add a patient to your list, add tasks to your list with a due date, or hand the result to another workflow or a Rhazes assistant along with its sources.
Running it. Trigger a workflow yourself, or schedule it daily, weekly or monthly at a time you pick. While a run is going, its progress plays out on the canvas with the camera following the active step. If a step needs you, the run waits rather than guessing — and a confirm gate means it, so answering no ends the run instead of carrying on anyway. If several runs are waiting on you at once, you can jump between their questions from the chat.
Reviewing what it did. Every step of a finished run opens up to show what it searched for, what it read, and what it produced — so a workflow is auditable rather than a black box. From the run page you can download the result, run it again, or open it back in the builder to adjust it.
Finding and sharing them. Workflows have their own home: the ones you built, the ones shared with you, your pinned ones, and a Discover page of workflows others have published — shown as their actual step sequence, not a wall of prompt text. Workflows now replace the older, simpler Tools section as the way to save and reuse a multi-step task.
