How to Write a Discharge Summary: Format, Template, Examples

A dependable structure runs from identification through to follow-up, in the order the reader needs it rather than the order events occurred. Put the reason for admission and the final diagnosis near the top; put the hospital course in the middle; put actions — medications, follow-up, pending results, warning signs — at the end where they will be looked for.

Keep the headings identical across every speciality in the hospital. A GP who receives summaries from your cardiology, surgical, and paediatric units should find the medication list in the same place every time. Specialty-specific content belongs inside a section, not as a rearrangement of the whole document.

The template below is deliberately conservative. Most hospitals do not need a novel format; they need the standard one filled in properly and consistently, which is a considerably harder problem.

More discharge harm originates in the medication section than anywhere else, and almost all of it comes from ambiguity rather than from a wrong drug. The summary must state, for every medicine, the generic name, strength, dose, route, frequency, and duration or a clear instruction to continue. Trade names alone and abbreviations that could be misread do not belong in a document leaving the hospital.

More importantly, the list must show what changed. A list of current medications without indicating which were started, stopped, or altered forces the next clinician to reconstruct the reconciliation from memory of the pre-admission list, which they may not have. Mark each line as continued, new, dose changed, or stopped, and state why for the stopped and changed ones.

Time-limited medicines need an explicit end date, not a duration the patient has to calculate. Antibiotics continued indefinitely because the summary said seven days without saying from when is a familiar and entirely preventable problem. HealUDoc discharge workflows can carry the reconciled list forward from the inpatient medication record so the summary reflects what was actually administered rather than a separately typed version of it.

Every admission ends with loose ends: a culture still incubating, a histopathology report awaited, an imaging study reported after discharge, a referral requested but not yet dated. These are the items most likely to be lost, because the team that ordered them has handed over and the team receiving the patient does not know they exist.

The summary needs an explicit section listing what is outstanding, who is responsible for chasing it, and what should happen depending on the outcome. Naming the responsible party matters — a pending result with no owner is an orphan. Where the hospital will follow up, say so and say how the patient will be contacted; where the GP is expected to follow up, say that plainly.

This section also protects the hospital. A documented, communicated handover of a pending result is a materially different position from a result that arrived after discharge and was never actioned by anyone.

Follow-up instructions fail when they are written as intentions rather than appointments. Review in two weeks is an intention. Review on the fourteenth at the cardiology clinic, appointment booked, bring this summary and the medication box, is an instruction. Where the appointment can be booked before discharge, book it and print it on the document.

Warning signs deserve their own short block in plain language, and they should be specific to this patient's condition rather than generic. What symptoms mean return immediately, what mean call the clinic, and which number to call at three in the morning. Two or three concrete items beat a paragraph of hedged advice.

Write this section, and ideally the whole patient-facing portion, at a reading level that does not assume clinical training, and provide it in the language the patient actually speaks. A perfectly written English summary handed to a family who read only the regional language is a compliance artefact, not a communication.

A good summary is easier to write when the system assembles the invariant parts. Identifiers, dates, procedures performed, the administered medication record, and results already in the system should be pulled in automatically, leaving the clinician to write the parts that require judgement: the hospital course, the reconciliation reasoning, and the plan. HealUDoc can draw those elements from the encounter record so the clinician is editing a partly assembled document rather than starting from an empty form.

Resist the temptation to auto-populate the narrative. Summaries generated by concatenating progress notes produce documents that are long, internally contradictory, and unread. The value of the summary lies precisely in a clinician deciding what mattered, and that decision cannot be automated away.

Build in blocking checks for the small number of things that must never be missing: a final diagnosis, a complete medication list with change status, and either a follow-up plan or an explicit statement that none is required. Everything else can be a soft prompt. A form with thirty mandatory fields produces thirty perfunctory entries.

Timeliness is the easiest measure and a reasonable proxy: the proportion of summaries completed before the patient physically leaves. A summary that reaches the GP three weeks later has been overtaken by events, however well written.

For content quality, sample rather than measure everything. Take a small number of summaries per unit per month and have a clinician who was not involved in the case answer three questions: could you safely take over this patient's care from this document alone, is the medication list unambiguous, and is it clear what is outstanding and who owns it. Those three questions find more real problems than a twenty-item checklist.

Feed the results back to named units with examples, including good ones. Clinicians respond far better to seeing a well-constructed summary from a colleague than to a score, and the good examples become the de facto house standard more effectively than any policy document manages.