Agent skill

Reconciling Problem Lists

by maziyarpanahi in maziyarpanahi/openmed

Deduplicate and reconcile OpenMed-extracted conditions into one clean active problem list with clinical status (active / resolved / historical).

Apache-2.0Auto-check passedBusiness, Finance & HR

Install Reconciling Problem Lists

skills CLI
$ npx skills add maziyarpanahi/openmed --skill reconciling-problem-lists -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install maziyarpanahi/openmed reconciling-problem-lists --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/maziyarpanahi/openmed.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/reconciling-problem-lists .claude/skills/reconciling-problem-lists && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
reconciling-problem-lists
GitHub stars
5.5k
Token cost
~1.8k tokens
SKILL.md length
570 words
Files
1
Skills in repo
74
Repo updated
First seen
Licence
Apache-2.0

At a glance

Deduplicate and reconcile OpenMed-extracted conditions into one clean active problem list with clinical status (active / resolved / historical).

  • Works in 6 steps: Collect Disease/Condition entities from… → Attach clinical context per mention with… → Exclude what isn't a problem. Drop… → …
  • Wants a problem list
  • SKILL.md covers When to use, Quick start, Workflow and Hand-off to / from OpenMed, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Reconciling Problem Lists is an agent skill from maziyarpanahi/openmed. Deduplicate and reconcile OpenMed-extracted conditions into one clean active problem list with clinical status (active / resolved / historical). Use after NER and context resolution when the user wants a problem list, condition reconciliation, dedup of synonymous diagnosis mentions, or active-vs-resolved status from a note. Covers clustering synonymous mentions into one concept, excluding negated mentions, applying clinical context (historical / hypothetical / recent) to set status, and emitting a…

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Business, Finance & HR, covering Accessibility, Accounting and bookkeeping and Clinical and healthcare research. The repository describes itself as: Local-first healthcare AI: clinical NER and HIPAA PII de-identification on hardware you control. 2,200+ medical models, 35 model-backed PII languages, and Python, MLX, Android… The licence is Apache-2.0.

When your agent uses it

  • Wants a problem list
  • Condition reconciliation
  • Dedup of synonymous diagnosis mentions
  • Active-vs-resolved status from a note

Example prompts

  • “/reconciling-problem-lists”

Requirements

  • Python 3

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Collect Disease/Condition entities from analyze_text across the whole
  2. Attach clinical context per mention with resolve_span_context (or the
  3. Exclude what isn't a problem. Drop NEGATED mentions (patient denies /
  4. Cluster synonymous mentions into one concept. Fold surface variants
  5. Assign status by aggregating context. A concept that is RECENT/active
  6. Emit the reconciled list — one record per concept with status, mention

What it can do on your machine

Read from SKILL.md and the folder at commit 9dca507. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are python).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • healthit.gov
    • hl7.org
    • snomed.org

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Reconciling Problem Lists loads about 1.8k tokens when it runs. Until then it costs about 189 tokens; SKILL.md has 570 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~189
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from maziyarpanahi/openmed at commit 9dca507, republished under its Apache-2.0 licence (© maziyarpanahi). 570 words, ~1,770 tokens.

Download SKILL.mdSave it as .claude/skills/reconciling-problem-lists/SKILL.md (or your agent's skills folder).
name
reconciling-problem-lists
description
Deduplicate and reconcile OpenMed-extracted conditions into one clean active problem list with clinical status (active / resolved / historical). Use after NER and context resolution when the user wants a problem list, condition reconciliation, dedup of synonymous diagnosis mentions, or active-vs-resolved status from a note. Covers clustering synonymous mentions into one concept, excluding negated mentions, applying clinical context (historical / hypothetical / recent) to set status, and emitting a USCDI-Problem-shaped list. SNOMED CT concept grounding is user-supplied and out-of-process. Hand-off: consume openmed.analyze_text Disease entities plus resolving-clinical-context axes. Pairs after extracting-clinical-entities.
license
Apache-2.0
metadata.project
OpenMed
metadata.category
clinical-nlp
metadata.pairs
after
metadata.version
1.0

Reconciling problem lists

A single note mentions the same condition many ways — "DM2," "type 2 diabetes," "diabetes mellitus" — across PMH, HPI, and A&P, some negated, some historical. A usable problem list collapses those mentions into one concept per problem, drops what the patient does not have, and assigns a clinical status (active / resolved / historical). This skill turns OpenMed's per-mention entity stream plus ConText axes into that reconciled, de-duplicated list, shaped for USCDI "Problem" exchange.

When to use

  • After extracting-clinical-entities and resolving-clinical-context, when the user wants a clean problem list, condition reconciliation, or dedup of repeated diagnosis mentions.
  • You need active-vs-resolved-vs-historical status per problem, not just raw mentions.
  • You are assembling a FHIR Condition list or a USCDI Problem element and need one entry per concept.

Quick start

python
import openmed
from openmed.clinical import resolve_span_context, NEGATED, HISTORICAL, HYPOTHETICAL

note = ("PMH: type 2 diabetes, prior MI 2019 (resolved). "
        "A&P: poorly controlled DM2; denies chest pain.")

ents = openmed.analyze_text(note, model_name="disease_detection_superclinical",
                            output_format="dict")

def normalize(surface: str) -> str:
    # Cheap synonym folding; replace with SNOMED grounding (out-of-process).
    s = surface.lower().strip()
    return {"dm2": "type 2 diabetes", "diabetes mellitus": "type 2 diabetes"}.get(s, s)

problems = {}  # concept -> reconciled record
for e in ents:
    surface = e["word"]
    ctx = resolve_span_context(surface, note)
    if ctx.negation == NEGATED:
        continue                                   # patient does NOT have it -> exclude
    concept = normalize(surface)
    status = ("resolved" if ctx.temporality == HISTORICAL else
              "active")
    if ctx.temporality == HYPOTHETICAL:
        continue                                   # not asserted as present
    rec = problems.setdefault(concept, {"concept": concept, "status": status,
                                        "mentions": 0})
    rec["mentions"] += 1
    # Active anywhere wins over a historical mention of the same concept.
    if status == "active":
        rec["status"] = "active"

problem_list = list(problems.values())
# -> [{"concept": "type 2 diabetes", "status": "active", "mentions": 2}, ...]
# "chest pain" excluded (negated); "MI" -> historical/resolved.

Workflow

  1. Collect Disease/Condition entities from analyze_text across the whole note (or per section if you ran segmenting-clinical-sections).
  2. Attach clinical context per mention with resolve_span_context (or the axes from resolving-clinical-context): negation, temporality, uncertainty.
  3. Exclude what isn't a problem. Drop NEGATED mentions (patient denies / no evidence of) and HYPOTHETICAL mentions (conditional, not asserted). These must never land on the active list.
  4. Cluster synonymous mentions into one concept. Fold surface variants (abbreviations, word order, lexical synonyms) to a single canonical key. Cheap normalization gets you started; SNOMED CT concept grounding is the robust path — run it out-of-process with the user's own license and key on the concept code, not the surface string.
  5. Assign status by aggregating context. A concept that is RECENT/active anywhere (typically A&P) is active; one seen only as HISTORICAL ("history of," "resolved," PMH-only) is resolved/historical. Active wins over historical when the same concept appears both ways.
  6. Emit the reconciled list — one record per concept with status, mention count, and provenance offsets — shaped for USCDI Problem / FHIR Condition.
Show full SKILL.md (270 more words)Show less

Hand-off to / from OpenMed

  • From extracting-clinical-entities: consumes analyze_text Disease entities. Run on a sectioned note (segmenting-clinical-sections) for best active-vs-historical signal.
  • From resolving-clinical-context: this skill depends on the negation / temporality / uncertainty axes — reconciliation without them would put "denies chest pain" on the active list.
  • OpenMed calls: from openmed import analyze_text and from openmed.clinical import resolve_span_context, NEGATED, HISTORICAL, HYPOTHETICAL.
  • To FHIR / USCDI: each reconciled problem becomes a Condition with clinicalStatus active/resolved (from temporality) and verificationStatus refuted/provisional (from negation/uncertainty). SNOMED CT codes are user-supplied and grounded out-of-process — OpenMed produces the dedup'd concept and status, not the terminology binding.

Edge cases & gotchas

  • Surface dedup is lossy. "MI" and "myocardial infarction" only fold if your normalizer knows the synonym. Lexical folding handles the easy cases; lean on SNOMED CT grounding for real reconciliation, and never bundle SNOMED — call it out-of-process with the user's credentials.
  • Active beats historical for the same concept. "History of asthma" in PMH plus "asthma exacerbation" in A&P is one active problem, not two entries. Aggregate before assigning status.
  • Don't resurrect resolved problems. A concept seen only as HISTORICAL / "resolved" stays resolved; don't promote it to active just because it appears.
  • Negated and hypothetical are exclusions, not statuses. They never become problem-list entries. Keep them out entirely.
  • Carry provenance. Keep offsets / source sections per problem so a reviewer can trace each entry back to the note text.
  • Local-first, advisory-only. Runs on-device; the reconciled list is decision support for clinician review, not an autonomous diagnosis.

Standards & references

© maziyarpanahi, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/reconciling-problem-lists of maziyarpanahi/openmed.

Open the folder on GitHubat commit 9dca507

Compare with similar skills

Reconciling Problem Lists next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Reconciling Problem Lists compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Reconciling Problem Lists this skillmaziyarpanahi/openmed5.5k—~1.8kAutomated safety check: PassApache-2.0
Sync Upstreamnyaruka/phonenumbers1.6k—~2.8kAutomated safety check: PassMIT
Radiology Tablehuang-sir1/radiology-skills1.9k—~1.3kAutomated safety check: PassCustom licence
ERPClaw ERP Controlleravansaber/erpclaw116—~18kAutomated safety check: PassGPL-3.0
Odoo Agency Fleet Reviewerpipe-org/mcp-odoo421—~699Automated safety check: PassMIT
Beancount Closebex-co/beancount-io296—~1.4kAutomated safety check: PassMIT

Similar skills

  • Sync Upstream

    nyaruka/phonenumbers

    Sync this Go port with a new upstream google/libphonenumber release — regenerate the embedded metadata and reconcile the ported Java logic.

    1.6k GitHub stars~2.8k tokensUpdated 8 days ago
    Business, Finance & HRAuto-check passed
  • Radiology Table

    huang-sir1/radiology-skills

    Create/audit editable publication tables with source reconciliation; not figures or statistical inference.

    1.9k GitHub stars~1.3k tokensUpdated 19 days ago
    Business, Finance & HRAuto-check passed
  • ERPClaw ERP Controller

    avansaber/erpclaw

    Operates the ERPClaw self-hosted ERP in plain language: accounting, invoicing, inventory, purchasing, tax, HR, payroll and reports, treating the ERP as the single source of truth.

    116 GitHub stars~18k tokensUpdated yesterday
    Business, Finance & HRAuto-check passed
  • Odoo Agency Fleet Review

    erpipe-org/mcp-odoo

    Review many client Odoo databases at once through odoo-mcp's cross-instance tools — fleet-wide accounting health, per-client aging, partial-failure triage — for agencies and partners managing 5–50…

    421 GitHub stars~699 tokensUpdated 1 mo ago
    Business, Finance & HRAuto-check passed
  • Beancount Close

    bex-co/beancount-io

    Close an accounting period in a Beancount ledger by reconciling each active account through beancount-reconcile, checking assertions and recurring gaps, reviewing flags, then proposing a commit with…

    296 GitHub stars~1.4k tokensUpdated today
    Business, Finance & HRAuto-check passed
  • Forward Implementation First

    Vuk97/forward-implementation-first

    Keeps an agent building and validating real output instead of servicing its own bookkeeping.

    176 GitHub stars~1.8k tokensUpdated 1 mo ago
    Business, Finance & HRAuto-check passed

More from maziyarpanahi/openmed

All 74 skills in this repo
  • Checks OpenMed de-identified clinical text against the 18 HIPAA Safe Harbor identifier categories and reports gaps and residual re-identification risk.

    5.5k GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • OpenMed Model Card Writer

    maziyarpanahi/openmed

    Fills in a model card for an OpenMed clinical NER or de-identification model from its evaluation reports: intended use, metrics, subgroups and limitations.

    5.5k GitHub stars~1.8k tokensUpdated today
    Auto-check passed
  • Walks a data pipeline against the HIPAA Privacy and Security Rule checklist and produces a gap report before it processes patient data.

    5.5k GitHub stars~2k tokensUpdated today
    Auto-check passed
  • ICD-10 Coding Assistant

    maziyarpanahi/openmed

    Suggests candidate ICD-10-CM diagnosis and ICD-10-PCS procedure codes for clinical text extracted by OpenMed, with rationale for a certified coder to review.

    5.5k GitHub stars~2k tokensUpdated today
    Auto-check passed
  • OpenMed ETL to OMOP CDM

    maziyarpanahi/openmed

    Maps OpenMed-extracted, terminology-coded conditions, drugs and measurements into OMOP CDM v5.4 tables for OHDSI and ATLAS analytics.

    5.5k GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Extracting SDOH and Z-Codes

    maziyarpanahi/openmed

    Finds social risks such as housing instability or food insecurity in clinical notes and proposes matching ICD-10-CM Z-codes for a coder to confirm.

    5.5k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

Questions about Reconciling Problem Lists

What does Reconciling Problem Lists do?

Deduplicate and reconcile OpenMed-extracted conditions into one clean active problem list with clinical status (active / resolved / historical). Reconciling Problem Lists is an agent skill from maziyarpanahi/openmed. Deduplicate and reconcile OpenMed-extracted conditions into one clean active problem list with clinical status (active / resolved / historical).

When should I use Reconciling Problem Lists?

Reconciling Problem Lists fits situations like: wants a problem list; condition reconciliation; dedup of synonymous diagnosis mentions; active-vs-resolved status from a note.

How do I install Reconciling Problem Lists in Claude Code?

Run `npx skills add maziyarpanahi/openmed --skill reconciling-problem-lists -a claude-code`. Or copy the skill folder (skills/reconciling-problem-lists in maziyarpanahi/openmed) into .claude/skills/reconciling-problem-lists in your project. Claude Code loads it when a task matches its description.

How do I install Reconciling Problem Lists in Codex?

Run `npx skills add maziyarpanahi/openmed --skill reconciling-problem-lists -a codex`. Or copy the skill folder (skills/reconciling-problem-lists in maziyarpanahi/openmed) into .agents/skills/reconciling-problem-lists in your project. Codex loads it when a task matches its description.

Can I use Reconciling Problem Lists in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add maziyarpanahi/openmed --skill reconciling-problem-lists -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/reconciling-problem-lists, .gemini/skills/reconciling-problem-lists, .github/skills/reconciling-problem-lists and .opencode/skills/reconciling-problem-lists in your project.

What does Reconciling Problem Lists need to run?

SKILL.md names no scripts, command-line tools or credentials: Reconciling Problem Lists is instructions for the agent only. Our summary lists: Python 3.

Does Reconciling Problem Lists access the network?

SKILL.md names 3 domains. As links in the text: healthit.gov, hl7.org and snomed.org. This is read from the text; nothing was executed.

Is Reconciling Problem Lists safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Reconciling Problem Lists use?

Reconciling Problem Lists is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Reconciling Problem Lists use?

About 1.8k tokens (SKILL.md is roughly 7.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Reconciling Problem Lists?

Skills that share tags, products or a category with Reconciling Problem Lists: Sync Upstream (nyaruka/phonenumbers, 1.6k stars), Radiology Table (huang-sir1/radiology-skills, 1.9k stars), ERPClaw ERP Controller (avansaber/erpclaw, 116 stars) and Odoo Agency Fleet Review (erpipe-org/mcp-odoo, 421 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Reconciling Problem Lists?

maziyarpanahi (a GitHub user) maintains it in maziyarpanahi/openmed, which has 5,500 GitHub stars. The repository holds 74 skills in this directory. The repository was last updated on October 9, 2026.

Source: maziyarpanahi/openmed on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.