-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ingest OMOP2OBO mappings #7
Comments
Sounds great! Just so it's recorded here and since the way we import might be impacted by this. The mappings I sent this morning are the most "confident" i.e. those that are an exact match to a string in a label, definition, or synonym or those that were obtained from an existing dbxref from one the ontology or a support resource. There are other ways to get mappings (e.g., hierarchical search/traverse for parents or children and some fancy new recursive search that we can also leverage) and we can explore those in the future if you think they would be useful. I also want to get your feedback on what I have included in the file since I opted to include a lot of information that makes the file sizes larger and that might not actually be helpful. |
Last thing. In case it is helpful, here are all of the sources that the first version includes mappings from to a Mondo. The number is the count of unique Mondo concepts mapped to each source. There are duplicates here as I am reporting the original way a source has named each vocabulary (when I process these they are normalized on the backend). Summary tables<style> </style>
|
Just documenting here per Nico's request. Tiffany recently produced and explained these ICD10::Mondo mappings:
My basic understanding is that OMOP2OBO was used to generate ICD10/ICD10CM::Mondo mappings. I think an input file (perhaps Mondo itself) was used, because there are some In addition to direct mappings (first tab in the file) there were also mappings done between Mondo terms and ICD term ancestors (first tab), and children (second tab). Sometimes ICD terms were mapped to Mondo children (second tab). I assume that in mapping to ancestors or children, there needed to be a starting place, so I imagine that came from the original set of mappings (from Mondo?) used as an input to this process. @callahantiff If you can correct any of my misunderstanding, that would be great. Here's the raw text from Tiffany's explanation:
|
Lets focus on MONDO/ICD10 related ones for now.
cc @callahantiff
The text was updated successfully, but these errors were encountered: