본문으로 건너뛰기
cccskills
무료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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

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

설치 방법 보기

이럴 때 유용합니다

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

포함된 파일(2)

  • SKILL.md3.8 KB
  • .skill_id32 B

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

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.8천2026년 8월 13일 업데이트

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.8천2026년 8월 13일 업데이트

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.8천2026년 8월 13일 업데이트

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.8천2026년 8월 13일 업데이트

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.8천2026년 8월 13일 업데이트

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.8천2026년 8월 13일 업데이트

HKUDS의 스킬 모두 보기

이 스킬의 문제 신고