resolve-conflicts

To resolve conflicting RxNorm mappings, you can use a Python script to scan EMA and Latvia TSV files, group disagreements by EMA product folder, and launch subagents to update the less accurate mapping.tsv entries.

RxNorm mapping conflicts occur when the same medicinal product is assigned different concept_ids across EMA and Latvia files, often caused by strength or form mismatches and branded versus unbranded concept disagreements.

You align EMA and Latvia RxNorm TSV files by running included Python scripts that build a Latvia folder index, enumerate conflicting MA numbers, and emit folder paths for subagent-based resolution.

Yes, git repository access is required because the conflict resolution process relies on included Python scripts to scan TSV files and update product-level mapping.tsv files grouped by EMA folder.

The best way to batch resolve RxNorm concept disagreements is to run the conflict finder script to list affected EMA folders, then launch one parallel subagent per folder to inspect source data and update mappings.

A limitation is that the Python scripts only process repositories containing ema-to-rxnorm.tsv and latvia-to-rxnorm.tsv files, and require manual subagent inspection to determine which concept assignment is more accurate.