15:53:47 RRSAgent has joined #hcls 15:53:47 logging to http://www.w3.org/2015/03/03-hcls-irc 15:53:49 RRSAgent, make logs world 15:53:49 Zakim has joined #hcls 15:53:51 Zakim, this will be HCLS 15:53:51 ok, trackbot; I see SW_HCLS()11:00AM scheduled to start in 7 minutes 15:53:52 Meeting: Semantic Web Health Care and Life Sciences Interest Group Teleconference 15:53:52 Date: 03 March 2015 15:56:49 egonw has joined #HCLS 15:57:09 Tony has joined #HCLS 15:57:42 SW_HCLS()11:00AM has now started 15:57:49 + +1.978.794.aaaa 15:58:10 zakim aaaa is Tony 15:58:18 +ericP 15:58:27 egombocz has joined #HCLS 15:58:49 bpech has joined #hcls 15:58:50 +DBooth 15:59:01 +egombocz 15:59:59 + +1.678.999.aabb 16:00:14 zakim, aabb pbech 16:00:14 I don't understand 'aabb pbech', dbooth 16:00:25 zakim, aaaa is Tony 16:00:25 +Tony; got it 16:00:26 zakim, aabb is bpech 16:00:27 +bpech; got it 16:01:12 zakim, who is here? 16:01:12 On the phone I see Tony, ericP, DBooth, egombocz, bpech 16:01:14 On IRC I see bpech, egombocz, Tony, egonw, Zakim, RRSAgent, dbooth, TallTed, ericP, cloudcell_, trackbot 16:01:17 Lloyd has joined #HCLS 16:01:33 Will be late connecting to audio 16:01:49 + +1.512.680.aacc 16:02:01 zakim, aacc is Darrell 16:02:01 +Darrell; got it 16:02:10 DNelson has joined #HCLS 16:02:20 + +1.604.250.aadd 16:02:21 Topic: FHIR RDF and Validation/Translation Task force kickoff (Fridays 11am Boston timezone) 16:02:36 rhausam has joined #HCLS 16:02:53 zakim, aadd is Pknapp 16:02:53 +Pknapp; got it 16:03:01 + +1.916.783.aaee 16:03:06 topic: Approve Minutes of previous meetings 16:03:08 Claude has joined #hcls 16:03:17 Zakim, aaee is DNelson 16:03:17 +DNelson; got it 16:03:41 + +1.801.949.aaff 16:03:52 zakim, pick a victim 16:03:52 Not knowing who is chairing or who scribed recently, I propose DBooth 16:04:01 Zakim, aaff is rhausam 16:04:01 +rhausam; got it 16:04:03 zakim, pick a victim 16:04:03 Not knowing who is chairing or who scribed recently, I propose rhausam 16:04:05 + +1.202.528.aagg 16:04:35 Marc_Twagirumukiza has joined #HCLS 16:04:42 Ingeborg has joined #HCLS 16:04:59 zakim, aagg is Ingeborg 16:05:00 +Ingeborg; got it 16:05:22 Feb 24 minutes: http://wiki.hl7.org/index.php?title=ITS_RDF_Concall_Minutes_20150224 16:06:08 pknapp_ has joined #HCLS 16:06:12 http://wiki.hl7.org/index.php?title=ITS_RDF_Concall_Minutes_20150224 16:06:42 RESOLVED: Feb 24 minutes approved! 16:07:09 Topic: Back to FHIR RDF and Validation/Translation Task force kickoff (Fridays 11am Boston timezone) 16:07:28 + +1.323.444.aahh 16:07:35 work on mechanics of transformation and validation in RDF 16:07:37 + +1.507.261.aaii 16:07:37 - +1.507.261.aaii 16:07:41 tool is shape expressions 16:07:50 Zakim,aahh is Marc_Twagirumukiza 16:07:50 +Marc_Twagirumukiza; got it 16:08:12 extensions which allow creating artifact like a new document 16:08:47 GJiang has joined #HCLS 16:08:56 transform FHIR RDF to FHIR XML 16:09:00 mscottm has joined #hcls 16:09:07 q+ 16:09:32 q+ 16:09:40 + +1.507.261.aajj 16:09:52 + +31.62.427.aakk 16:09:57 zakim, aahh is Marc 16:09:57 sorry, dbooth, I do not recognize a party named 'aahh' 16:10:17 Zakim, aakk is mscottm 16:10:17 +mscottm; got it 16:10:26 ack DNelson 16:10:40 q+ Tony 16:11:34 Dale - provide method of validating CCDA via RDF? 16:11:46 s/Dale -/Dale:/ 16:13:57 discussion of CCDA validation 16:14:08 ack dbooth 16:14:19 Eric - validation language may only handle transformation bits 16:15:09 ack Tony 16:15:12 David - new call for transformation on Friday 16:15:22 s/David -/David:/ 16:17:01 Eric: There is XSLT that translates FHIR XML into FHIR RDF. That XSLT is generated by a script, from the FHIR spec. 16:17:25 ... That code could also generate the FHIR ontology. 16:18:27 michel has joined #hcls 16:18:34 Tony: Assuming the property resources are the formal declaration, looking at mapping to OWL ontology. Is your tooling robust enough to work? 16:19:09 Eric: It's a proving ground. It's like using chopsticks with chopsticks. 16:20:04 + +1.310.266.aall 16:20:05 q+ To note that another potential route we're exploring is to use JSON-LD, which would mean that any JSON-LD RDF parser could turn FHIR JSON(-LD) into RDF. 16:21:18 Eric: We can take this approach, and see if there are pieces we want to change. 16:21:53 ... The script is python. 16:22:03 ... Manual transformations are XSLT. 16:22:18 ... With a hand-tooled footer for the XSLT. 16:22:30 zakim, aall is claude 16:22:30 +claude; got it 16:22:34 ack dbooth 16:22:34 dbooth, you wanted to note that another potential route we're exploring is to use JSON-LD, which would mean that any JSON-LD RDF parser could turn FHIR JSON(-LD) into RDF. 16:24:05 Tony: Wise to do the parallel exploration. 16:24:34 michel has joined #hcls 16:24:48 David: Task Force call will start this Friday 11am Eastern. 16:25:39 rafael_richards has joined #HCLS 16:25:54 Eric: Timezone chaos in the next 2 weeks. All calls are relative to Boston time. 16:26:01 -Pknapp 16:26:07 +michel 16:26:13 Topic: FHIR JSON-LD update (David) 16:26:28 http://dbooth.org/2015/fhir/json-ld/fhir-in-json-ld.pdf 16:26:35 +Pknapp 16:30:04 David: FHIR is a closed content model. That's very helpful for the JSON-LD. 16:30:11 +[IPcaller] 16:30:53 +[IPcaller.a] 16:31:02 Tony: Worth investigating whether the structure represents graphs or only tree structure. 16:31:05 zakim, ipcaller.a is lloyd 16:31:05 +lloyd; got it 16:32:22 Daylight savings time in the U.S. starts Sunday March 8, in EU, it starts Sunday March 29. In practice, this means people calling in from Europe have to translate their normal call times by -1 hours to keep in sync with Boston, i.e., U.S. will have a *smaller* time difference with EU in the chaotic period. So, this weeks Task Force call will be at 5PM CET as usual for EU participants but next week's will be at 4PM CET and so on until March 29. 16:33:31 yes 16:33:50 Wed is difficult for me. 16:34:36 it will be ok for me 16:34:51 Wed works for me 16:35:25 Topic: FHIR examples for driving ontology developments (SKIPPED) 16:35:39 Topic: Valuesets in FHIR (Lloyd) 16:35:49 Keep in mind that in 3 weeks the call will be at 5PM CET for the long run. 16:36:06 https://global.gotomeeting.com/join/157514853 16:36:06 Access Code: 157-514-853 16:36:21 egonw has joined #HCLS 16:37:08 zakim, who is here? 16:37:08 On the phone I see Tony, ericP, DBooth, egombocz, bpech, Darrell, DNelson, rhausam, Ingeborg, Marc_Twagirumukiza, +1.507.261.aajj, mscottm, claude, michel, Pknapp, [IPcaller], 16:37:12 ... lloyd 16:37:12 On IRC I see egonw, rafael_richards, michel, mscottm, GJiang, pknapp_, Ingeborg, Marc_Twagirumukiza, rhausam, DNelson, Lloyd, bpech, egombocz, Tony, Zakim, RRSAgent, dbooth, 16:37:12 ... TallTed, ericP, cloudcell_, trackbot 16:37:20 Alejandra has joined #hcls 16:37:24 s/Friday/Wednesday/ 16:37:31 Hello all 16:37:47 http://hl7-fhir.github.io/datatypes.html 16:37:51 sorry, cannot join the call but wanted to express that Wed would be good for me, thanks! 16:39:37 lloyd: Giving background on how FHIR handles terminology, and how we may use RDF to represent FHIR and link to other ontologies such as SNOMED. 16:39:59 ... First look at what datatypes we have: http://hl7-fhir.github.io/datatypes.html 16:40:14 ... Then talk about FHIR's notion of bindings, then valuesets. 16:40:56 ... At the simplest level is a Code datatype -- a string. Namespace and allowed choices. We use it for status codes, gender, etc. 16:41:15 ... Reasonable to use when the set of codes will not change without a major new release of FHIR. 16:41:23 Great, tx Eric 16:41:30 ... Second type is Coding and CodeableConcept. 16:42:05 ... Coding represents a single code: both the code and the code system (URI). Maybe also a version -- important to some systems, if meaning changes bewteen versions. 16:42:38 ... Code + System + Version = meaning of the context. 16:42:50 http://hl7-fhir.github.io/datatypes.html#coding 16:43:08 -Marc 16:43:20 -michel 16:43:22 ... The notion of a system being a URI will map well to URI, but version string will not. 16:43:36 ... Code system defines what the version string looks like. 16:43:46 -Marc_Twagirumukiza 16:44:04 ... Also the Code itself is not part of the URI. 16:44:24 +michel 16:44:24 ... We'll avoid spaces in codes for codes we define, but other code systems might have them or other funny chars. 16:44:44 Tony: Is a code unique within a Coding system? 16:45:41 ... There's an expectation that we do not have homogeny (same code having differnet meanings). Some systems do that (UCUM). Code "M" could mean "meter" or "milli", but milli would not stand by itself so that isn't a problem. 16:45:53 ... But FHIR does not prohibit code systems that do that. 16:47:20 ... We have System, Code, Version, and need to be alble to reconstitute them when going between FHIR representations. They can have slashes, hashes, etc., that will make them very difficult to concatenate into a URI. 16:48:07 ... Which I think means that RDF will need to retain them as separate properties, and we'll need to use some kind of equivalence to a full URI. 16:48:22 -> https://www.w3.org/wiki/HCLS/ClinicalObservationsInteroperability/FDATherapeuticAreaOntologies#Coding_specificity example mapping between Coding and URL 16:48:29 Tony: Could have both version code and URI. 16:49:49 lloyd: But the conversion must use a single algorithm that is independent of code system. 16:51:36 ... Might have a companion ontology that links FHIR ont to specific coding system. 16:53:05 eric: Could define a URI transformation, but would be nice if the coding system URI is dereferenceable. 16:53:30 lloyd: Can we make an algorithm that would work for them all? Maybe, but scary. 16:54:07 -Darrell 16:54:08 http://hl7-fhir.github.io/datatypes.html#codeableconcept 16:54:33 ISSUE: How to represent coding system, code and version as round-trippable URIs? 16:54:33 Created ISSUE-3 - How to represent coding system, code and version as round-trippable uris?. Please complete additional details at . 16:54:36 +Darrell 16:55:28 lloyd: Common with coded data to have more than one code from different coding systems, which are more or less equivalent. That's purpose of CodeableConcept. 16:56:08 .... Code from SNOMED might be the first or 5th. People can pass instances that meet a variety of consumers without separate instances for each target. 16:57:15 Eric: If we get a document with a Mayo code, SNOMED code and CPT code, and we spit it back out with all 3 codes in different order, is that ok for round tripping? 16:57:36 lloyd: FHIR rule is that it is an array, and the ordering is significant. 16:57:59 ... We don't assign significance in this case, but it would break a hash of the message. 16:58:10 Claude: Can label one as preferred? 16:58:47 lloyd: One can be labeled as Primary. That means "This is the one the user chose". If someone codes after the fact (reading the text), then none would be primary. 16:59:20 ... If you're translating, you want to start with Primary. 16:59:51 -Pknapp 17:00:31 -michel 17:00:39 ACTION: David to sent calendar invite for Wed 17:00:39 'David' is an ambiguous username. Please try a different identifier, such as family name or username (e.g., dderour, dhansen2, dhau2, dnewman, dshotton, dwild). 17:00:44 -bpech 17:01:03 - +1.507.261.aajj 17:01:03 -Ingeborg 17:01:05 -rhausam 17:01:06 -Tony 17:01:08 -Darrell 17:01:13 -egombocz 17:01:14 -DNelson 17:02:03 -claude 17:06:32 -lloyd 17:06:33 -DBooth 17:06:47 -ericP 17:06:50 Chair: David Booth and Paul Knapp 17:07:42 rrsagent, draft minutes 17:07:42 I have made the request to generate http://www.w3.org/2015/03/03-hcls-minutes.html dbooth 17:09:30 -mscottm 17:14:31 disconnecting the lone participant, [IPcaller], in SW_HCLS()11:00AM 17:14:32 SW_HCLS()11:00AM has ended 17:14:32 Attendees were +1.978.794.aaaa, ericP, DBooth, egombocz, +1.678.999.aabb, Tony, bpech, +1.512.680.aacc, Darrell, +1.604.250.aadd, Pknapp, +1.916.783.aaee, DNelson, +1.801.949.aaff, 17:14:32 ... rhausam, +1.202.528.aagg, Ingeborg, +1.323.444.aahh, +1.507.261.aaii, Marc_Twagirumukiza, +1.507.261.aajj, +31.62.427.aakk, mscottm, +1.310.266.aall, claude, michel, 17:14:34 ... [IPcaller], lloyd 17:30:21 dbooth has joined #hcls 17:30:26 s/zakim aaaa is Tony// 17:30:38 ADJOURNED 17:31:25 scribenick: rhausam 17:33:39 zakim, who was here? 17:33:39 I don't understand your question, dbooth. 17:36:12 Present: Claude_Nanjo David_Booth Dale_Nelson Darrell Guoqian_Jiang Lloyd_McKenzie Ingeborg Marc_Twagirumukiza Paul_Knapp Tony_Mallia Brian_Pech Erich_Gombocz EricP Michel_Dumontier mscottm Rob_Hausam Rafael_Richards (IRC only) 17:36:30 rrsagent, draft minutes 17:36:30 I have made the request to generate http://www.w3.org/2015/03/03-hcls-minutes.html dbooth 17:38:35 s/Topic: FHIR RDF and Validation/Translation Task force kickoff (Fridays 11am Boston timezone)//g 17:39:09 s/Topic: Back to/Topic: FHIR RDF and Validation/Translation Task force kickoff (Fridays 11am Boston timezone)/ 17:39:13 rrsagent, draft minutes 17:39:13 I have made the request to generate http://www.w3.org/2015/03/03-hcls-minutes.html dbooth 17:40:54 s|Topic: FHIR RDF and Validation/Translation Task force kickoff (Fridays 11am Boston timezone)||g 17:41:29 s|Topic: Back to|Topic: FHIR RDF and Validation/Translation Task force kickoff (Fridays 11am Boston timezone)|g 17:41:34 rrsagent, draft minutes 17:41:34 I have made the request to generate http://www.w3.org/2015/03/03-hcls-minutes.html dbooth 17:43:09 s|FHIR RDF and Validation/Translation Task force kickoff (Fridays 11am Boston timezone) FHIR|FHIR|g 17:43:12 rrsagent, draft minutes 17:43:12 I have made the request to generate http://www.w3.org/2015/03/03-hcls-minutes.html dbooth 17:44:38 i/work on mechanics/ScribeNick: rhausam 17:45:09 s/Eric -/Eric:/g 17:45:40 i/Eric: There is XSLT/ScribeNick: dbooth 17:45:54 rrsagent, draft minutes 17:45:54 I have made the request to generate http://www.w3.org/2015/03/03-hcls-minutes.html dbooth 17:46:57 s|s/Topic: FHIR RDF and Validation/Translation Task force kickoff (Fridays 11am Boston timezone)//|| 17:47:14 s|s///g|| 17:47:20 rrsagent, draft minutes 17:47:20 I have made the request to generate http://www.w3.org/2015/03/03-hcls-minutes.html dbooth 18:23:40 egonw has joined #HCLS 20:01:49 Zakim has left #hcls