15:03:23 RRSAgent has joined #hcls 15:03:23 logging to https://www.w3.org/2018/10/30-hcls-irc 15:03:28 rrsagent, make logs public 15:03:36 Meeting: FHIR/RDF 15:03:40 Chair: David Booth 15:05:32 hsolbrig has joined #hcls 15:48:17 Topic: FHIR/RDF 15:49:14 harold: Big thing right now is graph DBs and knowledge graphs. Conjecture: RDF could be viewed as the bridge between FHIR and these knowledge graphs. 15:50:50 david: FHIR/RDF is top hit when searching google for fhir knowledge graph: https://www.google.com/search?q=fhir+knowledge+graph&sa=Search&sitesearch= 15:53:08 https://findwise.com/blog/tinker-knowledge-graphs/ 15:55:03 harold: We need to become more knowledgeable about [other] graph DBs. 15:56:18 eric: What do people want to do with these knowledge graphs? 15:57:04 ... They strip down the data to the bits they care about. E.g., clinical encounters at the same facility, therefore MRSA probably followed this vector. Not a wholesale import to KB. 15:58:05 harold: They're using it for exactly what the Linked Data community does. 15:59:51 ... At the moment they're using OBO ontologies, as unifying factor. They're either creating new OBO resources or mapping existing OBO resources to the new facts coming in. 16:01:19 ... They're looking at can this be transformed to disease ontology, LOINC code. They want to map it into low/high measures that disease ont has (hypo/hyper). 16:04:53 david: FHIR/RDF is already stepping up a level from bare RDF -- a domain-specific language based on RDF. 16:06:05 harold: FHIR/RDF is a first exmaple of RDF representation is available from the beginning. 16:06:40 david: Action items? 16:07:09 harold: 1. Possible Yosemite presentation. 2. positioning of RDF vs knowledge graphs. 16:07:47 s/positioning/relationship/