aeo-devel Mailing List for A_E_O_obsolete
Brought to you by:
yongqunh
Menu
▾
▴
aeo-devel — AEO developer list
You can subscribe to this list here.
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(5) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(41) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2011 |
Jan
(22) |
Feb
(25) |
Mar
(11) |
Apr
(6) |
May
|
Jun
(14) |
Jul
(14) |
Aug
(32) |
Sep
(10) |
Oct
(9) |
Nov
(4) |
Dec
|
| 2012 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <abr...@us...> - 2012-01-23 15:44:45
|
Revision: 108
http://aeo.svn.sourceforge.net/aeo/?rev=108&view=rev
Author: abrayguo
Date: 2012-01-23 15:44:34 +0000 (Mon, 23 Jan 2012)
Log Message:
-----------
added cerivastatin drug term AG
Modified Paths:
--------------
trunk/src/ontology/AEO.owl
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: He, Y. <yon...@me...> - 2011-11-04 23:58:00
|
I will need to talk to Alan and Chris about this. As I know, that AEO name space has not been active. CARO is the one for anatomical entity. Oliver From: Xiang, Allen [mailto:zx...@me...] Sent: Friday, November 04, 2011 12:33 PM To: aeo...@li... Subject: [Aeo-devel] AEO name space taken Hi All, AEO name space is taken in obolibrary by Anatomical Entity Ontology. See http://www.obofoundry.org/cgi-bin/detail.cgi?id=aeo. We may need to find another name, any thoughts? Thanks, Allen ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues |
|
From: Xiang, A. <zx...@me...> - 2011-11-04 16:33:29
|
Hi All, AEO name space is taken in obolibrary by Anatomical Entity Ontology. See http://www.obofoundry.org/cgi-bin/detail.cgi?id=aeo. We may need to find another name, any thoughts? Thanks, Allen ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues |
|
From: <all...@us...> - 2011-11-04 16:21:47
|
Revision: 107
http://aeo.svn.sourceforge.net/aeo/?rev=107&view=rev
Author: allenxiang
Date: 2011-11-04 16:21:41 +0000 (Fri, 04 Nov 2011)
Log Message:
-----------
Added a merged version to release
Added Paths:
-----------
releases/aeo.owl
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <abr...@us...> - 2011-11-03 13:52:50
|
Revision: 106
http://aeo.svn.sourceforge.net/aeo/?rev=106&view=rev
Author: abrayguo
Date: 2011-11-03 13:52:44 +0000 (Thu, 03 Nov 2011)
Log Message:
-----------
added chemotherapy recovery and drug administration terms
Modified Paths:
--------------
trunk/src/ontology/AEO.owl
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <abr...@us...> - 2011-10-28 16:51:35
|
Revision: 105
http://aeo.svn.sourceforge.net/aeo/?rev=105&view=rev
Author: abrayguo
Date: 2011-10-28 16:51:29 +0000 (Fri, 28 Oct 2011)
Log Message:
-----------
added dose range and recovery rate terms along with associated definitions. AG
Modified Paths:
--------------
trunk/src/ontology/AEO.owl
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <yon...@us...> - 2011-10-20 20:02:30
|
Revision: 104
http://aeo.svn.sourceforge.net/aeo/?rev=104&view=rev
Author: yongqunh
Date: 2011-10-20 20:02:24 +0000 (Thu, 20 Oct 2011)
Log Message:
-----------
added terms AE risk factor, AE incidence. Oliver and Abra
Modified Paths:
--------------
trunk/src/ontology/AEO.owl
trunk/src/ontology/catalog-v001.xml
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <abr...@us...> - 2011-10-20 02:58:40
|
Revision: 103
http://aeo.svn.sourceforge.net/aeo/?rev=103&view=rev
Author: abrayguo
Date: 2011-10-20 02:58:34 +0000 (Thu, 20 Oct 2011)
Log Message:
-----------
added CNS neurotoxicity term
Modified Paths:
--------------
trunk/src/ontology/AEO.owl
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <abr...@us...> - 2011-10-19 19:28:41
|
Revision: 102
http://aeo.svn.sourceforge.net/aeo/?rev=102&view=rev
Author: abrayguo
Date: 2011-10-19 19:28:35 +0000 (Wed, 19 Oct 2011)
Log Message:
-----------
Modified Paths:
--------------
trunk/src/ontology/AEO.owl
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <yon...@us...> - 2011-10-13 22:35:59
|
Revision: 101
http://aeo.svn.sourceforge.net/aeo/?rev=101&view=rev
Author: yongqunh
Date: 2011-10-13 22:35:52 +0000 (Thu, 13 Oct 2011)
Log Message:
-----------
More updates on ontofox CHEBI input and output files.
Modified Paths:
--------------
trunk/src/ontology/CHEBI_import.owl
trunk/src/ontology/imports/CHEBI_import_input.txt
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <yon...@us...> - 2011-10-13 22:27:16
|
Revision: 100
http://aeo.svn.sourceforge.net/aeo/?rev=100&view=rev
Author: yongqunh
Date: 2011-10-13 22:27:10 +0000 (Thu, 13 Oct 2011)
Log Message:
-----------
Updated the CHEBI ontofox input and output files. Oliver
Modified Paths:
--------------
trunk/src/ontology/CHEBI_import.owl
trunk/src/ontology/imports/CHEBI_import_input.txt
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <yon...@us...> - 2011-10-13 20:31:50
|
Revision: 99
http://aeo.svn.sourceforge.net/aeo/?rev=99&view=rev
Author: yongqunh
Date: 2011-10-13 20:31:44 +0000 (Thu, 13 Oct 2011)
Log Message:
-----------
Added CHEBI term cisplatin using ontofox. Oliver and Abra
Modified Paths:
--------------
trunk/src/ontology/AEO.owl
trunk/src/ontology/PATO_import.owl
trunk/src/ontology/catalog-v001.xml
trunk/src/ontology/imports/PATO_import_input.txt
Added Paths:
-----------
trunk/src/ontology/CHEBI_import.owl
trunk/src/ontology/imports/CHEBI_import_input.txt
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <yon...@us...> - 2011-10-13 19:51:04
|
Revision: 98
http://aeo.svn.sourceforge.net/aeo/?rev=98&view=rev
Author: yongqunh
Date: 2011-10-13 19:50:58 +0000 (Thu, 13 Oct 2011)
Log Message:
-----------
added many neuropathy AE terms. Oliver and Abra.
Modified Paths:
--------------
trunk/src/ontology/AEO.owl
trunk/src/ontology/catalog-v001.xml
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <yon...@us...> - 2011-10-06 14:14:06
|
Revision: 97
http://aeo.svn.sourceforge.net/aeo/?rev=97&view=rev
Author: yongqunh
Date: 2011-10-06 14:13:59 +0000 (Thu, 06 Oct 2011)
Log Message:
-----------
Added ontofox file for importing DO term. updated OGMS import. Oliver and Abra.
Modified Paths:
--------------
trunk/src/ontology/AEO.owl
trunk/src/ontology/OGMS_import.owl
trunk/src/ontology/catalog-v001.xml
trunk/src/ontology/imports/OGMS_import_input.txt
Added Paths:
-----------
trunk/src/ontology/DOID_import.owl
trunk/src/ontology/imports/DOID_import_input.txt
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <yon...@us...> - 2011-09-29 20:03:47
|
Revision: 96
http://aeo.svn.sourceforge.net/aeo/?rev=96&view=rev
Author: yongqunh
Date: 2011-09-29 20:03:41 +0000 (Thu, 29 Sep 2011)
Log Message:
-----------
Added Abra Guo as a creator. With Abra, added a few terms related to distal sensory neuropathy AE. -- Oliver
Modified Paths:
--------------
trunk/src/ontology/AEO.owl
trunk/src/ontology/catalog-v001.xml
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: He, Y. <yon...@me...> - 2011-09-05 20:18:17
|
Dear Luca, You also made a good point. I agree that we need to consider the roles of pharmacogenomics, drug-drug interactions, and food-drug interactions on the adverse drug events (ADE). In these regards, ADEs are more complex than vaccine adverse events when we look for prediction of AE outcome and the mechanism study. I will make a note on this later. However, with this in mind, I think the current adverse event definition still holds. I think that the complexity of these ADE issues is exactly why we need to develop AEO. Thanks, Oliver -----Original Message----- From: Luc...@me... [mailto:Luc...@me...] Sent: Monday, September 05, 2011 3:32 PM To: He, Yongqun; 'Ryan Brinkman' Cc: Alan Ruttenberg; aeo...@li... Subject: AW: Re: [Aeo-devel] Notes from the AEO/AERO call Dear Oliver, Good point, however i forgot what it has been decided about drugs: in the context of personalized medicine the pharmacogenomics plays a rule, as well drug-drug interactions and food-drug interactions. Often ADEs happen only in very specific situations ... How is that going to be taken care, both at definition level and aswell in practice ? Isn't the definition you are proposing too "specific" for only the Vaccine-related AEs (that due to the underlying biology all share very similar biomedical processes and are perhaps so robust not to care about dose and also about interactions with other entities such as co-admin of drugs or food or genomics..) ? Regards Luca Sincerely your Luca This message and any attachment are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, you must not copy this message or attachment or disclose the contents to any other person. If you have received this transmission in error, please notify the sender immediately and delete the message and any attachment from your system. Merck KGaA, Darmstadt, Germany and any of its subsidiaries do not accept liability for any omissions or errors in this message which may arise as a result of E-Mail-transmission or for damages resulting from any unauthorized changes of the content of this message and any attachment thereto. Merck KGaA, Darmstadt, Germany and any of its subsidiaries do not guarantee that this message is free of viruses and does not accept liability for any damages caused by any virus transmitted therewith. Click http://disclaimer.merck.de to access the German, French, Spanish and Portuguese versions of this disclaimer. ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues |
|
From: <Luc...@me...> - 2011-09-05 19:31:54
|
Dear Oliver, Good point, however i forgot what it has been decided about drugs: in the context of personalized medicine the pharmacogenomics plays a rule, as well drug-drug interactions and food-drug interactions. Often ADEs happen only in very specific situations ... How is that going to be taken care, both at definition level and aswell in practice ? Isn't the definition you are proposing too "specific" for only the Vaccine-related AEs (that due to the underlying biology all share very similar biomedical processes and are perhaps so robust not to care about dose and also about interactions with other entities such as co-admin of drugs or food or genomics..) ? Regards Luca Sincerely your Luca This message and any attachment are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, you must not copy this message or attachment or disclose the contents to any other person. If you have received this transmission in error, please notify the sender immediately and delete the message and any attachment from your system. Merck KGaA, Darmstadt, Germany and any of its subsidiaries do not accept liability for any omissions or errors in this message which may arise as a result of E-Mail-transmission or for damages resulting from any unauthorized changes of the content of this message and any attachment thereto. Merck KGaA, Darmstadt, Germany and any of its subsidiaries do not guarantee that this message is free of viruses and does not accept liability for any damages caused by any virus transmitted therewith. Click http://disclaimer.merck.de to access the German, French, Spanish and Portuguese versions of this disclaimer. |
|
From: He, Y. <yon...@me...> - 2011-09-05 19:22:23
|
Hi Ryan,
Good point. I have thus removed the words " and is possibly induced by the medical intervention " in the definition of the 'adverse event' and moved the possibility story to an editor's note. Now it becomes a definition that I think we all agree:
adverse event = def. "a pathological bodily process that occurs after a medical intervention"
I have also summarized some main goals of the AEO research:
The main scope of AEO includes: (1) represent terms and relations in the area of adverse events, (2) assess possible associations between an adverse event and a medical intervention, particularly, identify any causal effect of a medical intervention to an adverse event; and (2) understand the mechanism (including molecular mechanisms) of causal adverse events.
I added the third aim because that is what many groups (including mine) are working now to identify some molecular markers and pathways under specific adverse events.
Best,
Oliver
-----Original Message-----
From: Ryan Brinkman [mailto:rbr...@bc...]
Sent: Sunday, September 04, 2011 8:05 PM
To: He, Yongqun
Cc: Melanie Courtot; Alan Ruttenberg; si...@um...; aeo...@li...
Subject: Re: Notes from the AEO/AERO call
On 2011-09-04, at 4:51 PM, He, Yongqun wrote:
> Hi Melanie,
> Good notes! We had a very good meeting last Friday. I am glad that you agree the global term adverse event belongs to AEO and AERO will use the AEO term.
>
> As discussed, I have removed the may or may not sentence out of the AE definition. I have also added a note on the work to be done in the scope, notably regarding temporal association.
>
> I have updated the AEO definition of 'adverse event' to this:
> "a pathological bodily process that occurs after a medical intervention and is possibly induced by the medical intervention."
> One note: I still keep the second half of the definition (" is possibly induced by the medical intervention") for some more discussion.
"possibly induced" is the same as "may or may not be induced" and for the same reason as above probably wouldn't this belong in the editor's note?
> My reasons:
> (1) I feel that our ultimate goal (or the goal in clinics) of study adverse events is to assess if the adverse event outcome is due to the medical intervention. Of course, there is different level of association. I would argue that all adverse events reported in VAERS are possibly associated with the medical intervention. This is why the data are collected, and assessment of the association needs to be done.
> (2) Also, by including the second half of definition, we do not have to include any time frame in the definition any more. If the time is too long (e.g., one year) for one flu vaccine for a symptom (e.g, rash), we would consider that it is impossible (or very very low chance) to be related to the vaccination. Since it is impossible, according to the definition, we will not need to study it. For some new medical invention, since we don't know how long the incubation time would be, we will then need to monitor longer time.
> (3) Broadly, the definition also covers those AEs that were eventually found to have not association with the intervention. It this case, the probability is 0.
>
> In this sense, I generated a term 'causal adverse event probability' under 'information content entity'. I think for each adverse event, it can have some superclass:
> has_output some 'causal adverse event probability'.
>
> under the term 'causal adverse event probability', we have two subclasses already:
> Naranjo ADR probability score
> DIPS score
> these two scores have been frequently used in drug adverse event probability assessment.
>
> Any suggestions and comments are welcome.
> Thanks!
> Oliver
>
> ________________________________________
> From: Melanie Courtot [mco...@gm...]
> Sent: Friday, September 02, 2011 7:14 PM
> To: He, Yongqun; Ryan Brinkman; Alan Ruttenberg; si...@um...
> Subject: Notes from the AEO/AERO call
>
> A few notes from our call:
>
> - global term adverse event belongs to AEO. Current definition to be updated to "a pathological bodily process that occurs after a medical intervention" with in an editor note "An adverse event can be caused by the medical intervention, or may not be caused by the medical intervention." (having may or may not in the definition logically cancels itself) An additional note will be added to indicate that some work is needed on how to restrict the scope of this term, notably regarding temporal association
>
> - AERO will include "recorded AE" (such as those from randomized clinical trials, could be anything eg pregnancy etc), defines as "an AE that has some information entity about it recorded in an EHR"
>
> - AERO will include "reported AE" to represent those recorded AEs that are selected and evaluated against guidelines to determine if they should be reported higher-up (such as in VAERS)
>
> - those selection and evaluation processes will be added to AERO (including assessment of "serious AE" etc) as those are done against specific guidelines
>
> - AERO will provide the framework to represent those against the guidelines, and will provide documentation to address Oliver's needs
>
> - Melanie will clarify with her clinicians if "recorded AE" should be a subclass of AE or instead should be "recorded event" and be sibling (i.e., are all recorded events adverse events?) and will update above definitions as needed
>
> - Oliver will produce a list of the types of statements AEO aims to make
>
> Cheers,
> Melanie
> **********************************************************
> Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
>
**********************************************************
Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
|
|
From: <yon...@us...> - 2011-09-05 19:21:43
|
Revision: 95
http://aeo.svn.sourceforge.net/aeo/?rev=95&view=rev
Author: yongqunh
Date: 2011-09-05 19:21:36 +0000 (Mon, 05 Sep 2011)
Log Message:
-----------
modified the AE definition and notes. Oliver
Modified Paths:
--------------
trunk/src/ontology/AEO.owl
trunk/src/ontology/catalog-v001.xml
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <yon...@us...> - 2011-09-05 00:28:33
|
Revision: 94
http://aeo.svn.sourceforge.net/aeo/?rev=94&view=rev
Author: yongqunh
Date: 2011-09-05 00:28:27 +0000 (Mon, 05 Sep 2011)
Log Message:
-----------
addes a superclass for 'adverse event':
preceded_by some 'medical intervention'
Oliver
Modified Paths:
--------------
trunk/src/ontology/AEO.owl
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: Ryan B. <rbr...@bc...> - 2011-09-05 00:05:10
|
On 2011-09-04, at 4:51 PM, He, Yongqun wrote:
> Hi Melanie,
> Good notes! We had a very good meeting last Friday. I am glad that you agree the global term adverse event belongs to AEO and AERO will use the AEO term.
>
> As discussed, I have removed the may or may not sentence out of the AE definition. I have also added a note on the work to be done in the scope, notably regarding temporal association.
>
> I have updated the AEO definition of 'adverse event' to this:
> "a pathological bodily process that occurs after a medical intervention and is possibly induced by the medical intervention."
> One note: I still keep the second half of the definition (" is possibly induced by the medical intervention") for some more discussion.
"possibly induced" is the same as "may or may not be induced" and for the same reason as above probably wouldn't this belong in the editor's note?
> My reasons:
> (1) I feel that our ultimate goal (or the goal in clinics) of study adverse events is to assess if the adverse event outcome is due to the medical intervention. Of course, there is different level of association. I would argue that all adverse events reported in VAERS are possibly associated with the medical intervention. This is why the data are collected, and assessment of the association needs to be done.
> (2) Also, by including the second half of definition, we do not have to include any time frame in the definition any more. If the time is too long (e.g., one year) for one flu vaccine for a symptom (e.g, rash), we would consider that it is impossible (or very very low chance) to be related to the vaccination. Since it is impossible, according to the definition, we will not need to study it. For some new medical invention, since we don't know how long the incubation time would be, we will then need to monitor longer time.
> (3) Broadly, the definition also covers those AEs that were eventually found to have not association with the intervention. It this case, the probability is 0.
>
> In this sense, I generated a term 'causal adverse event probability' under 'information content entity'. I think for each adverse event, it can have some superclass:
> has_output some 'causal adverse event probability'.
>
> under the term 'causal adverse event probability', we have two subclasses already:
> Naranjo ADR probability score
> DIPS score
> these two scores have been frequently used in drug adverse event probability assessment.
>
> Any suggestions and comments are welcome.
> Thanks!
> Oliver
>
> ________________________________________
> From: Melanie Courtot [mco...@gm...]
> Sent: Friday, September 02, 2011 7:14 PM
> To: He, Yongqun; Ryan Brinkman; Alan Ruttenberg; si...@um...
> Subject: Notes from the AEO/AERO call
>
> A few notes from our call:
>
> - global term adverse event belongs to AEO. Current definition to be updated to "a pathological bodily process that occurs after a medical intervention" with in an editor note "An adverse event can be caused by the medical intervention, or may not be caused by the medical intervention." (having may or may not in the definition logically cancels itself) An additional note will be added to indicate that some work is needed on how to restrict the scope of this term, notably regarding temporal association
>
> - AERO will include "recorded AE" (such as those from randomized clinical trials, could be anything eg pregnancy etc), defines as "an AE that has some information entity about it recorded in an EHR"
>
> - AERO will include "reported AE" to represent those recorded AEs that are selected and evaluated against guidelines to determine if they should be reported higher-up (such as in VAERS)
>
> - those selection and evaluation processes will be added to AERO (including assessment of "serious AE" etc) as those are done against specific guidelines
>
> - AERO will provide the framework to represent those against the guidelines, and will provide documentation to address Oliver's needs
>
> - Melanie will clarify with her clinicians if "recorded AE" should be a subclass of AE or instead should be "recorded event" and be sibling (i.e., are all recorded events adverse events?) and will update above definitions as needed
>
> - Oliver will produce a list of the types of statements AEO aims to make
>
> Cheers,
> Melanie
> **********************************************************
> Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
>
|
|
From: He, Y. <yon...@me...> - 2011-09-04 23:51:13
|
Hi Melanie,
Good notes! We had a very good meeting last Friday. I am glad that you agree the global term adverse event belongs to AEO and AERO will use the AEO term.
As discussed, I have removed the may or may not sentence out of the AE definition. I have also added a note on the work to be done in the scope, notably regarding temporal association.
I have updated the AEO definition of 'adverse event' to this:
"a pathological bodily process that occurs after a medical intervention and is possibly induced by the medical intervention."
One note: I still keep the second half of the definition (" is possibly induced by the medical intervention") for some more discussion.
My reasons:
(1) I feel that our ultimate goal (or the goal in clinics) of study adverse events is to assess if the adverse event outcome is due to the medical intervention. Of course, there is different level of association. I would argue that all adverse events reported in VAERS are possibly associated with the medical intervention. This is why the data are collected, and assessment of the association needs to be done.
(2) Also, by including the second half of definition, we do not have to include any time frame in the definition any more. If the time is too long (e.g., one year) for one flu vaccine for a symptom (e.g, rash), we would consider that it is impossible (or very very low chance) to be related to the vaccination. Since it is impossible, according to the definition, we will not need to study it. For some new medical invention, since we don't know how long the incubation time would be, we will then need to monitor longer time.
(3) Broadly, the definition also covers those AEs that were eventually found to have not association with the intervention. It this case, the probability is 0.
In this sense, I generated a term 'causal adverse event probability' under 'information content entity'. I think for each adverse event, it can have some superclass:
has_output some 'causal adverse event probability'.
under the term 'causal adverse event probability', we have two subclasses already:
Naranjo ADR probability score
DIPS score
these two scores have been frequently used in drug adverse event probability assessment.
Any suggestions and comments are welcome.
Thanks!
Oliver
________________________________________
From: Melanie Courtot [mco...@gm...]
Sent: Friday, September 02, 2011 7:14 PM
To: He, Yongqun; Ryan Brinkman; Alan Ruttenberg; si...@um...
Subject: Notes from the AEO/AERO call
A few notes from our call:
- global term adverse event belongs to AEO. Current definition to be updated to "a pathological bodily process that occurs after a medical intervention" with in an editor note "An adverse event can be caused by the medical intervention, or may not be caused by the medical intervention." (having may or may not in the definition logically cancels itself) An additional note will be added to indicate that some work is needed on how to restrict the scope of this term, notably regarding temporal association
- AERO will include "recorded AE" (such as those from randomized clinical trials, could be anything eg pregnancy etc), defines as "an AE that has some information entity about it recorded in an EHR"
- AERO will include "reported AE" to represent those recorded AEs that are selected and evaluated against guidelines to determine if they should be reported higher-up (such as in VAERS)
- those selection and evaluation processes will be added to AERO (including assessment of "serious AE" etc) as those are done against specific guidelines
- AERO will provide the framework to represent those against the guidelines, and will provide documentation to address Oliver's needs
- Melanie will clarify with her clinicians if "recorded AE" should be a subclass of AE or instead should be "recorded event" and be sibling (i.e., are all recorded events adverse events?) and will update above definitions as needed
- Oliver will produce a list of the types of statements AEO aims to make
Cheers,
Melanie
**********************************************************
Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
|
|
From: <yon...@us...> - 2011-09-04 23:27:05
|
Revision: 93
http://aeo.svn.sourceforge.net/aeo/?rev=93&view=rev
Author: yongqunh
Date: 2011-09-04 23:26:59 +0000 (Sun, 04 Sep 2011)
Log Message:
-----------
added one note to the AE term.
Modified Paths:
--------------
trunk/src/ontology/AEO.owl
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <yon...@us...> - 2011-09-04 23:15:09
|
Revision: 92
http://aeo.svn.sourceforge.net/aeo/?rev=92&view=rev
Author: yongqunh
Date: 2011-09-04 23:15:03 +0000 (Sun, 04 Sep 2011)
Log Message:
-----------
Updated the definition of 'adverse event'. Added an AEO scope description. Added a new term 'causal adverse event probability'.
Modified Paths:
--------------
trunk/src/ontology/AEO.owl
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <yon...@us...> - 2011-08-22 14:36:30
|
Revision: 91
http://aeo.svn.sourceforge.net/aeo/?rev=91&view=rev
Author: yongqunh
Date: 2011-08-22 14:36:21 +0000 (Mon, 22 Aug 2011)
Log Message:
-----------
added 10 DIPS questions and 10 Naranjo criteria, which are used for causality analysis of adverse drug reactions.
Modified Paths:
--------------
trunk/src/ontology/AEO.owl
trunk/src/ontology/OBI_import.owl
trunk/src/ontology/catalog-v001.xml
trunk/src/ontology/imports/OBI_import_input.txt
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
2 messages has been excluded from this view by a project administrator.
