The person who ends a consultation is not necessarily the person who will see the next result. What matters is an explicit, functioning arrangement for review, action and communication. A test request, an automated message and a task sent to another inbox are different events; none should be treated as proof that the clinical follow-up is complete.
This original fictional case unfolds across several contacts. It is a teaching exercise, not a report of care, a legal allocation of responsibility or a clinician-reviewed assessment item. Pause at each stage and identify the information needed and the next action owner before reading the discussion.
First contact: the investigation is requested
A patient attends a planned clinic with a persistent symptom. The clinician documents a working explanation, requests an investigation and tells the patient that the result will be reviewed. The clinician is covering the clinic temporarily. Their note says, "Follow-up through usual team."
The patient leaves believing that someone will contact them. The usual team can see the consultation, but there is no explicit allocation of the pending result in the fictional record provided.
Before continuing, answer two questions. What has been arranged, and what has merely been assumed? The investigation has been requested. A follow-up intention has been expressed. The record does not yet establish a named review process, what the patient should expect or how the covering clinician's departure affects the task.
Do not solve the case by inventing a universal rule that a particular job title always owns the result. Establish the local arrangement and the responsibilities of the clinicians involved. The uncertainty itself is the problem to resolve.
Second contact: the result changes the question
The investigation report returns after the covering clinician has left. It describes an abnormal finding and recommends further clinical assessment. The report is placed in an inbox that is monitored, but the patient's existing appointment is with a different service.
The tempting administrative response is to forward the result to that service. Before doing so, ask whether the service has accepted responsibility for this issue and whether the existing appointment addresses it. A future appointment somewhere in the system does not establish that the new finding will be assessed appropriately.
The clinical task also needs attention. What does the report establish, what remains uncertain and how should the patient's current condition affect the next step? This fictional exercise does not provide the information needed to select a specific pathway or urgency. Those decisions require appropriate clinical review, not an administrative inference from the presence of an appointment.
Separate the tasks in the record: result reviewed, clinical interpretation made, further action determined, communication attempted and responsibility assigned. Combining them under "dealt with" makes it difficult to see what remains unfinished.
Third contact: the message was sent but not understood
A message asking the patient to contact the clinic is sent. The patient does not respond. Later, they explain that they saw a notification but thought it referred to an appointment already booked. Their symptoms have also changed since the original consultation.
At this point, a delivery status is not evidence of understanding. Nor does a lack of reply establish that the patient declined further assessment. The new symptom information needs clinical attention in its own right, rather than being treated as a reason to resend the same administrative message.
Ask what the service knows about the patient's communication needs and the agreed contact method. Use an appropriate alternative process where required and record what actually happened. The case does not support assumptions about motivation, adherence or the patient's ability to navigate services.
A useful revised explanation would make the purpose explicit: there is new information that requires discussion, it concerns this investigation, and this is the agreed route to the next assessment. The actual content and urgency must follow clinical review.
Fourth contact: the handover must transfer meaning
A clinician now hands the task to a colleague. "Please chase result" is inadequate because the result already exists. The unresolved work concerns interpretation, contact and arrangements for further assessment.
An original, more informative handover might say: "The investigation has been reviewed and requires this further action under the agreed clinical plan. The first contact attempt did not establish patient understanding. The patient has since reported a change that needs reassessment. Please confirm the next clinical contact and document who will review the outcome."
The wording is illustrative, not a template to paste without thought. It should contain the actual findings, urgency and responsibilities in a real case. Its value is that it distinguishes the work completed from the work still pending.
The GMC's continuity-of-care guidance, checked on 19 September 2026, addresses sharing relevant information and checking transfer of responsibility where practical. The case applies those principles without inventing a blanket responsibility rule for every service.
Build an action chain, not just a chronology
A chronology records what happened. An action chain adds what should happen next, who is responsible and how completion becomes visible. For each stage, record the trigger, interpretation, action, owner and evidence of completion.
In this case, the trigger is the returned report; interpretation requires clinical review; action concerns further assessment and communication; ownership must be explicit; completion requires more than a forwarded task. The same approach can reveal an unfinished step before it becomes lost among later entries.
Do not force every situation into an elaborate table. A clear, concise note may be enough. The aim is to preserve the decision and responsibility, not generate paperwork that obscures them.
Use the case for teaching without inventing product capabilities
Ask a group to review only the first stage, then reveal each later contact. Record which assumptions were reasonable, which were unsupported and which became outdated when new information arrived. Do not grade the first decision using facts revealed only at the end.
iatroX publishes this educational case. As described in September 2026, its Rounds, questions and relevant simulations can support case discussion and rehearsal. This article does not claim that the application runs a persistent multi-visit version of this fictional story or manages clinical results.
A clinical-reference question may help clarify background knowledge. It cannot confirm that a real handover was accepted or that a patient received a message. Those facts belong to the actual service and record.
Frequently asked questions
Does sending a task transfer clinical responsibility automatically?
Do not assume that it does. Check the applicable arrangement, the information shared and whether the receiving clinician or team has taken over the relevant task.
Is a delivered message evidence that the patient understood the plan?
No. Delivery and understanding are different, and a non-response may need investigation through the appropriate local process.
Is this a clinician-reviewed simulation from the iatroX library?
No. It is an original article-based teaching case, not a verified reproduction of a reviewed product case or a completed clinical assessment.