Comparison
A patient navigation team does the highest-judgment work in the building; its ceiling is how many patients it reaches
This is the most delicate of the four comparisons, because the navigation unit is usually the best team in the building. Everything that follows assumes that as its starting point.
What does a patient navigation team do well?
- Continuity. The same person follows the whole case, and the patient recognises the voice that calls.
- Clinical judgment. They know when a delay genuinely matters and when it can wait two weeks with no consequence.
- Escalation power. They can go get the slot, call the specialist, unblock the calendar hold no system sees.
- Institutional trust. They are in-house, carrying the provider's name naturally.
None of those four automate well, and no serious provider should try.
Where is the ceiling?
The ceiling is arithmetic. Each person holds a panel of finite size, and that number is fixed by the real time each case demands: call, wait for a reply, call again, coordinate with the calendar, follow up after the visit.
Multiply that panel by the size of the team and you have the unit's total coverage. Everything outside that number receives zero contacts, and never shows up in any report as a zero.
That is the blind spot. A navigation unit's indicators are calculated over the patients the unit took on: how many accepted, how many attended, how many completed treatment. The honest denominator is how many patients had a pending order that month, which is always a considerably larger number.
How does the team choose who to accompany today?
Rarely by an explicit criterion. In practice the panel fills with the patient who became visible: the one who came to the counter, the one who called, the one who landed with whoever had a free afternoon.
The patient who went home with the order in their pocket is invisible to the process, and is often the one who needs it most. When the channel's luck does the selecting, the unit ends up accompanying the patients with the most initiative of their own, which is the opposite of closing a care gap.
How do they compare, line by line?
| Dimension | Patient navigation team | Surface |
|---|---|---|
| How many patients it reaches | The panel the team can hold at quality. | Everyone with a pending order in the period. |
| How well it resolves a complex case | Better than any system: clinical judgment, memory of the case, and the power to unblock a calendar. | Detects the case and hands it to a person. |
| What the patient experiences | The same voice throughout, already familiar with their history. | Contact under the provider's brand, on the channel that patient answers. |
| How it picks who to contact | By visibility: the patient who made themselves noticed. | By explicit criteria: clinical deadline, priority and the state of the order. |
| What data you get back | Fine-grained records, over the patients the unit managed to take on. | Orders written against orders completed, over the whole period. |
| What happens when volume rises | The panel per person stretches and coverage falls. | Response time does not change. |
What changes when the list arrives ordered?
Surface does the mechanical part: read every record, find the pending orders, sort them by deadline and priority, write to the patient, offer a slot, confirm and remind. Most of those cases close without anyone in the unit touching them.
What reaches the unit is what survives that filter: the patient who answers on no channel, the one who says yes and does not attend, the one who needs a clinical decision before anyone offers a slot. That list is shorter and harder.
Coverage stops depending on panel size, and the team's clinical judgment gets spent where it changes the patient's outcome.
When should you not add Surface here?
If your population is small and already fully covered, do not add a system. A unit that manages to contact every patient with a pending order has no coverage problem, and this is of no use to it.
Nor when the relationship is part of the treatment. In oncology, mental health or palliative care, the bond with one person carries clinical value of its own, and automating first contact there subtracts. Use Surface across the rest of the provider and leave that programme untouched.
And if the unit exists on the org chart but nobody wrote down what it does, write the protocol first. A system executing a protocol that does not exist executes the disorder faster.
What happens to the unit?
It stays whole, with the same mandate. It receives a shorter list, sorted by clinical urgency, with the repetitive volume already resolved and every prior contact typed so nobody starts from zero.
The team stops chasing patients and goes back to clinical navigation, which is what it was created for.