Meeting minutes
Intros
detlef: Work for Sohard, Germany.
… Developed semantic DICOM access system, converting DICOM to RDF. Goal is to integrate clinical data into huge KG and use AI to get new knowledge from it.
… We have proprietary solution right now. Already using FHIR RDF. Very handy.
dbooth: Which version of FHIR RDF.
detlef: Not sure.
Concept IRIs
gaurav: Waiting for content check. Not sure what it means. If no movement soon, will poke someone.
… Planned to figure out next steps of IRI stems, -- next week.
Turtle generation
jim: Getting set up to figure out Tim Prudhomme's last status. Test one example at a time, rather than all.
DICOM
josh: Interested in bridging from large imaging with DICOM.
erich: Want casting of DICOM data to RDF, and also integrate it to FHIR.
… Want a complete picture. Various projects on DICOM RDF, but nothing official. Want it official.
eric: Need to document overlap between FHJIR resoures and DICOM metadata. That would inform use cases and what to standardize.
erich: From design standpoint, would be good to have it complete.
dbooth: Could either map DICOM to FHIR, then get FHIR RDF for free; or map DICOM directly to RDF.
erich: If it isn't a complete mapping to FHIR, then it might not be enough.
eric: If we map directly to RDF, we'll still need to determine FHIR overlap.
… But if we map from DICOM to FHIR it won't be complete.
dbooth: But could be complete, because FHIR has extensibility.
eric: but wouldn't want to use the extensions -- too hard.
detlef: Patient overlap definitely.
erich: I emailed the FHIR imaging group, but haven't heard back yet.
dbooth: Might need to join one of their calls, to get more attention.
rob: Two calls in March, 12 and 19, 11am ET. 19th call is canceled.
eric: Is there a sympathetic ear in that group? Want to determine the overlap of DICOM and FHIR
… Probably they've already document the overlap somewhere.
https://
ACTION: Erich to join the March 12 call.
Issue review
ACTION: DBooth to figure out if this was promised for the R01 grant w3c/
ADJOURNED