concept-mapping-drug

To map source drug concepts to OMOP RxNorm, the process parses ingredient, strength, and dose form from concept labels, then validates three-component equivalence against OMOP vocabulary tables loaded in DuckDB. It uses relationship traversal and structured search to return approved mappings.

Preventing incorrect drug terminology matches requires strict validation of ingredient, strength, and dose form equivalence. The mapping process blocks unsafe matches for incompatible dose forms, incorrect strengths, categories instead of specific drugs, and homeopathic or diluted products to ensure clinical accuracy.

Concept mapping for OMOP drugs requires a DuckDB session at /tmp/concept-mapping-session.duckdb. This database must contain the concept, concept_synonym, concept_relationship, concept_ancestor, source_concepts, and existing_mappings tables to successfully query and validate RxNorm Clinical Drug candidates.

Trade-name synonyms can be used for RxNorm drug mapping through optional synonym resolution. When structured search based on ingredient, strength, and dose form is performed, the system queries the concept_synonym table to resolve trade names to their corresponding OMOP RxNorm Clinical Drug concepts.

Limitations when mapping drugs to RxNorm include blocking mappings for incompatible dose forms, incorrect strengths, categories mapped instead of specific drugs, and homeopathic or diluted products. The strict validation rules ensure only exact three-component equivalence passes the mapping process.