Inbound vs. Outbound Referrals: Who Owns Each Handoff?

Inbound referrals are requests your organization receives; outbound referrals are requests your organization sends. The same referral can be outbound for one office and inbound for another. Each side owns different administrative actions and evidence. Compare the directions by who sends, receives, assigns, schedules, reports status, and returns documentation, then agree on the information required at each handoff.

Begin with one request and two perspectives

A primary care office sends a referral to a specialty office. The primary care team sees an outbound workflow: prepare the approved request, transmit it, establish that it reached the intended destination, and track subsequent information.

The specialty team sees an inbound workflow: receive the request, establish its administrative context, identify missing items, assign the next action, and communicate its status.

An organization can occupy both positions. A multispecialty group may receive outside referrals while sending other patients to external services. A referral between two of its own locations can cross internal responsibilities even when it stays inside the same organization.

The direction does not determine a patient's clinical needs. It tells an operations team which side of an information and responsibility exchange it is managing.

Use the referral management process guide for the complete lifecycle. This comparison focuses on the agreements that connect its participants.

Compare the responsibilities side by side

The following is an original proposed handoff model. Adapt the owner roles and evidence to your organization and its partner agreements.

A task's completion must have a subject. "Transmission task complete" is useful. "Referral complete" is ambiguous if the receiver has only just logged the request.

HL7 R4 represents referral requests through ServiceRequest and separately tracks activities through Task. The proposed handoff table is an operational design, not a mandatory technical mapping.

Make acknowledgment mean something specific

There are several possible acknowledgments. A fax transmission report may establish transport. An intake record may establish receipt. A receiving team may then accept administrative responsibility or request more information.

Ask partners which event their acknowledgment represents. Do not convert a delivery confirmation into evidence that a scheduler is working the referral.

For outbound teams, retain the last confirmed event, its source and the next action. If the only evidence is that a packet was sent, say so. An unknown status is an information gap to resolve, not proof that the patient went elsewhere.

For inbound teams, acknowledgment can include the request reference and the status of administrative processing through approved communication channels. It should not promise an appointment or a clinical outcome that has not been established.

When the receiving office cannot identify the packet, reconcile destination and request references before creating another copy. A resend may be necessary, but it should link to the original transmission history.

Write a shared handoff agreement

A handoff agreement does not have to be long. It should let either team answer six questions:

1. What event starts the handoff?
2. Which team is responsible for sending it?
3. Which destination and identifier are used?
4. What evidence shows the receiving team has it?
5. What happens when the handoff is incomplete or rejected?
6. Who investigates silence or disagreement?

Include a version and contact owner. Review the agreement when destinations, staffing or system arrangements change.

For a missing-information request, for example, the receiver identifies the item and sends it through the agreed route. The sender assigns the request, returns the material or explains the unresolved condition, and preserves the original referral reference. The receiver then associates the update rather than opening another episode automatically.

Use referral intake automation for the detailed receiving-side association process. The agreement here identifies who supplies and who accepts the update.

Map a sending and receiving handoff with Linear Health using one synthetic request and both teams' expected evidence.

Avoid duplicate counting when a network handles both directions

A referral can generate multiple local records without representing multiple unique requests at the network level.

Hypothetical network example: During a period, Site A sends 100 referrals. Eighty go to external organizations, and 20 go to Site B within the same network. Site B also receives 60 referrals from outside the network.

Site A has 100 outbound records. Site B has 80 inbound records: 20 internal plus 60 external. Adding those gives 180 directional records, but the 20 internal requests appear twice.

If the network's defined measure is unique request episodes represented by those records, the count is 100 + 60 = 160, assuming each request is otherwise unique. Both the 180 directional workload count and the 160 unique-episode count can be useful if clearly labeled.

For the 20 internal referrals, suppose Site B acknowledges 18 and two await receipt reconciliation. The outbound dashboard should not mark all 20 acknowledged because Site A's transmission jobs completed.

Suppose 12 of the acknowledged requests have confirmed bookings. That is a scheduling outcome, not confirmation of 12 completed visits. Report the event observed.

This example illustrates accounting, not a recommended clinical or quality-reporting measure.

Give shared staff separate operational views

The same coordinator can work both directions. The question is whether each task has a clear owner, due action and backup when competing demands arise.

Build views around the work: new receipts needing association, outbound requests lacking acknowledgment, inbound items awaiting documents, and expected documentation not yet received.

Do not assume inbound work always has priority or outbound work can wait for a monthly review. Apply the organization's approved priorities and service expectations to each task.

Allocate protected time or designated ownership for quieter follow-up work if it otherwise goes unworked. Verify the effect using actual queue age and completion evidence, rather than assuming a staffing model is universally superior.

A shared team also needs a way to switch roles without confusion. A coordinator updating a receiving-side state should not accidentally close the sending-side task. Use labels that identify organization, direction and event.

For a state dictionary and aging process, see referral tracking in healthcare.

Choose automation according to the handoff that fails

If the incoming source is not being collected, the next project may concern intake. If documents are present but nobody owns clarification, the project is assignment and follow-up. If the sender cannot establish what happened after transmission, it needs status exchange and reconciliation.

These are different tasks even when a product describes all of them as referral automation.

Ask the proposed workflow to show the handoff from both perspectives. An intake tool may demonstrate a clean queue while leaving the sending office uninformed. A tracking tool may display a status while leaving the receiver's manual data-entry work unchanged.

This is not a reason to demand one product for everything. It is a reason to identify the remaining work, its owner and how information will cross the boundary.

For the broader software category, review referral coordination software. Select capabilities against the specific agreements your organization needs to execute.

Measure each direction with the evidence it controls

Inbound teams can track receipt-to-assignment, missing-information resolution, and confirmed booking outcomes. Use the referral-to-appointment conversion guide when defining the booking cohort and observation window.

Outbound teams can track acknowledgment availability, unresolved external dependencies, and documentation receipt. For the final document-specific workflow, see consult note return.

For both directions, separate "unknown" from an established negative outcome. An absence of information should create a reconciliation task.

A shared operational review should inspect disagreements. The receiver may say a request was returned for information while the sender sees it as awaiting acceptance. Link the records and investigate the missing communication rather than arguing over which dashboard is right.

Test the agreement before expanding it

Run a synthetic request through receipt, acknowledgment, missing-information exchange and a corrected status update. Ask both teams to identify the same episode and explain the next owner.

Test an interrupted handoff too. If the response never reaches its destination, can staff find the unresolved state and recover the work?

Write down what the test did not cover. A successful internal handoff does not prove an external partner's process, and one partner's connection does not establish all others.

Book a discussion of your inbound and outbound handoffs when you can identify which evidence currently disappears between the teams. Start with that boundary and expand after the agreement works.

FAQ

Sources

• HL7 FHIR R4 ServiceRequest, representation of service and referral requests.
• HL7 FHIR R4 Task, representation of activities and their tracked states. The handoff table and the network example in this article are original editorial tools.