14:59:01 RRSAgent has joined #hcls 14:59:05 logging to https://www.w3.org/2025/05/01-hcls-irc 14:59:05 rrsagent, make logs public 14:59:08 Chair: David Booth 14:59:11 Meeting: FHIR RDF 15:06:59 FHIR RDF Playground 15:07:09 https://fhircat.github.io/fhir-rdf-playground/ 15:07:59 erich: I'm writing a java lib to make Amazon storage look like linked web storage. 15:08:15 ... 30-40 billion triples 15:08:42 ... Stress testing the use of RDF lists. 15:10:11 ... Complex datatypes would help, such as being discussed now. 15:11:21 erich: Also looking at https://www.w3.org/TR/dx-prof-conneg/ 15:12:04 ... How would FHIR RDF be in a SOLID pod? 15:12:45 ericP: We used all turtle in Janeira Digital. One thing that will be confusing: FHIR is using weak media types but claiming them as strong. 15:13:08 ... They're violating the rules of strong etags, in a way that makes them weak. 15:15:20 s/FHIR RDF Playground/Topic: FHIR RDF Playground/ 15:16:36 erich: How FHIR compliant are EHRs like Cerner? 15:16:54 ericP: A lot of systems are pretty far behind, like DSTU 2 or3. 15:17:09 ... Paris system is using FHIR R4, but have extensions for R5. 15:18:10 ... Business interests want vendor lock-in, rather than standards compliance. 15:18:13 dbooth: I've heard that F5 doesn't have much uptake, but they expect R6 to have more. 15:19:47 gaurav: Playground has a bunch of IRI code, and some tests. I wrote a PR that fixes that. 15:20:26 ACTION: EricP to review gaurav's playground PR 15:20:54 Present: EricP, Erich Bremer, Jim Balhoff, Gaurav Vaidya 15:25:52 Topic: URIs for FHIR Paths -- issue 61 15:25:53 https://github.com/w3c/hcls-fhir-rdf/issues/61 15:30:46 Agreed to close due to lack of interest/expertise. 15:30:48 Topic: Update HAPI server to RDF R5 features #100 15:30:56 https://github.com/w3c/hcls-fhir-rdf/issues/100 15:31:14 ericP: Waiting for ShEx validation of examples 15:32:16 Topic: Need to re-enable shex validation in FHIR build #81 15:32:35 https://github.com/w3c/hcls-fhir-rdf/issues/81 15:32:56 jim: round-trip validation has been disabled for a long time, because it is too slow. 15:33:11 ericP: ShEx validation is also disabled. 15:33:32 ... Grahame made a change that broke it, and it took a lot of time to figure out why. 15:33:41 ... But it also took a long time to run. 15:34:02 ... Iovka is working on an efficient validator for current FHIR RDF ShEx (using EXTENDS). 15:34:23 ... Claude and I will work w her in Lille on that (in a few days). 15:35:19 ... Then it could be re-enabled in the build process. 15:37:38 dbooth: EricP is planning to get this working again soon, and hoping to get it back into the FHIR build process. 15:46:28 Topic: Add a top level node for each FHIR code ontology? #57 15:46:34 https://github.com/w3c/hcls-fhir-rdf/issues/57 15:47:27 Present+ Rob_Hausam 15:49:05 rrsagent, pointer? 15:49:05 See https://www.w3.org/2025/05/01-hcls-irc#T15-49-05 15:50:01 dbooth: I think this would become more important to folks who are using the FHIR valuesets in reasoning 16:00:00 dbooth: Closing due to lack of interest/expertise. 16:00:06 Topic: FHIR RDF ontology URLs do not resolve #48 16:00:12 https://github.com/w3c/hcls-fhir-rdf/issues/48 16:00:36 jim: The classes in our ont have URLs that do resolve. 16:01:00 ... e.g. http://hl7.org/fhir/ClinicalUseDefinitionWarningComponent 16:04:32 ericP: The way forward would be to come up w a compelling use case, then go to Grahame. 16:06:52 TallTed has joined #hcls 16:14:55 dbooth: That's assuming we don't change the URIs. Another possibility would be to change those URIs, to put them under subdirectories that we can more easily control. 16:15:08 ADJOURNED 16:15:14 rrsagent, draft minutes 16:15:15 I have made the request to generate https://www.w3.org/2025/05/01-hcls-minutes.html dbooth 16:42:28 TallTed has joined #hcls