Open andrewsu opened 1 year ago
Just realized that the correct mappings from these UMLS IDs to MeSH IDs are being returned by the prod instance of Node Normalizer:
But I'll leave this issue open in case dev is being used to test release candidates to prod.
Yes, we’re hoping to push dev to prod soon, so this would be great to fix before we do!---Typed on a tiny phone.On Feb 7, 2023, at 12:43 PM, Andrew Su @.***> wrote: Just realized that the correct mappings from these UMLS IDs to MeSH IDs are being returned by the prod instance of Node Normalizer:
https://nodenorm.transltr.io/1.3/get_normalized_nodes?curie=UMLS:C0039286 https://nodenorm.transltr.io/1.3/get_normalized_nodes?curie=UMLS:C0035525 https://nodenorm.transltr.io/1.3/get_normalized_nodes?curie=UMLS:C0023570
But I'll leave this issue open in case dev is being used to test release candidates to prod.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>
Node Normalizer currently reports no mappings to MESH for tamoxifen: https://nodenormalization-sri.renci.org/1.3/get_normalized_nodes?curie=UMLS:C0039286. But the UMLS metathesaurus browser does include MESH mapping (https://uts.nlm.nih.gov/uts/umls/concept/C0039286 -> D013629)
Same applies to ribavirin:
and levodopa