Sending a referral tells you that one team has acted. It tells you very little about whether another team is in a position to help the patient.
A transmission is an event. A handoff is an agreement.
A document can reach an inbox without being reviewed. A reviewed referral can be missing the information needed to accept it. An accepted referral can still be waiting for the patient to book.
These states matter because they call for different actions. Treating them as one status makes the unfinished work harder to see.
Name the receiving team.
A useful handoff identifies the team being asked to act, the reason for the request, and the context it needs. Acceptance makes that team’s role explicit.
Until acceptance, responsibility needs to remain with a defined person or team. Otherwise each side can reasonably assume the other is taking care of it.
Keep booking and completion separate.
Acceptance is progress. It is not an appointment, and an appointment is not completed care. Your workflow should make each transition visible and give unfinished work an owner.
The patient should also understand the current state. “Your referral was sent” is a much less useful message than a clear explanation of what happens next and who can help.
Start with one pathway.
Choose a common referral. Write down the states from the clinical decision through acceptance, booking, and follow-up. For each state, ask who can move it forward, what they need, and how the team knows they have done so.
That small exercise often tells you more about the coordination problem than another aggregate count of referrals sent.
Further reading
AHRQ: Care Coordination