Concept explainer
Real-time updates
Explains how the dock, the due list and the process board stay current as work happens, so a member of staff sees the latest state without refreshing.
Your screens stay current as work happens. The dock, your due list and the process board reflect the latest state, so you see what is true now without refreshing.
What real-time means here
A live screen mirrors the state the platform holds. When that state changes, the screen changes with it, so you read the current picture rather than a copy from when you last loaded the page.
What stays current
The surfaces you work from update on their own as the hospital works. Each shows a different slice of the same live state.
| Surface | What it shows | What keeps it current |
|---|---|---|
| The dock | The actions your role and relationships allow | A change to your access or your patients |
| Your due list | The tasks and doses due to you now | A dose given, a task completed, a new due item |
| The process board | Every case running through a process | A step finished, a step falling overdue |
The dock
The dock is the home screen you land on when you sign in to Chamber, the staff desktop. It shows the actions your role and your relationship to each patient allow.
When your access changes, the dock changes with it. A patient discharged from your ward drops from your reach, and the dock updates to match, so you act only where you hold a current reason.
Read how the dock draws itself from a permission decision in the dock and its actions.
The due list
Your due list is the personal list of tasks and doses due to you, ordered by time. Quest keeps it current through the shift.
When a colleague gives a dose you were both watching, it clears from your list as it clears from theirs. When an order adds a new dose, a fresh card arrives in place. If a task falls past its due time, it moves to the top so it stays in front of you.
Read how due work is built in your due list.
The process board
The process board is the live view of every case running through an operational process. Cadence keeps each case on its current step.
When a member of staff finishes a step, the case advances on the board for everyone watching. When a step runs past its time, the board flags it as overdue in place. A manager reads the board once and sees where every case stands.
Read how a process runs in running a process.
From change to screen
A live update follows one plain path. Work happens, the change is recorded once, and every open screen that shows that piece of work catches up to match.
Because the change is recorded once and read by every screen, two people looking at the same patient see the same state. The picture stays consistent across the ward.
A dropped connection
A live screen depends on a connection to the platform. If that connection drops, the screen holds the last state it read and tells you it is catching up.
When the connection returns, the screen reconciles to the current state on its own. Your work holds, and the screen lands back on the true picture.
The screen tells you when it is stale
A live surface shows its own freshness. If a screen is catching up after a break in the connection, it marks itself as stale, so you read a delay honestly rather than trusting an old picture as current.
Common questions
Do I need to refresh to see the latest state?
Your screens update on their own. The dock, your due list and the process board stay current as work happens around you.
Will two people see the same patient the same way?
Yes. Every screen reads one recorded state, so two people looking at the same patient read the same picture.
What happens to a live screen if the network drops?
The screen holds its last state and marks itself as catching up. When the connection returns, it reconciles to the current state on its own.
Read how an alert reaches the right people the moment it fires in alerts.