map-latvia-drugs

Map Latvian medicinal product presentations to RxNorm concepts in mapping.tsv files.

5|1|Updated Dec 4, 2025
One-click install
npx skills add https://github.com/mi-erasmusmc/ema-authorised-to-rxnorm-mappings --skill map-latvia-drugs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: map-latvia-drugs
Source: https://github.com/mi-erasmusmc/ema-authorised-to-rxnorm-mappings/tree/main/.claude/skills/map-latvia-drugs
Command: npx skills add https://github.com/mi-erasmusmc/ema-authorised-to-rxnorm-mappings --skill map-latvia-drugs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes Latvian national medicinal product records by mapping presentation-level product entries to RxNorm/OMOP concepts, reducing manual lookup and inconsistent mappings across datasets.

Core Features & Use Cases

  • Presentation-level mapping: Read data_*.tsv files to map each product presentation (product_id, strength, form, total dose) to an appropriate RxNorm concept.
  • Context-aware verification: Use info.txt and, only when necessary, SmPC/PIL references to resolve ambiguous doses, formulation bases, or country-specific naming conventions.
  • Integration and validation: Invoke repository search and validation tools to generate mapping.tsv files that follow the map-drugs schema and support downstream overview generation.

Quick Start

Open the product folder under data/latvia/products, read the data_*.tsv and info.txt, perform RxNorm searches using find-concepts, and create a validated mapping.tsv following the map-drugs schema.

Frequently Asked Questions about map-latvia-drugs

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

FAQPage Schema
How do I map Latvian medicinal product entries to RxNorm standard concepts?

Map Latvian medicinal products to RxNorm by reading presentation-level data_*.tsv files, performing broad RxNorm searches with find-concepts, and validating outputs with map-drugs scripts to generate a schema-compliant mapping.tsv file.

When do I need to consult SmPC or PIL references during drug vocabulary mapping?

Consult SmPC or PIL references during drug vocabulary mapping only when needed to resolve ambiguous doses, formulation bases, or country-specific naming conventions that cannot be clarified from presentation-level data_*.tsv and info.txt files alone.

Can I use RxNorm find-concepts searches to resolve ambiguous pharmaceutical formulations in OMOP datasets?

Yes, you can use RxNorm find-concepts searches to resolve ambiguous pharmaceutical formulations in OMOP datasets by querying standard concepts and then verifying the matches against presentation-level data and info.txt context.

What is the best way to validate vocabulary mapping outputs for OMOP compliance?

The best way to validate vocabulary mapping outputs for OMOP compliance is to run repository map-drugs validation scripts on your generated mapping.tsv file to ensure all records conform to the required downstream schema.

How do I resolve country-specific naming conventions when mapping national medicinal products to RxNorm?

Resolve country-specific naming conventions by reading the local presentation-level data_*.tsv and info.txt files first, and only consulting SmPC references if the product naming or formulation base remains ambiguous after the initial data review.

What are the limitations of mapping presentation-level drug records without SmPC context?

Mapping presentation-level drug records without SmPC context risks misinterpreting ambiguous doses or formulation bases, because data_*.tsv and info.txt files may lack the detailed pharmaceutical descriptions needed for accurate RxNorm standard concept matching.