Skip to content

LeoYeAI/agent-master-skills / skills/automated-soap-note-generator

automated-soap-note-generator

Verified

Transform unstructured clinical input (dictation, transcripts, or rough notes) into standardized SOAP (Subjective, Objective, Assessment, Plan) medical documentation. Use ONLY for initial documentation draft generation; ALL output requires physician review before entering patient records. Not for complex cases requiring nuanced clinical reasoning.

FileKindSize
SKILL.mdskill md24.4 KB
_meta.jsonconfig313 B
references/clinical_guidelines.mdmarkdown2.8 KB
references/medical_terminology.mdmarkdown3.9 KB
references/sample_soap_notes.mdmarkdown6.4 KB
requirements.txtmanifest17 B
scripts/main.pyscript16.5 KB

references/clinical_guidelines.md

View on GitHub
# Clinical Documentation Guidelines

## SOAP Note Standards

### Subjective (S)
**Purpose**: Document patient-reported information

**Required Elements**:
- Chief complaint (CC)
- History of present illness (HPI)
  - Onset
  - Duration
  - Character
  - Aggravating/Alleviating factors
  - Associated symptoms
  - Severity (1-10 scale)
- Review of systems (ROS) - relevant
- Past medical history (PMH)
- Medications
- Allergies
- Social history (relevant)
- Family history (relevant)

**Writing Tips**:
- Use patient's own words when appropriate
- Document negative findings with "denies"
- Include temporal information

### Objective (O)
**Purpose**: Document observable, measurable data

**Required Elements**:
- Vital signs (with time)
- Physical examination findings
- Laboratory results
- Imaging results
- Other diagnostic data

**Writing Tips**:
- Use standard medical terminology
- Include measurements and values
- Note "WNL" (Within Normal Limits) for normal findings
- Describe abnormal findings specifically

### Assessment (A)
**Purpose**: Clinical interpretation and diagnosis

**Required Elements**:
- Primary diagnosis
- Differential diagnoses
- Problem list
- Status/changes from previous encounters

**Writing Tips**:
- Be specific with diagnoses
- Include diagnostic reasoning
- Address all problems identified
- Note stability/instability

### Plan (P)
**Purpose**: Treatment and management strategy

**Required Elements**:
- Medications (drug, dose, route, frequency)
- Procedures/tests ordered
- Consultations/referrals
- Patient education
- Follow-up plan

**Writing Tips**:
- Be specific with dosing
- Include patient instructions
- Specify timeframe for follow-up
- Document informed consent

## Medical Documentation Principles

### 1. Clarity
- Use unambiguous language
- Avoid abbreviations that could be misinterpreted
- Write legibly (if handwritten)

### 2. Completeness
- Document all relevant information
- Include negative findings
- Record all decisions and reasoning

### 3. Timeliness
- Document during or immediately after encounter
- Include date and time for all entries

### 4. Accuracy
- Verify all facts before recording
- Correct errors properly (single line through, initial, date)
- Never alter records after the fact

### 5. Objectivity
- Distinguish fact from opinion
- Quote patient when documenting subjective information

## Legal Considerations

- All entries must be dated and signed
- Use permanent ink for handwritten notes
- Never leave blank spaces
- Document informed consent discussions
- Include patient non-compliance if applicable

## Quality Metrics

Effective SOAP notes should be:
- **Specific**: Avoid vague terms like "good" or "normal"
- **Measurable**: Include quantifiable data
- **Actionable**: Clear next steps
- **Relevant**: Focus on pertinent information
- **Time-bound**: Include timelines for follow-up
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