A queue that reflects the actual work
Waiting on a patient, waiting on records, and waiting on acceptance are different states with different next actions.
For care coordination teams
Less chasing. More care moving.
A clear owner. A useful next action. A way to see what is waiting and why.
Let’s talk about your workflowExample coordination queue
What needs attention, and why.
01
Referral awaiting records
Needs actionIntake team · request missing notes
02
Patient needs a time
ReadyScheduling team · offer appointment
03
Specialty accepted
MovingReferring team · follow booking progress
Illustrative workflow · Platform vision
The everyday reality
You should not have to remember what the system forgot.
You know which request is waiting on records, which office needs another call, and which patient needs help choosing a time. Too much of that knowledge lives in your head.
Your team’s practical knowledge should shape the workflow. It should not be the only thing holding it together.
A better way forward
Make the work between the messages visible.
Preferral is designed around an owned next step. When a request cannot move forward, the person who can help should be able to see the reason and the context.
Context that survives the handoff
Keep the reason for the request and the relevant history close to the work, so the next person can pick it up.
Exceptions that stay in view
When an automated step cannot finish, unfinished work needs to return to a responsible person rather than disappear.
A few useful questions
Let’s make it concrete.
Every organization has its own starting point. The right conversation begins with yours.
Does automation remove the need for coordinators?
Our approach depends on clear human responsibility. Automation should move a known step forward and make exceptions easier for the right person to resolve.
How do you define a completed handoff?
Sending a request, having it accepted, booking a visit, and completing care are separate events. The workflow should make those distinctions clear and define who owns each step.
Can our coordinators help shape the workflow?
They should. A useful starting point is a walk-through of your current queue, recurring exceptions, and the calls your team makes to find out what happened.
A better next step
Show us the work you keep having to chase.
The best starting point is the part of your day you already know could work better.