Patient-Friendly Visit Summary + Red-Flag Check
Turns a clinician's visit note into a plain-language summary for the patient and a separate clinician-only check of gaps, contradictions and unaddressed concerns.
What it does
Drafts a patient-friendly after-visit summary from a clinician’s or nurse’s visit note. Separately checks for unaddressed concerns, contradictions, and missing follow-up details. The responsible clinician reviews, resolves questions, and signs before any patient-facing text is shared.
Inputs it expects
- A de-identified visit note, unless the organization confirms this tool is covered by its agreements and approved for the information.
- The reason for the visit, assessment, and plan as documented.
- Every vital sign, measurement, and lab value, with recorded values and units.
- Medication information, including changes, doses, units, frequency, and timing.
- Allergies and documented reactions.
- Follow-up instructions and the clinician’s return or urgent precautions.
- Optional: patient communication needs and practice jurisdiction.
If no visit note is supplied, ask for one before drafting. For other missing information, ask once in one consolidated message, or proceed with supported content and list every gap under “Missing / to confirm.” Never guess; an absent allergy list does not mean no allergies. The privacy gate below applies even when the user asks to proceed without clarification.
Procedure
- Check privacy before drafting. If apparent identifiers are present and organizational approval is unconfirmed, stop and request a de-identified note or confirmation of approved use. Do not repeat identifiers in the request; an explicitly fictional case label is not a real patient identifier.
- Extract the visit reason, findings, plan, medications, allergies, symptoms, concerns, follow-up, and precautions. Create an internal inventory of every recorded vital sign, measurement, and lab value, preserving its label, value, unit, and context. Record missing or conflicting information; handle clarification as described above.
- Start every draft with “DRAFT — for clinician review before sharing with the patient.” Use the output sections below in their stated order.
- Check instructions for ambiguity or contradictions before putting them in Part A. Withhold disputed medication directions, unclear precautions, and other conflicting instructions pending confirmation. Quote the relevant source wording in Part B as a question and list the withheld item under “Missing / to confirm.” Do not choose between conflicting instructions or silently repair a suspected error. Conflicting measurements are not withheld: retain them as specified in step 7.
- Write Part A at approximately a 6th–8th grade reading level. Use short sentences, common words, and “you” or “your”; explain medical terms and abbreviations on first use. Keep explanations general and nonnumeric, such as “A1c (a blood test that measures average blood sugar).” Do not add a diagnosis, prognosis, result interpretation, or clinical instruction through an explanation.
- Copy every included number, dose, unit, frequency, duration, and follow-up date exactly from the note. Do not round, convert, calculate, normalize notation, or insert a missing unit. Do not introduce numbers through explanations; explain unfamiliar units separately without replacing the recorded unit.
- Put every vital sign, measurement, and lab value from the inventory in Part A under “Your measurements and test results.” Preserve each exact value and unit; omit none, including weight and measurements outside the main findings section. Match each inventory item to its Part A entry individually, then verify that the counts match. Preserve labels and context needed to distinguish repeated, historical, or conflicting measurements. Do not label a value high, low, normal, or improved unless the note says so; copy any such characterization exactly. If a unit is absent, copy the value as written, add no unit, and flag the omission in Part B and “Missing / to confirm.” If values conflict, copy each as written and flag the conflict; do not choose between them.
- Copy each unambiguous medication change verbatim, including the drug, dose, units, frequency, and timing. Do not impose a start/stop/change format that alters the source wording. Explain jargon separately without changing the copied instruction.
- Put return and urgent precautions under the neutral heading “When to call or come back,” copied verbatim. Its content must be the clinician’s words only: no added symptom, threshold, time frame, condition, or explanation. Never add a destination such as “go to the ER,” “urgent care,” “call 911,” or “call the office” unless the clinician stated it. This restriction also applies to headings, labels, and lead-ins; do not introduce urgency or emergency labels. If the clinician named a destination, copy it exactly as written. If precautions are absent or withheld, omit this field and flag the gap in Part B and “Missing / to confirm.”
- Build Part B by checking each documented symptom and patient concern against the plan. Check allergies against planned medications, dose and unit inconsistencies, conflicting instructions, and conflicting results. Check for missing allergy information and other missing inputs that limit review. Check follow-up timing, location, and arrangements for documented tests or referrals; flag details needed to act that are absent. Do not assume an undocumented test or referral is required.
- Phrase every Part B flag as a question to the clinician, quoting the source text that prompted it. For omissions, identify the relevant section and what it does not specify. Never turn a flag into patient advice. If no flags are identified, write “No flags identified; this does not establish clinical safety.”
- Build “Missing / to confirm” with one item per missing, unclear, conflicting, or withheld detail. Keep this list clinician-only; ensure each item has a corresponding Part B question. If there are no identified gaps, write “None identified.”
- Audit Part A line by line against the note. Remove unsupported medications, doses, targets, diagnoses, prognoses, warnings, and other clinical advice. Recheck each measurement against the inventory, character for character for values and units, and verify the count. Compare medication changes and precautions verbatim against the source. Check all Part A text, headings, labels, and lead-ins for added destinations, conditions, or urgency; remove any additions. Do not present the draft as approved or signed.
Output format
DRAFT — for clinician review before sharing with the patient.
## Part A — Your visit summary
Reason for your visit: <supported plain-language summary>
Your measurements and test results: <every recorded value and unit exactly; terms explained>
Findings: <documented findings; terms explained>
Medicines: <verbatim, unambiguous medication changes>
Next steps: <documented follow-up; exact timing>
When to call or come back: <the clinician's precaution words only, verbatim>
## Part B — Clinician check (not for the patient)
- <Question to clinician, with source quote or identified omission>
## Missing / to confirm
- <Clinician-only gap, conflict, or withheld instruction>
Omit unsupported Part A fields rather than filling them with assumptions; never omit a recorded measurement. Retain the banner and all three section headings; replace placeholders with actual content. Part B and “Missing / to confirm” are for clinician review only, not for the patient.
Hard limits
- Never add a new medication, dose, target, diagnosis, prognosis, or warning to patient text.
- Never drop, round, convert, or independently interpret a recorded vital sign, measurement, or lab value.
- Never add a destination or condition to precautions that the clinician did not state, including in headings or labels.
- Never repair a suspected clinical error, resolve a contradiction independently, or imply that the check establishes safety.
- Input must be de-identified unless the organization confirms this tool is covered by its agreements and approved for the information; do not repeat unnecessary identifiers.
- US: under HIPAA, a cloud/AI service that creates, receives or maintains ePHI for a covered entity is a business associate and needs a BAA.
- HHS — HIPAA guidance on cloud computing (business associate agreements for cloud/AI services handling ePHI) — https://www.hhs.gov/hipaa/for-professionals/special-topics/health-information-technology/cloud-computing (checked 2026-10-19)
- The licensed, responsible clinician must verify clinical accuracy, every figure, medication change, precaution, and follow-up instruction against the source record, and resolve flagged concerns and gaps before sharing.
- The clinician signs; the summary is not medical advice from the tool. Remove Part B and “Missing / to confirm” from the patient version and review it after edits.
- UK/AU practitioners must verify applicable professional, privacy, and documentation requirements with their responsible organization or licensing body; the US statement does not establish their rules.
- Before sending or signing, see references/checklist.md.
Example
Input (fictional; “Sample” is an invented case label):
Case: Sample. Visit for knee pain. Vitals: BP 128/84 mmHg, weight 82 kg.
Assessment: knee strain. Patient also reports poor sleep.
Medication changes: none.
Plan: Follow up in 2 weeks.
Precautions: Call if knee pain worsens.
Output (abbreviated; proceeding with missing information flagged):
DRAFT — for clinician review before sharing with the patient.
## Part A — Your visit summary
Reason for your visit: Knee pain.
Your measurements and test results: blood pressure (BP) 128/84 mmHg (millimeters of mercury, a pressure unit); weight 82 kg (kilograms).
Findings: Knee strain (an injury to a muscle or tendon around the knee).
Medicines: Medication changes: none.
Next steps: Follow up in 2 weeks.
When to call or come back: Call if knee pain worsens.
## Part B — Clinician check (not for the patient)
- Was "poor sleep" assessed, and does it need a plan?
- Where should follow-up occur? "Follow up in 2 weeks" gives no location.
- Can you confirm allergies and reactions? The note contains no allergy information.
## Missing / to confirm
- Plan for reported poor sleep; follow-up location.
- Allergy information.
Tested models
- Claude Claude Opus 5.5
- Claude Claude Sonnet 5
- Claude Claude Fable 5.1
How to install
Claude Code
Download the ZIP, unpack it into ~/.claude/skills/ (or .claude/skills/ inside your project) and restart Claude Code. The skill loads when your request matches its description.
Claude Project (no terminal)
Open a Claude Project → Project instructions, paste the SKILL.md text below, and save. Every chat in that project follows it.
Free to use, adapt and share, including commercially, under CC BY 4.0. Credit required. Details in our terms.
All skills are also on GitHub, installable as a Claude Code plugin: aiprofessions/claude-skills · /plugin marketplace add aiprofessions/claude-skills
---
name: healthcare-visit-summary
description: "Use when a clinician or nurse pastes a visit note to draft a patient-friendly summary, a clinician-only red-flag check, and a missing-information list."
---
# Patient-Friendly Visit Summary + Red-Flag Check
## What it does
Drafts a patient-friendly after-visit summary from a clinician's or nurse's visit note.
Separately checks for unaddressed concerns, contradictions, and missing follow-up details.
The responsible clinician reviews, resolves questions, and signs before any patient-facing text is shared.
## Inputs it expects
- A de-identified visit note, unless the organization confirms this tool is covered by its agreements and approved for the information.
- The reason for the visit, assessment, and plan as documented.
- Every vital sign, measurement, and lab value, with recorded values and units.
- Medication information, including changes, doses, units, frequency, and timing.
- Allergies and documented reactions.
- Follow-up instructions and the clinician's return or urgent precautions.
- Optional: patient communication needs and practice jurisdiction.
If no visit note is supplied, ask for one before drafting.
For other missing information, ask once in one consolidated message, or proceed with supported content and list every gap under "Missing / to confirm."
Never guess; an absent allergy list does not mean no allergies.
The privacy gate below applies even when the user asks to proceed without clarification.
## Procedure
1. Check privacy before drafting.
If apparent identifiers are present and organizational approval is unconfirmed, stop and request a de-identified note or confirmation of approved use.
Do not repeat identifiers in the request; an explicitly fictional case label is not a real patient identifier.
2. Extract the visit reason, findings, plan, medications, allergies, symptoms, concerns, follow-up, and precautions.
Create an internal inventory of every recorded vital sign, measurement, and lab value, preserving its label, value, unit, and context.
Record missing or conflicting information; handle clarification as described above.
3. Start every draft with "DRAFT — for clinician review before sharing with the patient."
Use the output sections below in their stated order.
4. Check instructions for ambiguity or contradictions before putting them in Part A.
Withhold disputed medication directions, unclear precautions, and other conflicting instructions pending confirmation.
Quote the relevant source wording in Part B as a question and list the withheld item under "Missing / to confirm."
Do not choose between conflicting instructions or silently repair a suspected error.
Conflicting measurements are not withheld: retain them as specified in step 7.
5. Write Part A at approximately a 6th–8th grade reading level.
Use short sentences, common words, and "you" or "your"; explain medical terms and abbreviations on first use.
Keep explanations general and nonnumeric, such as "A1c (a blood test that measures average blood sugar)."
Do not add a diagnosis, prognosis, result interpretation, or clinical instruction through an explanation.
6. Copy every included number, dose, unit, frequency, duration, and follow-up date exactly from the note.
Do not round, convert, calculate, normalize notation, or insert a missing unit.
Do not introduce numbers through explanations; explain unfamiliar units separately without replacing the recorded unit.
7. Put every vital sign, measurement, and lab value from the inventory in Part A under "Your measurements and test results."
Preserve each exact value and unit; omit none, including weight and measurements outside the main findings section.
Match each inventory item to its Part A entry individually, then verify that the counts match.
Preserve labels and context needed to distinguish repeated, historical, or conflicting measurements.
Do not label a value high, low, normal, or improved unless the note says so; copy any such characterization exactly.
If a unit is absent, copy the value as written, add no unit, and flag the omission in Part B and "Missing / to confirm."
If values conflict, copy each as written and flag the conflict; do not choose between them.
8. Copy each unambiguous medication change verbatim, including the drug, dose, units, frequency, and timing.
Do not impose a start/stop/change format that alters the source wording.
Explain jargon separately without changing the copied instruction.
9. Put return and urgent precautions under the neutral heading "When to call or come back," copied verbatim.
Its content must be the clinician's words only: no added symptom, threshold, time frame, condition, or explanation.
Never add a destination such as "go to the ER," "urgent care," "call 911," or "call the office" unless the clinician stated it.
This restriction also applies to headings, labels, and lead-ins; do not introduce urgency or emergency labels.
If the clinician named a destination, copy it exactly as written.
If precautions are absent or withheld, omit this field and flag the gap in Part B and "Missing / to confirm."
10. Build Part B by checking each documented symptom and patient concern against the plan.
Check allergies against planned medications, dose and unit inconsistencies, conflicting instructions, and conflicting results.
Check for missing allergy information and other missing inputs that limit review.
Check follow-up timing, location, and arrangements for documented tests or referrals; flag details needed to act that are absent.
Do not assume an undocumented test or referral is required.
11. Phrase every Part B flag as a question to the clinician, quoting the source text that prompted it.
For omissions, identify the relevant section and what it does not specify.
Never turn a flag into patient advice.
If no flags are identified, write "No flags identified; this does not establish clinical safety."
12. Build "Missing / to confirm" with one item per missing, unclear, conflicting, or withheld detail.
Keep this list clinician-only; ensure each item has a corresponding Part B question.
If there are no identified gaps, write "None identified."
13. Audit Part A line by line against the note.
Remove unsupported medications, doses, targets, diagnoses, prognoses, warnings, and other clinical advice.
Recheck each measurement against the inventory, character for character for values and units, and verify the count.
Compare medication changes and precautions verbatim against the source.
Check all Part A text, headings, labels, and lead-ins for added destinations, conditions, or urgency; remove any additions.
Do not present the draft as approved or signed.
## Output format
```markdown
DRAFT — for clinician review before sharing with the patient.
## Part A — Your visit summary
Reason for your visit: <supported plain-language summary>
Your measurements and test results: <every recorded value and unit exactly; terms explained>
Findings: <documented findings; terms explained>
Medicines: <verbatim, unambiguous medication changes>
Next steps: <documented follow-up; exact timing>
When to call or come back: <the clinician's precaution words only, verbatim>
## Part B — Clinician check (not for the patient)
- <Question to clinician, with source quote or identified omission>
## Missing / to confirm
- <Clinician-only gap, conflict, or withheld instruction>
```
Omit unsupported Part A fields rather than filling them with assumptions; never omit a recorded measurement.
Retain the banner and all three section headings; replace placeholders with actual content.
Part B and "Missing / to confirm" are for clinician review only, not for the patient.
## Hard limits
- Never add a new medication, dose, target, diagnosis, prognosis, or warning to patient text.
- Never drop, round, convert, or independently interpret a recorded vital sign, measurement, or lab value.
- Never add a destination or condition to precautions that the clinician did not state, including in headings or labels.
- Never repair a suspected clinical error, resolve a contradiction independently, or imply that the check establishes safety.
- Input must be de-identified unless the organization confirms this tool is covered by its agreements and approved for the information; do not repeat unnecessary identifiers.
- US: under HIPAA, a cloud/AI service that creates, receives or maintains ePHI for a covered entity is a business associate and needs a BAA.
- HHS — HIPAA guidance on cloud computing (business associate agreements for cloud/AI services handling ePHI) — https://www.hhs.gov/hipaa/for-professionals/special-topics/health-information-technology/cloud-computing (checked 2026-10-19)
- The licensed, responsible clinician must verify clinical accuracy, every figure, medication change, precaution, and follow-up instruction against the source record, and resolve flagged concerns and gaps before sharing.
- The clinician signs; the summary is not medical advice from the tool. Remove Part B and "Missing / to confirm" from the patient version and review it after edits.
- UK/AU practitioners must verify applicable professional, privacy, and documentation requirements with their responsible organization or licensing body; the US statement does not establish their rules.
- Before sending or signing, see references/checklist.md.
## Example
Input (fictional; "Sample" is an invented case label):
```text
Case: Sample. Visit for knee pain. Vitals: BP 128/84 mmHg, weight 82 kg.
Assessment: knee strain. Patient also reports poor sleep.
Medication changes: none.
Plan: Follow up in 2 weeks.
Precautions: Call if knee pain worsens.
```
Output (abbreviated; proceeding with missing information flagged):
```markdown
DRAFT — for clinician review before sharing with the patient.
## Part A — Your visit summary
Reason for your visit: Knee pain.
Your measurements and test results: blood pressure (BP) 128/84 mmHg (millimeters of mercury, a pressure unit); weight 82 kg (kilograms).
Findings: Knee strain (an injury to a muscle or tendon around the knee).
Medicines: Medication changes: none.
Next steps: Follow up in 2 weeks.
When to call or come back: Call if knee pain worsens.
## Part B — Clinician check (not for the patient)
- Was "poor sleep" assessed, and does it need a plan?
- Where should follow-up occur? "Follow up in 2 weeks" gives no location.
- Can you confirm allergies and reactions? The note contains no allergy information.
## Missing / to confirm
- Plan for reported poor sleep; follow-up location.
- Allergy information.
```
Changelog
- v1.1 Added FR (France) and PT (Brazil) adaptations to local practice (not a translation): written by claude-opus-5-5, edited by gpt-6-astra, tested on separate pre-written rubrics and inputs: FR Claude Opus 5.5 5 of 5 (3 of 3 runs); FR Claude Sonnet 5 5 of 5 (3 of 3 runs); FR Claude Fable 5.1 5 of 5 (3 of 3 runs); PT Claude Opus 5.5 5 of 5 (3 of 3 runs); PT Claude Sonnet 5 5 of 5 (3 of 3 runs); PT Claude Fable 5.1 5 of 5 (3 of 3 runs); judge gpt-6-astra.
- v1.1 Revised after the first test round (EN v1.1, ES v1.1): behaviour rules fixed, rewritten by claude-opus-5-5, edited by gpt-6-astra, re-tested on the same pre-written rubric and input. Test: EN Claude Opus 5.5 5 of 5 (3 of 3 runs); EN Claude Sonnet 5 5 of 5 (3 of 3 runs); ES Claude Opus 5.5 5 of 5 (3 of 3 runs); ES Claude Sonnet 5 5 of 5 (3 of 3 runs); judge gpt-6-astra. Added 2026-10-20: Claude Fable 5.1 on the same version, inputs and rubrics: EN 5 of 5 (3 of 3 runs); ES 5 of 5 (3 of 3 runs); judge gpt-6-astra.
- v1.0 First release. Written by claude-opus-5-5, edited by gpt-6-astra. First test round: EN Claude Opus 5.5 4.7 of 5 (3 of 3 runs); EN Claude Sonnet 5 4.7 of 5 (3 of 3 runs); ES Claude Opus 5.5 4 of 5 (3 of 3 runs); ES Claude Sonnet 5 4 of 5 (3 of 3 runs).
One tested AI workflow a week
Tested prompts and skills for your profession, with dates and limits. No sponsors, no popups.