16:17:22 RRSAgent has joined #hcls 16:17:22 logging to http://www.w3.org/2014/11/11-hcls-irc 16:17:31 rrsagent, make logs public 16:17:50 topic: Support for Building WHO Terminologies 16:17:58 mark: WHO is working on ICD, which has been around since the 19th century, and gets an upgrade every decade 16:18:00 ... this explosion of codes has made people leary of ICD10 16:18:11 ... 11 will be next major rev 16:18:11 scribenick: dbooth 16:18:44 mark: ICD currently published as a book. WHO sees a need for change 16:18:51 ... ICD9-CM is a laundry list of terms. 16:19:09 scribenick: ericP 16:19:34 mark: [WHO slide: ICD-11 -- An Enriched Information Model] 16:19:46 ... describes the high-level components 16:20:13 ... these are part of the content model for ICD11 16:20:27 ... these are represented as OWL classes 16:20:37 ... the terms are OWL individuals 16:21:15 ... WHO was afraid of the postcoordination model but more afraid of the "exploding bicycle" precoordination model 16:21:36 ... WHO wants ICD to be useful in urban US and rural developing countries. 16:22:08 ... "linearaizations" result in practice-specific terminologies, etc. 16:22:22 ... [slide ICD is no longer just a list of terms ...] 16:22:51 ... the goal is not to create a general KB of medicine but to capture enough for machines to do some reasoning. 16:23:11 ... [slide ICD-11 "Linearizations"] 16:23:23 ... morbidity for public health 16:23:34 ... mortatily for death certificates 16:23:48 ... [sldie Revision Org Structure] 16:24:06 ... not a big yelling competition in geneva 16:24:21 ... distributed contributions reviewed by peers 16:24:38 ... reduces "last man standing" standards 16:24:56 ... [iCAT slide] 16:25:12 ... iCAT is Web Protege with some custom interface conventions 16:25:45 ... e.g. comments left for developers 16:25:53 ... on the right is the WHO content model 16:26:16 ... as applied to the code in the hierarchy on the left 16:26:36 ... [slide: iCAT Functionalities] 16:27:38 ... some turf battles around what tag applies to the hierarchy 16:27:53 ... intense discussions, multimedia, pointing to web docs 16:28:13 ... shows how webprotege features are used for the development of a very large ontology 16:28:23 ... [slide: weekly changes] 16:28:59 ... ICD11 has gone from a prototype to what WHO calls a "data phase" ready for testing 16:29:10 ... [slide: Post-coord] 16:29:25 ... "what are the ways that asma can be post-coordinated?" 16:29:53 ... specify with selections of terms 16:30:04 ... [slide: logical definition tab] 16:30:48 ... important to relate asthma with occurance "intermitten" with "intermittent asthma" 16:31:14 ... [slide: WHO adopted the same approache for international classification of traditional medicine] 16:31:32 ... same approach applied to ICTM 16:31:54 ... e.g. TCM, korean, japanese traditional medicine 16:32:17 ... WHO considers all medical care important. 16:32:40 ... much of the world recieves these traditional meds but currently no representation 16:32:57 ... [slide: Bioportal screenshot] 16:33:15 ... ~350 ontologies from Allen Brain to Zebra fish 16:33:46 ... goal: use the terms and value sets in bioportabl to unify WHO terminologies with existing terminologies 16:34:02 ... [slide: iCat allows users...] 16:34:40 ... we can map all of the bioportal terms related to meridian systems to ICTM 16:34:55 ... [slide: Next up: CPT] 16:35:09 ... AMA's "Current Procedural Terminology" 16:35:20 ... currently distributed as a book 16:35:33 ... working with AMA to clean up CPT 16:36:12 ... also working with AMA and WHO to reconcile ICPT with ICHI (intl classif health interventions) 16:36:34 ... discussed with WHO heatlh interventions meeting in barcelona 16:37:01 ... can have all of these in OWL, instantiated by particular terminology, supported by bioportal 16:37:20 ... [slide: family of OWL-based ontologies] 16:37:52 ... Bioportal provides a modacum of the yosemite vision 16:38:07 dbooth: questions? 16:38:51 rafael: can icat link to freebase or dbpedia? 16:39:16 mark: no. iCAT has limited the webprotege interface. 16:39:22 ... but a good idea. 16:39:41 Tony: structure of ICD11 IRIs in OWL 16:39:55 mark: there's no attempt to be compatible with IHTSDO 16:40:03 ... structure dicated by WHO 16:40:25 ... agreement between WHO and IHTSDO to have shared content, but not started yet 16:40:43 Tony: the SNOMED seems like the same structure. 16:41:12 ... SNOMED has a standoff to the code 16:41:38 ... when we examine the binding of a health record. 16:41:57 Hung: how can we access bioportal 16:42:17 mark: NCBO website, bioportal website 16:42:29 ... no workshops planned at this point 16:42:40 annete: what programming langs? 16:42:48 mark: java/google web toolkit 16:43:05 claude: goal for linking terminologies? 16:43:09 Claude: How successful was iCat for use by medical experts who are not familiar with ontologies, RDF or OWL? 16:43:24 mark: desire for convergance, but money to be made in terminologies 16:43:41 ... AMA makes more money from CPT than its membership dues 16:43:56 ... IHTSDO has of course a licenseing model 16:44:13 ... WHO has a need to do this for financing in the future 16:44:27 ... desire is there, but the economics favor the status quo 16:44:33 How does this relate to CDISC/HL7 RDF-ization efforts? 16:44:54 mark: parallel play. desire for more coordinated activity 16:45:28 dbooth: what would it take to make iCAT support linkage to multiple standards? 16:45:38 ... suppposed you want to link them after development. 16:46:04 mark: we do this in a less-than-ideal way. we can store them all in bioportal. 16:46:27 ... anything that we put into bioportal is linked to every other ontology by mappings. 16:46:38 ... most programmatic, but accuracy isn't bad 16:47:06 ... surprisingly, we get lots of web interface and bioportal API use of the linkages. 16:47:28 ... the mappings are complex (how created, provenance, accuracy via user feedback) 16:47:51 ... we don't have a compact linkage but the mappings are a step in the right direction 16:47:59 dbooth: are the maps separate ontologies? 16:48:13 mark: instances of OWL classes. readable through the API 16:48:29 ... a user can flag an incorrect mapping. 16:48:44 ... can flag concepts or mappings. 16:49:00 ... we also allow users to select mappings from particular provenance. 16:49:11 ... we don't have a well-defined governance process. 16:49:23 ... adjustment is done on an ad-hoc basis. 16:49:36 http://en.wikipedia.org/wiki/ISO/IEC_11179 16:49:41 ... we don't have enough feedback to motivate automation 16:50:02 ... there's been no effort to map to 11179. parallel universes. 16:50:47 Sal: ... clinical trials ... NCI ... 11179 ... 16:51:58 ericP: i think PhUSE has done a mapping 16:52:13 David: How successful was iCat for use by medical experts who are not familiar with ontologies, RDF or OWL? 16:52:18 dbooth: how successful was iCAT for non-RDF-expert medical folks 16:52:46 ... folks managing these terminologies are esteemed medical professionals, not technocrats. 16:53:21 ... we weren't getting funding for the UI, and ICD is complex, so we were pleased that the PAGs were able to do as well as they could 16:53:59 ... that said, they shied away from iCAT, working in spreadsheets, but they were ultimately moved to iCAT and folks have used it. 16:54:27 ... it was hard for iCAT to overcome the allure of Excel, but folks were more than happy to work online 16:54:40 rafael: pipelines... 16:54:51 Rafael: What new features or directions are already planned or in the works? 16:55:28 mark: in iCAT, lots of work done to customize to match WHO structure: governing body/topic advisory groups/... 16:55:45 ... worried that iCAT is overfitted to WHO workflow 16:56:04 dbooth: planned new features? 16:56:06 David: What new features or directions are already planned or in the works? 16:56:23 mark: mainly in response to AMA CPT project 16:56:43 ... AMA wants to share value sets, etc. 16:57:04 ... precerticiation of procedures 16:57:20 ... same work in WHO wrt ICTM 16:57:35 ... we will have scalability issues 16:57:53 Claude: What new features or directions are already planned or in the works? 16:57:53 ... also UI to deal with overwhelming scale 16:58:01 oops, bad paste 16:58:05 Mark: iCAT is open source 16:58:14 ... IHTSDO could use Protege 16:58:15 claude: Could iCAT be more generalized for adoption at, say, IHTSDO, that is, for general terminology management? Is iCAT open source (sorry, I may have missed this)? 16:58:27 ... they are currently committed to their own tools and DL 16:58:32 Tony: What is the reperesentation of Value Sets? Are they just part of he Class hierarchy? 16:59:13 mark: considering UI enhancements to browse sets. 16:59:38 ... when users go to iCAT or webprotege, users want to browse stuff in its context. hard at large scale. 16:59:41 What about marrying iCat with BioPortal? To what extent are they integrated? Can or should they be integrated? 17:00:16 mark: integration is such that iCAT and webprotege users can go to bioportal to grab terms from ontologies 17:00:37 ... iCAT/webprotege comments can appear in bioportal 17:00:45 ... shows user feedback in a nice way 17:00:54 ... plan tighter coordination 17:01:18 ... clicking a link in bioportal to bring up a webprotege interface 17:01:40 ... also for folks using webprotege to use bioportal for the repo 17:04:11 RRSAgent, please draft minutes 17:04:11 I have made the request to generate http://www.w3.org/2014/11/11-hcls-minutes.html ericP 17:05:01 disconnecting the lone participant, EricP, in SW_HCLS()11:00AM 17:05:03 SW_HCLS()11:00AM has ended 17:05:03 Attendees were +1.412.624.aaaa, ericP, [IPcaller], Vipul, Ingeborg, +1.978.794.aabb, +1.919.201.aacc, Ratnesh 17:05:23 Zakim, please disconnect ericP 17:05:23 sorry, ericP, I don't know what conference this is 17:57:50 rafael has joined #hcls 17:57:50 dbooth has joined #hcls 17:57:50 TallTed has joined #hcls 17:57:50 egonw_ has joined #hcls 17:57:50 cloudcell has joined #hcls