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
Consider them identical to all Ingredient (IN) identifiers -- in this case, RXCUI 5640 "ibuprofen". But note that this does not work with MINs, which work the other way, and tell you which drugs include this one.
Add additional names from RxNorm -- trade names, formulations, etc -- as synonyms of this concept.
This will have the side-benefit of getting rid of a lot of e.g. "Ibuprofen 50MG" entries in NameRes, since they would be cliqued into their ingredients. We could also extract RxNorm-UMLS and RxNorm-MeSH mappings (maybe to other sources as well: ChEBI? UNII?) so that we clique them together with other drugs.
This does basically 2 things -
1. It adds in RXNORM identifiers and creates a Drug compendium
2. It pulls in RXNORM relationships and PUBCHEM RXNORM annotations and creates a drug/chemical conflation
Fixes#150Fixes#144
RxNorm is a definitive source for drug information, and so we need to include RXCUIs in cliques.
The general algorithm we should use is:
This will have the side-benefit of getting rid of a lot of e.g. "Ibuprofen 50MG" entries in NameRes, since they would be cliqued into their ingredients. We could also extract RxNorm-UMLS and RxNorm-MeSH mappings (maybe to other sources as well: ChEBI? UNII?) so that we clique them together with other drugs.
Would close TranslatorSRI/NodeNormalization#127
The text was updated successfully, but these errors were encountered: