Referral Tracking in Healthcare: Build a Worklist Teams Can Act On
Build a referral tracking record with clear states, timestamps, evidence, owners and next actions, including cancellations, reopenings and handoffs.

Define the purpose of each state
Define a state by the event or evidence that lets a person apply it. If two coordinators use "in progress" for different situations, write down the distinction needed for the next action. The proposed dictionary below is an original administrative design to adapt to the local workflow.
| State | Purpose | Entry evidence | Exit evidence |
|---|---|---|---|
| Received, not reconciled | Hold new transmissions until they are matched to an episode | Document or request received | Identity and episode relationship resolved |
| Information needed | Make a specific missing administrative item visible | Named item recorded as missing | Item received or an authorized disposition recorded |
| Ready for assigned action | Show that the required inputs for the assigned administrative step are present | Required inputs present | Action result recorded |
| Outreach in progress | Show that a contact attempt has been made and its outcome captured | Attempt and outcome logged | Response, booking or documented disposition |
| Booking confirmed | Link the episode to an appointment that exists | Appointment confirmation linked | Attended, cancelled, rescheduled or other recorded outcome |
| Administrative follow-up due | Keep outstanding documents or outcome evidence on the worklist | Expected evidence still outstanding | Evidence received and routed |
| Administratively closed | Record a reasoned stop to administrative work | Closure reason and authorizing evidence | Reopening event if later work is required |
This is an operational design, not a clinical protocol. Clinical priority, coverage decisions and medical appropriateness sit outside the dictionary. Where a step depends on one of those decisions, record the authorized role responsible and the administrative follow-up, and do not let staff infer a clinical decision from how old a record is.
Keep a state only when it communicates a meaningful difference in evidence, responsibility or next action. The right number depends on the workflow; the example is a starting dictionary, not a required count.
Keep owner and next action beside status
A status alone tells a reader where the referral is. It does not tell them what to do. The worklist row should carry the principal state, the blocker, the next action, the owner and backup, the next-action due time, the last meaningful event and a link to the authorized source record.
Two habits keep this honest. First, never write "follow up" as the whole next action. Write what is needed, from whom, and what happens if it does not arrive. Second, record a backup owner and a handoff rule. Several teams may contribute to one episode, but an unqualified list of participants does not tell a covering colleague who must ensure the next action occurs.
Handoffs between organizations deserve the same discipline. A message sent to another office is evidence that something was sent. It is not evidence that the other office accepted the work. Define the event that transfers administrative responsibility and retain follow-up on your side until that event is confirmed. Keep the acknowledgment or accepted assignment as part of the history. The companion piece on why referrals get lost between primary care and specialists provides a method for tracing an unclear handoff.
Separate evidence from assumptions
Look for states whose evidence is missing. A booked state with no linked appointment confirmation requires reconciliation. A closed episode with no recorded reason requires clarification. A returned consult note establishes document receipt; it does not establish that a clinician reviewed it. Keep those questions visible rather than filling the missing evidence with an assumption.
Keep these three event distinctions in the record:
- Store event time separately from data-entry time when they differ. A coordinator may log an event after it happened, and an integration may deliver a message late.
- Treat the report extraction timestamp as neither the receipt time nor proof that the referral advanced.
- Record a returned document as an administrative evidence event with its originating organization, associated visit, received time and routing destination. If the visit link is uncertain, open a reconciliation task rather than closing by assumption.
Use separate clocks for separate questions. Episode age begins at the defined receipt or creation event. State age begins at the genuine entry into the current state. The next-action due time records an operating commitment. A valid new state or revised action may change its corresponding clock, but retain the prior value and reason. Reassignment or a note edit should not silently make the episode younger.
Handle repeated or conflicting updates
Real referrals arrive more than once and change after they are booked. The record has to absorb that without creating duplicate episodes or losing history.
Resends. Preserve intake identifiers and inspect whether the new transmission belongs to the same referral episode. If that relationship is confirmed, retain it as another transmission on the episode. If it is uncertain, assign reconciliation. The same patient may have separate referrals, so patient identity alone is not enough to merge them.
Conflicting updates. When two sources disagree, for example a scheduling system shows an appointment cancelled while a coordinator note says it was kept, do not pick one silently. Open a reconciliation task with both pieces of evidence attached, assign an owner, and set a due time. The principal state should reflect that the scheduling path needs an action.
Reopenings. Walk through this illustrative case, which uses fictional data and is not a customer example. Referral REF-1042 is received on day 1. A missing administrative item is requested on day 2 and received on day 4. An appointment is booked on day 5 for day 20. On day 10 the patient asks for a different date, so staff cancel the original occurrence. On day 12 a replacement is confirmed for day 25.
The episode still began on day 1. The first-booking event remains day 5. The second booking is a second transaction on the same episode, so the referral counts once in a unique-episode booking measure while both occurrences remain in the history. If the episode had been administratively closed before the patient responded, record a reopening with its reason and owner instead of creating a new episode to keep the open count tidy.
If you want to see how a system handles this exact sequence, bring a synthetic referral history to a Linear Health demo and ask to see the original clock, the cancelled occurrence, the replacement booking and the current next action on one screen.
Review stale records without hiding unknown outcomes
Review old open records without converting uncertainty into an outcome. "No confirmed outcome after approved follow-up" states what is known more precisely than an undefined "lost" label. Retain the follow-up history and permit later evidence to be reconciled under the approved process.
Run a periodic exception review using synthetic cases and a permitted sample of actual records. Look for:
- open tasks with no owner or no next-action due time
- negative durations or events recorded before the episode began
- duplicate episodes for one source request
- booked states with no appointment evidence
- closed records with outstanding assigned work
Then reconcile the total open count to the rows staff can see. Check permissions, filters and status mappings before concluding that a record disappeared. A view that hides another team's tasks should still make the handoff and responsibility understandable.
Finally, test a handoff during an absence. If the backup cannot identify the next step from the record, fix the field or reference that failed rather than copying every detail into the worklist. Put the right information in the right maintained source.
A practical evaluation method
This section is editorial guidance for comparing your current tracker, a spreadsheet, an EHR work queue or a vendor product. It is not a measured result.
- Write the dictionary first. List your states with entry evidence, purpose and exit evidence before looking at any tool. A tool that cannot represent your states will force you to reinterpret its labels.
- Run one messy case end to end. Linear Health's Operational AI Evaluation Kit recommends a representative case with normal complexity, missing data and at least one exception, scored only on evidence you can inspect, and treats privacy, security, safety and accountability issues as gates that a high score cannot offset (Linear evaluation kit). Use REF-1042 or a similar synthetic history.
- Check the row, not the dashboard. For each state, can a covering colleague see owner, backup, next action, due time, last meaningful event and source link without opening the full history?
- Check the clocks. Confirm that reassignment and note edits do not reset episode age, and that event time and entry time are stored separately.
- Check the history. Cancel and rebook an appointment, close and reopen an episode, and confirm nothing is overwritten.
- Map workflow impact. AHRQ's Workflow Assessment for Health IT Toolkit is designed to help ambulatory organizations recognize how health IT affects clinical and administrative workflow during planning and implementation (AHRQ). Use it to document who touches the worklist today and who will after any change.
If you are weighing tracking against broader referral coordination automation, use these same checks as acceptance cases. Automation should preserve inspectable episode history and next-action ownership rather than create a second, contradictory tracking record. The operational AI evaluation kit gives a scorecard for that review, and the guides on referral automation ROI and best referral management software categories cover the financial and category questions separately. When you are ready to test a vendor against your own statuses and a difficult handoff, book a tracking-workflow review and bring the dictionary with you.
Frequently asked questions
What statuses should a referral tracker include?
Should a referral have one owner or several?
When should an aging clock reset?
Can a spreadsheet serve as a referral tracker?
What does closing a referral mean?
Sources

Sami founded Linear Health after spending a decade at the intersection of clinical operations and scaled healthcare technology. Connect on LinkedIn.


