-
Notifications
You must be signed in to change notification settings - Fork 54
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
Revise classification of MONDO:0044013 'puerperal disorder' #652
Comments
Maybe define pregnancy disorder more generally, to include during or having a causal link to? |
@cmungall I opened a ticket for EFO so we can come back to this. Thanks. |
@cmungall - @paolaroncaglia and others discussed this when we met earlier this week - it seems like some of the subclasses of pregnancy disorder are not proper children of 'female reproductive system disease' (which is a disease with a location in the female reproductive system). For example, 'gestational diabetes' is not located in the female reproductive system, or 'chorea gravidarum'. I suggest we revise the text def of pregnancy disorder and reclassify it to a child of 'disease or disorder'. |
@cmungall and @pnrobinson any objections to my comment above? |
@nicolevasilevsky @cmungall The difficulty is that if we want to define diseases "logically" there will be a massive and inconsistent hierarchy. Having superclasses such as pregnancy disorder make things difficult because there is no specialist for puerperal disorders -- all of this is the obstetrician. |
@pnrobinson @nicolevasilevsky @cmungall |
@cmungall should we follow EFO's proposal (EBISPOT/efo#417)? If yes, I can work on implementing this in Mondo |
@paolaroncaglia I am reading through this thread and EBISPOT/efo#490 and want to clarify what the action items are: Should Mondo create a new term 'perinatal condition' (per EBISPOT/efo#490) and 'puerperal disorder' should be reclassified as a child of this term? Should 'pregnancy disorder' be a child of 'disease or disorder'? Thanks! |
@nicolevasilevsky "Should Mondo create a new term 'perinatal condition' (per EBISPOT/efo#490)" "and 'puerperal disorder' should be reclassified as a child of this term?" "Should 'pregnancy disorder' be a child of 'disease or disorder'?" Ideally we should synchronize the changes in EFO and MONDO, to avoid inconsistency post-release(s). I'll see if I can edit EFO before I leave for a short trip + bank holiday (away from my desk 22-29 August), and will update EBISPOT/efo#490 accordingly. Many thanks for your work. |
Thanks for the clarification @paolaroncaglia! I'll wait until you have updated this ticket (EBISPOT/efo#490), then I will follow your workflow. |
@nicolevasilevsky |
No problem, enjoy your holiday! |
Just a comment -- should we really use prenatal "condition" -- is there an intentional distinction to "disease"? |
@pnrobinson |
@nicolevasilevsky |
@nicolevasilevsky
Nothing else would be needed from Mondo at this stage, although (not urgent) you might want to
Many thanks, |
@nicolevasilevsky |
No need to apologize @paolaroncaglia, thanks for the nudge. I tagged this with our new milestone "December release". Regarding MONDO:0044014 postpartum thyroiditis: |
I deleted the xref to EFO_1001428, it does seem wrong |
MONDO:0044013 'puerperal disorder' is a subclass of 'pregnancy disorder'.
But pregnancy goes from conception to birth, while puerperium covers the six-to-eight-week period after birth.
I was going to suggest that 'puerperal disorder' should be a subclass of 'female reproductive system disease' instead, but puerperal disorders cover other areas too (see e.g. its children 'postpartum psychosis' and 'postpartum thyroiditis'). So I'm not sure what broader parent would work for 'puerperal disorder', other than the top-level 'disease or disorder'... I can't see any of the existing terms being appropriate. On the other hand, grouping disorders that occur during that time might be useful from a medical perspective.
Suggestions please?
(EFO has the same issue, but our 'puerperal disorder' was modelled after yours ;-) )
The text was updated successfully, but these errors were encountered: