Creating a workflow
Create a workflow three ways: describe it and let Rhazes build it, start from a blank canvas, or install one another clinician shared.
Updated
Describing what you want
The fastest route is to describe the work in your own words, and let Rhazes build the workflow from your description.
It composes in the background. The workflow appears straight away and is refined while you get on with something else, marked as building until that finishes.
It can only use what you have
Rhazes grounds the workflow against your own account: your Spaces, your templates, your PDF forms, your coding standards. It cannot invent a guideline collection you are not a member of or a template you have never made.
That is why a described workflow comes back runnable rather than aspirational, and it is also why it is worth setting up the Space or template you want it to use before describing the workflow that needs it.
Be specific about the work, not the steps
Describe the job the way you would explain it to a colleague: what comes in, what you want out, what has to be checked on the way. You do not need to know which steps you want. Working that out is what the composer is for.
If the build fails
A failed build keeps your original description, so you can retry without retyping it. If it keeps failing, describing a smaller piece of the work usually gets further than describing the whole thing.
Starting from blank
Build the sequence yourself on the canvas. Right when you already know the steps, or when you are reproducing something precisely. See Building a workflow.
Installing one from the community
Other clinicians publish workflows, and installing one gives you an editable copy. Expect to point some steps at your own material before it will run. See Sharing and installing workflows.