W3C

- DRAFT -

Semantic Web Health Care and Life Sciences Interest Group Teleconference

14 Jul 2015

See also: IRC log

Attendees

Present
Rob_Hausam, Tony_Mallia, Paul_Knapp, David_Booth
Regrets
Chair
David Booth & Paul Knapp
Scribe
dbooth

Contents


<trackbot> Date: 14 July 2015

Approve Minutes

Last week's call was canceled

june 30 mintues: http://wiki.hl7.org/index.php?title=ITS_RDF_Concall_Minutes_20150630

APPROVED: June 30 minutes

HL7 Project Scope Statement (PSS) for computable semantic links from FHIR to RIM

Paul: no news yet

FHIR RDF and Validation/Translation Task Force

Tony: worked on CodeableThingy last week. Lloyd sent def. Seems ok. It's in today's version 6 side-by-side

FHIR RDF and Validation/Translation Task Force

http://wiki.hl7.org/index.php?title=File:FHIR_RDF_Sample_side_by_side_comparisons.pdf

CTS Ontology Workshop, Sept 23-25, Charleston SC

david: Reminder: Need to get FHIR ontology and RDF examples checked into github

SNOMED-CT Expo

Rob: Should present this work at the Expo. Want to make a submission.
... Mtg is in Uruguay in October.
... Submissions due Friday

tony: joint paper submission?

<scribe> ACTION: Rob to start drafting submission, and distribute for comment [recorded in http://www.w3.org/2015/07/14-hcls-minutes.html#action01]

<trackbot> Created ACTION-27 - Start drafting submission, and distribute for comment [on Rob Frost - due 2015-07-21].

http://www.ihtsdo.org/participate/attend-ihtsdo-events/snomed-ct-expo

rob: final papers due oct 12

Side-by-side example of two FHIR RDF approaches (Tony Mallia)

http://wiki.hl7.org/index.php?title=File:FHIR_RDF_Sample_side_by_side_comparisons.pdf

tony: changed primitive datatypes, including CodeableThingy
... Added index primitive also

FHIR lines 23-27 are reflected in RDF in lines 90-94

tony: fhir:CodeableThingy is equiv to CodeableConcept
... fhir:code becomes a CodeableThingy

rob: what's the relationship between CodeableThingy and the other three?

tony: line 99

david: Purpose is to use the same RDF structure for the three different ways of indicating codes in FHIR.

paul: How do you distinguish them when going back to XML? look for the absence of property?

david: dangerous to rely on the absence of certain properties to conclude which kind it was originally.

paul: could use breadcrumb

david: agree
... Could tag it with an additional RDF class to indicate where it originally came from.

<scribe> ACTION: Tony to ask lloyd about attaching a class breadcrumb to a CodeableThingy instance to indicate what FHIR form it was originally [recorded in http://www.w3.org/2015/07/14-hcls-minutes.html#action02]

<trackbot> Error finding 'Tony'. You can review and register nicknames at <http://www.w3.org/2014/HCLS/track/users>.

david: This makes querying more consistent -- all three use the same RDF structure -- but makes the RDF less concise. comments?

tony: the coding system could be added in.

david: Depends on what information is guaranteed to be available during FHIR XML to RDF conversion

tony: You would need to look at the structure definition.

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.

rob: I believe the coding system can only be fixed in structure definitions that are a part of the FHIR standard.

david: Can we confirm that?

<scribe> ACTION: Rob to check with Lloyd about whether someone can define a Code, specifying a new coding system URI in [recorded in http://www.w3.org/2015/07/14-hcls-minutes.html#action03]

<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].

tony: fhir:index is defined on line 678 and following lines
... fhir:index-primitive is the datatype for the range of fhir:index
... That's the same way that the other FHIR datatypes are defined.

<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]

Summary of Action Items

[NEW] ACTION: Rob to check with Lloyd about whether someone can define a Code, specifying a new coding system URI in [recorded in http://www.w3.org/2015/07/14-hcls-minutes.html#action03]
[NEW] ACTION: Rob to start drafting submission, and distribute for comment [recorded in http://www.w3.org/2015/07/14-hcls-minutes.html#action01]
[NEW] ACTION: Tony to ask lloyd about attaching a class breadcrumb to a CodeableThingy instance to indicate what FHIR form it was originally [recorded in http://www.w3.org/2015/07/14-hcls-minutes.html#action02]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.140 (CVS log)
$Date: 2015/07/14 16:33:34 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.140  of Date: 2014-11-06 18:16:30  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

No ScribeNick specified.  Guessing ScribeNick: dbooth
Inferring Scribes: dbooth
Present: Rob_Hausam Tony_Mallia Paul_Knapp David_Booth
Found Date: 14 Jul 2015
Guessing minutes URL: http://www.w3.org/2015/07/14-hcls-minutes.html
People with action items: rob tony

[End of scribe.perl diagnostic output]