15:45:25 <RRSAgent> RRSAgent has joined #hcls
15:45:29 <RRSAgent> logging to https://www.w3.org/2024/11/07-hcls-irc
15:45:31 <dbooth> rrsagent, make logs public
15:45:35 <dbooth> Meeting: FHIR RDF
15:45:41 <dbooth> Chair: David Booth
16:17:42 <dbooth> dbooth has joined #hcls
16:18:45 <dbooth> ... I know Larry already.
16:19:04 <dbooth> ... He's co-chair for WG23, which is AI group
16:22:23 <dbooth> detlef: What would convince them to adopt RDF?
16:23:02 <dbooth> erich: I've been hearing that end users spend a lot of time homogenizing and ETL-ing data before they can use the data.  There's an effort for common vocabs.  This is a use case for RDF.
16:23:25 <dbooth> ... You want to connect the information to clinical info.  how?   Allow the data to connect.
16:24:03 <dbooth> detlef: If you want to build out a KG you'll need a lot of converters.
16:24:15 <dbooth> ... RDF would help that.
16:24:34 <dbooth> ... In my case, linking ICD10 codes
16:25:54 <dbooth> erich: Also, when people publish anything, how do you find the value?  Look at citations.  Want to include the publication data.
16:26:14 <dbooth> ... To link it all together, there's so much effort in connecting it.
16:26:32 <dbooth> ... In RDF you can bring that data together a lot faster.
16:30:17 <dbooth> detlef: Also, their data is hierarchical, which doesn't fit well with relational.
16:30:40 <dbooth> ... And you can link directly from one doc to another.
16:31:07 <dbooth> ... RDF is much better choice than JSON, for example.
16:31:41 <dbooth> erich: Gen vast amounts of data from deep learning pipelines.  You can try to put that in JSON in MongoDB, but it's tricky to deal with at that scale.
16:32:09 <dbooth> ... Want to pull out features at this scale, and search it.  That's my argument for geosparql.
16:32:22 <dbooth> ... Good like w trying to do this w MongoDB!
16:32:43 <dbooth> ... THrowing it all in a triplestore is hard at scale.
16:32:55 <dbooth> ... YOu end up with n log n speed problem.
16:33:16 <dbooth> ... I split it apart into independently indexed files.  But RDF allows me to link it back together quickly.
16:33:26 <dbooth> ... Wouldn't try to attempt this w a relational DB.
16:33:32 <dbooth> ... I'm implementing it.
16:33:54 <dbooth> ... When DICOM added polygon features, but the left out spacial indexing.
16:34:44 <dbooth> ... A POC is not enough.  Need to handle it at scale.
16:35:09 <dbooth> ... This is why DICOM should use RDF: allows all the pieces to be brought together.
16:37:10 <dbooth> Topic: DICOM arrays
16:37:11 <dbooth> https://github.com/w3c/hcls-fhir-rdf/issues/149
16:37:49 <dbooth> erich: I think geospatial is the way to go.
16:38:15 <dbooth> ... There's "grid spacing", but no clear guidance on what the grid is
16:38:47 <dbooth> ... Sometimes the x and y spacing differs.
16:39:12 <dbooth> ... They're proposing an RDF way to specify a spacing.  I want to be sure that x and y spacing can differ.
16:39:33 <dbooth> ... E.g. 0.43 microns per pixel.
16:40:15 <dbooth> ... Still trying to figure out how to do that.
16:40:35 <dbooth> ... Virtuoso is still at geosparql 1.0, and Jena is also.
16:52:24 <dbooth> Topic: CURIEs in codes
16:52:26 <dbooth> https://github.com/w3c/hcls-fhir-rdf/issues/127
16:53:21 <dbooth> dbooth: Discussed w ITS group yesterday, and they agreed to say "don't put the prefix in the code", but pushed back on also saying "but accept the prefix if it's in there".
16:53:38 <dbooth> ... So I took out the part about "but accept the prefix if it's in there".
16:54:07 <dbooth> ... The ITS group voted to accept the amended proposal.
16:54:36 <dbooth> https://jira.hl7.org/browse/FHIR-48787
16:58:21 <dbooth> ADJOURNED
16:59:07 <dbooth> Present: EricP (last 5 minutes), Gaurav Vaidya, Erich Bremer, Detlef Grittner, David Booth
16:59:10 <TallTed> TallTed has joined #hcls
16:59:49 <dbooth> rrsagent, draft minutes
16:59:50 <RRSAgent> I have made the request to generate https://www.w3.org/2024/11/07-hcls-minutes.html dbooth