15:59:16 <RRSAgent> RRSAgent has joined #hcls
15:59:21 <RRSAgent> logging to https://www.w3.org/2025/01/09-hcls-irc
15:59:21 <dbooth> rrsagent, make logs public
15:59:32 <dbooth> Meeting: FHIR RDF
15:59:32 <dbooth> Chair: David Booth
16:03:34 <dbooth> Topic: DICOM
16:03:57 <dbooth> erich: Suggest we close issue 146, as addressed.
16:04:30 <dbooth> detlef: RDF lists sounds fine.
16:06:26 <dbooth> detlef: But it might cause problems for something that points to an item in the list.
16:07:00 <dbooth> ... Want to investigate further.
16:07:07 <dbooth> https://github.com/w3c/hcls-fhir-rdf/issues/146
16:07:49 <dbooth> ACTION: Detleft to investigate 146
16:07:56 <dbooth> erich: Also looking at 142 https://github.com/w3c/hcls-fhir-rdf/issues/146
16:08:45 <dbooth> erich: detlef suggested using instance UID.   Two different files might use the same one, causing a clash.  Should we worry about that?
16:09:04 <dbooth> detlef: In our case, the first wins and the other goes into quarantine for human intervention.
16:09:40 <dbooth> erich: That's similar to other clashes that can happen.  I'm okay with that.  I used to use a file hash to avoid clash.
16:10:04 <dbooth> ... But my DCM to RDF converter allows either.  I'm fine w your suggestion.
16:11:03 <dbooth> detlef: THere's a second in DICOM to use your own IDs without registering your root ID, like for research projects that need to shuffle around file.  They use their own IDs.
16:11:13 <dbooth> ... So there's one that means "locally generated" ID
16:11:54 <dbooth> erich: If someone copies a folder (w copy of original files) the metadata will be identical.  If I use the SOP instance UID, I won't get duplicate because they're literally the same file.
16:12:13 <dbooth> ... But for a SOP instance ID in converstion to RDF, I want to see 'derived from ...'
16:12:27 <dbooth> ... I want to see that there are multiple files that are really the same thing.
16:12:49 <dbooth> ... Want to avoid duplicate series.
16:13:31 <dbooth> ... Want to avoid accidental file duplication: same file but different folders.
16:13:50 <dbooth> detlef: But what if the data is transferred over a network?  The info is lost.
16:14:34 <dbooth> detlef: We treat them as completely different files.
16:14:59 <dbooth> ... If there are different sub-instance UIDs, they'll be treated as different.
16:15:53 <dbooth> erich: I need a way to detect duplicated files.
16:17:05 <dbooth> detlef: Need to recognize that subinstance UID is always part of it.  Might need to look into the file.
16:17:42 <dbooth> erich: I was using prov:derivedFrom
16:18:23 <dbooth> ... So I might have 10 prov:derivedFrom but they're all copies of the same file.
16:20:02 <dbooth> detlef: Sometimes the original file program is not relevant.   subinstance UID is enough to find a local copy.
16:20:20 <dbooth> dbooth: Pack system?
16:20:34 <dbooth> erich: Main engine for imaging system.
16:22:16 <dbooth> dbooth: Any harm in having also the prov:derivedFrom ?
16:23:04 <dbooth> detlef: No harm, but could be confusing.
16:24:39 <dbooth> erich: It would expose details of the original system that might not want to be exposed.
16:25:09 <dbooth> ... I'm fine w leaving it as an option on my own converter.
16:26:26 <dbooth> AGREED: Use SOP instance UID
16:26:48 <dbooth> rrsagent, draft minutes
16:26:49 <RRSAgent> I have made the request to generate https://www.w3.org/2025/01/09-hcls-minutes.html dbooth
16:28:11 <dbooth> Topic: IRI stems
16:28:27 <dbooth> https://github.com/w3c/hcls-fhir-rdf/issues/123#issuecomment-2580679839
16:29:03 <dbooth> gaurav: We had a spreadsheet of all of the naming and code systems in HL7 UTG.   Updated that, and added a link to the issue.
16:31:26 <dbooth> ... It's in its own branch.  A Scala script creates it.  Probably don't want to integrate the script  into UTG itself.   Where to put it?
16:32:11 <dbooth> dbooth: I suggest the HCLS github space.
16:32:25 <dbooth> ACTION: Gaurav to look at where to store the scala script
16:32:45 <dbooth> gaurav: Also created a ticket for IRI stem lookup code being out of date.
16:33:01 <dbooth> https://github.com/fhircat/fhir-rdf-playground/pull/17
16:34:26 <dbooth> https://github.com/w3c/hcls-fhir-rdf/issues/156
16:35:43 <dbooth> Topic: FHIR RDF examples
16:36:00 <dbooth> jim: I opened 3 PRs on the HAPI core repo.
16:36:19 <dbooth> https://github.com/hapifhir/org.hl7.fhir.core/pulls
16:36:39 <dbooth> jim: I think there were other issues I was going to address..  I'll look.
16:37:23 <dbooth> ... I also opened an issue a out xsd:anyURI strings that have pipe symbols.   Jena doesn't complain about them.
16:37:56 <dbooth> ... HAPI FHIR code says "Illegal URI".  It has a regex.
16:38:16 <dbooth> ... Jena doesn't complain, but only because it's not parsing any URIs.
16:45:28 <dbooth> ... In https://github.com/w3c/hcls-fhir-rdf/issues/155 Jena allows the fhir:v "http://hl7.org/fhir/ValueSet/all-languages|5.0.0"^^xsd:anyURI ; statmeent, but complains about the hir:link <http://hl7.org/fhir/ValueSet/all-languages|5.0.0> statmement.
16:45:36 <dbooth> dbooth: We need ericP for further discussion.
16:46:14 <dbooth> Topic: DICOM issue 144
16:46:39 <dbooth> erich: Want to look more at 144 and check w our radiology people.
16:46:59 <dbooth> https://github.com/w3c/hcls-fhir-rdf/issues/144
16:47:08 <dbooth> Topic: DICOM issue 151
16:47:40 <dbooth> https://github.com/w3c/hcls-fhir-rdf/issues/151
16:48:47 <dbooth> erich: Suggest we use w3id URI until we get an official DICOM URI
16:50:26 <dbooth> dbooth: There might be a danger of establishing a w3id if an official DICOM URI is later issued.
16:56:00 <dbooth> dbooth: Suggest waiting until a common URI is really needed
16:57:00 <dbooth> ADJOURNED
16:57:23 <dbooth> Present: Gaurav Vaidya, Jim Balhoff, Erich Bremer, Detlef Grittner, David Booth
16:57:29 <dbooth> rrsagent, draft minutes
16:57:31 <RRSAgent> I have made the request to generate https://www.w3.org/2025/01/09-hcls-minutes.html dbooth