domains / families / documents / automated-soap-note-generator

automated-soap-note-generator

combined

Transform unstructured clinical input (dictation, transcripts, or rough Generate structured SOAP notes from clinical narratives, transcripts, or existing notes; use when the user needs de-identified clinical documentation organized into Subjective, Objective, Assessment, and Plan sections, with clear assumptions and review points.

When to use

• Converting physician dictation into structured SOAP format for efficiency
• Processing audio-to-text transcripts from patient encounters
• Transforming consultation rough notes into formal documentation
• Generating initial draft documentation to reduce administrative burden
• Standardizing clinical encounter summaries for consistency
• Creating preliminary notes for routine follow-up visits
• Input contains PHI that hasn't been de-identified for testing/training
• Complex psychiatric cases requiring nuanced mental status documentation → Use specialized psychiatric documentation tools

When not to use

• **Not a diagnostic tool**: Cannot make medical decisions or diagnoses
• **Specialty coverage**: Best performance in internal medicine, family practice; variable in highly specialized fields
• **Language**: Optimized for English; limited support for other languages
• **Context window**: May lose context in very long, complex encounters
• **Ambiguity**: Struggles with highly ambiguous or contradictory input
• **Rare conditions**: May not recognize very rare diseases or new medications
• **Non-verbal cues**: Cannot interpret tone, emphasis, or non-verbal information from audio
• Do not proceed when required input files, identifiers, parameters, or context are missing — ask the user to provide them first.

Skill page

Conflict

Both copies describe the same SOAP note generation workflow and share the same core capabilities, parameters, and preprocessing steps. However, the aipoch copy adds a concrete script-backed validation workflow (py_compile, --help, sample run) and a generic fallback/assumption workflow, while the LeoYeAI copy adds explicit safety constraints (physician review required, PHI de-identification, do-not-use cases) and integration with upstream/downstream skills. Neither copy is a strict reproduction of the other; crowning one would hide either the validation commands or the safety/integration constraints.