Pathways and documents

Clinical Documentation

Discharge summaries, referrals and patient letters

Clinical Documentation turns a clinician's notes into a draft for revision and signature: a discharge summary, a referral or clinic letter, an SBAR handover, or a plain-language letter for the patient. It draws only on what has been entered, leaves a labelled blank where a detail is missing rather than guessing, and keeps uncertainty exactly as the notes express it. A short list of problems found in the notes follows, with safety issues at the top.

Who it is for

  • Residents and house officers writing discharge summaries at the end of a busy shift
  • Registrars and consultants drafting referral and clinic letters that need the question and the urgency at the top
  • Clinicians who want a version of a letter for the patient that carries the same facts as the clinical letter

What it does

  • Nothing added to the notes

    Draws only on what is entered. If a date, dose or result is absent, the draft shows a labelled gap, such as [date of procedure] or [antibiotic end date], instead of a plausible guess, so nothing unverified reaches the reader.

  • Identifiers left blank

    Leaves the patient's name, date of birth and hospital number, and the author's name and designation, as bracketed fields to complete from the hospital record, even when they appear in the notes.

  • Discharge summaries for the next clinician

    Leads with the diagnoses, then the course problem by problem, procedures and the patient's state on leaving. Each medicine is labelled as started, altered, unchanged or discontinued, with why; allergies, outstanding results, follow-up and tasks for the GP come next.

  • Referrals that lead with the question

    Puts why the patient is being referred, how soon, and exactly what is being asked of the specialist in the opening lines, followed by the relevant history and findings, investigations, medicines, allergies, treatments already tried, and what the patient understands and wants.

  • Handovers and clinic letters

    Handovers follow the SBAR pattern and end with jobs still to do and when to escalate; clinic letters put the diagnoses and plan first and assign each action to a named person or team.

  • Checks before sending

    After the draft comes a short list of problems found in the notes: gaps it could not fill, a prescribed drug that clashes with a recorded allergy, a pending result nobody owns, or a possible interaction, with safety issues first.

How it works

  1. Name the document and its reader, for example a discharge summary for the general practitioner or a referral to cardiology.
  2. Paste the notes: diagnoses, course, results, medication changes with reasons, follow-up and the advice given about when to seek help.
  3. The engine drafts the document in the structure that type of document needs, keeping 'possible', 'probable' and 'confirmed' exactly where the notes put them.
  4. Missing details appear as labelled blanks, and identifiers are left for the hospital record to fill.
  5. A list of checks follows the document; references are added only where the engine has contributed clinical advice of its own.

What to include

  • The type of document and who will read it
  • Your notes: diagnosis, course, results and plan
  • Medication changes with reasons
  • Follow-up and what to do if things worsen

Example cases

  • Write a discharge summary: 5-day admission with community-acquired pneumonia, CURB-65 of 2, IV co-amoxiclav then oral, new AF started on apixaban, follow-up chest X-ray in 6 weeks.
  • Draft a referral to cardiology for exertional chest pain with a positive family history, normal resting ECG and LDL 4.9 mmol/L.
  • Explain a new diagnosis of type 2 diabetes and starting metformin in plain language for the patient.

What the report contains

  1. The drafted document, titled by type
  2. Checks Before Sending
  3. Key Evidence & References, only when clinical advice has been added
  4. Square-bracketed blanks for missing details and identifiers

Limits

  • Documents are drafted only from the facts supplied. Each one must be checked, completed and signed by the responsible clinician before it is sent.
  • The engine cannot see the medical record, so it cannot confirm that a dose, date or result matches what was actually given or reported; medicines reconciliation still has to be done against the chart.
  • Hospital templates, national conventions and legal requirements for clinical documents differ. The hospital's own format and policies apply, and a draft may need reshaping to fit them.

Frequently asked questions

What should a hospital discharge summary include?

Start with the main diagnosis and any others, then the important findings and tests, a short course by problem with procedures, and the patient's condition on leaving. List every medicine as started, changed, continued or stopped, with the reason, then allergies, results still awaited and who will chase them, the follow-up booked, clear tasks for the GP, and the warning signs the patient was told about.

How should a referral letter to a specialist be structured?

Open with why you are referring, how soon the patient should be seen, and the precise question for the specialist. Then summarise the history, the relevant findings and results, current medicines and allergies, the treatments already tried, and what the patient understands and prefers. A specialist triaging the letter should be able to judge its urgency from the first lines.

Does the engine put patient names or hospital numbers into the document?

No. Name, date of birth and hospital number appear as bracketed blanks even when they were typed into the notes, so that they are added from the hospital record. It is still good practice to de-identify a case before entering it, and the linked article explains how.

Can it produce a letter the patient can understand?

Yes. It can write a plain-language letter in short sentences without abbreviations, carrying the same facts as the clinical version. For fuller explanations, medicine instructions or a text in another language, the Patient Education engine is built for that job.