The Summary That Arrives Too Late
Ask a primary care physician what happens after their patient is discharged and the answer is a familiar complaint: the summary arrives days after the follow-up visit — or never — and the phone call that replaces it reconstructs the hospitalization from memory. The discharge summary is the most important document the hospital produces, and the one most likely to be incomplete, late, or addressed to nobody in particular.
This template rebuilds the handoff as a structured record with a defined reader: the clinician who receives the patient next. Every field exists because that reader needs it in the first week after discharge.
What the Receiving Clinician Needs, Field by Field
| Section | Why the next clinician needs it |
|---|---|
| Patient identifiers — name, date of birth, medical record number | Matches the summary to the right chart, unambiguously |
| Discharge diagnosis and comorbidities | The one-line reason this hospitalization happened |
| Procedures performed | What was done to the patient, with dates |
| Reconciled medication list | The single highest-risk field in the document |
| Pending results | Tests still outstanding, and who chases them |
| Follow-up appointments — date fields | What is booked, and what the receiving team must book |
| Attending physician contact | A phone number for the clinical question that will come |
The pending-results row deserves emphasis: an unowned pending culture is a patient silently lost to follow-up. Name the chaser or remove the row.
Medication Reconciliation Is Its Own Discipline
Most post-discharge harm traces to the medication list. The structured section should capture every discharge medication with dose, frequency, and route — and, critically, the disposition of every pre-admission medication: continued, changed, or deliberately stopped. An open text field per change decision gives the receiving prescriber the reasoning, which is what turns a list into a reconciliation. Adherence aids — a photographed pill card through file upload, or a printed schedule — attach to the same record.
Follow-Up Ownership, Stated
Every discharge generates appointments, and every appointment needs an owner: which follow-up the hospital booked, which the primary care team must arrange, and by when. Structured date fields make the calendar explicit and the gaps visible — a specialist review the hospital assumed the family doctor would book is exactly the kind of failure this section prevents.
Routing the Record
Completed summaries flow to the receiving practice through webhooks or export — arriving before the follow-up visit, which is the entire point. Within the hospital, organization roles keep clinical summaries visible to the treating team while administrative staff handle volume without opening records. Standard discharge documentation pairs with the wider healthcare forms collection.
Frequently Asked Questions
Who completes the summary — physician or nurse?
Clinical content is the physician’s; the structured fields make delegation safe. A resident or pharmacist can complete identifiers, medications, and appointments from the chart, with the attending attesting to the clinical narrative.
How is this different from the EHR's discharge summary?
It produces the same artifact with discipline the EHR template often lacks: reconciled medication decisions with reasons, owned pending results, and follow-up ownership stated. Many teams complete this first, then paste into the EHR — the structure improves the source document.
What about patients discharged against medical advice?
The summary matters most for them and gets completed least. Keep a short version — diagnosis, medications issued, follow-up recommended, risk discussed — as a duplicate of the master, finishable in three minutes.
Does the patient ever see this document?
The receiving clinician is its reader; the patient needs their own plain-language instructions, which belong to a separate patient-facing document. Conflating the two produces a summary that serves neither audience well.