15:59:50 RRSAgent has joined #hcls 15:59:54 logging to https://www.w3.org/2023/02/09-hcls-irc 15:59:54 rrsagent, make logs public 16:00:06 Meeting: FHIR RDF 16:00:33 Chair: David Booth 16:04:21 Topic: FHIR Build 16:05:49 jim: Opened a couple of PRs. One on FHIR Core, and the other on Kindling. https://github.com/HL7/kindling/pull/111 16:06:42 https://github.com/hapifhir/org.hl7.fhir.core/pull/1110 16:07:12 jim: Also theh profiles (structure defs) 16:08:00 jim: Looking at this example: http://hl7.org/fhir/patient.profile.ttl.html 16:09:32 dbooth: propose address other things first. the Turtle structure defs are less important. 16:12:29 eric: We're looking at the meta level. Claude helped him work out a list of lower priority things. 16:13:05 eric: Low priority to even look for problems at the meta level. 16:13:42 dbooth: Agreed. 16:14:48 dbooth: I saw what looked like extra type arcs. 16:15:50 jim: fhir:deceased[x] has type arcs. 16:16:15 dbooth: Okay, that looks right. 16:16:24 eric: Multi-line comments in examples? 16:16:41 jim: That's still a problem. Will try to fix it. 16:19:36 jim: loinc concept IRIs are hard coded. 16:20:39 dbooth: Loinc prefix should be https://loinc.org/rdf/ 16:20:50 ... per Gaurav's google doc. 16:23:13 dbooth: Suggest adding others defined in the Gaurav's document: https://docs.google.com/document/d/1sW3Tgj2J_wBzlUWih07e0Vf_M9Ue8YyPqjK0arhajS8/edit# 16:24:37 jim: There's parsing work to be done also. 16:25:24 dbooth: Discussing parsing FHIR RDF and going back to FHIR JSON or XML. 16:27:11 jim: Can we drop that code? Is it used for anything? 16:27:24 eric: Maybe was used for round-trip testing. 16:27:58 ACTION: Jim check w Grahame about dropping the RDF parsing code (in favor of HAPI). 16:29:56 Topic: Ont generation 16:30:13 Present: Daniel Stone, Rob Hausam, Jim Balhoff, EricP, David Booth 16:30:37 daniel: Made two commits for updates. 16:30:58 https://github.com/Fhircat/kindling/tree/R5_ontology_update 16:31:04 https://docs.google.com/spreadsheets/d/1Ncjs-AAFWZEtP0KCEjTcUJa_HMVeg4Xoh3QPFEW6C0s/edit#gid=0 16:33:34 eric: Tried to see if there were commonalities between the various FHIR properties. In principle that would be a nice-ish way to populate the rdfs:labels. 16:34:18 dbooth: How should daniel gen the rdfs:labels ? 16:35:10 eric: 1. Grab the first of each. 2. omit rdfs:label 3. Hand-craft the property names. 16:36:22 dbooth: Option 4. How about concatenate them all? 16:36:42 eric: Option 5: Do option 4 but hand-craft some conspicuous ones. 16:37:46 daniel: Generated a subset for key elements we might care about. 16:38:42 ... Then ran rdfdiff to compare latest changes. 16:41:48 eric: Maybe we should not invent generic labels, since they are not currently in FHIR. 16:43:00 dbooth: Propose concatenate the labels for each property, separated by vertical bars, into an rdfs:label 16:44:59 eric: Proposed generic labels might motivate the FHIR group to create generic labels. 16:46:04 ... They already have a need for such a doc. 16:46:26 rob: Partly agree. Slowly trying to converge. 16:49:01 TallTed has joined #hcls 16:53:51 AGREED: Including truncated concatenated labels is better than omitting them. 16:56:05 AGREED: Daniel should use a list of generic labels if he has time, and fall back to trucated concatenated labels for others. 16:56:59 Topic: Punning for shortened propoerties? 16:57:17 AGREED: Use punning. 16:59:55 daniel: What other OWL assertions do we need? 17:00:10 dbooth: I think we need these: 17:00:12 [[ 17:00:12 1. Add global declarations: 17:00:12 fhir:_Resource rdfs:subClassOf [ owl:onProperty fhir:modifierExtension; owl:minCardinality 1 ]. 17:00:12 [] a owl:AllDisjointClasses ; 17:00:13 owl:members ( fhir:Resource fhir:_Resource ) . 17:00:13 2. And for each FHIR resource such as fhir:Obs, add this declaration: 17:00:15 :_Obs rdfs:subClassOf fhir:_Resource. 17:00:17 ]] 17:03:15 jim: Seems ok to me. 17:06:47 eric: Not sure it should be fhir:Resource. Maybe fhir:DomainResource. 17:07:04 eric: need to investigate more. 17:07:54 daniel: example: 17:07:55 [[ 17:07:56 This is the only way that I could get blank node to appear in code atm: 17:07:56 [ a owl:AllDisjointClasses ; 17:07:56 owl:members ( fhir:Resource fhir:_Resource ) 17:07:56 ] . 17:07:57 ]] 17:08:15 eric: That's fine that way. 17:09:14 ACTION: DBooth to investigate whether it should be fhir:Resoruce or fhir:DomainResource 17:09:30 http://hl7.org/fhir/extensibility.html 17:09:36 • There are a few resources (ones that do not specialize DomainResource) where extensions are not allowed on the root element, but extensions can appear elsewhere through the resource 17:09:51 eric: Can look at the content model of them, and also at the datatypes. 17:11:24 dbooth: So that quote Rob found indicates that the declaration should be for fhir:DomainResource and fhir:_DomainResource 17:11:50 eric: And only declare them on individual resources that are under fhir:DomainResource . 17:12:34 ... directly or indirectly. 17:20:01 ADJOURNED 17:20:18 rrsagent, draft minutes 17:20:20 I have made the request to generate https://www.w3.org/2023/02/09-hcls-minutes.html dbooth 17:49:03 present+ James Champion 17:49:06 rrsagent, draft minutes 17:49:08 I have made the request to generate https://www.w3.org/2023/02/09-hcls-minutes.html dbooth