Referral tracking follows a request for care from the referring team to the receiving team and back to the person who needs the result. It records whether the request arrived, whether the patient received care, and whether the expected findings reached someone who can act on them.
For a pharmacy providing clinical services, the handoff runs in both directions: a practice may send a patient for a medication review, or a pharmacist may refer a patient for evaluation elsewhere. A completed pharmacy appointment can still leave the referring clinician waiting for an answer; tracking both events makes the unfinished handoff visible.
Agree on what comes back
A referral needs a clear purpose. “Please review this patient's medications and send your findings to our clinical inbox” gives the receiving pharmacy a different assignment from “Please contact this patient to offer an appointment.” Agree on the service, the information needed to perform it, the contact for questions and the response expected afterward.
The CDC's pharmacy linkage guide describes both physician-to-pharmacist and pharmacist-to-physician referrals. For a pharmacy receiving a clinical-service referral, settle who contacts the patient, which location provides the service and where the pharmacist sends the findings. For an outgoing referral, identify the receiving office and who at the pharmacy will follow up.
Use the receiving team's approved communication route. A fax, Direct message or portal submission may provide evidence of transmission, but the next useful question is whether the right team can use the request. Our Direct Secure Messaging guide covers the transport and attachment questions in more detail.
One completed visit, one missing report
Consider a hypothetical primary-care practice referring a patient to a pharmacy for a medication review before the patient's next practice visit. The two organizations have agreed that the pharmacist will return a summary of the review and any questions needing the prescriber's decision. Assume the pharmacy has already verified the service and payment arrangement.
The pharmacy receives the referral, confirms that it can provide the requested service and contacts the patient. The patient chooses another location in the same pharmacy organization because its appointment hours work better. The referral's assigned location changes with the booking so the original location doesn't keep calling the patient.
The pharmacist completes the review and saves the clinical note. At that point, “visit completed” accurately describes the encounter. If the note remains only in the pharmacy record, the referring practice still has no answer. The pharmacy sends the agreed summary to the named clinical inbox, including the specific question for the prescriber.
A delivery confirmation establishes that the summary reached the destination supported by that channel. It doesn't establish that the prescriber answered the question. If that answer is needed for the pharmacy's next action, the follow-up remains assigned until a qualified person resolves it. The tracker can show the visit as completed and the prescriber response as pending at the same time.
This distinction also prevents duplicate work. If the practice asks about the referral, staff can request the missing response or resend the existing summary through the agreed route instead of booking a second medication review.
Read the status together with its evidence
Software labels vary. In the example, the useful milestones are receipt confirmed, appointment booked, visit completed, summary returned and follow-up resolved. Each should point to the event that supports it, such as the receiving office's reply, the calendar entry or the encounter note.
Keep the source visible when it changes what staff should do. “Patient says the visit happened” supports contacting the receiving office for the expected report. “Report received” supports routing that report for clinical review. Neither calls for starting the referral again.
“Closed” needs a defined outcome too. A patient who declines, a receiving office that cannot provide the service and a completed consultation should remain distinguishable. Record the reason and any remaining clinical follow-up before removing an item from the active queue. Administrative closure shouldn't silently remove an unanswered clinical question.
The Institute for Healthcare Improvement's referral guide carries the process through returned information, clinician acknowledgment and communication of the plan to the patient. That is the aim of closed-loop referral tracking: the findings return to the responsible team and inform the patient's care.
A quality-measure definition can be narrower. The 2026 CMS50v14 measure focuses on the referring clinician receiving a report from the first clinician to whom the patient was referred. That specific reporting measure doesn't establish a universal pharmacy tracking requirement or mean every recommended follow-up action has occurred.
Follow up on the actual barrier
Give each unresolved referral a responsible person or team and a next follow-up date. Set the interval around clinical urgency, the expected appointment or response, and the agreement with the receiving organization. A routine reminder queue should not determine how long an urgent clinical concern can wait; the pharmacist should use the pharmacy's clinical escalation process.
When a referral stalls before booking, contact the patient or receiving office to identify the barrier. The AHRQ referral guidance addresses appointment help, transportation, language access and the information exchanged between organizations. A patient who cannot reach the office needs different help from an office waiting for missing clinical information.
Explain who will call whom and how the patient can ask for help. If the patient misses or cancels the appointment, route that outcome back to the responsible team rather than let the original booking continue to imply progress. Once the visit occurs, follow up on the expected report and any question it leaves unresolved.
Choose software by the handoff it can show
For a small referral volume, an existing clinical record and assigned task queue may support the work. A dedicated referral platform becomes worth evaluating when staff must coordinate several destinations, locations or communication channels and cannot reliably see which handoffs need attention. The choice depends on the work and connections required, rather than a universal referral-count threshold.
Public software guidance shows different approaches. Elation's referral guide describes group reminders, checking the patient record for completion evidence and contacting the patient or receiving office. It also limits its unread-alert option to recipients with access to particular Elation platforms. An alert that works inside one network may not tell you what happened at an outside office.
Ask a vendor to demonstrate the medication-review example from receipt through the returned summary. Include the location change, a missed appointment and a report that arrives through another channel. See which updates are automatic, which require staff confirmation, who receives overdue work and where the supporting document appears. Check access controls, history and export options for any tracker holding patient information.
DocStation supports patient records, clinical notes, scheduling and patient messaging. When evaluating a separate referral tool, check how the encounter and its outcome reach your clinical record. Our patient intake software guide explains how incoming information can land as a document, a note or chart fields. During a referral-software demonstration, have a second staff member take over the unfinished example: they should be able to find the missing response and continue the work without reconstructing it from someone's inbox.
