Use when documenting a patient encounter in a structured clinical note format for medical records, communication, or billing
Scanned 9/8/2026
Install to Claude Code
npx -y skills add jeffreytse/grimoire-core --skill write-clinical-note-soap --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Write Clinical Note Soap?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/jeffreytse-write-clinical-note-soap)More formats (shields.io, HTML) on the badges page.
---
name: write-clinical-note-soap
description: Use when documenting a patient encounter in a structured clinical note format for medical records, communication, or billing
source: Weed "Medical Records, Medical Education, and Patient Care" (1969) SOAP originator; Joint Commission documentation standards; USMLE clinical skills documentation curriculum
tags: [medicine, clinical-documentation, soap, medical-records]
verified: true
---
# Write Clinical Note SOAP
Document a patient clinical encounter using the SOAP format (Subjective, Objective, Assessment, Plan) to create a clear, legally defensible, and clinically actionable medical record.
**Disclaimer:** This skill is for documentation formatting assistance only, not medical advice. It is intended for use by licensed healthcare providers; it does not replace clinical judgment, diagnostic training, or consultation with a qualified healthcare provider.
## Why This Is Best Practice
**Adopted by:** Joint Commission accreditation standards for US hospitals, CMS (Centers for Medicare & Medicaid Services) documentation requirements, WHO patient safety records guidelines, all major EHR systems (Epic, Cerner, Athena).
**Impact:** SOAP-structured notes reduce medication errors by 23% and improve care team communication efficiency by 30% (Reisman & Brown 2016); poor clinical documentation contributes to 20% of adverse events due to miscommunication (WHO Patient Safety Report 2005); SOAP format is the global standard for 98% of clinical training programs.
**Why best:** Weed's problem-oriented medical record (POMR) with SOAP structure created a systematic, reproducible framework that separates data collection from clinical interpretation, preventing cognitive bias and ensuring complete documentation for medico-legal, billing, and continuity-of-care purposes.
Sources: Weed (1969) Year Book Medical Publishers; Joint Commission Standards RI.01.01.01; AMA CPT documentation guidelines (2019 update); Podder et al. StatPearls (2023).
## Steps
1. **Header** — date, time, provider name and credentials, patient identifier, encounter type (in-person, telehealth, follow-up), relevant context (referral source, care setting).
2. **S — Subjective** — document the patient's own words and reported experience: chief complaint (CC) in direct quotes; history of present illness (HPI) using OLDCART or OPQRST framework (Onset, Location, Duration, Character, Aggravating/Alleviating factors, Radiation, Timing, Severity); pertinent past medical history, medications, allergies, family history, social history, and review of systems relevant to the CC.
3. **HPI structure with OLDCART** — for each symptom: Onset (when started, sudden vs. gradual), Location (where, does it radiate?), Duration (continuous vs. intermittent), Character (quality of symptom — burning, sharp, dull), Aggravating/Alleviating factors, Radiation, Timing (pattern), Severity (0–10 scale or functional impact).
4. **O — Objective** — document measurable, observable clinical data: vital signs (BP, HR, RR, temp, SpO2, weight, BMI); physical examination findings using systems (general, cardiovascular, respiratory, abdominal, neurological — only what is relevant); laboratory results (with reference ranges); imaging findings; EKG interpretation.
5. **Objective writing conventions** — use clinical descriptors: "lungs clear to auscultation bilaterally," "abdomen soft, non-tender, no organomegaly"; avoid subjective interpretations in this section; document both normal and abnormal findings relevant to the CC.
6. **A — Assessment** — state the working diagnosis and differential: primary diagnosis (most likely) first; ranked differential diagnoses with supporting and refuting evidence for each; ICD-10 code if required for billing; include severity, acuity, and complicating factors.
7. **Assessment conventions** — write as clinical reasoning: "32-year-old female presenting with 3-day productive cough, fever to 38.5°C, decreased breath sounds right base, and right lower lobe opacity on CXR, consistent with community-acquired pneumonia (J18.9)." Do not list diagnoses without clinical justification.
8. **P — Plan** — document specific actions for each problem listed in Assessment, organized by problem: diagnostics ordered (with clinical indication); medications prescribed (drug, dose, route, frequency, duration, number of refills); non-pharmacological interventions; referrals (to whom, urgency, indication); patient education provided; follow-up (timeframe and conditions for return).
9. **Plan specificity** — each plan element must be actionable and complete: "Amoxicillin 500 mg PO TID × 7 days for CAP; repeat CXR in 6 weeks to confirm resolution; return to ED if worsening dyspnea, O2 sat <94%, or inability to tolerate oral medications."
10. **Sign and timestamp** — physician signature (or co-signature for trainee), credentials, date and time of note completion. For billing compliance: attestation statement for supervising physician if note completed by resident or NP.
## Rules
- Never use copy-forward (cloning previous note) for the Subjective or Assessment sections — Joint Commission cites this as a patient safety risk; cloned notes fail to capture clinical change and create inaccurate records.
- Objective section contains only observations and measurements, never interpretation — interpretation belongs in Assessment.
- Document informed consent and patient education given, not just orders placed — medicolegally, if it is not documented, it was not done.
- Use approved abbreviations only — non-standard abbreviations are a leading cause of medication errors; follow facility-approved abbreviation list.
## Common Mistakes
- **Assessment listing diagnoses without reasoning** — writing "hypertension, diabetes" without clinical context does not demonstrate medical decision-making, which determines billing level.
- **Plan without specificity** — "continue medications" without listing which medications, doses, and durations is incomplete documentation that fails continuity-of-care.
- **Objective data in Subjective section** — mixing patient-reported symptoms with examination findings makes the note structurally invalid and harder to interpret.
- **Missing safety netting** — not documenting return precautions (conditions under which the patient should seek care before the scheduled follow-up) creates medicolegal exposure if the patient deteriorates.
## When NOT to Use
- For psychiatric progress notes where process-oriented narrative format (DAP: Data, Assessment, Plan) may be preferred and trauma-informed documentation conventions differ
- For emergency department notes where time-critical formats (Brief ED note, MDM-only billing) may be required by facility
- For operative reports, procedure notes, or discharge summaries — these have domain-specific formats that differ from SOAPIs this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!