Digital healthcare can make the beginning of a care episode remarkably straightforward. A patient finds a clinician, books an appointment or purchases access to an investigation. The difficult work often starts afterwards: a result needs interpretation, a referral requires acceptance, a medicine needs monitoring or a message arrives after the original clinician has finished their session.
The key question is not who owns the patient. It is who has accepted responsibility for the next clinical action. That distinction matters whenever care crosses organisational boundaries. This article offers a practical framework for clinicians and practice owners, using current service examples checked on 18 October 2026 without implying that any named provider has failed to manage follow-up.
Follow-up is work, not an incidental extra
A consultation can generate tasks that outlast the booked appointment. Those tasks require time, appropriate information and someone with the authority and competence to act. A business model that prices only the visible encounter can leave the remaining work poorly resourced.
Describe the episode in terms of its intended endpoint. Is the service providing an assessment and a written opinion, arranging an investigation with result discussion, or managing a condition over time? Patients and clinicians may answer differently unless the scope has been made clear.
An endpoint should not be defined solely by an invoice or an appointment status. "Completed" in a booking system can mean that attendance was recorded, while several clinical tasks remain outstanding. The operating procedure needs to distinguish those meanings.
Delivery, review and action are different events
A report being sent does not establish that it has been received by the right person. Receipt does not establish clinical review, and review does not establish that the patient has been contacted or the agreed action completed.
The GMC's delegation and referral guidance emphasises clarity about tasks and the responsibilities of the people involved. For a digital pathway, the practical implication is to define what counts as an accepted handover rather than relying on a delivery notification alone.
Use separate task states where possible. A small practice might not need sophisticated software, but it does need a dependable method for identifying work awaiting review, work awaiting patient contact and work awaiting confirmation from another organisation.
Build a responsibility map before the pathway goes live
For each transition, identify the service that initiates the action, the intended recipient, the information required and the fallback if the recipient cannot accept it. Include the expected timing and a route for clarification.
This map should cover ordinary as well as exceptional cases. A routine report that is delayed for weeks can create a different problem from an urgent finding, but both require an accountable process. The absence of an urgent alert should not be mistaken for evidence that everything else has been completed.
Name the responsible team or role rather than relying entirely on an individual who may be absent. Then establish how the task reaches someone appropriately qualified when that person is unavailable. The aim is continuity, not a document that becomes unusable whenever the rota changes.
Imaging shows why the distinction matters
Scan.com's UK FAQ describes clinical review of imaging reports and contact with patients about findings and potential next steps. That describes a particular service component; it should not be extrapolated into an assumption about all future care. The published pathway needs to be read alongside the actual arrangements applying to the patient.
Consider a fictional patient who receives a report recommending specialist assessment. The clinician should clarify who explains the finding, who makes the referral and what happens while the patient waits. Sending a copy to another practice may be helpful, but it does not by itself settle those questions.
The same reasoning applies when a patient brings a report obtained elsewhere. Review the clinical information appropriately while clarifying which organisation has undertaken, or is being asked to undertake, the next step.
Advice-and-guidance is not necessarily a transfer of care
An opinion from another clinician can help the original team decide what to do. It does not necessarily mean that the adviser has accepted the patient into an ongoing service. That boundary should be understood before advice is sought and communicated accurately afterwards.
Consultant Connect's National Consultant Network is one example of specialist support involving advice and referral-related work. The responsibilities in an actual case depend on the commissioned service and agreed pathway, not the presence of an expert response alone.
A useful response should therefore be translated into an action plan by the responsible team. Identify which recommendations can be followed locally, which need clarification and which require a formal referral or another service that has not yet accepted the patient.
Messages need a service promise that can be delivered
A portal can make sending a message feel similar to speaking directly to a clinician. The practice should explain who reads messages, when the channel is monitored and what it should not be used for. Those explanations need to match staffing and escalation arrangements.
Do not allow a broad promise such as "contact us anytime" to imply continuous clinical review unless that is genuinely provided. A booking system may be available at all hours while clinical staff are not. The distinction should be visible before a patient submits a potentially urgent concern.
Test the process when a message arrives after a locum has left or when a clinician is on leave. The task should enter an accountable service workflow rather than remain in an individual inbox that nobody else can access appropriately.
Price the care episode honestly
Estimate follow-up effort when designing contracts and appointment fees. A specialist opinion that regularly requires further correspondence should not be modelled as a fixed number of minutes merely because the initial call is short.
For a fictional illustration, ten consultations occupying 20 minutes each take 200 minutes. If associated documentation and follow-up average another ten minutes each, the total becomes 300 minutes. Gross fees divided by the first figure overstate the effective return by ignoring one-third of the actual time.
The answer is not to avoid necessary follow-up. It is to make the scope, staffing and remuneration realistic. Patients should understand what is included, while clinicians should not discover after the event that an apparently bounded task carries an undefined ongoing commitment.
Audit failures of process, not just bad outcomes
A service should not wait for harm before checking whether its follow-up process works. Sample completed episodes and ask whether intended actions occurred, whether records show acceptance and whether the patient understood the plan.
Include near misses: a report sent to an outdated address, a referral returned without being noticed or a message found in the wrong queue. These reveal where the process depends on individual vigilance rather than a reliable system.
Learning tools can support reflection on clinical reasoning and communication, but should not become a repository for identifiable patient records. iatroX's CPD resources can sit alongside an appropriately de-identified learning process; they do not operate the practice's task-management or handover system.
Design the end of the episode as carefully as the start
At the end of an encounter, state what is known, what remains uncertain, what will happen next and who is responsible. Provide a suitable route for deterioration or a missed expected contact. Record the plan in terms another clinician can understand.
A platform is useful when it helps those responsibilities become clearer and easier to fulfil. It is less useful when a polished interface conceals an ambiguous boundary between organisations.
The sustainable version of digital care therefore includes the hidden work. It treats follow-up as part of service design, staffing and commercial evaluation rather than as an administrative afterthought once the appointment has been booked.
FAQs
Does sending a result to another practice complete a handover?
Not necessarily. The pathway needs clarity about receipt, review, acceptance of responsibility and the intended action. A delivery notification alone does not establish all of those steps.
Does specialist advice automatically transfer the patient's care?
No. Advice and transfer of ongoing care are different arrangements. The responsible team should understand the scope of the service and make any subsequent referral or action explicit.
How can a small practice improve follow-up without buying another platform?
Define responsibilities, use a shared accountable task process, provide absence cover and review outstanding work regularly. Reliable procedures matter more than adding software without an agreed operating model.