Discharge summary in plain language

Rewrites clinical discharge summaries into plain-language patient instructions without altering clinical facts.

49|11|Updated Jul 31, 2026
One-click install
npx skills add https://github.com/vstorm-co/agenticos --skill discharge-summary-in-plain-language-vstorm-co
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Discharge summary in plain language
Source: https://github.com/vstorm-co/agenticos/tree/main/backend/app/core/catalog/skill_gallery/healthcare/discharge-summary-plain-language
Command: npx skills add https://github.com/vstorm-co/agenticos --skill discharge-summary-in-plain-language-vstorm-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Hospital discharge summaries are written for clinicians, not patients. Patients go home with documents full of abbreviations and terminology they cannot act on, which leads to missed medications, ignored warning signs, and skipped follow-ups. This Skill produces a patient-readable version of the same summary while preserving every clinical fact. ## Core Features & Use Cases - Terminology translation: Expands abbreviations and replaces clinical jargon with everyday words, keeping the clinical term in brackets on first use. - Fact preservation: Never drops or rewords a number, date, dose, or name, and flags ambiguous source content for a clinician instead of guessing. - Patient-ordered structure: Organizes output as what was wrong, what was done, what to do now, what to watch for (with exactly who to call), and follow-up arrangements, plus the often-missing guidance on driving, lifting, bathing, and returning to work. - Use Case: A ward clinician pastes a discharge summary for a post-surgical patient and receives a version the patient can read at home, with medication changes, wound care steps, and a clear distinction between "ring the ward" and "go to A&E". ## Quick Start Rewrite the attached discharge summary in plain language for the patient, keeping every clinical fact, dose, and date unchanged.

Frequently Asked Questions about Discharge summary in plain language

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I rewrite a discharge summary in plain language for patients?▼

Provide the clinical discharge summary and ask for a plain-language version. The output expands abbreviations, replaces terminology with everyday words, and reorders content into what was wrong, what was done, what to do now, warning signs, and follow-up.

Does plain-language rewriting change clinical facts or medication doses?▼

No. The rewriting rules prohibit dropping or rewording any number, date, dose, or name. Medications are never omitted even if unchanged, and warning signs are never softened.

What happens when the discharge summary is ambiguous?▼

Ambiguous source content is marked for a clinician to resolve rather than interpreted. The Skill never picks a reading of unclear clinical text, so the patient version stays faithful to the verified record.

What sections should a patient-friendly discharge summary include?▼

Five sections in patient priority order: what was wrong in one sentence, what was done, what to do now (medications, wound care, restrictions), what to watch for with exactly who to call, and follow-up details including who arranges it.

When should a patient call the ward versus go to A&E after discharge?▼

The rewritten summary makes this distinction explicit for each warning sign, stating exactly who to call in each case. The difference between ringing the ward and going to A&E is made unmissable rather than left implied.