Workflows
Automate clinical work as a sequence of steps: build it once, run it on demand or on a schedule.
25 articles
- What a Rhazes workflow isA Rhazes workflow automates clinical work as a repeatable sequence of steps you build once and run on demand or on a schedule.
- Creating a workflowCreate a workflow three ways: describe it and let Rhazes build it, start from a blank canvas, or install one another clinician shared.
- Building a workflowBuild a workflow on the Rhazes canvas: add steps, join them in order, pass values between them, and fix what validation flags before you run it.
- The Rhazes workflow steps you can useEvery workflow step available in Rhazes, from reading a patient record to calculating a score, branching, and producing a document.
- Passing values between stepsUse what an earlier step produced with a double-brace reference, and see which values each Rhazes workflow step offers to later steps.
- Asking the clinician mid-runPause a running Rhazes workflow to ask the clinician a question, then resume from that step, so automation stops when it does not know.
- Branching on a conditionRoute a Rhazes workflow down different paths using conditions, and handle the patient who fits none of the cases you planned for.
- Calculations you can rely onWrite clinical formulas Rhazes runs identically every time, showing their working for audit and banding the result into categories you can branch on.
- Working with patients in a workflowRead patient details and clinical records inside a Rhazes workflow, or create a new patient record from what the run found.
- Filing tasks from a workflowHave a Rhazes workflow file follow-up tasks onto your list with due dates, grouped into a task list it creates and reuses by name.
- Producing documents and formsEnd a Rhazes workflow with a finished clinical document or a completed PDF form, in the format you need to file it or send it.
- Choosing what a workflow can draw onPoint a Rhazes workflow at your own guidelines, spaces and reference documents so its output follows local practice, not generic advice.
- Running a workflowRun a Rhazes workflow from a chat or from its own page, turn one on or off, and why you should test a new one by hand first.
- Scheduling a workflowSchedule a clinical workflow in Rhazes to run automatically in your own timezone, and pause, edit or remove that schedule later.
- Following a Rhazes workflow runWatch a Rhazes workflow run live, read what each step produced, and cancel, retry or download the result when it finishes.
- Sharing and installing workflowsPublish a Rhazes workflow for other clinicians or install one from the gallery, and what happens to references that are not yours.
- Deleting a workflowDelete a Rhazes workflow and understand what happens to its schedule, its run history, and the tasks it has already filed on your list.
- Rhazes workflows worth building firstSix clinical Rhazes workflows that pay for themselves quickly, and how to judge which parts of your practice are worth automating at all.
- Post-clinic letters and follow-upsA Rhazes workflow that turns a recorded consultation into a clinic letter and the follow-up tasks it generated, in a single run.
- New referral intakeA Rhazes workflow that takes a referral letter through to a created patient, a structured summary, and the tasks it generates.
- Pre-clinic preparationPrepare clinic overnight with a scheduled Rhazes workflow that flags outstanding results, incomplete actions and monitoring now due.
- Structured chronic disease reviewA Rhazes workflow for consistent chronic disease reviews, with scores calculated deterministically and targets taken from your own protocol.
- Discharge documentation and codingA Rhazes workflow that produces the discharge summary, the clinical coding with its evidence, and the follow-up tasks from a single run.
- Weekly outstanding results sweepA scheduled Rhazes workflow that finds results nobody has actioned and files tasks to chase them, so nothing depends on being remembered.
- Chaining workflows togetherFinish one Rhazes workflow by running another, chaining several small workflows into a pipeline that runs unattended on a schedule.