15:01:42 RRSAgent has joined #hcls 15:01:42 logging to http://www.w3.org/2016/04/12-hcls-irc 15:01:44 RRSAgent, make logs world 15:01:44 Zakim has joined #hcls 15:01:46 Zakim, this will be HCLS 15:01:46 ok, trackbot 15:01:47 Meeting: Semantic Web Health Care and Life Sciences Interest Group Teleconference 15:01:47 Date: 12 April 2016 15:02:31 hsolbrig has joined #hcls 15:03:52 Topic: Planning for Montreal HL7 Meeting Tue May 10, 11:00am-12:30pm 15:04:29 Sajjad: I'll be coming to Montreal meeting, and will also be in the FHIR Connectathon 15:05:55 Tony has joined #HCLS 15:06:56 Sajjad_Hussain has joined #hcls 15:07:10 ... Which Connectathon tracks would you recommend? 15:07:54 lloyd: Newcomers are welcome, including those who have only browsed the spec 15:08:48 sajjad: Recommendation for starter on FHIR? 15:10:23 lloyd: Suggest the patient track 15:11:32 ... There are also other tutorials through the week. 15:12:49 dbooth: Other planning for Tuesday meeting in Montreal? 15:13:22 sajjad: Need to register for Tuesday? 15:13:36 dbooth: Yes, on HL7 site. 15:14:30 dbooth: Meeting room is the room for the ITS group -- they host the RDF subgroup. 15:18:04 dbooth: Status update, and review work products. 15:19:24 Topic: RDF page 15:19:59 eric: Updated to work with the RDF that Grahame generates 15:20:57 http://w3c.github.io/hcls-fhir-rdf/spec/rdf.html 15:22:55 Here is the previous version: http://w3c.github.io/hcls-fhir-rdf/spec/rdf-SBS.html 15:24:38 eric: Need a document that reflects WG decisions and has ShEx. Also need a user-facing doc. 15:24:58 ... The RDF templates on the ShEx side should reflect the WG decisions. 15:25:16 ... The RDF tab should capture it in a template. 15:27:59 dbooth: We have not previously discussed a second document, internal-facing, to catalog our decisions. 15:29:42 ... Concerned to add only additional document that we really need. 15:31:21 -> http://w3c.github.io/hcls-fhir-rdf/spec/rdf-SBS#fhir-codeableconcept-and-coding-structure-definition CodedableConcept 15:32:49 eric: We could put that in the issues list. Would it capture it well enough? 15:36:22 tony: Hard to capture the low level decisions in an issues list. Too many of them. Many of these are just the way that we have decided to write the RDF. 15:36:31 ... Need to do a detailed review. 15:37:07 eric: Bunch of decisions to make, such as CodableConcept, that will be reflected in the individual resource pages. 15:37:19 ... Those will be represented in RDF templates. 15:37:40 ... There's the question of how to visually parse an RDF template and generate FHIR instance. That's captured in rdf.html 15:38:24 ... Also, if our job is to write core FHIR resources, how do we write valuesets? 15:39:14 ... If we apply only the default mapping we won't get something computable. 15:41:41 tony: The structure def to schema is not 1-1. We're doing the equivalent of that for OWL. 15:42:29 dbooth: Ready to review eric's draft? 15:43:23 eric: Need to work through more of the datatypes, figure out their RDF representation, to drive the generation of the RDF. 15:44:11 eric: What should we do when we have an instantiation of another datatype? E.g., an age. 15:45:01 ... Person.age? Or just an integer? 15:45:18 harold: Do we make the range integer, or create a specialized type for age? 15:46:08 eric: Maybe look at SBS document to see what needs to be resolved, to make a TODO list: http://w3c.github.io/hcls-fhir-rdf/spec/rdf-SBS.html 15:46:20 tony: I'd rather review the new document. 15:46:59 eric: But the SBS doc drives the generation of the Turtle templates 15:48:51 sajjad: Are we driving toward a doc where an RDF expert can take the FHIR ont and start representing things in RDF? 15:49:26 eric: Guoqian and Harold are working on mapping structure def to templates for FHIR Turtle. 15:49:58 ... We're working on that for a JAMIA paper, but when we're finished it may be helpful to this work. 15:50:01 rhausam has joined #HCLS 15:50:46 sajjad: The other way around, a knowledge engineer takes FHIR RDF ont, and represents instances as RDF, rather than first knowing FHIR 15:51:04 ... As a user, I want to use FHIR as just another ontology. 15:51:46 harold: That's dangerous territory, because the FHIR ont only talks about medical records -- information models, not what they are about. 15:52:35 ... You may went to look at SNOMED and LOINC instead. 15:53:32 sajjad: If I want to represent clinical information model . . . 15:54:05 tony: We already have a model, it's the FHIR model. We're just representing it in RDF. 15:54:22 ... The template notation is a way to show how to write it. 15:54:44 harold: And ShEx is to the RDF as XML Schema is to XML. 15:56:06 eric: Two representations of the schema: the RDF template, and ShEx. There's also the ont, which does not map 1-1 to the structure def. 15:56:30 ... But there's a difference between an ont for an info model than one for OBO. 15:56:48 ... A little of that nuance can be captured in the ontology.html doc. 15:57:09 ... Do we have anything to allow an RDF geek to quickly grok the FHIR RDF model? 15:58:06 ... Might need another doc for that. Or maybe the ontology.html doc could also fill that role. 15:59:39 dbooth: want a concrete plan forward 16:00:07 sajjad: to learn FHIR RDF, I can read the examples. Another way is to read the FHIR spec and check the schemas. 16:00:36 ... As an RDF person, why not learn FHIR RDF? 16:01:03 lloyd: At some point you'll be able to focus on the FHIR RDF piece? But right now the RDF is not as prevalent as the other serializations. 16:01:49 ... But there's much more the FHIR than the syntax. You need to learn the other aspects of FHIR also. 16:02:08 ... We want RDF to be an equal sibling to XML or JSON. 16:02:47 ... We don't have material written yet to guide the RDF reader. 16:05:31 dbooth: Proposals forward I've heard: 1. review eric's latest draft http://w3c.github.io/hcls-fhir-rdf/spec/rdf.html 2. review the previous draft http://w3c.github.io/hcls-fhir-rdf/spec/rdf-SBS.html 16:06:02 tony: We've already reviewed the SBS doc -- that was the side-by-side doc. 16:07:18 eric: things are missing 16:08:00 dbooth: How do we identify the missing things? 16:08:24 eric: They arise in doing the ShEx for them. Harold could list things that are not covered. 16:08:33 Apologies - gotta go. Will try to assemble a list as per eric 16:15:41 eric: Each section with an instance should have the logical model (table) from FHIR, and some ShEx, and then also instances. 16:16:49 dbooth: Our work plan is to look up the logical model and insert the corresponding ShEx into the SBS document? 16:20:11 eric: maybe we would keep the SBS document, but first it will be used to capture our model decisions. 16:21:51 dbooth: Take out the OWL from the SBS doc? 16:22:02 eric: Yes. It is already in the ontology.html doc. 16:23:18 Chair: David Booth 16:23:53 Present: David Booth, EricP, Harold Solbrig, Rob Hausam, Lloyd McKenzie, Sajjad Hussain, Thomas Lukasik, Tony Mallia 16:24:02 ADJOURNED 16:24:20 rrsagent, draft minutes 16:24:20 I have made the request to generate http://www.w3.org/2016/04/12-hcls-minutes.html dbooth 18:57:51 Zakim has left #hcls 21:02:56 Tony has joined #HCLS 21:03:38 hsolbrig has joined #hcls 21:09:19 Topic: ========== 5pm Call ============= 21:10:06 dbooth: ontology.html target audience will be OWL users who want to use the downloadable OWL FHIR ontology. 21:10:52 Topic: ontology.html document 21:11:21 eric: ontology.html should say how to use the ont. 21:11:32 tony: that will also have the mapping from FHIR model to OWL? 21:11:54 eric: That's what the mayo JAMIA paper will describe. want to help with it? 21:12:43 rhausam_ has joined #HCLS 21:16:36 Topic: Reviewing the ShEx for the Side-by-side FHIR models 21:20:17 -> https://github.com/w3c/hcls-fhir-rdf/blob/gh-pages/data/definitions.shex ginourmous ShEx 21:21:16 -> http://www.w3.org/2016/FHIR-tutorial/Constellations Constellations document 21:23:20 -> https://github.com/w3c/hcls-fhir-rdf/blob/gh-pages/data/definitions.shex#L52 21:24:09 grahame: Single file for ShEx, or how would we modularize it? 21:25:05 eric: Can do it either way. Might be useful both ways. 21:25:34 ... In schema I generate modular schemas, and a combined schema, but some tools cannot cope with circular references with modular schemas. 21:25:49 ... line 63 AllergyIntolerance is a type name? 21:25:57 eric: Sort of. It's a shape. 21:26:26 grahame: Why does it say it is an instance of itself? 21:26:38 eric: That's the difference between a shape and a type. 21:26:50 [[ 21:26:50 { 21:26:50 a [fhir:AllergyIntolerance]?, 21:26:52 ]] 21:27:40 eric: is a shape; fhir:AllergyIntolerance is a type. 21:27:59 grahame: Is that saying that it might have an rdf:type stated in the data? 21:28:03 eric: yes. 21:28:18 grahame: Why is it optional? Why not mandatory? 21:29:09 eric: It is only mandatory for the root. 21:29:43 dbooth: I think we decided to make it mandatory if it is a root or if it is an embedded resource. 21:30:22 grahame: Line 65 ':AllergyIntolerance @*,' ? 21:30:47 harold: That's inheritance from DomainResource, but it's not right. 21:31:41 s/Reviewing the ShEx for the Side-by-side FHIR models/Reviewing the Ginormous ShEx/ 21:32:44 grahame: What's the difference between ":" and "fhir:" 21:32:52 eric: They should all say "fhir:" 21:33:29 eric: line 64 is a small set of possible values in square brackets 21:34:43 Topic Ginormous ShEx - fhir:Age 21:34:57 grahame: Age is a profile technically 21:36:16 dbooth: If Age is a profile, then the type should be the original type -- not a new type. 21:36:25 grahame: It should be element.id also 21:37:20 grahame: If you generate an AllergyIntolerance you'll see issues. 21:38:08 harold: When we're generating from the meta we've been using the snapshot. We're using the JSON rep of the element definition. 21:38:35 grahame: Every element has a base that tells you what it comes from, with a base path. 21:38:41 ... Use that. 21:39:36 harold: we had been liberally minting new predicates even if there was no difference from the root. 21:40:38 grahame: I'll need to build the ShEx in the build process. Are you using java? 21:40:57 harold: python. how should we dovetail with yours? 21:41:52 grahame: I'll put in a template Java class passing in the structure definitions, and we can both work on it there. 21:42:18 ... Once we can generate the ShEx i'll put it into the build. 21:42:55 harold: I'm looking at Medication Structures (sec 1) in the constellations doc: https://www.w3.org/2016/FHIR-tutorial/Constellations 21:44:19 FHIR exmaple: http://hl7-fhir.github.io/medicationexample2.ttl.html 21:46:01 grahame: Look at this example; 21:46:03 http://hl7-fhir.github.io/medicationorderexample1.ttl.html 21:48:41 grahame: see http://hl7-fhir.github.io/medicationorder.profile.json.html 21:48:50 ... notice "path": "MedicationOrder.id", 21:48:58 ... and 21:49:00 "base": { 21:49:00 "path": "Resource.id", 21:49:57 ACTION: Grahame to create a stub class for the ShEx generation, then harold will work on it with Grahame 21:49:57 Error finding 'Grahame'. You can review and register nicknames at . 21:52:23 dbooth: What work process? 21:52:44 harold: We will update the build process and review pieces as we go. 21:53:02 dbooth: Let us know what parts you have updated, so that we can review them. 21:55:39 grahame: We should then validate the ShEx against the Turtle examples. 21:58:49 harold: I'll work through the examples in the SBS document http://w3c.github.io/hcls-fhir-rdf/spec/rdf-SBS and do the ShEx for them 22:02:23 ... And I'll be guided by Grahame's RDF 22:02:36 ... And I'll also work with Eric to update the Constellations doc to align 22:03:55 dbooth: Ok, so let us know which example you convert and are ready to review. 22:08:33 Present+ (5pm call:) David Booth, EricP, Grahame Grieve, Tony Mallia, Lloyd McKenzie, Harold Solbrig 22:08:47 ADJOURNED 22:08:50 rrsagent, draft minutes 22:08:50 I have made the request to generate http://www.w3.org/2016/04/12-hcls-minutes.html dbooth