Meeting minutes
DICOM
erich: Suggest we close issue 146, as addressed.
detlef: RDF lists sounds fine.
detlef: But it might cause problems for something that points to an item in the list.
… Want to investigate further.
ACTION: Detleft to investigate 146
erich: Also looking at 142 w3c/
erich: detlef suggested using instance UID. Two different files might use the same one, causing a clash. Should we worry about that?
detlef: In our case, the first wins and the other goes into quarantine for human intervention.
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.
… But my DCM to RDF converter allows either. I'm fine w your suggestion.
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.
… So there's one that means "locally generated" ID
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.
… But for a SOP instance ID in converstion to RDF, I want to see 'derived from ...'
… I want to see that there are multiple files that are really the same thing.
… Want to avoid duplicate series.
… Want to avoid accidental file duplication: same file but different folders.
detlef: But what if the data is transferred over a network? The info is lost.
detlef: We treat them as completely different files.
… If there are different sub-instance UIDs, they'll be treated as different.
erich: I need a way to detect duplicated files.
detlef: Need to recognize that subinstance UID is always part of it. Might need to look into the file.
erich: I was using prov:derivedFrom
… So I might have 10 prov:derivedFrom but they're all copies of the same file.
detlef: Sometimes the original file program is not relevant. subinstance UID is enough to find a local copy.
dbooth: Pack system?
erich: Main engine for imaging system.
dbooth: Any harm in having also the prov:derivedFrom ?
detlef: No harm, but could be confusing.
erich: It would expose details of the original system that might not want to be exposed.
… I'm fine w leaving it as an option on my own converter.
AGREED: Use SOP instance UID
IRI stems
w3c/
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.
… 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?
dbooth: I suggest the HCLS github space.
ACTION: Gaurav to look at where to store the scala script
gaurav: Also created a ticket for IRI stem lookup code being out of date.
FHIR RDF examples
jim: I opened 3 PRs on the HAPI core repo.
https://
jim: I think there were other issues I was going to address.. I'll look.
… I also opened an issue a out xsd:anyURI strings that have pipe symbols. Jena doesn't complain about them.
… HAPI FHIR code says "Illegal URI". It has a regex.
… Jena doesn't complain, but only because it's not parsing any URIs.
… In w3c/
dbooth: We need ericP for further discussion.
DICOM issue 144
erich: Want to look more at 144 and check w our radiology people.
DICOM issue 151
erich: Suggest we use w3id URI until we get an official DICOM URI
dbooth: There might be a danger of establishing a w3id if an official DICOM URI is later issued.
dbooth: Suggest waiting until a common URI is really needed
ADJOURNED