14:02:08 <RRSAgent> RRSAgent has joined #hcls
14:02:08 <RRSAgent> logging to http://www.w3.org/2015/09/01-hcls-irc
15:00:20 <Tony> Tony has joined #HCLS
15:00:37 <dbooth> dbooth has joined #hcls
15:01:31 <dbooth> trackbot, start meeting
15:01:33 <trackbot> RRSAgent, make logs world
15:01:35 <trackbot> Zakim, this will be HCLS
15:01:35 <Zakim> I do not see a conference matching that name scheduled within the next hour, trackbot
15:01:36 <trackbot> Meeting: Semantic Web Health Care and Life Sciences Interest Group Teleconference
15:01:36 <trackbot> Date: 01 September 2015
15:01:51 <dbooth> Topic: Introductions
15:02:26 <dbooth> Paul: Head up Rosetta effort for PCD domain.  Medical devices.  LOINC project mapped 600 most popular terms.
15:02:55 <dbooth> ... Also heavy on valueset constraints.  Want rigorous testing of EMR data from devices.
15:04:03 <dbooth> Topic: ValueSets
15:04:04 <dbooth> http://wiki.hl7.org/index.php?title=File:Vocabulary_and_Terminology_in_RDFv2.pdf
15:04:59 <rhausam> rhausam has joined #HCLS
15:13:35 <dbooth> lloyd: line 50, allergy-intolerance-status needs to be a blank node, because there can be extensions on the URI
15:14:47 <dbooth> ... I could have the same system in 3 different places with 3 different extensions, so it needs to be a blank node.
15:17:40 <dbooth> tony: ok
15:18:08 <dbooth> lines 93-99
15:18:53 <dbooth> lloyd: Why have a class for the CodeSystem?
15:19:38 <dbooth> lloyd: Why not have 2 owl:hasValues?
15:19:52 <dbooth> tony: cleaner this way.
15:20:16 <dbooth> lloyd: We'll have instances w no predefined knowledge of the codeSystems or their versions.  E.g., string values for them.
15:20:39 <dbooth> ... I'm concerned that this approach may cause challenges.
15:21:19 <dbooth> tony: That's ok, but the reasoner won't infer any type for it.
15:21:57 <dbooth> david: Should we look at both options?
15:22:38 <dbooth> ACTION: Tony to draft a new version that shows both approaches (two owl:hasValues that Lloyd suggested, versus Tony's existing draft)
15:22:38 <trackbot> Error finding 'Tony'. You can review and register nicknames at <http://www.w3.org/2014/HCLS/track/users>.
15:22:58 <dbooth> lloyd: where is the OID coming from?
15:23:20 <dbooth> ... Resource instances won't have OIDs.
15:23:33 <dbooth> ... Namespaces I thought we wouldn't expose in RDF.
15:23:41 <dbooth> tony: CodeSystems have OIDs
15:24:17 <dbooth> lloyd: I wouldn't expect to see any of that in RDF?
15:24:29 <dbooth> eric: they are in the FHIR examples
15:24:37 <dbooth> tony: We don't need them.
15:24:58 <dbooth> lloyd: If they're in the examples, the should all be URIs, as "urn:..."
15:26:08 <dbooth> lloyd: lines 105-109 comes from where, what FHIR artifact?   Needs to come from a structure def, valueset, or something.  What XML file?
15:26:56 <dbooth> ... NamingSystem is used to define both CodeSystems and identifier systems.
15:27:39 <dbooth> tony: We can leave out lines 103-110
15:27:54 <dbooth> ... but where does lines 117-121 come from?
15:29:54 <dbooth> tony: lines 123-128, Authority is only for housekeeping, saying what comes from where.  Comes from the namespace of the ontology.
15:30:25 <dbooth> lloyd: FHIR ont is generated purely from FHIR artifacts -- no knowledge of LOINC or other ont.
15:30:59 <dbooth> tony: Want to know how the ont pieces are assembled to a combined ontology that allows the reasoner to work.
15:31:12 <dbooth> lloyd: We'll show for a couple of terminologies how to link them in.
15:32:11 <dbooth> david: Need to see an example of how Authority is used.
15:33:18 <dbooth> line 130
15:33:42 <dbooth> lloyd: Concepts can have more than one code.
15:35:23 <dbooth> eric: Two concepts that are equivalent, or a single concept with multiple codes?
15:36:41 <dbooth> lloyd: same concept can be identified by different combination of code system, code and version.
15:37:57 <dbooth> ... But ValueSet can prohibit certain codes (even though they may identify the same concept)
15:42:53 <dbooth> david: This could be modeled either way: as a single concept, with multiple codes; or as one concept per code, and those concepts are equivalent.
15:43:32 <dbooth> eric: Do i want to be able to validate ValueSets in OWL, versus ShEx or something else?
15:45:50 <dbooth> lloyd: OWL
15:51:16 <dbooth> lloyd: Should change line 130 to say "one or more code representations within that code system"
15:51:39 <dbooth> ACTION: Tony to change line 130 to say "one or more code representations within that code system"
15:51:39 <trackbot> Error finding 'Tony'. You can review and register nicknames at <http://www.w3.org/2014/HCLS/track/users>.
15:51:56 <dbooth> lloyd: Also need to bring in version.
15:52:14 <dbooth> ... Question of whether a single concept can span versions.
15:53:32 <dbooth> ... Same code and system may be bound to different concepts for different versions, or sometimes the same concept.
15:56:29 <dbooth> lloyd: Some code systems reuse code strings after 10 years, meanign completely different things.
15:57:01 <dbooth> ... And some change the hierarchy and properties between versions, even though the display name didn't change.
15:57:40 <dbooth> ... There are also fine-grained changes between versions.
15:59:04 <dbooth> tony: I'll address version later.
15:59:26 <dbooth> lines 133-150
16:00:04 <dbooth> lloyd: Abstract Concepts are declared wrt a particular intended use.
16:00:38 <dbooth> lines 179-189
16:02:00 <dbooth> lloyd: Is there any chance that someone else would have a concept with that snomed URI, <http://snomed.info/sct> ?
16:02:32 <dbooth> tony: We can change that to be a owl:hasValue against that string, instead.
16:03:46 <dbooth> lloyd: HL7 doesn't own that namespace URI, so HL7 cannot define what it means.
16:03:56 <dbooth> david: that would be URI squatting.
16:05:28 <dbooth> ACTION: Tony to change line 182 to use owl:hasValue restriction instead of URI squatting
16:05:28 <trackbot> Error finding 'Tony'. You can review and register nicknames at <http://www.w3.org/2014/HCLS/track/users>.
16:07:37 <dbooth> eric: For orgs that cannot manage their URIs well, HL7 could provide URIs for them.  But some orgs can manage them well and ensure that their URIs are uniquely defined.
16:08:13 <dbooth> tony: If we use owl:hasValue then we don't have to worry about collisions.
16:08:42 <dbooth> ... But if we use that URI directly as an RDF concept, then we risk URI collision.
16:09:09 <dbooth> eric: Can we get them to give us a safe URI?
16:09:51 <dbooth> lloyd: in theory, but that's probably 1% of the vocabularies.
16:12:21 <dbooth> Topic: Next Steps
16:13:36 <dbooth> s/Topic: Next Steps//
16:14:56 <dbooth> Present: Paul ___, Lloyd, EricP, Tony, David, Rob Hausam
16:17:08 <dbooth> Chair: David Booth
16:20:22 <dbooth> ADJOURNED
16:20:29 <dbooth> rrsagent, draft minutes
16:20:29 <RRSAgent> I have made the request to generate http://www.w3.org/2015/09/01-hcls-minutes.html dbooth
18:48:56 <Zakim> Zakim has left #hcls