Product overview
Operational workflows
Explains how Cadence runs a hospital's repeatable operational processes, tracking each live case through its steps from start to finish.
Cadence runs a hospital's repeatable operational processes. An administrator designs a process once, and Cadence tracks every live case through its steps from start to finish.
Where this sits
A process is how a hospital captures the way it does a recurring job. Read this page for the shape of the idea, then follow the links for designing, running and watching a process.
What a process is
A process is a repeatable set of steps that a hospital follows in a fixed order, defined once and used many times. An admission checklist is a process. An infection-control protocol is a process. An insurance-approval procedure is a process.
A case is a single live run of a process, following its steps from start to finish. Each time the process runs, Cadence opens a fresh case and moves it through the steps.
A step is one unit of work in a process. Each step holds its place in the order and the role that owns it.
From one design to many cases
An administrator designs the process once. From that single design, Cadence opens a case every time the work happens, and each case follows the same steps in the same order.
The same published process serves every department that runs it. Set an admission checklist once, and each ward opens its own cases from the same design.
What Cadence provides
Cadence carries a process from its design through every live run, and keeps each case legible while it is open.
| What Cadence provides | What it means |
|---|---|
| A process designed once | An administrator sets the steps and their order, and staff reuse the process across departments. |
| A live case for each run | Every time the process runs, Cadence opens a case and follows its steps. |
| The current step and the next | Each case shows the step it sits on and the step that follows. |
| An overdue flag | A step that runs past its expected time is marked overdue on the case and the board. |
| A live board | A manager sees every running case in one view. |
| Process performance | Cadence feeds how each process performs to the analytics tool. |
Cadence feeds process performance to Falcon, so a manager sees where cases wait and which steps run late over time.
How a case starts
A case starts when its trigger occurs, such as a visit opening in Gate, or when a member of staff opens it by hand. Either way, the case begins on its first step and advances as staff complete the work.
Where a process fits
Cadence draws on the rest of the platform for the people and the timing a process needs.
Each step is owned by a role, so the work lands with the right person.
Quest raises a reminder card for a step, so its owner sees it on their due list.
Falcon reads a process to show how it performs over many cases.
A manager watches every running case, its current step and any overdue work, in one place.
Common confusions
What is the difference between a process and a case?
A process is the design, set once. A case is one live run of that design. One published process opens many cases, one for each time the work happens.
Does one process belong to a single department?
A published process serves every department that runs it. Each department opens its own cases from the same design.
Who owns the work in a process?
Each step names a role that owns it. Cadence routes the step to that role and records the person who completes it.
Read how an administrator designs a process and publishes it for staff to use.