reconciling-problem-lists

Reconcile fragmented clinical condition mentions into deduplicated problem lists with statuses.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill transforms fragmented, repeated, negated, historical, and hypothetical condition mentions into one reliable, de-duplicated clinical problem list with clear active, resolved, or historical status.

Core Features & Use Cases

  • Condition Reconciliation: Clusters synonymous diagnosis mentions such as DM2, type 2 diabetes, and diabetes mellitus into unified concepts.
  • Clinical Status Resolution: Uses negation, temporality, uncertainty, and section context to exclude non-problems and distinguish active conditions from resolved or historical ones.
  • Structured Output: Produces USCDI Problem- and FHIR Condition-shaped records with mention counts and provenance for clinical review.
  • Use Case: Reconcile conditions from a clinical note after entity extraction and context resolution, excluding denied symptoms while preserving an active diagnosis mentioned in the assessment and plan.

Quick Start

Use this Skill to reconcile the extracted disease entities and clinical context from the attached note into a deduplicated problem list with statuses and source provenance.

Frequently Asked Questions about reconciling-problem-lists

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

FAQPage Schema
How do I reconcile fragmented clinical mentions into a deduplicated problem list?

Condition reconciliation clusters synonymous diagnosis mentions—such as DM2 and diabetes mellitus—into unified concepts and resolves their clinical status. This process relies on negation detection, temporality axes, and synonym normalization to produce a clean, deduplicated problem list.

How does negation detection work when filtering clinical notes for active conditions?

Negation detection identifies denied or hypothetical mentions within clinical notes and excludes them from the final problem list. By analyzing temporality, uncertainty, and section context, the system distinguishes active conditions from resolved or historical statuses.

Can I prepare FHIR Condition resources from extracted clinical note entities?

Yes, clinical condition mentions are reconciled into USCDI Problem- and FHIR Condition-shaped records. The output includes deduplicated conditions with active, resolved, or historical statuses, mention counts, and source provenance for clinical review.

Do I need SNOMED CT grounding to normalize synonymous diagnosis mentions?

Yes, synonym normalization requires user-supplied SNOMED CT grounding or OpenMed Disease entities. This grounding maps varied clinical mentions like type 2 diabetes to unified concepts for accurate condition reconciliation.

What is the best way to exclude hypothetical mentions when building a problem list?

The best way to exclude hypothetical mentions is applying negation and temporality axes alongside section context resolution. This ensures only active, resolved, or historical conditions are retained while denied symptoms are automatically filtered out.

How to track provenance for conditions during medical entity deduplication?

Provenance tracking records the source mentions and counts for each reconciled condition within the clinical note. This provides clinicians with the exact evidence trail needed to review the deduplicated problem list and verify clinical status assignments.