14:56:36 <RRSAgent> RRSAgent has joined #hcls
14:56:36 <RRSAgent> logging to http://www.w3.org/2015/07/14-hcls-irc
14:56:38 <trackbot> RRSAgent, make logs world
14:56:38 <Zakim> Zakim has joined #hcls
14:56:40 <trackbot> Zakim, this will be HCLS
14:56:40 <Zakim> I do not see a conference matching that name scheduled within the next hour, trackbot
14:56:41 <trackbot> Meeting: Semantic Web Health Care and Life Sciences Interest Group Teleconference
14:56:41 <trackbot> Date: 14 July 2015
14:59:44 <rhausam> rhausam has joined #HCLS
15:00:48 <pknapp> pknapp has joined #hcls
15:03:13 <dbooth> Topic: Approve Minutes
15:03:21 <dbooth> Last week's call was canceled
15:03:32 <dbooth> june 30 mintues: http://wiki.hl7.org/index.php?title=ITS_RDF_Concall_Minutes_20150630
15:04:29 <dbooth> APPROVED: June 30 minutes
15:05:19 <dbooth> Topic: HL7 Project Scope Statement (PSS) for computable semantic links from FHIR to RIM
15:05:24 <dbooth> Paul: no news yet
15:05:39 <mscottm> mscottm has joined #hcls
15:05:58 <Tony> Tony has joined #HCLS
15:06:51 <dbooth> Topic:  FHIR RDF and Validation/Translation Task Force
15:07:31 <dbooth> Tony: worked on CodeableThingy last week.  Lloyd sent def.  Seems ok.  It's in today's version 6 side-by-side
15:09:20 <dbooth>  FHIR RDF and Validation/Translation Task Force
15:09:43 <dbooth> http://wiki.hl7.org/index.php?title=File:FHIR_RDF_Sample_side_by_side_comparisons.pdf
15:11:06 <dbooth> Topic: CTS Ontology Workshop, Sept 23-25, Charleston SC
15:11:47 <dbooth> david: Reminder: Need to get FHIR ontology and RDF examples checked into github
15:12:34 <dbooth> Topic: SNOMED-CT Expo
15:12:52 <dbooth> Rob: Should present this work at the Expo.  Want to make a submission.
15:13:04 <dbooth> ... Mtg is in Uruguay in October.
15:13:27 <dbooth> ... Submissions due Friday
15:15:26 <dbooth> tony: joint paper submission?
15:18:49 <dbooth> ACTION: Rob to start drafting submission, and distribute for comment
15:18:49 <trackbot> Created ACTION-27 - Start drafting submission, and distribute for comment [on Rob Frost - due 2015-07-21].
15:19:16 <dbooth> http://www.ihtsdo.org/participate/attend-ihtsdo-events/snomed-ct-expo
15:19:23 <dbooth> rob: final papers due oct 12
15:20:00 <dbooth> Topic: Side-by-side example of two FHIR RDF approaches (Tony Mallia)
15:20:24 <dbooth> http://wiki.hl7.org/index.php?title=File:FHIR_RDF_Sample_side_by_side_comparisons.pdf
15:20:57 <dbooth> tony: changed primitive datatypes, including CodeableThingy
15:21:06 <dbooth> ... Added index primitive also
15:22:15 <dbooth> FHIR lines 23-27 are reflected in RDF in lines 90-94
15:24:59 <dbooth> tony: fhir:CodeableThingy is equiv to CodeableConcept
15:25:39 <dbooth> ... fhir:code becomes a CodeableThingy
15:26:25 <dbooth> rob: what's the relationship between CodeableThingy and the other three?
15:26:51 <dbooth> tony: line 99
15:38:47 <dbooth> david: Purpose is to use the same RDF structure for the three different ways of indicating codes in FHIR.
15:39:16 <dbooth> paul: How do you distinguish them when going back to XML?  look for the absence of property?
15:40:47 <dbooth> david: dangerous to rely on the absence of certain properties to conclude which kind it was originally.
15:40:53 <dbooth> paul: could use breadcrumb
15:40:59 <dbooth> david: agree
15:41:40 <dbooth> ... Could tag it with an additional RDF class to indicate where it originally came from.
15:42:45 <dbooth> ACTION: Tony to ask lloyd about attaching a class breadcrumb to a CodeableThingy instance to indicate what FHIR form it was originally
15:42:45 <trackbot> Error finding 'Tony'. You can review and register nicknames at <http://www.w3.org/2014/HCLS/track/users>.
15:44:27 <dbooth> david: This makes querying more consistent -- all three use the same RDF structure -- but makes the RDF less concise.  comments?
15:45:37 <dbooth> tony: the coding system could be added in.
15:45:54 <dbooth> david: Depends on what information is guaranteed to be available during FHIR XML to RDF conversion
15:46:30 <dbooth> tony: You would need to look at the structure definition.
15:48:18 <dbooth> david: If the structure definition is a part of the FHIR standard, then it can be used.  If it might be defined by some other organization, then the conversion cannot count on it being available.
15:49:01 <dbooth> rob: I believe the coding system can only be fixed in structure definitions that are a part of the FHIR standard.
15:49:09 <dbooth> david: Can we confirm that?
15:56:14 <dbooth> ACTION: Rob to check with Lloyd about whether someone can define a Code, specifying a new coding system URI in
15:56:14 <trackbot> Created ACTION-28 - Check with lloyd about whether someone can define a code, specifying a new coding system uri in [on Rob Frost - due 2015-07-21].
15:58:57 <dbooth> tony: fhir:index is defined on line 678 and following lines
15:59:33 <dbooth> ... fhir:index-primitive is the datatype for the range of fhir:index
16:00:27 <dbooth> ... That's the same way that the other FHIR datatypes are defined.
16:01:21 <rhausam> code should only be used when the following conditions are met: The data element forms an essential part of interpreting the meaning of the resource, such that safe processing would be impossible without it. I.e. the element must be “mustUnderstand” or the element is a part of the FHIR infrastructure and has no clinical or business meaning The element will be bound to a code list that is complete (non-extensible) and required (everyone must use it) The [CUT]
16:33:12 <dbooth> Present: Rob Hausam, Tony Mallia, Paul Knapp, David Booth
16:33:22 <dbooth> Chair: David Booth & Paul Knapp
16:33:28 <dbooth> rrsagent, draft minutes
16:33:28 <RRSAgent> I have made the request to generate http://www.w3.org/2015/07/14-hcls-minutes.html dbooth
17:03:13 <Zakim> Zakim has left #hcls