What Is Referral Management? The Lifecycle and Its Owners
Referral management connects people, information and follow-up around a referral. This overview explains the lifecycle, responsibilities and difference between tracking and completing the work.
Its purpose is broader than putting an order in an EHR. AHRQ describes care coordination as organizing care activities and sharing information among the people involved, with the patient's needs and preferences carried through those exchanges. Referral management applies that idea to a particular handoff between services. AHRQ care coordination overview
What is referral management intended to achieve?
The intended outcome is an appropriate handoff that can be followed through: the patient reaches the receiving service, and the referring team receives the information needed for ongoing care. A research study of primary-care referrals by Patel and colleagues describes this same endpoint as a completed specialty appointment with results available to the primary-care provider. Patel et al., Closing the Referral Loop
That definition makes two common shortcuts visible. Sending the order is not the same as completing the appointment. Completing the appointment is not the same as confirming that the referring team received a report.
For a practice leader, the useful question is therefore more specific than "How many referrals did we process?" Ask which event the count represents. Orders received, patients contacted, appointments booked and reports returned describe different parts of the work.
Keep the patient's experience in view as well. A technically complete order can still leave a person unsure whom to contact or what will happen next. Ask whether the handoff explains the next step and who can answer questions. AHRQ places communication of patient needs and preferences at the center of coordination. AHRQ care coordination
How is the referral different from the work around it?
A referral records the request for another clinician or service to become involved. Referral management is the surrounding work that makes the handoff usable and follows its outcome.
From the sending practice's perspective, it is an outbound referral. For the organization receiving it, it is inbound. The same patient journey crosses both views, but each team may use different queues and status labels. A practice can clarify this by describing what it sends, what it expects back and where responsibility changes hands.
Coverage checks and authorization questions may form part of that work. Keep them distinct from the referral itself and route applicable payer questions to the responsible staff. Our referral versus prior authorization guide explains the distinction in more detail. This overview does not assign a universal authorization requirement or decision deadline to every referral.
Likewise, an administrative team can gather information about the requested service without deciding what care the patient should receive. Preserve clinical questions for the referring or receiving clinician. The workflow should make that handoff visible instead of expecting a coordinator to infer an answer from an incomplete order.
What happens across the referral lifecycle?
The existing referral lifecycle is a useful way to organize the work: creation, administrative preparation, outreach, scheduling, pre-visit preparation, completion and return of information. Treat these as events to describe, not a rigid sequence that every referral must follow without exception.
Creation and preparation. The referring team records the request and the information needed by the receiving team. Administrative preparation includes identifying missing documents and assigning applicable coverage questions. When an item is missing, name it and name the person responsible for obtaining it.
Outreach and scheduling. The responsible team contacts the patient about the next step and, where appropriate, arranges the appointment. Record an unsuccessful contact attempt differently from a conversation and a conversation differently from a booking. If the patient cannot proceed, document the reported obstacle and the next assigned action.
Pre-visit preparation. The receiving team may need records or completed intake information. Any clinical preparation instructions should come from the appropriate clinical source. The coordination task is to communicate the approved information and identify questions that need a clinical response.
Completion and information return. After the appointment, record what is known about the outcome and whether the report reached the referring team. CMS's 2026 measure "Closing the Referral Loop: Receipt of Specialist Report" explicitly concerns receipt of a report by the referring clinician. It is a specific quality measure with its own specification, not a generic definition for every workflow count. CMS50v14 measure information
This status-to-evidence table can help a team agree on its vocabulary:
| If the status says | Evidence to look for | What the status does not establish by itself |
|---|---|---|
| Sent | A record of the referral being transmitted | That the receiver has reviewed it |
| Received | Acknowledgment or a receiving-system record | That an appointment is available or booked |
| Contacted | A documented exchange with the patient | That the patient has scheduled |
| Scheduled | An appointment record | That the appointment occurred |
| Visit completed | Documentation of the completed encounter | That the referring team has received the report |
| Report received | The report available to the referring team | That every subsequent clinical task is finished |
The table is an operational discussion aid. Agree locally how each status is recorded and who verifies it. If an event is unknown, keep that uncertainty visible rather than treating an empty field as proof that the event did not happen.
Want to see these stages run in a live workflow? Book a demo and we will walk through your referral handoffs.
Who owns the work at each handoff?
Start with the referring team, the receiving team and the patient. Depending on the workflow, coordinators, scheduling staff and coverage specialists may also have assigned tasks. The job is to make each responsibility explicit, not assume that one role can resolve every problem.
The referring team can establish the purpose of the referral, the information being sent and the route for clinical clarification. The receiving team can identify what it needs to process the request, communicate its scheduling outcome and return the relevant report. The patient needs a clear next step and a way to raise practical questions or barriers.
Use a hypothetical handoff to test the arrangement: the receiving office needs another document. Who requests it? Where does the request arrive? Who can supply it? Who tells the patient if that changes the next step? A status saying "pending" answers none of those questions unless the task and owner are also visible.
The same applies when an appointment is cancelled or does not occur. The record should show what happened and who will review the next action under the practice's established process. Do not close an unresolved referral merely because a fixed number of contact attempts has been exhausted.
For a fuller explanation of the coordinator's role, use our referral coordination guide. For detailed workflow design, continue to the referral management process guide.
How do tracking, coordination and software fit together?
Tracking answers, "What do we know about this referral now?" Coordination answers, "What action is needed, and who will take it?" Software can support the records and actions, but the names should not be treated as interchangeable.
A useful referral record connects the current state to its evidence, next action and owner. Without that connection, a queue may show a large number of items marked "pending" while giving the team little help deciding what to do with them.
Before evaluating software, describe the handoff you want it to support. Which information must be read? Which action is expected? Where should the result appear? How will a staff member see an exception or confirm that an update reached the intended system? These are evaluation questions, not assumptions that every product performs the same work.
Measurement needs the same precision. Patel and colleagues studied referrals in one large health system and distinguished scheduling attempts, documented appointments and completion status. Their study also described incomplete documentation. Its findings should not be turned into a universal completion benchmark for all practices. The practical lesson for your own review is to define the event and the available evidence before interpreting the count. Patel et al.
This is the gap Linear Health is built for. Tracking tools show your team which referrals are stuck. Linear completes the routine steps that move them (intake, patient outreach, scheduling and follow-up), records the result in your EHR, and hands the exceptions back to a coordinator with the context needed to act.
Our referral management versus tracking comparison develops this distinction. The software buyer's guide addresses requirements once the workflow is defined.
Where should a practice start?
Choose a small set of existing referrals and follow the records across the handoffs. The aim is to understand the current process, not calculate a universal loss rate from a small sample.
For each item, ask where it started, what the current status means, which evidence supports that status and who owns the next action. Include a completed referral as well as an unresolved one. Comparing the two can help the team describe what information is available when a handoff works and what is missing when it stalls.
Then name the problem precisely. Missing records point to an information handoff. Unclear ownership points to a process decision. A booked appointment without an outcome points to a tracking question. Each deserves a more specific response than "we need more automation."
Use the referral coordination overview when you are ready to discuss the operational workflow. For current CMS requirements, consult the separately maintained provider operations readiness guide rather than inferring a deadline from this definition article.
Ready to close the loop on your referrals? Book a demo.
Before Linear, I needed five systems just to get a patient from referral to appointment. Now I have one screen. The team is coordinating care instead of chasing it.
Frequently asked questions
What is referral management in healthcare?
How does referral management differ from referral tracking?
Which teams take part?
Is a referral complete when an appointment is booked?
When can software support referral management?
Sources
