Meeting minutes
Introductions
David Booth: Working w RDF and applying it to healthcare for several years. Started the FHIR/RDF effort a few years ago w Harold and others
Harold Solbrig: Soon-to-be retired asst prof at Johns Hopkins Univ. Worked on various FHIR/RDF projects.
Brad: SureScripts, AI expert ssystems 30 years, implemented our own RDF model of FHIR.
Darrell: Green Room tech, working w startups in Health tech, work w FHIR. Help companies integrate w EHRs and med devices. Worked w ont in the 1990s. Int in how we move this into the mainstream. -- integrate FHIR into knowledge graph world, and int in JSON-LD. int in SOLID.
Emily: Asst Prof, UNC Chapel Hill, EHR data, started in rel data world, but wrote dissertation on how FHIR/RDF could be used as common data across institutions.
Eric: Long-time RDF geek and HCLS group. Did the first mapping of FHIR to RDF with Josh Mandel. Also works on the SOLID project.
Gaurav: Sem web technologist at rennaisance computer institute. Emily's talking about working w FHIR/RDF.
Gerhard Kober: Austria, EHR records, doing PhD related to FHIR/RDF.
Gopi: Marquette Dental School, Wisconsin, worked on Yosemite Project for quite a while.
Jim Balhoff: Work w Gaurav at UNC. Background in bio, now working w bio ont, OBO Foundaries. OWL reasoning to bio data. Trying to apply ShEx to Gene Ontology annotations. Gaurav and I also working w Harold on cancer data.
Sajjad Sein: Google Healthcare, transforming initiatives, CDA to FHIR. Did work on ont mediation. https://
Sivaram: Previously active in HCLS. Physician, in sem web field 15+ years. Worked w David at Cleveland Clinic. Since then working on different disease areas at NIH. Consulting for 8-9 years, knowledge eng. Worked w OBO Foundary ont. Worked on Mayo project w Harold converting HL7 v3 data into RDF.
… Houston.
FHIR/RDF Goals and Status
Eric: SOLID is using standards without having to invent our own approach. Focus on patient control of their own data.
… Using HAPI FHIR server.
(slide 6)
harold: FHIR RDF provides linkage within the FHIR itself, object of one observation becomes the subject of another. One challenge after putting it into FHIR RDF is how to separate them back out again into FHIR resources. Ont let us start to reason about what's in the database.
… Ont allow bridging from SNOMED to NCI. Can also get into wikidata.
(slide 7)
harold: Aggregated phenopackets datawith other data.
(slide 9)
harold: Can we define JSON-LD rules to map FHIR JSON to RDF? The JSON-LD @context says how to map it.
… The @context is decoupled, and you can use different @contexts for different use cases.
sajjad: On slide 9, Is JSON-LD a data transformation language? Harold: Yes.
… No namespaces on the left, but they exist on the right. When we transform FHIR to RDF, is it specifically FHIR RDF?
harold: The example on slide 9 is misleading, because it isn't a FHIR example. Just showing JSON-LD mapping idea. But we have a full mapping into the FHIR namespace.
… FHIR/RDF says what is asserted in the FHIR record.
(slide 11)
harold: Project connected SNOMED CT and other ont w FHIR data and used a reasoner to draw interesting conclusions.
harold: fhir.ttl is an ont of FHIR, and gives you URIs for all nodes in a FHIR resource.
(slide 13)
harold: TermInfo problem. How to get from a code in one system to a code in another?
… We've been able to determine all the facts we know about something, then select what we want.
… JSON-LD is round-trippable: We can generate FHIR/RDF from other RDF.
sajjad: JSON-LD is instance data to instance to instance data. What about structure definitions? Schema info, like on slide 11? How did these classes come into existence?
harold: Current mapping is from structure defs to RDF triples. Now working on mapping structure defs.
(slide 17)
harold: FHIR server implementers were willing to implement FHIR/RDF if demand were demonstrated. JSON-LD makes the implementation task much easier.
… Right now all of the target nodes are bnodes, but that makes it harder to use in the common cases.
FHIR/RDF group wiki
harold: Suggest add a link to tutorial.
sajjad: Maybe walk through a small resource in FHIR, and show the JSON-LD and the resulting FHIR/RDF.
harold: Examples also exist in the FHIR spec.
http://
Action: Harold to prepare a FHIR JSON-LD example
eric: I can show a FHIR example with SOLID.
Action: David to add link to FHIR JSON-LD playground.
Action: David to add links to tutorials
<dbooth> s/Sajjad, Sajjad/Sajjad/
<dbooth> s|s/Sajjad, Sajjad/Sajjad/||