normalizing-rxnorm

Normalize free-text medication mentions into validated RxNorm RxCUIs via RxNav API.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts free-text medication mentions into stable RxNorm concepts, reducing ambiguity between brand names, generic ingredients, strengths, and dose forms while supporting interoperable clinical data.

Core Features & Use Cases

  • Medication normalization: Resolve drug names to RxNorm RxCUIs using exact and approximate RxNav REST API matching.
  • Product classification: Distinguish ingredients, semantic clinical drugs, semantic branded drugs, brand names, and precise ingredients.
  • Clinical interoperability: Attach NDCs, preserve source offsets and confidence scores, and produce US Core Medication-compatible coding.
  • OpenMed integration: Consume Pharmaceutical and Chemical entities extracted from clinical text while keeping raw patient notes out of external requests.
  • Use Case: Normalize mentions such as metformin 500 mg, Lipitor, or amoxicillin/clavulanate into validated RxCUIs for medication lists, analytics, and clinical exchange.

Quick Start

Use the normalizing-rxnorm skill after OpenMed medication entity extraction to resolve each de-identified drug span through RxNav and return its validated RxCUI, display name, term type, confidence, and source offsets.

Frequently Asked Questions about normalizing-rxnorm

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

FAQPage Schema
How do I normalize free-text medication mentions to RxNorm RxCUIs?

To normalize medication mentions to RxNorm RxCUIs, the skill uses the RxNav REST API for exact and approximate matching, resolving drug spans like metformin 500 mg into stable, interoperable clinical codes.

What is RxNorm medication normalization and when do I need it?

RxNorm medication normalization converts ambiguous drug names into validated RxCUIs, distinguishing between brand names, generic ingredients, strengths, and dose forms for clinical data exchange.

Can I resolve clinical drug mentions to RxNorm without sending raw patient notes to external APIs?

Yes, the skill consumes de-identified pharmaceutical and chemical entities extracted from clinical text, preserving source offsets while keeping raw patient notes out of external RxNav REST API requests.

How do I deduplicate brand and generic drug names using RxNav?

The skill classifies drug mentions into ingredients, semantic clinical drugs, and branded drugs using RxNav REST API matching, enabling brand and generic deduplication for medication reconciliation.

Does this medication normalization approach support US Core Medication workflows and NDC lookup?

Yes, the skill produces US Core Medication-compatible coding, attaches National Drug Code (NDC) identifiers, and validates RxNorm term types to support interoperable clinical workflows.

What are the limitations of approximate-match confidence gating in RxNav?

Approximate-match confidence gating requires validation of RxNorm term types and obsolete-concept checks, meaning low-confidence matches may be filtered out to ensure reliable medication normalization.