15:57:03 RRSAgent has joined #hcls 15:57:07 logging to https://www.w3.org/2026/01/29-hcls-irc 15:57:09 rrsagent, make logs public 15:57:14 Meeting: FHIR RDF 15:57:18 Chair: David Booth 15:59:26 TallTed has joined #hcls 16:03:32 Topic: Security alert: Does it affect our code? 16:03:32 https://github.com/advisories/GHSA-2xpw-w6gg-jr37 16:04:46 tim: Here is the Python used in that repo: https://github.com/search?q=repo%3Aw3c%2Fhcls-fhir-rdf++language%3APython&type=code 16:09:02 ACTION: Dbooth to move those python file to an archive. 16:09:11 tim: It only affects python 16:11:02 tim: I have a suggested related to @Gaurav Vaidya (RENCI) ’s work https://github.com/w3c/hcls-fhir-rdf/issues/123#issuecomment-340859655 16:11:02 Adding prefixes for the CodeSystems that are part of the “core” spec 16:13:40 s/ACTION: Dbooth to move those python file to an archive.// 16:14:00 ericp: It is only for a DOS attack that would not affect us. Easiest to do nothing. 16:14:03 dbooth: oky 16:14:48 Topic: IRI stems 16:14:52 tim: I have a suggested related to @Gaurav Vaidya (RENCI) ’s work https://github.com/w3c/hcls-fhir-rdf/issues/123#issuecomment-340859655 16:14:52 Adding prefixes for the CodeSystems that are part of the “core” spec 16:15:07 tim: Example usage of a code from a “core” CodeSystem: 16:15:07 The fhir:status of this example: https://build.fhir.org/diagnosticreport-example.ttl.html 16:15:07 I think it should at least have a fhir:l value, even if not using a prefix there 16:15:30 tim: Some CodeSystems are part of core FHIR, with a couple of different bases 16:15:52 ... Many are used in required bindings in the core spec. 16:16:19 ... Should we do prefixes for these core CodeSystems? 16:16:59 ... One reason we're doing it is for type assertions, and we're not currently doing that for examples that use the core CodeSystems 16:18:15 gaurav: We can put IRI stems on any CodeSystem we want, if we respect balloting rules. 16:19:08 ... Makes sense to do that even if we're only formalizing it. Grahame likes to just use a hash separator. We could propose to formalize that, but not sure if it will resolve to an RDF document. 16:19:42 ... FHIR core systems are maintained by HL7. I think Grahame would be ok with the hash approach. 16:20:20 ... For terminology.hl7.org we're recommending that people dong' tpu IRI stems on CodeSystems at all, because it only has NamingSystems now. 16:20:36 ... But it has CodeSystems for HL7 CodeSystems. 16:21:23 ... We now have the mechanism to do this. Just need to identify which ones we want IRI stems for, then talk w HL7 to come with IRI stems that we want. 16:22:06 tim: At least w SNOMED and LOINC, each concept has an obvious IRI for each concept/term, but it's not clearly the case for these internal core systems. 16:22:47 tim: Each code within the CodeSystem would not have its own URL. 16:24:17 gaurav: Interestingly https://hl7.org/fhir/codesystem-diagnostic-report-status.html#diagnostic-report-status-registered does resolve. Does resolve to the individual value >.> 16:25:29 tim: One use of this is to add a type assertion. We're only doing it for LOINC, SNOMED and MeSH. We should do it for any codes. 16:27:07 Official docs here https://build.fhir.org/rdf.html#representing-concepts 16:32:53 gaurav: I think the internal ones all start with hl7.org and end with code-system. 16:34:01 gaurav: Be warned that there are a lot of internal code systems: https://hl7.org/fhir/terminologies-systems.html# 16:34:17 tim: Diagnostic report status points to http://hl7.org/fhir/ValueSet/diagnostic-report-status 16:35:20 gaurav: We should not manually add IRI stems to individual CodeSystems, because there are 400+ of them. So we should use a rule. 16:36:17 gaurav: E.g. http://hl7.org/fhir/version-algorithm -> IRI stem should be “http://hl7.org/fhir/version-algorithm#” 16:39:10 ken: The largest hl7 valueset is about 150 terms, other than examples. 16:40:33 gaurav: CodeSystem pages for hl7.org/fhir have anchors for the codes. 16:42:04 ... But the anchors include the CodeSystem names. 16:42:09 dbooth: redundant. 16:43:09 tim: https://hl7.org/fhir/codesystem-diagnostic-report-status#code this isn’t so bad 16:45:24 gaurav: We should propose to put this into the rdf.html page 16:47:13 ACTION: Tim to post on zulip asking Grahame about formalizing adding a hash to hl7 internal CodeSystems to make IRI stems, and putting this rule on the rdf.html page 16:48:13 gaurav: http://hl7.org/fhir/reference-handling-policy 16:48:21 gaurav: https://jira.hl7.org/browse/UP-755 16:48:54 ... Mark changed it to a pro forma change. It still cannot be moved forward. Jessica Bota is looking into what's wrong. 16:49:04 gaurav: https://github.com/gaurav/hcls-fhir-rdf/blob/8e9385145b04ad68734105442ce2353371cdf6d2/data/utg/iri-stems-in-hl7.md 16:49:31 ... Also working on a markdown to magically making the IRI stem table of IRI stems 16:54:47 Topic: R6 testing 16:54:50 tim: The R5+6 files are ready for testing now: https://github.com/w3c/hcls-fhir-rdf/issues/213#issuecomment-3770736844 16:54:58 ericp: No progress yet. 16:55:22 Topic: FHIR ontology 16:55:44 ken: Eric Jahn and I are working on the use case, regarding housing insecurity 16:56:19 ... Hope to share something in a couple weeks. 17:00:55 ADJOURNED 17:01:49 Present: Erich Bremer, EricP, David Booth, Jim Balhoff, Tim Prudhome, Ken Lord, Gaurav Vaidya 17:01:51 rrsagent, draft minutes 17:01:52 I have made the request to generate https://www.w3.org/2026/01/29-hcls-minutes.html dbooth