segmenting-clinical-sections

Segment unstructured clinical notes into canonical LOINC-mapped sections for downstream NLP workflows.

5.0k|615|Updated Oct 4, 2025
One-click install
npx skills add https://github.com/maziyarpanahi/openmed --skill segmenting-clinical-sections
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: segmenting-clinical-sections
Source: https://github.com/maziyarpanahi/openmed/tree/main/skills/segmenting-clinical-sections
Command: npx skills add https://github.com/maziyarpanahi/openmed --skill segmenting-clinical-sections

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill separates unstructured clinical notes into canonical sections so downstream entity extraction and de-identification can interpret findings according to their clinical context, such as distinguishing historical conditions in Past Medical History from active problems in Assessment and Plan.

Core Features & Use Cases

  • Header Detection: Identifies common clinical section headers using line-based and heuristic parsing.
  • Section Normalization: Maps variants such as HPI and PMH to canonical labels and associated LOINC document-section codes.
  • Context-Aware Processing: Splits notes into provenance-preserving chunks for per-section NER, de-identification, temporality resolution, and problem-list reconciliation.
  • Use Case: Process a discharge summary by separating its history, medications, allergies, and assessment sections before sending each chunk to OpenMed clinical analysis tools.

Quick Start

Use the segmenting-clinical-sections skill to divide the attached clinical note into canonical sections, preserve unsectioned text and offsets, and prepare each chunk for OpenMed NER or de-identification.

Frequently Asked Questions about segmenting-clinical-sections

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I segment unstructured clinical notes into sections for downstream NLP?

Segment unstructured clinical notes by applying heuristic line-based parsing to detect headers, normalize section variants like HPI and PMH to canonical labels, and preserve text offsets for context-aware NLP. This process splits free-text notes into provenance-preserving chunks.

What is clinical note section segmentation and when do I need it?

Clinical note section segmentation separates free-text documents into canonical sections like history, medications, and assessment. You need it when downstream entity extraction or de-identification must interpret findings according to their clinical context, such as distinguishing historical from active conditions.

Can I map clinical section headers like HPI and PMH to LOINC document-section codes?

Yes, section normalization maps common clinical header variants such as HPI and PMH to canonical labels and their associated LOINC document-section codes. This standardization enables consistent context-aware processing across different clinical note types like discharge summaries.

Does clinical section segmentation preserve text offsets and provenance for de-identification?

Yes, the segmentation process preserves unsectioned text and character offsets while tracking provenance. This ensures that per-section de-identification and named entity recognition maintain accurate document mapping without losing original note context.

What is the best way to prepare discharge summaries for per-section named entity recognition?

Prepare discharge summaries by using heuristic parsing to separate history, medications, allergies, and assessment sections into provenance-preserving chunks. Send each normalized chunk to clinical analysis tools for context-aware named entity recognition and de-identification.

Are there limitations when segmenting progress notes with non-standard or missing headers?

Heuristic parsing handles common clinical headers but may struggle with non-standard or missing section headers in progress notes. Unsectioned text is preserved with offsets, ensuring no data loss, but canonical section mapping relies on recognizing standard header variants.