You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using a script to automate the mapping of medication data from NDC codes to RxNorm RXCUIs utilizing the "Non-Standard to Standard Relationship" mapping found in the OMOP common data model. Is semapv:MappingChaining the correct mapping justification in this case? or is there a better alternative for automated mappings?
The text was updated successfully, but these errors were encountered:
@a-chahin There are no 100% matured guidelines here. I would recommend using semapv:MappingChaining only when two already established mappings are combined. If there is a mapping justification and semantic mapping predicate for NDC->OMOP (i.e. semapv:LexicalMatching, and skos:exactMatch) and the same for OMOP->Rxnorm (which afaik there is not, because OMOP standard to non standard is "exact or broad", with no way to know which is which, and no formal justifications combined).
Its tough in your case. Depending on the mapping predicate you use for the NDC->RxNorm mapping, maybe semapv:MappingChaining is ok, but then I would make a comment in the mapping set metadata saying how the chaining exactly was applied (e.g. how you interpreted the OMOP NS-S mappings).
We are using a script to automate the mapping of medication data from NDC codes to RxNorm RXCUIs utilizing the "Non-Standard to Standard Relationship" mapping found in the OMOP common data model. Is
semapv:MappingChaining
the correct mapping justification in this case? or is there a better alternative for automated mappings?The text was updated successfully, but these errors were encountered: