Closed kanems closed 3 years ago
@kanems we would like to defer to your mapping, and I think all of the existing mappings in our file are legacy. One request would be to help us with providing instructions to our users of how to get the mapping from UMLS. It would be great if we could provide users with a script that would generate the current mapping, but I am not aware of how to do this. Would this be possible? @drseb @matentzn thoughts? In the meantime, I will remove these old legacy xrefs.
These are the issues:
Rod-cone dystrophy is the major phenotype of Retinitis pigmentosa, I think that is ok
Rachitic rosary is near-synonymous beading of ribs
I have corrected the above items. We will work towards a better way of recording the UMLS mappings this year.
I am working to resolve discrepancies in the UMLS CUI/HPO mappings in the NIH MedGen/GTR database and I have found several examples where HPO seems to be citing incorrect UMLS CUIs and SNOMEDCT IDs as cross references. I am attaching an excel file with examples, but can say it is almost certainly not an exhaustive list.
How are the Cross references on HPO terms determined? Does HPO compute these, or is it based on how UMLS has mapped/placed HPO concepts within their CUIs? How does HPO respond to/deal with UMLS mapping multiple HPO terms to a single UMLS CUI? (Or is this not problematic for your dataflow?)
Dec2020_HPO_UMLSCrossRefs.xlsx