nexu-io/open-design / design-templates/clinical-case-report
clinical-case-report
VerifiedStructured medical case presentation for clinical rounds, conferences, and documentation. Generates SOAP-format or narrative case reports with physiologically accurate vitals, labs, and evidence-based plans. Use when the brief mentions "case report", "case presentation", "SOAP note", "clinical case", "ward rounds", "case summary", or "patient presentation".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.6 KB |
| example.html | other | 27.0 KB |
| examples/example-stemi.html | other | 27.0 KB |
| references/case-formats.md | markdown | 2.8 KB |
| references/checklist.md | markdown | 3.1 KB |
references/case-formats.md
View on GitHub# Case Presentation Formats
Use this reference to choose the correct format for the user's context.
Read the brief carefully — the format should match the clinical setting.
---
## Format 1: SOAP (Default)
Use for: emergency presentations, ward documentation, clinic letters.
**S — Subjective**
Chief complaint, HPI (chronological narrative), past medical history,
medications, allergies, family history, social history.
**O — Objective**
Vital signs (table), physical examination (by system), investigations
(labs table, imaging findings, ECG).
**A — Assessment**
Primary diagnosis with reasoning, differential diagnosis list (3–5 items)
each with one sentence of supporting or excluding evidence, risk score.
**P — Plan**
Management steps organised by problem number. Each problem gets:
investigations ordered, treatments started, consults requested,
monitoring parameters, and disposition.
---
## Format 2: Conference / Grand Rounds
Use for: teaching cases, grand rounds, case conferences, interesting
or rare presentations.
Structure:
1. **Opening statement**
"We present a [age]-year-old [sex] with [chief complaint]."
2. **Clinical summary**
Condensed narrative HPI, 2–4 sentences.
3. **Key findings**
Bulleted list of critical exam and investigation abnormalities.
4. **Diagnostic challenge**
One paragraph explaining what made this case educationally valuable
(unusual presentation, diagnostic difficulty, rare diagnosis, etc.)
5. **Differential discussion**
Walk through 3–5 diagnoses in order of likelihood with reasoning.
6. **Final diagnosis**
State the confirmed diagnosis with supporting evidence.
7. **Management**
Summary of what was done, in chronological order.
8. **Outcome**
Patient's course and disposition.
9. **Learning points**
2–3 bullet points summarising what clinicians should take from this case.
---
## Format 3: Brief Ward Rounds
Use for: daily ward rounds, post-call handover, ICU reviews.
This format is short. One screen, fast to read.
Structure:
- **ID line**: [Age][sex] | Day [N] of admission | Admitted for [diagnosis]
- **Overnight/interval events**: Bulleted. New results, procedures, changes.
- **Current vitals**: Trend arrow (↑ ↓ →). Flag abnormals.
- **Active problem list**: Numbered.
- **Plan by problem**: One line per problem.
Do not include full HPI or examination in this format.
The reader knows the patient. They need the delta.
---
## Format Selection Guide
| User says | Use format |
|---|---|
| "case presentation", "formal rounds", "clinic" | SOAP |
| "conference", "grand rounds", "teaching case", "interesting case", "rare case" | Conference |
| "daily review", "ward round", "ward rounds", "handover", "ICU", "post-call" | Brief Rounds |
| "discharge summary", "clinic letter" | SOAP (narrative variant) |
| No format specified | SOAP |Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |