Comments (6)
@ImkeTammen I am interested in your thoughts here, in particular if your own mapping rules reflected in any of these.. Does this cover the choices you make to decide a mappings?
from disease-mappings.
cc @franknic
from disease-mappings.
For diseases:
2 diseases are the same when :
- They have the same “key” phenotypes/features* AND same etiology
- Note that there is always variability in the phenotypes between patients: not only all patients do not share all the phenotypes, and/or the severity of these phenotypes.
- If diseases share the “key” phenotypes/features but have different etiologies (e.g. variations in different genes are responsible), these diseases are probably of the same “general” group (e.g. Phenotypic series in OMIM; e.g ‘Usher Syndrome’ has multiple types based on the gene involved)
- The definitions of the diseases are the same or similar enough that they are describing the same concept. (this requires manual review).
- Note that the definition might not have enough details to determine whether the diseases are actually the same, and this often requires discussion between curators and sometimes experts
The following conditions are not sufficient to say that 2 diseases are the same, but they give a clue that they could be (ie someone needs to manually review, and additional information is needed)
- 2 diseases share the same label
- 2 diseases share the same phenotype/feature
- 2 diseases share the same etiology (e.g. variation in the same gene can lead to different diseases)
Diseases between species:
note that one cannot say that (for example) a mouse model “has Usher Syndrome”, because “Usher Syndrome” is a human condition. One should say that the mouse “models” Usher Syndrome, or “has the same features as patients with Usher Syndrome”... This is very nitpicky, but it is an important distinction (and also, our jobs :-) ).
I would group diseases of different species under the same “species agnostic disease term” when:
- They have similar “key” phenotypes/features (see notes about phenotypes/features above), AND same or orthologue etiology
- ie genes affected should be orthologous
- Phenotypes affect homologous structures.
(@matentzn , is it the information you are looking for?)
from disease-mappings.
This is excellent. Thank you! This is what I wanted. Let's see what @ImkeTammen has to add!
from disease-mappings.
Mapping phenotypes
2 phenotypes are the same when (I am assuming that it is between species?)
- 2 phenotypes inhere in homologous structures and exhibit the same quality (e.g. increased thickness)
- 2 phenotypes involve identical dysfunction of the same/orthologous process (Molecular Function in GO)
- For example, dysfunction in the “Wnt signaling pathway”. This assumes that genes involved in the “Wnt signaling pathway” were determined for each species and were shown as orthologous between species
- “Identical dysfunction” means that the disruption should be the same, or similar. For instance: a block in Wnt Signaling pathway (ie no output) is different than upregulation
- Note that this should be in homologous structures when known
- Orthologous genes are affected in the same way (e.g. both are down regulated)
- Note that this should be in homologous structures when known
from disease-mappings.
A slightly tangential but illuminating read on clinical mappings https://www.ohdsi.org/web/wiki/doku.php?id=documentation:vocabulary:mapping
from disease-mappings.
Related Issues (17)
- Integrate other mapping sources (drop links)
- Prefix maps do not exist HOT 1
- Ingest Mondo mappings
- Ingest DO, ORDO, OMIM, NCIT mappings HOT 17
- Document ICD10 mapping sources HOT 3
- Ingest OMOP2OBO mappings HOT 3
- Build ingest pipeline for SNOMED-ICD10 mappings HOT 3
- Boomer pipeline prototype implementation for Mondo ICD10CM mapping HOT 4
- Capturing confidence levels from the side of the registry
- Basic progress monitor for mappings HOT 3
- Include Meddra mappings from Open Targets
- Change default license HOT 1
- Rules for disease mappings
- Add mapping sets to disease mapping commons
- Slurp Medgen HPO mappings HOT 1
- UMLS - HPO Mappings HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from disease-mappings.