A patient asks, “Has my referral gone through?” The clinic may know it was sent while the receiving service is still reviewing it. A helpful answer explains the administrative state without guessing about triage, urgency or an appointment date.
Use one authoritative record, five states, an owner and a checkpoint. Clinical decisions remain with qualified staff.
Check the authoritative referral record first
Start with the referral or booking system the clinic has designated as the source of truth. A message thread can preserve the patient’s question and the team’s reply, but it should not silently become the referral record.
Verify the patient using the clinic’s approved process, then check the referral identifier, destination, date sent, latest state, required action and update time. Do not infer “received” from a sent email.
Current NHS England e-Referral guidance distinguishes referrals requiring booking, waiting for triage, waiting for provider booking and booked appointments. Follow local approved terms.
Keep five referral states separate
“In progress” hides who has the referral and what must happen next. A small status model makes replies more precise.

- 1SentConfirm only the sending step.
- 2ReceivedConfirm the receiving record.
- 3ReviewDo not predict the outcome.
- 4ActionName the documented next item.
- 5AppointmentSeparate an offer from a booking.
| State | What the clinic can confirm | What it must not imply |
|---|---|---|
| Sent | The referral left the authorised sending route | The receiving service accepted it |
| Received | The receiving service recorded it | A clinician has reviewed or approved it |
| Under review | The documented review or triage step is open | The outcome, priority or appointment date |
| Action needed | A specific documented item or decision is outstanding | That the patient caused the delay |
| Appointment available or booked | An offer exists, or a time is recorded | That an offer and a confirmed booking are the same |
Keep each system’s official labels in the authoritative record, then translate them into careful patient language. The NHS patient service, for example, separates eligible first referral appointments from later appointments managed by the provider.
Build the update from four facts
Each reply needs the verified state, the next owner, the next checkpoint and what the patient should do now. If no action is required, say so.
For example: “The referral record shows that the specialist service received it on Monday. Their review is still open. Our referral coordinator will check the record again on Thursday and update you by 3 p.m. You do not need to send anything now.”
That is more useful than “please wait” and safer than predicting an appointment. If an item is missing, name only the approved administrative item and its secure route. Follow the clinic’s administrative and clinical routing boundary for symptoms, urgency or treatment.
Give every open referral one owner and checkpoint
The owner does not decide clinical priority. They own the next administrative check and update. Record the identifier, verified state, source, next action, team and promised reply time.
A shared inbox can make ownership and handover visible on supported, configured channels. It does not read the referral system, perform triage or book an appointment by itself. Test any configured state sync and keep the clinical or booking system authoritative.
Use the lost-enquiry workflow when responsibility moves. Keep the promised checkpoint attached so the next team knows what was said.
Keep referral, authorization and booking decisions apart
A referral can be received while insurance authorization remains pending. Authorization can be approved before an appointment exists. An appointment offer can expire without changing the clinical referral decision.
Use the prior authorization status guide for payer decisions and the waiting-list confirmation process for released offers. One positive state is not proof of another.
Handle confirmed appointments, changes and cancellations through the appointment reply workflow. A preference is not a booking.
Protect privacy and clinical boundaries
Use only the information required to coordinate the referral. Keep notifications neutral. Do not paste diagnoses, referral letters or results into support. Follow applicable privacy rules and the UAE Government data-protection overview where relevant.
General messaging is not the route for assessing deterioration or emergencies. Use approved urgent instructions and a qualified clinical path. A coordinator can explain the record, not reinterpret a clinical decision.
Measure whether uncertainty is being managed
Count referrals without an owner, missed checkpoints, pending actions, repeat contacts and replies that did not match the authoritative state. Review each mismatch.
Do not treat a fast first reply as proof of improvement. The useful outcome is a truthful state, a visible owner and a completed next action.
Frequently asked questions
Does “referral sent” mean the hospital accepted it?
No. It confirms only that the authorised sending step was recorded. Check the receiving service’s record before saying it was received, accepted or reviewed.
Can reception tell a patient when the appointment will be?
Only when the authoritative booking record supports a date or an approved estimate. Otherwise, give the current state and the next honest checkpoint.
What if the patient says their condition has changed?
Do not answer that as a routine status enquiry. Follow the clinic’s approved clinical escalation or emergency route and preserve only the minimum administrative handover information.
Want help applying this guide?Ask the DripTell team
From reading to action
Want help applying this to your business?
Share your details. We will read the article you are on and start with a useful answer for your team.
DripTell Editorial
Practical guidance reviewed by the DripTell product and customer workflow team.
See how DripTell checks product claims, uses primary sources and handles corrections.
Editorial and source policy



