Clinical note summarization
Skill bg-szy/TOP-SKILLS/skills/awesome-skills/clinical-note-summarization
全球最大的 Claude Code 技能聚合库 · 收录 3900+ 来自 12+ 来源的技能,提供在线搜索与趋势分析看板 / The world's largest Claude Code skill aggregation hub — 3900+ skills from 12+ sources with online search and trend dashboard
npx -y skills add bg-szy/TOP-SKILLS --skill clinical-note-summarizationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Structure raw clinical notes into SOAP-format summaries with explicit contradictions, missing data, and ICD-linked assessments using the provided prompt + usage script.
SKILL.md
2.1 KB, as published. Nobody here has run it
At-a-Glance
- description (10-20 chars): SOAP builder
- keywords: clinical-notes, SOAP, guardrails, ICD10, gaps
- measurable_outcome: Produce SOAP markdown + JSON (when requested) covering all four sections with ≥95% note coverage and explicit missing info in ≤2 minutes per note.
Inputs
note_text(dictation, OCR, or EHR export) and optionalpatient_contextmetadata.output_format(markdowndefault,jsonwhen downstream validators need schema).
Outputs
- Structured SOAP summary with Subjective/Objective/Assessment/Plan bulleting.
- Alerts plus missing-information checklist.
- Optional JSON payload using schema from README.
Workflow
- Load system prompt:
prompt.mdenforces no hallucinations + data gap surfacing. - Normalize input: Pre-clean vitals, labs, and timeline context when available.
- Generate summary: Call preferred LLM (OpenAI, Anthropic, Gemini, OSS) using
usage.pyas a template. - Validate: Cross-check extracted values vs. source text and ensure contradictions/missing data are spelled out.
- Deliver output: Provide markdown + JSON as required and log PHI handling steps.
Guardrails
- Never invent findings; state "not provided" explicitly.
- Mark outputs as documentation support only—not clinical decisions.
- Strip/re-mask PHI before storing prompts/responses.
References
- For detailed schema, guardrails, and integration snippets see
README.md,prompt.md, andusage.py.