메뉴
Map EMA centrally authorised product presentations to RxNorm standard concepts. Use when asked to map an EMA product or create/review a mapping.tsv in an EMA product folder.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Search for RxNorm standard concepts using the Hecate semantic search API. Primary search tool for drug mapping.
Parse EMA Authorised Presentations PDF files into structured TSV format. Use when asked to parse, extract, or process raw EMA product PDFs, or to fetch/download new EMA data.
Map Spanish national medicinal products from the AEMPS CIMA registry to RxNorm standard concepts. Use when asked to map a Spanish product, review or correct a Spain `mapping.tsv`, validate a Spain product folder, fix a bad EMA auto-link via `nro_definitivo`, or handle Spain-specific cases such as duplicate `nro_definitivo`, generics, biosimilars, herbal products, or radiopharmaceuticals.
General principles for mapping pharmaceutical products to RxNorm concepts. Covers mapping types (EXACT/BROAD/NO_MAPPING), terminology adaptation, unit conversions, and common pitfalls.
Map Latvian national medicinal products to RxNorm standard concepts. Use when asked to map a Latvian product or create/review a mapping.tsv in a Latvia product folder.
Organize and structure Latvian national medicinal product data from the ZVA registry into product folders.
| name | map-ema-drugs |
| description | Map EMA centrally authorised product presentations to RxNorm standard concepts. Use when asked to map an EMA product or create/review a mapping.tsv in an EMA product folder. |
Map EMA centrally authorised product presentations to RxNorm standard concepts.
When asked to map an EMA product to RxNorm, or create/review a mapping.tsv in an EMA product folder.
To list all product folders that have parsed data but no mapping.tsv:
make find_unmapped
Refer to the find-concepts skill for how to search for RxNorm concepts, and the map-drugs skill for general mapping principles and the standard workflow.
Each product folder under data/ema/products/<ema_number>/ contains:
ema-info.txt: Product metadata (medicine name, active substance, INN, therapeutic area)parsed_data*.tsv: One row per authorised presentation with ma_number, strength, pharmaceutical_form, route_of_administration, packaging, content, pack_size, product_name, active_substance, etc.Read both files to understand the product before mapping.
Create mapping.tsv in the product folder following the schema in the map-drugs skill. The source ID column is ma_number (EU marketing authorisation number from parsed_data.tsv).
One row per ma_number in parsed_data*.tsv. Every presentation must be mapped.
IMPORTANT: Do not assume any logical ordering of ma_number values — they are NOT sorted by strength, dose form, or any other attribute. Always look up each ma_number's actual strength and form from parsed_data*.tsv individually.
If a mapping.tsv already exists, check the mappings and note any needed changes in flag.tsv.
If ema-info.txt contains Biosimilar: Yes, follow the biosimilar mapping rules in the map-drugs skill.
After creating or editing mapping.tsv, validate it:
make validate_mapping ARGS="data/ema/products/<ema_number>/mapping.tsv"
Fix any errors, then regenerate combined files:
make generate_mapping_overviews
If no suitable RxNorm results exist or mapping needs validation, add a flag.txt in the product folder explaining the issue.
Some EMA products have no FDA equivalent and no RxNorm concept. Leave concept fields empty, populate suggestion with the ideal concept name, and create flag.txt.