14:59:27 <RRSAgent> RRSAgent has joined #hcls
14:59:31 <RRSAgent> logging to https://www.w3.org/2025/07/24-hcls-irc
14:59:32 <dbooth> rrsagent, make logs public
14:59:35 <dbooth> Meeting: FHIR RDF
14:59:38 <dbooth> Chair: David Booth
15:02:26 <dbooth> Topic: INtros
15:04:53 <dbooth> ericP: Long tie RDF geek
15:05:18 <dbooth> gaurav: Semantic web technologist at U of NC
15:05:57 <dbooth> jim: Also at U of NC.  We've been contributing to FHIR RDF through a grant under Mayo clinic.  Done a lot of bio ontology work.
15:06:28 <dbooth> tim: Healthcare software dev.  Strong interest in ont and RDF.  Working for Firely.
15:07:12 <dbooth> erich: Work at Stonybrook U, long time RDF boy.  Been working on a DICOM RDF represesntation.  Also int in FHIR RDF.
15:08:19 <dbooth> eric-jhan: Interop arch at BitFocus.  Moving heaviliy into OWL.  Implementing FHIR more and more.  Also int in how FHIR and other RDF representations relate.  Been following since 2014.
15:09:47 <dbooth> Rita_Torkzadeh: On a call w Brian Pech and David Booth before.  Int in DICOM RDF rep.
15:10:23 <dbooth> DBooth: Started this FHIR RDF effort with EricP and others.
15:12:33 <dbooth> https://github.com/w3c/hcls-fhir-rdf/issues/120
15:12:58 <dbooth> ericP: canonical and Reference don't use the same resolution path.
15:13:14 <dbooth> ... They requred differnet kinds of queries.
15:13:31 <dbooth> ... We invented fhir:link
15:14:05 <dbooth> ... RDF itself does not have relative URLs, but each RDF format does.
15:14:39 <dbooth> ... So in converting them to abolute URIs, we had to prepend a base with "../"
15:16:31 <dbooth> ... Values of FHIR "uri", "url" and "canonical" types need to have a fhir:link generated as an RDF node, like <http://example.org/fhir/..foo>
15:16:50 <dbooth> ... There was a debate about how to do this with Reference.
15:22:53 <dbooth> (Jim shows code changes he did to implement this)
15:24:11 <dbooth> ... Something like "uri" needs a prefix added, to be absolute.
15:25:07 <dbooth> ericP: Not sure that profiles are being generated properly anyway, so I suggest disableing profile generation of examples.
15:30:10 <dbooth> dbooth: Does the problem only appear in profiles?
15:30:33 <dbooth> jim: I will check.
15:32:48 <dbooth> ericP: I noticed that MolecularDefinition has a problem.
15:33:15 <dbooth> ... Wonder how example errors are handled in the FHIR build
15:38:57 <dbooth> dbooth: Would be good if there's an error in an example, to generate an RDF example with a comment saying the example could not be generated due to an error in the original.
15:40:35 <dbooth> dbooth: Should ask the other FHIR folks what to do if an error is found in an exampe.
15:44:47 <dbooth> Topic: ValueSet bindings for ontology & validation #167
15:44:54 <dbooth> https://github.com/w3c/hcls-fhir-rdf/issues/167
15:47:06 <dbooth> tim: This has a valueset binding.
15:47:57 <dbooth> ... ValueSets are not yet linked to Code systems, but adding fhir:link would handle that.
15:48:25 <dbooth> ... Wouldn't be able use OWL to validate, becuase of OWA, but ShEx could validate it.
15:48:56 <dbooth> ... Right now the shex only says it needs to be CodeablConcept.
15:49:04 <dbooth> ... Could improved the shex to check it.
15:49:55 <dbooth> ... But would probably be worth putting it into the ontology.
15:50:16 <dbooth> ... Also related to another issue: 168
15:50:20 <dbooth> https://github.com/w3c/hcls-fhir-rdf/issues/168
15:50:54 <dbooth> tim: When you define a valueset, you can do it w a rule.
15:51:14 <dbooth> ... E.g., if you have a code here, it needs to be a descendent of a SNOMED code.
15:51:35 <dbooth> ... Would be nice to represent the descendant rel as an RDF subclass rel.
15:51:51 <dbooth> ... That would allow OWL to do valueset expansion.
15:55:36 <dbooth> tim: For finding the rel, OWL could do that.  But for validation shex would still be needed, for CWA.
15:56:48 <dbooth> ericP: I don't think you'll get validation without connecting to a terminology server.
15:58:19 <dbooth> ... Could use a semantic action to talk to a terminology server.
15:59:03 <dbooth> tim: Could put this into FHIR R6.  They want R6 changes by Nov 2025.
16:01:59 <dbooth> ericP: The addition of fhir:link breaks a lot of my shex code.  Want to consider changing the name of fhir:link to fhir:n .
16:02:06 <dbooth> ACTION: EricP to make a new issue for that
16:03:16 <dbooth> Present: Eric Jahn, Tim Prudhomme, EricP, Gaurav Vaidya, Jim Balhoff, Rita Torkzadeh, David Booth
16:03:20 <dbooth> ADJOURNED
16:03:27 <dbooth> rrsagent, draft minutes
16:03:29 <RRSAgent> I have made the request to generate https://www.w3.org/2025/07/24-hcls-minutes.html dbooth