Meeting minutes
Concept IRI
Gaurav: No major updates. Up to 9 of 15 votes for UP 377, adding IRI stems to MeSH
https://
gaurav: out next week
ShEX
ericp: Did some GPT experiments for composing queries given ShEX
… ChatGPT
… Llama 3.1 didn't do well.
erich: If you run it through Ollama, the context window is tiny.
ericP: I trimmed the shex first, to only the part needed.
… But I was able to do some experiments.
erich: I'm using Ollama
… I'm testing memory usage. I'm only running 8Billion parameter one.
… Not surprised if ChatGPT does better, w a bigger model.
… I
… I'll see if we can give you access to our bigger machine.
DICOM
erich: Wanted to try adapting code, instead of RDF lists, to geoparql well-known text string. But didn't find sample data.
… Looking in my data for sample.
ACTION: Detlef to see if he has some sample data having polygons
erich: Talking w Dave Beckett could help us close out some issues.
… They used OWL. Would be good to write OWL for what we're doing
ericP: If you're maintaining the current plan, that would obviate my attempt at a meta issue.
ACTION: Erich Bremer to create issue for writing OWL, and also SHACL. Starting to learn ShEx.
DBooth: What's going to be our process for tying our DICOM RDF work back to FHIR RDF work?
ericp: Might demo that we can move data from one form to another.
dbooth: That would demo the value of RDF in a DICOM context
erich: I'll make my code public.
dbooth: How would DICOM RDF be connected to FHIR RDF data?
erich: FHIR RDF would reference the DICOM?
ericP: ImagingStudy resource?
erich: They're grouped and connected back to a parent Study
detlef: You define a Study, make a request to DICOm, and modality starts a series.
… That needs StudyInstance ID. That should be the link.
ericp: Would FHIR also address into these DICOM things, so you're not pointing at the whole blob?
detlef: I don't think that can be done w the old approach. Could only be done w DICOM RDF approach.
ericp: Wondering if StudyInstance can point to something more specific in a DICOM report.
erich: There is stuff in DICOM that allows those annotations.
… When spatial indexing is turned on, in Virtuoso, the geosparql well-known text takes advantage of it.
… It's the same argument for pushing everything into XSD types, so SPARQL store s can use them. Doing the same thing for spatial data.
ericP: Would be fun to add that to QLever
… If you want to point to a piece of a giant scan, to you abstract that portionfirst?
detlef: You can specify delineations
… And you can do a structured report, diagnosis in a radiology image. Making statements about it.
… These DICOM structures have their own modalities and their own instances.
ericP: Is that a good use case for us to chase?
detlef: I think so.
dbooth: Need to make sure we have the ability to do that kind of referencing in FHIR?
ACTION: ericP to check whether appropriate referencing portions of a DICOM document
erich: It might change depending on the modality
… You have xray type, CAT scan type, etc. Then within that you now have pathology, whole site imaging. They're single layer images. As this normalized in RDF, how does it play together?
ericP: And if there's a tension between putting stuff in FHIR vs DICOM
… DICOM folks have been pushing for adding pathology info. Annotations are more numerous w whole site images.
… David Clooney has a paper on having both TIF and DICOM together.
… But the tooling to look at whole slide imaging is immature.
… TCI group is very int in DICOM and RDF.
… Cancer Imaging Warehouse -- lots of dde-iDed data available to use.
… I'm nudging them toward RDF, to deal with disparate datasets.
… DICOM meets continuously, and releases a new version every quarter.
DICOM sequence tags
erich: I think we can use a blank node stand off to an object.
ACTION: Erich to add example to issue 146
ACTION: Detlef to supply example that cross references
ADJOURNED