Skip to content

nexu-io/open-design / design-templates/clinical-case-report

clinical-case-report

Verified

Structured 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".

FileKindSize
SKILL.mdskill md8.6 KB
example.htmlother27.0 KB
examples/example-stemi.htmlother27.0 KB
references/case-formats.mdmarkdown2.8 KB
references/checklist.mdmarkdown3.1 KB

references/checklist.md

View on GitHub
# Clinical Case Report — Quality Checklist

## P0 — Must Pass Before Emitting Artifact

- [ ] Chief complaint or ID line is clearly stated in the opening line
- [ ] **SOAP / Conference format only:** HPI is written as a chronological prose narrative with at least one timeline marker (e.g. "2 hours prior to presentation"); skip for Brief Rounds
- [ ] **Brief Rounds format only:** ID line present; interval events / current status documented; active problems listed; plan-by-problem present; full HPI and examination sections are not required
- [ ] Vital signs are present and physiologically plausible
- [ ] Vital signs are internally consistent with the diagnosis (allowing for clinical variability — bradycardic shock, medication-blunted tachycardia, afebrile pneumonia, early STEMI with normal troponin, etc.)
- [ ] Assessment contains a clearly stated primary diagnosis
- [ ] Plan is present and directly addresses the primary diagnosis
- [ ] If the plan includes medications: a prescribing-safety block is present before drug recommendations, confirming known inputs (allergies, renal/hepatic function, anticoagulants) and calling out unknowns (weight, bleeding risk, pregnancy); doses defer to "per local formulary/protocol" when key variables are missing
- [ ] Medication plan is labelled as educational/simulated — not a substitute for clinician judgment
- [ ] No real patient identifiers (direct or indirect): no names, MRNs, exact dates, locations, images, rare condition combos, occupation details, or verbatim stories from real cases
- [ ] All data is synthetic, de-identified, or clearly fictional
- [ ] If based on a real case, apply formal de-identification before use
- [ ] HTML renders without errors in a browser
- [ ] All major sections tagged with `data-od-id`

## P1 — Should Pass

- [ ] Past medical history includes conditions relevant to the presentation
- [ ] Medications list is present
- [ ] Physical examination findings are organised by system
- [ ] Differential diagnosis contains 3 to 5 items
- [ ] Each differential item includes one sentence of supporting or refuting evidence
- [ ] Lab values use correct units and are within realistic ranges for the diagnosis
- [ ] Plan is specific — drug names, doses, routes, and frequencies are written out where safety inputs are known; unknown variables defer to "per local formulary/protocol"
- [ ] Plan is organised by problem using numbered headers
- [ ] Critical findings are visually highlighted (red callout box)
- [ ] Document is print-friendly (white background, `@media print` rules present)
- [ ] A validated risk score is included where applicable (TIMI, GRACE, Killip class + Shock Index for STEMI/cardiogenic shock, CURB-65, qSOFA, Wells)

## P2 — Nice to Have

- [ ] Pertinent negatives documented in HPI and Review of Systems
- [ ] Imaging findings described in investigations section
- [ ] Specialist consult noted where clinically indicated
- [ ] Disposition or follow-up plan included
- [ ] Monitoring parameters specified (e.g. repeat troponin at 3h and 6h)
- [ ] Secondary prevention addressed for chronic disease presentations
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexUnverifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall