Referral Tracking Across Healthcare Services

Solution design

Every referral has a visible receiving step

The referral coordination service gives each handoff a shared reference across existing healthcare systems. Receipt, missing information, acceptance and subsequent administrative actions remain separate states. Each unresolved request identifies the team responsible for its next step. Access follows service responsibilities, supporting coordination without creating an unrestricted copy of the clinical record.

Sending and receiving teams share the administrative status they need to continue a referral. Unacknowledged requests and missing information have named owners, while clinical records and decisions remain with the systems and authorised teams responsible for them.

• Visible acknowledgement of transferred requests
• Specific ownership of missing information
• Clear next actions across service boundaries

Business context

A healthcare network coordinating referrals and appointment administration between separate services or locations.

Core capability

Software Development

Sent is a transport event, not an accepted referral

A sending team may see a successful transfer while the receiving service has not reviewed the request. Missing information, an unmatched patient reference or an unattended queue can leave the referral between organisations. Staff then rely on calls and repeated messages to discover who has it and whether anything is happening.

The shared record distinguishes transmission, receipt, acceptance and the next administrative action. It gives each unresolved stage an accountable owner. Staff see the information needed to coordinate that step without gaining unrestricted access to every record in the network. The service supports the handoff around care; clinical assessment remains a separate responsibility with its own authorised workflow.

Both sides need to agree what acknowledgement means

The process map follows one referral type through the sending team, receiving queue and scheduling handoff. It records required administrative information, review responsibilities and the conditions for accepting, redirecting or returning a request. Questions that currently require a phone call identify which state or ownership detail is missing from the record.

Status definitions are agreed across the boundary. Received confirms arrival in the intended queue; accepted confirms the receiving service's next responsibility under its process. Scheduled and completed describe later actions and are not interchangeable with those earlier stages. This shared vocabulary avoids a reassuring status on one side being interpreted as a clinical or operational commitment that the other side has not made.

A shared reference connects the existing systems

The coordination record links the request identifier, sending service, receiving service, required administrative context and acknowledgement history. It retains references to authoritative source records instead of creating another editable clinical record. Patient matching uses the agreed identifiers; uncertain matches go to review rather than being resolved through a loose comparison of names.

Updates retain their origin and time. Each service maps its local workflow into the agreed network states, with explicit exceptions where a direct mapping is inappropriate. Access is scoped by organisation, role and task. Audit events record meaningful actions while routine technical logs avoid unnecessary patient details, allowing integration support to diagnose failures without broad access to the underlying clinical content.

Missing information becomes a specific request back to the sender

Before transfer, the sending workflow checks the required administrative fields and destination. The receiver acknowledges the request under its original reference and begins the appropriate review. If information is missing, the receiving team identifies what is needed and assigns the request back to the responsible source, retaining the link to the original referral.

The sender can respond to that request without creating another referral. Acceptance then leads to the defined administrative next step, such as scheduling or a further authorised review. The originating team sees the permitted progress and disposition. Closure, redirection and return include an intelligible reason, so staff can explain the next step without inferring it from a record that has simply vanished from a queue.

A missing acknowledgement is different from a refusal

An unavailable receiving system, a failed message and an unresolved identity match need different responses. Each produces an owned exception with the last confirmed state. Retried transfers reuse the original identifier to prevent duplicate referrals. An acknowledgement failure is investigated as a delivery or processing issue; it is not silently translated into rejection by the receiving service.

Network access also follows the task. A sending team may need confirmation that a referral has progressed without needing the full receiving record. Clinical urgency and prioritisation follow the provider's approved assessment process rather than being inferred from incomplete administrative fields. Where urgent action is required, the established clinical route remains explicit and separate from routine integration recovery.

The first handoff establishes the contract between services

The initial scope joins one sender, one receiver and one defined request type. Both teams agree on required fields, acknowledgement meanings and exception ownership before integration is enabled. Tests include duplicate transfers, missing data, an unavailable receiver and an ambiguous patient match. Staff rehearse recovery as well as ordinary acceptance.

Further services join by mapping their local processes to that contract. The implementation does not force every clinical pathway into identical steps merely to simplify a shared screen. New mappings are checked against access needs, source references and responsibility changes. Parallel reconciliation confirms that requests visible in the shared queue correspond to the records each service actually holds.

The receiving queue has an operational owner

The network process owner maintains the shared status definitions and handoff rules. Each service owns its receiving queue and the next action it accepts. Clinical and scheduling teams retain their respective decisions, information-governance owners manage access arrangements, and technical operations maintains transport and reconciliation. Escalation follows the responsible role.

Working reviews focus on unacknowledged requests, missing-information loops and records without a current owner. Repeated returns may indicate a source form problem rather than poor receiving performance. Changes to a service boundary require both a process agreement and the corresponding system mapping. Recovery actions retain an audit trail so staff can distinguish a corrected transfer from a newly submitted request.

The useful measure is where the request is waiting

Acknowledgement time and time without a next action are reviewed by service and request type. A network-wide average can hide one receiving queue where work regularly stalls. Missing-information requests are grouped by cause, making it possible to correct an unclear source field or an inconsistent receiving requirement rather than repeatedly chasing individual referrals.

Reconciliation checks the shared record against its sources, especially after outages and replays. Access reviews confirm that each role sees the administrative state it needs and that changed responsibilities do not leave old access in place. Staff can then locate a request, explain its position and identify the team able to move it forward.

The choices behind the solution

How the solution is evaluated

These measures define the evaluation criteria for the workflow, its controls and the quality of completed tasks.