14:16:22 RRSAgent has joined #hcls 14:16:22 logging to http://www.w3.org/2013/06/05-hcls-irc 14:16:28 zakim, who is here? 14:16:28 sorry, oliver, I don't know what conference this is 14:16:29 On IRC I see RRSAgent, Zakim, oliver, matthias_samwald, egonw, ericP 14:16:29 zakim, this is hcls 14:16:29 ok, matthias_samwald; that matches SW_HCLS(LODD)10:15AM 14:16:41 zakim, who is here? 14:16:41 On the phone I see +1.715.389.aaaa, fjh, oliver 14:16:42 On IRC I see RRSAgent, Zakim, oliver, matthias_samwald, egonw, ericP 14:17:35 zakim, +1.715.389.aaaa is simon_lin 14:17:35 +simon_lin; got it 14:17:43 zakim, fjw is matthias_samwald 14:17:43 sorry, matthias_samwald, I do not recognize a party named 'fjw' 14:17:43 w3cpgx has joined #HCLS 14:17:57 zakim, fjh is matthias_samwald 14:17:57 +matthias_samwald; got it 14:18:10 Simon has joined #HCLS 14:18:50 w3cpgx has joined #hcls 14:18:53 michel has joined #hcls 14:19:32 +michel 14:19:38 hello, who are you, pault? 14:21:47 +BobF 14:22:15 BobF has joined #hcls 14:24:42 scribenick: matthias_samwald 14:24:55 simon: see docs.google.com/document/d/12leHdI-GT2dzRgvVIx13wsXAaCLj6eNGvQ-L2B749f4/edit 14:25:03 pault = Paul Trevithick of PanGenX in Newton MA 14:25:23 ... we hope that this use case can be used to drive development of clinical genomics 14:25:35 ... feel free to edit the Google-Doc! 14:26:11 ... In a month / a few months we can wrap the ideas up in a joint manuscript 14:26:46 Bob: What will this document be used for? 14:27:06 Simon: We started to draft the document for internal requirements at Marshfield Clinic. 14:27:22 ... but we realized that we also need outside input to have use-cases for community in general 14:28:08 ... genomics is a large domain. this use-case should only focus on data storage needs. 14:28:22 Bob: For clinical use or also research? 14:28:40 Simon: Clinical genomics is primary target. For medical providers. 14:29:09 Bob: One thing I would ask: is the typical process of QC etc. in the scope of this document? 14:29:21 Simon: That is in scope. 14:29:56 Bob: Review, annotation, interpretation etc. should also be in there. 14:30:31 ... at Mayo, the results are interpreted by clinical geneticists that write a textual interpretation. That text is then used by the practicing clinicians. 14:31:19 ... the EMR would be between the clinical geneticist and the clinician. 14:31:38 ... But what goes into EMR? They were not designed for (next gen) genetic data. 14:32:11 ... At Mayo, a large panel test is only interpreted in the context in which it was ordered. 14:32:38 ... So interpretation is usually quite limited. You could also infer other information from the raw data. 14:32:55 Bob: Are you re-using the data? 14:33:10 (error: last comment was from simon) 14:33:50 Bob: This is work in progress, we are setting up an Oracle database for genetic data (and re-interpretation as needed). Lab reports will still go into established EMR. 14:34:22 Simon: We are planning similar setup at Marshfield. 14:34:44 Bob: This will be a common theme for the next few years, EMR systems are not designed for large genetic data. 14:35:37 Simon: CLIA conformant? 14:35:56 Bob: Pipeline for everything that ends up in EMR is CLIA-conformant. 14:36:22 Bob: PGRN-Seq chip is not yet CLIA conformant, but we will adopt it inside a CLIA environment. 14:36:52 Simon: How do genetic counselers want the genetic data? 14:38:02 TallTed has joined #hcls 14:38:08 Bob: I believe they get results from analysis pipeline within CLIA environment. They can look at QC metrics and raw data if they wish. They can also check if variants are novel or have already been documented (internally or in external databases). Report from clin geneticist is returned to clinician via EMR 14:38:24 Simon: Very similar to radiology workflow. 14:38:29 Bob: Exactly. 14:40:00 Simon: Are you using VCF files or are you using more than that? 14:40:54 Bob: VCF is used on the research side in bioinformatics pipelines. Not used clinically (as of yet). 14:41:16 ... Clinical systems are quite self-contained, they pipe data from one site to the next efficiently. 14:41:37 ... We are discussing using VCF clinically, it is not unlikely that this will happen. 14:41:58 ... Clinical systems currently use HL7 messages. Result set and size of data are currently still quite small. 14:42:27 ... Some of them are quite customized and were built together with vendors of machines. 14:42:39 ... But basically they are standard HL7 V2 messages. 14:43:31 ... Part of the problem we had with genetic results is that they are so text-based and unstructured. 14:44:05 ... They were designed as extensions of clinical tests that were set up before genomics era (similar to Cholesterol measurements etc.) 14:45:28 Matthias: Oracle? 14:45:40 Bob: We are using TRC Product from Oracle. 14:45:53 http://www.oracle.com/us/industries/health-sciences/hs-translational-research-497571.html 14:46:39 Bob: They have several products that can work together under this platform. 14:47:07 ... Mayo Clinic is a member of some of the respective Oracle groups. We are pushing the system past the design specs. 14:47:38 ... Will also work on Molecular Decision Support with them. 14:48:26 Matthias: Decision support capabilities in Oracle? 14:48:47 Bob: At the moment very little/almost none, but they are interested in adding this. 14:49:05 Simon: What is the volume of data you expect to put into the Oracle system? 14:49:25 Bob: We are planning on thousands of Genomes within the next year. 14:49:46 ... We expect the system to scale well. 14:51:40 Bob: Not sure regarding SemWeb component in Oracle 14:52:58 Simon: Another topic: retrieval 14:53:10 Bob: Before retrieval, there are other things to consider 14:53:18 ... integration 14:53:39 ... a patient might have different, contradicting results for a single SNP 14:54:27 ... this could be part of continual QC effort (e.g., scanning data and flagging such contradictions) 14:55:25 Bob: We are using TRC system as foundation for our molecular CDSS 14:55:46 ... So retrieval is needed to get data to EMR, to CDS engines 14:58:09 ... With the cost of sequencing coming down, it might become cheaper to simply re-sequence patients. 14:58:33 ... But of course then you have to handle partly duplicated, triplicated results. 14:59:02 Oliver: How do you handle patient consent, access restrictions? 14:59:22 ... We are thinking about regular clinical practice, same as doing a cholesterol test. 15:01:39 -simon_lin 15:02:27 Michel: We made some progress on drug-drug interactions. 15:02:46 ... I met with Rich, we had a discussion on curating information from drug labels 15:02:59 ... Plan to use DOMEO 15:03:19 ... Rich produced HTML pages from product labels to use with DOMEO 15:04:11 ... Will share once infrastructure is set up 15:05:53 matthias_samwald: invited to write an editorial for pharmacogenomics journal 15:07:03 matthias_samwald: submitted to the reasoner evaluation workshop on cds ontology 15:10:46 -BobF 15:10:48 -michel 15:10:50 -matthias_samwald 15:10:59 -oliver 15:11:01 SW_HCLS(LODD)10:15AM has ended 15:11:01 Attendees were oliver, simon_lin, matthias_samwald, michel, BobF 15:11:59 pault has left #hcls 15:13:23 RRSagent, please draft minutes 15:13:23 I have made the request to generate http://www.w3.org/2013/06/05-hcls-minutes.html matthias_samwald 15:14:16 RRSagent, please make minutes world-visible 15:14:16 I'm logging. I don't understand 'please make minutes world-visible', matthias_samwald. Try /msg RRSAgent help 15:14:26 RRSagent, please make logs world-visible 16:29:53 oliver has joined #hcls 16:46:10 Zakim has left #hcls 18:29:49 egonw has joined #HCLS