15:58:50 RRSAgent has joined #hcls 15:58:55 logging to https://www.w3.org/2026/01/08-hcls-irc 15:58:58 rrsagent, make logs public 15:59:02 Meeting: FHIR RDF 15:59:05 Chair: David Booth 16:04:17 Topic: IRI stems 16:04:19 https://github.com/w3c/hcls-fhir-rdf/issues/160 16:04:50 gaurav: Issue 160 tracks what I plan to finish this month. 16:05:15 ... Main update is #205 https://github.com/w3c/hcls-fhir-rdf/issues/205 16:05:39 ... Seems to be how HTML files are generated. But all CodeSystem files have been removed from THO. 16:07:32 ... Now we only have the NamingSystem records. So there's still an issue. Should update our guidance: 1. only put the IRI stem in NamingSystems. 2. Make them more visible. 16:08:17 ... Could put the IRI stem in the meta record file. 16:09:07 https://terminology.hl7.org/external_code_systems.html 16:09:50 gaurav: Now you're supposed to go to external code system on THO, and within this table there's an identification record, machine readable, and a metadata record file that is not machine readable. 16:10:17 ... We have it in the machine readable file, but not worth putting it into the non-machine readable file. 16:10:55 ... So we should change our rec to put the IRI stem into the machine readable file. 16:11:18 dbooth: Changing the rec in the rdf.html page appendix? gaurav: yes 16:13:47 gaurav: Expect to make progress next week. 16:13:58 Topic: Expanding the ontology 16:15:59 https://lists.w3.org/Archives/Public/public-semweb-lifesci/2026Jan/0001.html 16:19:38 ken: Background on data exchange in healthcare. Semantic layer can help improved data exchange. 16:20:26 ... My company's view is that exchanging data between formats requires (for precision and accuracy) the ability to match semantically what that data means. 16:20:50 ... For the moment, ignoring the problem of transforming values. 16:20:59 ... But concepts need to match. 16:21:50 ... For interop, the formats (eg FHIR, CDA, V2, etc.) are really data formats -- not really an easy way to get at semantics. 16:22:17 ... They have structures that imply semantics at a high level, which makes it hard to determine semantics. 16:22:38 TallTed has joined #hcls 16:22:43 ... Did some work in the OMG. 16:23:24 ... Last principle was that this needs to be a shared ont -- not proprietary. Looking for a place where people could dev such an ont as an open resource. 16:23:38 ... My company is implementing some of this. 16:25:18 dbooth: That fits within our mission. Devil is in the detail of what is practical for us to do. 16:25:37 eric_jahn: I'll need a person class, whether part of FHIR or not. 16:26:15 ... We need a person class to connect healthcare data to housing data. 16:27:39 ericP: That's an interesting case, because whenever we take clinical data there's always a tension between a single table vs 6000 tables. Could use schema.org concept of Person, but then you might want attributes of a person. 16:28:03 ... That's the kind of place where it would be interesting to see concrete proposals, and analyze use cases. 16:28:31 ... Need to spend a little time modeling to see if it solves sufficient problems to be worth the time investment. 16:28:58 ken: Being able to make rels btwn classes is helpful. Difficult to do w data models. 16:30:36 dbooth: Need a concrete starting proposal. 16:31:03 ken: Suggestions? 16:32:10 dbooth: Pretty sure we won't want to invent our own Person class. 16:33:42 gaurav: Biolink Model has a “Case” (patient: https://biolink.github.io/biolink-model/Case/) 16:33:56 ... It provides general classes for things like proteins and genes. 16:34:03 ... They also have a Patient class. 16:35:18 dbooth: Please create an issue on our issues list, and put a concrete starting proposal in it. 16:36:47 dbooth: We would be starting w our existing fhir.ttl ont. 16:37:07 ken: There's a class called BackboneElement that we need to refine. 16:39:27 eric_jahn: I think we could add a person class that connect to something like schema.org 16:40:57 ericP: On the use of Patient, there's a bunch of places in FHIR where they flattened things. (BTW, Backbone is just a structure.) 16:41:00 ... There's a bunch of places where the modeling isn't great. 16:41:34 ... Could say that fhir:Patient is a subclass of something else. 16:42:04 ... But then we might have to say it has to be unioned with the class of animals. 16:42:27 Topic: DICOM 16:43:17 erich: New version of imaging data commons scan as been generated and loaded into qlever. 16:43:28 ... I'll send Detlef the link. 16:45:01 Topic: Changes from R5 to R6 16:45:11 https://github.com/w3c/hcls-fhir-rdf/issues/214 16:45:57 ACTION: Dbooth to try this. 16:47:54 Topic: R6 testing 16:54:24 ericP: Tim Prudhomme is working on that 16:54:29 Topic: Issues list 16:54:38 https://github.com/w3c/hcls-fhir-rdf/issues/208 16:59:22 https://github.com/w3c/hcls-fhir-rdf/issues/201 16:59:46 ericP: Should we de-sync the RDF version of FHIR from the regular version of FHIR? 16:59:57 ... That would be hard. 17:01:24 ... Could detect every time a structure changes, but to deal w it properly, (such as going from a name to a structure) we'd have to rename it and deprecate the old one. Could do it, but would need a tie-in to the change process (i.e. the structure def spreadsheet source), and then we could run across that to see the changes. 17:05:47 ACTION: Ericp to propose an alternate approach 17:15:07 Present: EricP, Eric Jahn, Erich Bremer, Ken Lord, Gaurav Vaidya, Detlef Grittner, David Booth 17:15:55 ADJOURNED 17:15:59 rrsagent, draft minutes 17:16:00 I have made the request to generate https://www.w3.org/2026/01/08-hcls-minutes.html dbooth