map-ema-drugs

To map EMA drug products to RxNorm, read ema-info.txt and parsed_data*.tsv files to create a mapping.tsv entry with one row per ma_number, then validate results using provided repository scripts.

Find unmapped EMA product presentations by running the find_unmapped.py script in the skill directory, which lists product folders containing parsed data but missing a mapping.tsv file.

Handling biosimilars during EMA to OMOP mapping involves following guided workflow instructions to parse product data and generate accurate mapping.tsv rows, including specific rules for EU-only products.

Create a flag.txt file during EMA drug mapping validation when items require manual review or lack suitable RxNorm concepts, ensuring proper tracking of presentations that cannot be automatically mapped.

Yes, the EMA to RxNorm mapping workflow supports integration by explaining how to regenerate combined overviews and cross-check mapping.tsv outputs with existing repository validation scripts.

EMA product mappings fail validation if the mapping.tsv schema is incorrect, rows are missing for ma_numbers, or unmapped presentations requiring a flag.txt were not properly identified during the workflow.