What should a GP practice do when an urgent referral is rejected?

A rejection is a new clinical handover, not a closed task

A GP sends an urgent referral. The receiving service rejects it because it was sent to the wrong clinic, lacks required information or uses the wrong digital form. The message returns to a worklist. If the practice files it as administrative correspondence, the patient may believe a hospital appointment is being arranged while no provider has accepted the referral. The immediate work is to understand the rejection, reassess the person's clinical risk and establish a confirmed next step.

NHS England's e-Referral Service guidance explains that a referral can remain on an awaiting booking or acceptance worklist and that a receiving provider may reject an appointment with advice or redirect it to a more appropriate service. A status of awaiting acceptance is not proof the provider has reviewed and accepted the referral. NHS England's primary care patient safety strategy uses referral failures to illustrate harm when urgency, communication or follow-up breaks down. The practice needs a process that does not equate “sent” with “accepted” or “patient seen”.

Open the rejection message and original referral promptly. Record when it was received, who reviewed it, the stated reason and whether the message gives a suggested route. Check the patient's current condition and the original reason for urgency. If symptoms have worsened, the clinician may need a more urgent pathway than the original referral. A booking issue must not displace a clinical assessment. If the patient needs immediate emergency care, use the appropriate emergency route and direct communication.

This page owns a referral that has been returned, rejected or redirected after an urgent GP decision. A patient who simply has no appointment yet may be part of the same owner if the problem is a failed handover. The GP clinical-system outage draft owns system downtime and its transaction reconciliation. The GP test-results backlog draft owns laboratory-result queues. The broad Complys GP compliance guide retains general CQC readiness.

Find out what actually happened to the referral

Check the route and status in the system used. Was an appointment booked and then rejected? Was the request never submitted because an attachment failed? Did the receiving service return it for more clinical information? Did a triage team advise a different specialty or a diagnostic test first? The response depends on which handover failed. A patient can have an electronic reference number yet no accepted appointment. Keep the message thread, status history and relevant call notes available to the clinician.

Compare the original referral with the clinical record. Confirm patient identifiers, urgency code, intended specialty, reason for referral, relevant examination and investigation results, attachments and safety-netting advice. A referral marked urgent in free text but routine in the electronic priority field can be triaged differently from what the GP intended. NHS England's patient safety strategy describes a case where an urgent letter was paired with a routine e-referral, and the practice did not know the patient was not being seen urgently. The lesson is to verify the actual route and priority transmitted, not just the clinician's draft letter.

Do not silently assume that the receiving service is at fault. The wrong form or missing information may have been supplied by the practice. Equally, a rejection may reflect a service configuration or local pathway problem. Record the facts without delaying care while parties assign blame. Ask the receiving service for clarification through an approved route when the message is unclear. Note the name, role, time and advice given. A telephone conversation is useful only if the next clinical action and accepting service are clear afterward.

Separate a return for information from a clinical rejection

A request for a missing document may be resolved by supplying it, but the practice should still verify that the referral remains live and the original urgency has not been lost. A clinical triage rejection may require a new assessment, alternative service or direct discussion between clinicians. An administrative rejection due to a wrong location or form should prompt a corrected submission and receipt check. Do not treat every rejection as “send the same letter again”. Repeating an invalid route can create another delay.

If a service redirects the referral within the e-Referral Service, establish whether it has actually done so and whether the receiving service has accepted it. A note saying “please redirect” may place the task back with the referrer. If the receiving provider offers advice rather than an appointment, the GP must interpret that advice in light of the patient's condition. Where the advice does not resolve the clinical concern, seek clarification or escalate through the local pathway. Keep the clinical decision, not just the administrative action, in the patient record.

Reassess urgency before choosing another route

The original referral may have been urgent because of symptoms, examination findings, test results or a suspected serious condition. Time has passed since it was sent. Ask whether new symptoms or information make the need more urgent. A clinician should review the patient record and, where needed, contact the patient for a fresh assessment. Do not let an administrator choose a routine substitute because the urgent electronic option is unavailable. The clinician should approve the destination and priority.

Follow the exact pathway for the suspected condition. Urgent suspected cancer referrals have specific national and local rules. NHS England's cancer waiting-times monitoring guidance says that urgent suspected cancer referrals received outside e-RS should not be rejected merely for using another route in the interests of patient safety, and it describes agreed local protocols between referrers and providers. This is a particular pathway rule. It should not be stated as a universal ban on rejecting any referral for any service. Confirm the current cancer pathway and local escalation contact before acting.

Where the referral was to a different urgent service, such as community response or diagnostics, its own acceptance and redirection rules apply. Do not borrow a cancer pathway deadline for a non-cancer referral. Record the clinical target and the basis for it. If the receiving service cannot accept the patient, discuss an alternative with the appropriate clinician or coordination team. In some cases the safe next step is direct same-day assessment. In others it is a corrected electronic referral with documented monitoring. The article cannot set a universal waiting time because clinical urgency differs.

Consider the patient's ability to navigate the alternative. A change of service may mean a different location, telephone number, portal or appointment process. A patient with language, disability, transport or digital access needs may require extra support to complete the handover. Do not simply tell the patient to “rebook online” if the practice knows that route will not work for them. The responsible team should make reasonable arrangements under its local access procedures and record them.

Send the corrected referral and confirm receipt

Prepare a corrected referral that states the clinical question, urgency, relevant history and supporting information clearly. Include the rejection reason and how it has been addressed where useful. If the receiving service asked for a specific test result or form, verify that the attachment is complete and legible. A file name on an upload screen does not prove the content arrived. The clinician should confirm that the urgency selected in the digital field matches the written letter.

Submit through the approved route. Record the receiving organisation, service, method, reference number, date and time. If sent by an exceptional route, follow the local protocol and obtain confirmation. Do not use personal email or informal messaging for identifiable clinical information. If the original referral remains live, avoid duplicate bookings by clarifying whether it should be withdrawn, amended or redirected. A duplicate can confuse triage and the patient, while withdrawing the wrong request can erase the only active pathway.

Check acceptance. This may mean reviewing the e-RS worklist, receiving an acknowledgement, speaking to the service or confirming an appointment, depending on the pathway. A submission receipt and a clinical acceptance are different facts. Keep a named task open until the practice has evidence that the next provider has taken the handover or an alternative clinical plan has been agreed. If acceptance is delayed beyond the clinical plan, escalate rather than waiting for the patient to chase.

Define who owns the gap between providers

The receiving service has responsibility for clinical review of referrals presented to it, as NHS England's e-RS guidance explains. Once a referral is rejected or returned, the GP practice still needs to respond to the message and protect the patient while arranging the next step. The exact responsibilities can depend on the pathway and contractual arrangements. Avoid broad claims that one side owns all care until a specific system status changes. Instead, document the immediate clinical owner and confirm the accepting service through direct handover.

If the rejection arrived on a shared inbox, assign it to a named clinician or referral coordinator with clinical escalation. Staff absence must not leave the message in an unmonitored worklist. The task should show whether clinical review, patient contact, corrected submission and acceptance have each been completed. Closing the inbox item after forwarding it to a GP may hide the fact that no new referral was made. Use a handover rule that preserves an open owner until the receiving clinician accepts the task.

Tell the patient what has changed

The patient may believe an appointment is already arranged. Explain that the original route has not been accepted, what the practice is doing, who will contact them next and what symptoms require urgent help meanwhile. Use clear language that matches the clinical plan. Do not describe the referral as “cancelled” if it was redirected and remains active. Do not promise a date the receiving service has not confirmed. Record the conversation and any communication needs.

Ask whether the patient has received messages from the service or has already booked an appointment. Their information can reveal a status that has not reached the practice, but it should be verified through the service when necessary. If the patient cannot be contacted, choose a contact and escalation plan based on urgency and vulnerability. An unanswered text is not adequate evidence that the patient understands a change to an urgent pathway. There is no universal number of attempts that closes every case.

If the corrected pathway takes longer, discuss interim care. The GP may need to review symptoms, arrange appropriate tests or give safety-netting advice while awaiting specialist assessment. Those steps require a clinical decision for the individual patient. The practice should not treat “hospital referral pending” as a reason to leave an evolving condition without monitoring. Document what the patient should do if symptoms change and when the practice will reassess if no appointment arrives.

Keep the patient informed when responsibility changes. A referral may be accepted but then re-triaged to a different service. Where the practice receives that message, it should update its record and determine whether the new route matches the clinical concern. A patient should not have to reconcile conflicting messages from the GP, referral service and hospital alone. Agree a single contact point for questions where the pathway is complex.

Monitor urgent referrals until a meaningful handover

Create a worklist that distinguishes sent, awaiting booking, awaiting provider acceptance, rejected or returned, redirected, accepted and patient seen where those states are available. Each state supports a different action. Do not mark a referral complete when the letter is typed or when the electronic request is submitted. Set a review date based on clinical urgency and the local pathway. Escalate a referral that remains unresolved rather than allowing it to age invisibly.

Look across the worklist for repeated rejection reasons. A wrong online form may affect many patients, especially after a pathway change. Missing attachments may point to a template or training problem. A specialty that regularly rejects appropriate referrals may need a joint discussion with the provider or commissioner. Count the patients affected and assess whether any need urgent review. A process fix should include existing open cases, not merely prevent future errors.

The practice can test its safety net by sampling recent urgent referrals. Can it show the original decision, actual urgency field, submission, provider response, patient communication and final accepted route? If a sample shows uncertainty, search for similar cases. A clean average referral turnaround time can hide a few serious outliers. The incident corrective-action owner can help test whether a changed form, worklist or handover rule prevents recurrence.

An older CQC inspection report describes a GP service with referral monitoring failures and reliance on patients to chase missed referrals. It is a historical example, not current law or evidence about this practice. Use it to test the question: would the team know that an urgent patient has no accepted pathway without the patient calling? If the answer is no, the safety net needs repair.

Assess any delay or harm separately

If rejection caused a delay, review the patient's condition and determine whether the delay created a patient safety event. Use the practice's reporting and learning process. If harm may have occurred, assess the relevant duty-of-candour and CQC notification criteria on the facts. Do not wait for a final specialist diagnosis before making an urgent clinical response. Equally, do not state that every rejected referral automatically meets a statutory notification threshold.

Preserve the referral history, rejection message, contacts, clinical reassessment, new submission and provider acceptance. Keep patient details in approved clinical systems. A governance summary can record the event, learning and action without copying the full referral into a broad compliance folder. If an external service contributed to the failure, coordinate the review and share relevant information through an approved route. A joint systems issue needs more than a local reminder to staff.

When the immediate patient is safe, ask why the failure was not caught sooner. Did the worklist go unreviewed during staff leave? Did the clinician use an old form? Did a patient-facing message imply acceptance too early? Did the receiving service change criteria without an accessible update? Assign fixes to the process that failed. Then test a new referral through the corrected route and audit the next set of returns. “Staff reminded” is not evidence that the handover now works.

A practical rejection response record

The following record can support a real-time response:

This is a decision aid. The urgency, pathway and escalation must come from the patient's clinical circumstances and the current service rules. A practice should not use it to impose a fixed response time on all specialties. Keep enough detail for another clinician to take over if the original referrer is absent.

Use Complys for governance evidence within its product boundary

The Complys GP and clinic page describes a compliance layer alongside clinical and patient-record systems. Subject to actual configuration, a practice could use it to assign review of a referral-process failure, track corrective actions, retain audit evidence and remind an owner to test the new process. The live patient referral, clinical decision, identifiers and acceptance status should remain in the approved clinical and referral systems. This draft does not claim that Complys reads e-RS, monitors individual referrals or sends clinical messages to receiving providers.

The governance tool can record an aggregate issue such as repeated form rejection and its fix. It should not become the only place where a named patient's urgent referral is followed. A restricted link or reference can connect governance learning to the clinical incident for staff with appropriate access. Verify both the product capability and local permission model before using that workflow. A reminder does not prove that the receiving service accepted a referral.

CTA: Review how Complys can assign referral-process improvement actions and preserve audit evidence, while patient-level tracking stays in approved GP and referral systems. Related tool opportunity: An urgent-referral return decision log for clinicians and referral coordinators. Validate its fields with local e-RS, cancer and specialty pathways before release. Internal links out: GP clinical-system outage; GP test-results backlog; incident corrective-action effectiveness. Internal links in proposed: Broad GP CQC guide, future GP referral tracking page only if a separate intent is validated, GP continuity owner and clinical correspondence owner if approved.