Close referral handovers without rewarding inappropriate referrals

A clinic sends an authorised referral to an imaging centre. Its email system reports delivery, but the destination has not acknowledged responsibility and no booking is confirmed. The clinic's dashboard marks the referral complete because the message left its outbox.

Hospital referral tracking should identify the next accountable owner and the evidence for each state. Transmission, acceptance of the handover and completion of a requested service are separate events. Administrative coordination can follow those events without deciding whether a referral is clinically appropriate or redirecting it automatically.

Start with the request and permitted handover

Use a stable referral reference linked to the authorised source request, its version, intended destination, coordination owner and approved communication route. Record enough information to match the handover correctly; the receiving organisation's information requirements and permitted disclosures need review.

Build the tracking example around a request already authorised by the responsible clinician. Changes to clinical scope return to that owner. Before sharing real information, obtain the organisations’ approved purpose, access and communication requirements from clinical and privacy/legal owners. A sent message or acknowledgement records a communication event; neither establishes authority to refer or permission to share.

HL7 FHIR R4 Task separates task tracking from the referenced details of the work. Use that specification as a technical reference only where the partners support it. Agree their actual identities, acknowledgements, version changes and permitted interfaces, and test recovery with synthetic requests. The standard does not establish that either system implements the proposed referral workflow.

Follow referral R-26 without collapsing its states

In an illustrative case, R-26 version 1 is sent at 10:00. The receiving system confirms technical delivery at 10:01. An authorised coordinator acknowledges the handover at 11:20 and later proposes an appointment. Those records answer different questions.

If no acknowledgement arrives, the source coordinator should have an open follow-up task under the agreed escalation procedure. The software must not label the patient as having declined or the destination as having rejected the referral merely because a timer expired.

Preserve changes and cancellations

Suppose the clinician changes the request after the destination has booked a visit. Link version 2 to version 1, show which version the destination acknowledged and record the agreed action on the existing booking. Do not silently replace the attached request while leaving an earlier acknowledgement displayed as current.

A cancellation also requires an explicit state and a supported notification process. An integration timeout should leave the destination outcome uncertain until reconciled. Staff need a documented manual contact path when the electronic handover cannot establish a reliable result.

Compare shared software with a coordination register

A shared platform may expose acknowledgements and booking states directly. Separate organisations may initially need a controlled register and authorised human communication. Compare response visibility, correction support and the administrative burden before promising an automated closed loop.

Require evidence of supported access and partner agreement. A public portal or an emailed document does not by itself authorise automated scraping, login or onward transfer. Test the actual product edition, identifiers and error responses with synthetic records.

The proposed tracker records request ownership and completion evidence; it contains no commission ranking or referral-volume target. If a provider wants destination scoring, incentives or performance measures, obtain a separate clinical, governance and legal decision defining what is permitted. The administrative timestamps in this guide cannot establish the appropriateness of a destination or arrangement.

Measure the handover you can explain

Report unacknowledged referrals, acknowledgement age, changed requests awaiting confirmation and permitted outcomes not yet returned. State the reporting cutoff and distinguish patient choice, destination capacity and missing administrative evidence where they are actually known. Leave unknown reasons unclassified rather than inventing a persuasive explanation.

The acceptance set should include a duplicate message, a wrong destination, a changed request and a booking that exists despite a lost callback. Each case needs a traceable source version, current owner and supported next action. A closed coordination task should mean the agreed evidence is present, not merely that somebody sent a reminder.

Referral software earns its place by making the handover understandable to both teams. It supports continuity through reliable coordination while clinical decisions and permitted disclosures retain their own authority.

Next actions

1. Map one referral pathway with the source and destination coordinators.
2. Agree state meanings, sharing conditions and the evidence required to close coordination.
3. Test changed requests, missing acknowledgements and manual recovery before implementing a cross-system connection.

Topics: hospital referral tracking · referral management hospital · clinic referral status · referral handover tracking