Workshop on Clinical Trial Ontology

From NCBO Wiki
Jump to navigation Jump to search

General Information

The National Center for Biomedical Ontology will host a two-day workshop focused on the Ontology of Clinical Trials. The workshop will take place in March 2007; venue to be determined.

Aim of the workshop

The aim of the workshop is to foster the creation of a reference ontology (high-quality controlled structured vocabulary) for clinical trial annotation. The ontology should provide a definitions for terms like: cohort, randomization, placebo, response, efficacy, control, protocol, null hypothesis, control, etc., including also major relevant statistical terms.

The proposed CTO should:

(1) fully and faithfully capture the types of entities and relationships involved in clinical trials of any experimental design

(2) comprehend all the terms needed for the task of meta-analysis of clinical trials

(3) support trial bank interoperation

(4) form an integral part of a more comprehensive investigation ontology, including also the Functional Genomics Investigation Ontology, which should form part of the OBO Foundry.

The purpose of the meeting is to bring together representatives of the major groups involved in clinical trial informatics, design, execution, analysis and standardization in order to approve an initial draft of the CTO and create a strategy for its further development and testing.

Further topics to be addressed include:

i. The relation between CTO and data-model-oriented initiatives (HL7, CDISC, BRIDG, caBIG). ii. The relations between CTO and a drug (trial) ontology iii. The relations between CTO and an epidemiology study ontology

>> think that in medical informatics, we tend to conflate #2 and #4 >> because we're always thinking of data for a particular patient (or >> clinical trial) as the most specific information that needs to be >> captured. So, needing to capture eg Jane's particular oophorectomy, >> the type may be SURGICAL-INTERVENTION, the sub-type may be >> OOPHORECTOMY, and the instance JANE'S-OOPHORECTOMY. From the point >> of view of an ontologist of surgery, however, who doesn't deal with >> actual cases of oophorectomies, OOPHORECTOMY can well be an >> instance, with no need to consider or represent particular >> oophorectomies. In contrast, because many medical informaticians >> take care of patients, we tend to care about particular >> oophorectomies and consider those to be the 'instances'. This then >> causes us to draw the type-instance distinction at a different level >> of specificity than a pure ontologist of surgery would. >> >> In sum, I don't think the naming of meaning #4, or any of the >> meanings, is the problem, but rather a different conceptualization >> of how specific/particular a representation has to be. I hope that >> clarified rather than confused things? And hard to do this by email! >> >> Do you have a tentative month/days for the workshop? >> >> Best, >> Ida >> >> >> On 5/27/06 2:54 AM, "Smith, Barry" <phismith@buffalo.edu> wrote: >> >> Dear Ida, >> I plan to organize a clinical trials ontology workshop in 2007, as >> one of the Center's dissemination workshops, and I am hoping very >> much that you will be involved. Here, to set us going, is my >> thinking on types vs. instances: >> The term 'instance' is used in different ways by different communities. >> 1. In the database world it means, officially, a complete database >> environment, including software, table structure, etc.; used when >> administrators need to describe multiple instances of the same database type. >> 2. However, the term 'instance' is also used loosely in the >> information modelling world (e.g. by HL7), to mean the data in a >> database about a specific case or particular (the data about Jane, >> the data about Jane's oophorectomy). >> >> 3. Sometimes ontology people use 'instance' to mean 'leaf node' in an is >> 4. In the philosophical ontology world, however, and increasingly in >> the GO/OBO world, 'instance' is used to mean: a particular >> (individual, spatiotemporal, normally observable) entity which >> instantiates a given type. Thus a particular organism, cell, tumor, >> pill, surgical intervention, .... >> Did I miss anything out? >> I think we need a term to cover meaning 4., though I would be happy >> to substitute another term for this if one is suggested. >> With greetings >> Barry >> At 10:58 PM 5/26/2006, Ida Sim wrote: >> Chris, >> Thanks for this. It's great to see the trial bank schema and instance data >> imported into OBD as a first step. >> We are indeed interested in a reference ontology for clinical trials but I >> don't think we've resolved the issue of types vs. instances. This requires >> much more discussion. >> Simona Carini has just joined our project and will work with UVic to push >> the visualization project further along. That will start to provide concrete >> uses for OBD and we can then work towards some more implementation >> questions. >> Best, >> Ida >> On 5/24/06 5:14 PM, "chris mungall" <cjm@fruitfly.org> wrote: >>> >>> Sorry for the lack of subject line in the previous email! I hate it >>> when people do that. Here it is again, with subject line. >>> >>> On May 24, 2006, at 5:06 PM, chris mungall wrote: >>> >>>> I've added a new wiki page: >>>> >> <http://smi.stanford.edu/projects/cbio/mwiki-internal/index.php/>http://smi.s >> tanford.edu/projects/cbio/mwiki-internal/index.php/ >> >>>> Clinical_Trials_in_OBD >>>> >>>> This is reachable from the OBD wiki page >>>> >>>> The page contains a link to the demo and a discussion of where to go >>>> next for representing clinical trials in OBD. In particular OBD, will >>>> require that terms are represented as types and not as instances, >>>> which will require a shift away from the current trialbank >>>> representation. From Ida's slides at the last all hands, it seems >>>> that trialbank may be moving in this way anyway, towards a reference >>>> ontology for clinical trials? >>>> >>>> Cheers >>>> Chris >>>> --++**==--++**==--++**==--++**==--++**==--++**==--++**== >>>> cbio-developers mailing list >>>> cbio-developers@lists.stanford.edu >>>> https://mailman.stanford.edu/mailman/listinfo/cbio-developers >>>> >>> > > Ref: ontology for clinical trial


Ricardo Pietrobon co-chairs the MSI Ontology Working Group that represents the metabolomics domain in FuGO.


Ricardo is Assistant Professor at Duke University and his current work is primarily in clinical and translational research. He uses an ontology to encode randomized trials.


In particular, his group seeks to expand existing ontologies, by including 'quantitative terms' (e.g. such as risk ratio, confidence intervals, variables) , so that these would work with statistical packages such as R/bioconductor.


Ricardo has also been in contact with Ida Sim.


Therefore, also as MSI Ontology Working Group, we will be very interested to know more about the plans of this ontology for clinical trial and contribute where possible.

Agenda

Participation

Requests for participation are welcome. Please send a brief statement of your expertise to Barry Smith.

Participants (First Tentative List)

Russ Altman -- Stanford University

Lindsay Cowell -- Duke University

Ted Grasela -- Cognigen Corporation, Amherst, NY

Mark Musen -- NCBO, Stanford University

Fabian Neuhaus -– NCBO, University at Buffalo

Ricardo Pietrobon -- Duke University

Nigam Shah -– NCBO, Stanford Medical Informatics

Susanna Sansone -- EBI, Hinxton, Cambridge

Ida Sim -- NCBO, University of San Francisco Medical Center

Barry Smith -– NCBO, University at Buffalo

Still more tentative: BRIDG: Doug Fridsma, Joyce Niland (maybe) CDISC: Becky Kush HL7: Lakshmi Grama caBIG: not sure exactly who would be right NIH Roadmap: Stuart Speedie (U. Minn) AMIA CT WG: Michael Kahn, Charlie Barr, AMIA KR WG: not sure who Columbia group on Clinical Trials Informatics

Venue