Procedure
Designing a process
Walks an administrator through defining a multi-step process in Cadence, setting each step and the order they run in, and publishing it for use.
This page walks an administrator through defining a multi-step process in Cadence. You set each step, the order the steps run in, and publish the process for staff to use.
Before you begin
Confirm these before you open the designer.
What a step holds
Each step in a process carries a small set of facts. You set these once when you design the process.
What the step asks a person to do.
The role responsible for completing the step.
Where the step sits in the sequence.
How long the step has before it is marked overdue.
Defining the process
Work through the designer in order. Each step you add appears in the sequence, and you arrange the order as you go.
- 1
Name the process
Give the process a name that staff recognise, such as an admission checklist or an infection-control protocol. The name shows on every case the process opens.
- 2
Add the steps
Add each step in turn. Write what the step asks a person to do, in the words the ward already uses.
- 3
Set the order
Arrange the steps in the order they run. A case follows this order from the first step to the last.
- 4
Assign an owner to each step
Set the role that owns each step, so the work lands with the right person. Cadence routes the step to whoever holds that role and is on shift.
- 5
Set an expected time
Give each step the time it has before Cadence marks it overdue. This is what lets a manager see a late step on the board.
- 6
Set how a case starts
Choose the trigger that opens a case, such as a visit opening, or leave it for staff to start a case by hand.
- 7
Publish the process
Publish the process. Staff across the departments you choose run it from the moment it is published.
A running case holds its design
A running case follows the version of the process it started under. A later edit to the process leaves cases already running unchanged, so a case always reads as it was designed when it began.
Setting the order
The order you set is the path every case takes. Read the sequence top to bottom before you publish, and check that each step's owner can act at that point in the run.
Reuse across departments
One design, many departments
One published process serves every department that runs it. Set the process once, and each department opens its own cases from the same design, so the hospital runs a recurring job the same way everywhere.
Common confusions
What happens to running cases when I edit a process?
Cases already running keep the version they started under. Your edit reaches the next case that starts, so a change is safe to make while cases are open.
Do I set an owner as a person or a role?
Set a role. Cadence routes the step to whoever holds that role and is on shift, drawn from the duty roster.
Read how a live case moves through the process you published.