Skip to content
cccskills
FreePublished on GitHub

soap-note-creation

Create structured medical notes in SOAP format, covering patient reports, observed findings, assessment, and care plans. The skill organizes supplied clinical information, writes all four sections to a file together, and checks that the record is complete.

OriginalShow the original description

Create structured medical SOAP notes with all four components in a single comprehensive file write

See how to install

Good for

  • Organizing patient visit information into SOAP notes
  • Documenting medical meetings in a consistent format
  • Checking all four sections of a clinical record

Files included (2)

  • SKILL.md3.8 KB
  • .skill_id32 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

SOAP Note Creation

This skill captures the pattern of creating complete, structured medical documentation (SOAP notes) by writing all required sections to a file in one iteration.

When to Use

Use this skill when you need to create medical meeting notes, patient visit documentation, or clinical encounter records that follow the standard SOAP format.

Core Technique

Write the entire SOAP note in one comprehensive file write rather than building it incrementally. This ensures completeness and consistency across all sections.

Required Sections

Every SOAP note must include these four components:

1. Subjective (S)

  • Chief Complaint (CC): Patient's primary reason for visit
  • History of Present Illness (HPI): Detailed narrative of current symptoms
  • Past Medical History (PMH): Relevant medical history, medications, allergies
  • Family/Social History: Pertinent family and social context

2. Objective (O)

  • Vital Signs: BP, HR, RR, Temp, SpO2, weight, height
  • Physical Examination: System-by-system findings (HEENT, Cardiovascular, Respiratory, Abdomen, Neurological, etc.)
  • Diagnostic Data: Lab results, imaging findings if available

3. Assessment (A)

  • Primary Diagnosis: Main clinical diagnosis
  • Differential Diagnoses: Alternative considerations
  • Clinical Reasoning: Brief justification for assessment

4. Plan (P)

  • Management: Treatments, medications, interventions
  • Follow-up: Timing and conditions for return
  • Patient Education: Instructions, lifestyle modifications, warning signs

Execution Pattern

1. Gather all patient information and clinical data
2. Structure content into the four SOAP sections
3. Write the complete note to file in ONE operation
4. Verify all four sections are present and complete

Example Structure

# SOAP Note - [Patient Name/ID]
## Date: [Visit Date]

## SUBJECTIVE
### Chief Complaint
[Patient's reason for visit in their own words]

### History of Present Illness
[Detailed symptom narrative using OLDCARTS or similar framework]

### Past Medical History
[Relevant conditions, surgeries, medications, allergies]

### Family/Social History
[Relevant family history and social context]

## OBJECTIVE
### Vital Signs
- BP: [value]
- HR: [value]
- Temp: [value]
- [etc.]

### Physical Examination
- **HEENT**: [findings]
- **Cardiovascular**: [findings]
- **Respiratory**: [findings]
- **Abdomen**: [findings]
- **Neurological**: [findings]
- [etc.]

### Diagnostic Data
[Labs, imaging, other test results]

## ASSESSMENT
### Primary Diagnosis
[Diagnosis with ICD code if applicable]

### Differential Diagnoses
1. [Alternative 1]
2. [Alternative 2]

### Clinical Reasoning
[Brief explanation linking findings to diagnosis]

## PLAN
### Management
- [Medications with dose/frequency]
- [Procedures/interventions]
- [Referrals if needed]

### Follow-up
[Timeline and conditions for return visit]

### Patient Education
[Instructions, lifestyle mods, warning signs to watch]

Best Practices

  1. Completeness First: Include all four sections before writing—do not build incrementally
  2. Specificity: Use concrete values (vitals, dates, doses) rather than placeholders
  3. Clinical Accuracy: Ensure assessment logically follows from subjective and objective data
  4. Actionable Plan: Plan items should be specific and implementable
  5. File Size: Comprehensive notes typically range 3000-8000 bytes depending on complexity

Common Mistakes to Avoid

  • Writing sections separately across multiple iterations
  • Leaving sections incomplete or with placeholder text
  • Omitting differential diagnoses in Assessment
  • Creating vague, non-actionable Plan items
  • Missing vital signs or key physical exam findings

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Prepare audio stems, the separate parts of a track, for mixing by matching their durations with silence, loops, or crossfades. Verify each generated and processed file before moving to the next production step.

  • Match audio parts with different durations
  • Extend drums and melodic parts using suitable methods
  • Check audio specifications before mixing
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

Produce audio in separate stems, meaning individual instrument tracks, and verify each output as you go. Align track lengths with silence, loops, or crossfades, then apply effects, mix a master, and package the files.

  • Align instrument tracks to a reference audio file
  • Choose how to extend tracks that are too short
  • Verify audio properties after generation and effects
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

Build serverless endpoints that relay external API requests for a dashboard while keeping API keys on the server. Includes Vercel examples for input checks, caching, cross-origin access, and consistent JSON responses.

  • Connect a dashboard to external APIs without exposing API keys
  • Create endpoints for stock quotes and news
  • Standardize API responses and error handling
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

Produce a master track and separate audio parts through a structured Python workflow. Apply filters and reverb, export WAV files with consistent settings, package them in a ZIP archive, and check that the deliverables meet the requested specifications.

  • Export a master track with separate audio parts
  • Apply filters and reverb to audio
  • Check duration and format across deliverables
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

Keep document creation moving when web searches and page retrieval repeatedly fail. The skill preserves the original task, uses the model’s existing knowledge, and clearly identifies information that could not be checked against external sources.

  • Continue drafting after repeated web retrieval failures
  • Preserve task requirements during network errors
  • Mark information that could not be externally verified
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

When Python execution repeatedly fails in execute_code_sandbox, use a file-based alternative: save the script, run it through the shell, and capture results or errors. The guidance covers paths, imports, timeouts, structured output, and optional cleanup.

  • Retry Python work through the shell after repeated sandbox failures
  • Run longer tasks with an adjusted timeout
  • Execute Python work that needs multiple files or system utilities
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

See all skills by HKUDS

Report a problem with this skill