-
Notifications
You must be signed in to change notification settings - Fork 4
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
Influenza #52
Comments
We should discuss whether influenza, A, B, and other (variants H5N1, etc.) should be modeled separately. |
Agree we should discuss. I added precisely what was requested.
…On Thu, Jul 13, 2023 at 10:29 AM Harry Hochheiser ***@***.***> wrote:
We should discuss whether influenza, A, B, and other (variants H5N1, etc.)
should be modeled separately.
—
Reply to this email directly, view it on GitHub
<#52 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJR55TMWXRCYILSEAAYMTDXQAH65ANCNFSM6AAAAAA2CCSI2I>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
With respect to influenza, anyway. I think I varied from request on HIV
because of peculiarities of the NCBI Taxon resource.
…On Thu, Jul 13, 2023 at 11:02 AM Bill Hogan ***@***.***> wrote:
Agree we should discuss. I added precisely what was requested.
On Thu, Jul 13, 2023 at 10:29 AM Harry Hochheiser <
***@***.***> wrote:
> We should discuss whether influenza, A, B, and other (variants H5N1,
> etc.) should be modeled separately.
>
> —
> Reply to this email directly, view it on GitHub
> <#52 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAJR55TMWXRCYILSEAAYMTDXQAH65ANCNFSM6AAAAAA2CCSI2I>
> .
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***>
>
|
Looking at the data, I think we should at least have these possibilities:
We can maybe add a specific variant (for example H5N1) if necessary. |
NCBI Taxon ID 11309 is not a parent class of both Influenza A and Influenza B. In fact, the associated label is "unidentified influenzavirus". Inappropriate mixing of epistemology and ontology aside, it cannot serve the function we wish it to. Here is the classification from NCBI: Orthomyxoviridae |
And of course GitHub stripped out all my indentations!!! |
Orthomyxoviridae
|
Thanks for information, To provide more information:
First, the current For the pathogen associated with the disease "Influenza", as the "Influenza" can represent case from either A, B or unknown or both, it is difficult to assign a pathogen. Tycho has an unidentified influenza virus used for "Influenza" disease.
I understand the remark. I don't think something other than "unclassified" pathogen can be use here as we don't know how to "classify" the associated pathogen with the data associated with Influenza, as it can be (A and B) or one strain only but not tested. However, as FLU A and B are the main viruses that routinely spread and cause the seasonal epidemics each year (CDC), I think for some data, we can assume we have both (A and B) in our "Influenza" datasets. So, I have 2 propositions: Proposition I (use the imperfect unidentified pathogen):
Proposition II (have no pathogen specific to Influenza and have A and B as children):
Thanks! |
@hoganwr -- discussed with @LucieContamin. We agreed that proposition II is preferred, diseases and pathogens should be in distinct, mirrored subtrees (with appropriate relationsships between them). |
Just to clarify my proposition II, I was thinking to have in the ontology:
and:
|
I will add the virus classes needed. The "Influenza due to Influenza A" and "Influenza due to Influenza B" part is going to require some extra thinking/work. No OBO ontology has those classes, and I'm not set up at the moment to pull in IRIs from non-OBO artifacts. |
Following the issue #49 ,
Influenza was added to the ontology with:
Would it be possible to update it to have:
It would allow us to have all type of Influenza (as we don't always know the detail) and to match Tycho ontology (https://www.tycho.pitt.edu/dataset/US.6142004/)
Please let me know if any issues or need more information, thanks!
The text was updated successfully, but these errors were encountered: