See also: IRC log
hi rich, can I post your 3-6-12 months goals to the wiki page on http://www.w3.org/wiki/HCLSIG/Pharmacogenomics/Meetings/2013-05-01_Conference_Call
okay, i will do that right away.
<boycer> phone is quite, is anyone speaking
<boycer> quiet (i meant)
<michel> matthias: reasoner workshop submission
<michel> ... good opportunity to put our ontology in front of the ontology developers
<michel> michel: met with ian horrock's group; they are developing many reasoners; need datasets
<michel> matthias: building the ontology-backed framework for clinical decision support. better, bigger, faster; how to put this all into clinical practice
<michel> ... medical safety codes to give personalized drug/drug dosing recommendations based on a small but highly relevant set of biomarkers, as cheaply as posible
<michel> ... make clinical decision support equally available; genomic CDS ontology + OWL reasoning
<michel> ... in the next year, we'll continue to develop this so to have a working system and in 3+years time to have in clinical practice
<michel> ... in the next 3 months: submit CDS to owl reasoner workshop; finalize decision support rules - need to collaborate with Jeff Pan (TrOWL); submit a paper to a journal on the ontology work
<michel> eric: have interest in TrOWL; closed world, una, other reasoning tasks
<ericP> W3C RDF Validation Workshop
<michel> matthias: update w3c wiki and associated web sites
<ericP> (it would be nice to get some TrOWL examples into http://www.w3.org/2012/12/rdf-val/SOTA#CWA_UNA)
<michel> bobF: lots of potential to collaborate
<michel> ... tremendous potential for medical safety codes
<michel> ... pharmgkb interest in bioinformatics; aware of scope creep; limiting to their own priorities; willing to collaborate, but resourced elsewhere / no new maintenance requirements
<michel> ... what would that relationship look like
<michel> ... at mayo - set of priorities have been identified; anything beyond that can be pursued on their own time.
<michel> ... standardized coding of genetic results
<michel> ... evaluation of genetics-based ontologies
<bobP> PGRN chip for 84 genes
<michel> ... pgrn chip - 84 pgx genes, will be adopted by many sites including EMERGE network; for a large number of patients
<michel> ... near term: think of how we can facilitate the interpretation of that data
<michel> ... medical safety code
<michel> matthias: ontology based on a set of genes and markers created last year. pgrnseq came up with their own genes; should be put into the ontology and medical safety code project
<michel> ... different profiles for different projects/countries
<michel> ... still need to select the most important markers is essential
<bobP> (Foundation Medicine also has a list of 200+ genes, in an important selection)
<michel> bobF: if we can come up with an ontology that can be extended at will, then any arbitrary set of variants could be selected, encoded and sent to server for ui display
<michel> ... if you have 84 gene panel, then that's what you encode and resolve
<michel> michel: how feasible is this customization?
<michel> matthias: concern about proliferation of codes / systems
<michel> ... best solution would be to curated and selected collection based on the work done by others
<michel> ... advertising post-doc position to work on all this. would speed it up. if you know somebody, let matthias know!
<michel> rich: collab with school of pharmacy; optimize use of information in product labelling; feedback to regulatory agency
<michel> ... using semantic model to annotate large number of drugs that have biomarkers; represent that using open annotation standard; more provenance and linking; demonstrate the value with useability studies
<michel> ... have phd student working on the project; proof of concept to provide recommendations in different care settings
<michel> ... have server to serve up demonstration with lab data to trigger rules in genomic CDS ontology; then expand PoC - make this as clinically useful as possible
<michel> ... 3 month - finish annotations. new group will start in the fall.
<michel> ... 6 months - quality; task-oriented usability study.
<michel> ... get funding and write papers !
<michel> michel: want to have access to product label annotation platform : drug effects, drug indications, drug-drug interactions
<scribe> scribenick: matthias_samwald
michel: our work focused on
phenotypes a lot
... using phenotype ontology (drug effects in animal models)
... elucidate drug effects, relation to pathways, mechanistic basis of drug effects
... in 10-15 years: understandig how genetic variant affect system as a whole
... in next 6 months i hope to integrate data from Bio2RDF to help drive some more ontology-based research
... how do we formalize data in RDF as OWL ontologies?
... can we find contradictions in animal models?
... we will continue the discussion in the next meeting and hear about the plans of people who could not talk about them today
<boycer> +1 for additional discussion, especially on how to support mutual research interests
This is scribe.perl Revision: 1.138 of Date: 2013-04-25 13:59:11 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found ScribeNick: matthias_samwald Inferring Scribes: matthias_samwald WARNING: No "Topic:" lines found. Default Present: +1.206.371.aaaa, michel, Bob_Powers, ericP, +1.507.269.aabb, Tony Present: +1.206.371.aaaa michel Bob_Powers ericP +1.507.269.aabb Tony WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Got date from IRC log name: 01 May 2013 Guessing minutes URL: http://www.w3.org/2013/05/01-HCLS-minutes.html People with action items: WARNING: No "Topic: ..." lines found! Resulting HTML may have an empty (invalid) <ol>...</ol>. Explanation: "Topic: ..." lines are used to indicate the start of new discussion topics or agenda items, such as: <dbooth> Topic: Review of Amy's report[End of scribe.perl diagnostic output]