skip to main content
iatroX JournalDiagnostic AI

Writing an Advice and Guidance Request: A Practical Guide for Consultant Connect, Cinapsis and Local Pathways

Featured image for Writing an Advice and Guidance Request: A Practical Guide for Consultant Connect, Cinapsis and Local Pathways

A good advice and guidance request makes the unresolved decision easy to see. The specialist should not have to infer whether you want diagnostic advice, interpretation of a result, a management suggestion or help choosing a referral route. Equally, a request is not complete until someone is responsible for acting on the reply.

Consultant Connect and Cinapsis, whose public descriptions were checked on 19 September 2026, support specialist communication and referral-related workflows. The locally commissioned service determines what is available, who responds and how the request is handled. A platform name is not a promise of a particular response time or an alternative to an urgent clinical pathway.

Lead with the decision, not the entire history

Before writing, complete one sentence: "I need help deciding whether..." That sentence should describe a decision within the recipient's scope. It might concern the next investigation, the interpretation of discordant findings or the most appropriate service to assess the patient.

Then establish whether asynchronous advice is appropriate. A patient needing urgent assessment should not wait because the electronic request looks complete. Follow the local escalation pathway and communicate directly when the situation requires it. The article's writing framework does not determine clinical urgency.

A request can be concise without being thin. Include information that changes the decision, and distinguish absent findings from findings that have not been assessed. "No relevant symptoms" is less useful than a brief account of which symptoms were actually considered.

A fictional request before editing

Consider this original educational example: "Please advise regarding abnormal blood results. Patient tired for a while. Repeat bloods similar. Does this need referral?"

The request sounds reasonable but leaves several questions unanswered. Which result is abnormal? How has it changed? What has been assessed? Is the question about urgency, further investigation or destination? What has the patient been told? The specialist may spend the first exchange asking for information already available to the sender.

The problem is not that the request lacks a long differential diagnosis. It lacks a defined decision and the evidence needed to address it. Adding several paragraphs of unrelated past history would make it longer without repairing that defect.

The same request after editing

A more useful structure would be: "Please advise on the next investigation and whether specialist referral is appropriate for persistent fatigue with the specified abnormal result on two dated samples. The relevant history, examination findings and completed investigations are attached below. I have not established the cause. The patient is currently being managed through the described local pathway, and the requesting team will communicate the advice and arrange the agreed next step."

In a real request, replace the descriptive placeholders with the actual findings and dates in the approved clinical system. They are deliberately not invented here. Include why the proposed next step is uncertain, such as a result that does not fit the initial interpretation or a local pathway that does not address the particular circumstance.

This version tells the recipient what to answer. It also prevents the act of sending advice from being mistaken for transfer of care. The GMC's continuity and delegation guidance, checked on 19 September 2026, emphasises sharing necessary information and clarifying responsibility when care passes between clinicians or teams.

Build a small evidence packet

Use an ordered account rather than an unfiltered record dump. State the current problem, relevant background, findings, investigations and treatments already tried where they affect the question. Identify the dates of results and whether a document contains historical or current information.

For images or attachments, follow the approved local pathway and the service's requirements. Check that the attachment is the intended document, legible and linked to the correct patient. Do not move clinical photographs into personal messaging or a general AI workspace to make the request easier to draft.

One useful editing test is to remove a sentence and ask whether the recipient's decision would change. If not, it may belong in the record rather than the main request. Keep essential negative findings, however, because an apparently reassuring omission is not the same as an assessed negative.

Make the question answerable

Avoid asking for "management advice" when the specific uncertainty is whether one further investigation should precede referral. Conversely, do not force a narrow question if the case has become too complex for a single asynchronous answer. A request for help determining the appropriate assessment route may be more honest.

Separate your working interpretation from confirmed facts. "I suspect this reflects..." tells the specialist how you are reasoning. Presenting the same suspicion as an established diagnosis can anchor the exchange incorrectly.

It can also help to state the practical constraint: a test is unavailable locally, the patient has declined a proposed intervention, or a previous service has not accepted the referral. Report the constraint neutrally and explain what decision it creates. Do not use it as a reason to omit necessary assessment.

Plan the reply before pressing send

Decide where the response will arrive, who will review it and what happens during absence. Record how the patient will hear the outcome and how outstanding actions will be tracked. If the response recommends referral, confirm whether the platform has actually initiated one or merely advised the sender to do so.

After reading the reply, reconcile it with any change in the patient's circumstances. Advice based on yesterday's information should not be applied mechanically when today's problem is different. Clarify ambiguous instructions rather than translating them into a definitive plan without checking.

Where iatroX can help, and where it cannot

This guide is published by iatroX and includes its reference tools as a complement to specialist communication. The September 2026 product brief describes free Ask-iatroX access for source-linked clinical questions. That can support background understanding or help identify the knowledge gap behind a request, using a non-identifiable educational formulation.

iatroX is not the receiving specialist, referral service or local advice pathway. For an unresolved patient-specific decision, use the commissioned service and appropriate clinical supervision. For the learning that follows, explore the reasoning and retain a genuine professional development record rather than treating the specialist's reply as an answer to memorise.

Frequently asked questions

Should an advice request contain the whole medical record?

Usually the main request should contain a focused, decision-relevant account, with appropriate supporting information available through the approved system.

Does sending advice and guidance transfer responsibility?

Do not assume so. Clarify the local workflow and who will review the response, contact the patient and complete the next action.

Can iatroX send a specialist advice request for me?

This article does not establish a referral or specialist-advice integration; iatroX is included for background reference and learning only.

Prepare a focused clinical learning question →

Back to Journal