-
Notifications
You must be signed in to change notification settings - Fork 9
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
Check: Marfan syndrome #101
Comments
This is an area where nosologies break down. Many of the listed diseases (e.g., Marfan) are soo pleiotropic that they can be placed in many categories. Nonetheless, I think that MDs would expect to see these diseases as children of "Genetic aneurysm syndrome" (since the aortic manifestations represent the major clinical problem). I would not recommend futher subclassing (i.e., it is not really the case that Marfan syndrome type 2 is_a Marfan syndrome in a logical sense). |
I agree that the pleiotropy makes syndromic classification unwieldy. Note I only showed a single path as I wanted to focus on the Mf-Mf1-Mf2 triad. But with regards to the syndromic classication, if I were to show the full graph you would see it under 'Rare disease with thoracic aortic aneurysm and aortic dissection', thanks to Orphanet (DO has a flatter classification). But focusing on the Marfan, Marfan1 and Marfan2 quandary, can you elaborate on:
This is what Orphanet has:
Logically, this does not seem wrong. However, the parent definition is weak/underspecified. So perhaps when you say "it is not really the case that Marfan syndrome type 2 is_a Marfan syndrome in a logical sense" you have a stricter definition of (unqualified) "Marfan syndrome" in mind? |
Note DO has no definition for Marfan syndrome. |
Would calling the parent class Marfanoid syndrome help? E.g.
I understand better your point about syndromic classifications. |
Revisiting this Orphanet has:
this causes issues since the OMIM 'canonical' Marfan is mapped to the parent Here is the pre-merge graph (showing common UMLS IDs) @pnrobinson do you think it makes sense to:
|
This is incorrect. AFAIK OMIM does not have Marfan syndrome type 2 because there are doubts as to whether this disease really exists. Please do not make them synonymous! |
I'm OK with whatever solution Peter deems best, provided we don't end up with diseases that have no phenotypes as this looks a bit odd. |
As mentioned there are doubts as to whether this diagnosis is medically valid and whether there should be an entry called Marfan type 2 at all. I personally have worked in this area for about ten years and have never seen a patient with what is called Marfan type 2, and so I would be for putting this diagnosis on our ignore list. |
Right, so let's just take the ID out of our corpus so that we don't end up with zombie entries. :) |
Remember our general strategy is to push fixes upstream, in this case to Orphanet - @annieolry what is Orphanet's position on this? Thus far we have not obsoleted or excluded or merged any orphanet IDs in the merge process, but it sounds like we need to start doing this. |
And just to reiterate, the issue is that we have two Orphanet IDs, one for M, one for M-type-I. Our position is we believe these should be equivalent. I assume we want to take the parent as the primary |
MonDO hierarchy:
Note the apparent duplicate marked
***
.This is the k-boom resolution of this subgraph:
So @pnrobinson will undoubtedly correct me if I'm wrong here, and what we are seeing is that there is more than one type of Marfan. E.g.
http://www.ncbi.nlm.nih.gov/pubmed/18377530 "Marfan syndrome type II: there is more to Marfan syndrome than fibrillin 1."
We are consistent with orphanet here, as can be seen on the kboom resolution. However, we select the OMIM label to be the default. However, OMIM often names a specific disease like a generic disease, so we end up with a merged ontology that is logically fine but terminologically confusing.
It seems we should probably elect Orphanet to have priorities when it comes to labels.
The text was updated successfully, but these errors were encountered: