W3C

- DRAFT -

FHIR/RDF

11 Sep 2018

Attendees

Present
Regrets
Chair
David Booth
Scribe
dbooth

Contents


e

FHIR/RDF

harold: FHIR is coming up on R4. Need to find out what they'll think if we start mucking w RDF again.

david: Grahame wanted to see evidence of FHIR/RDF use. We have a tutorial almost ready fo released (from Harold's webinar), and Harold is using it and Joao wanted to use it.

harold: We should contact Grahame directly about FHIR/RDF. We'll be doing a presentation at SWAT.
... Most interesting thing is NCATS translator group. We've created a FHIR researouce (proposed it) for exchanging aggregated statistical data. We'll be presenting it to the group. They want to tie it into OBO, Monarch and Disease Ont that they're doing. Want to use ICD-10 and LOINC codes. RDF will make that a whole lot easier.
... That will give us some traction. Need to tell Grahame to hold off, because the promise of RDF is opening doors.
... HL7 meeting end of Sept is in Baltimore.

david: Should check with Michael Van Der Zel also, about his continued interest.

harold: Can we get an active team involved again?

<scribe> ACTION: Harold to contact Grahame about re-vitalizing FHIR/RDF

harold: JH looking at Trinetix, put together by big pharma. Looks like I2B2 with better GUI.
... I want to pursue fhir.schema.org . Grahame said I could host it on his site.
... I think that could have a lot of future.

<scribe> ACTION: David to find Marc T's email for Harold

harold: Might use JSON-LD for warehousing FHIR.
... The FHIR reference tag now has a type field to indicate the target type. So we don't have to parse the URL to figure it out!

FHIR/RDF home page

http://build.fhir.org/rdf.html

david: RDF is not mentioned on the home page, though JSON and XML are: http://build.fhir.org/

Harold: what to do about Tony's FHIR ontology? http://w3c.github.io/hcls-fhir-rdf/spec/ontology.html

david: Need to mark it as obsolete, and point to http://build.fhir.org/fhir.ttl

<scribe> ACTION: David to make FHIR downloads page point to http://build.fhir.org/fhir.ttl

http://build.fhir.org/downloads.html

david: also, what about the formal spec on the W3C site? http://w3c.github.io/hcls-fhir-rdf/spec/
... Would the FHIR shex file be enough? http://build.fhir.org/fhir.schema.shex.zip

harold: The shex is not enough. But should we document it in the W3C space or HL7 space?

david: A big benefit of putting it in the HL7 space is it could be part of the FHIR build process.
... But it increases the chances of it being pruned.

Next steps

Harold: I'm out next week.

<scribe> ACTION: Harold to review the two links on FHIR RDF spec (from minutes)

ADJOURNED

Summary of Action Items

[NEW] ACTION: David to find Marc T's email for Harold
[NEW] ACTION: David to make FHIR downloads page point to http://build.fhir.org/fhir.ttl
[NEW] ACTION: Harold to contact Grahame about re-vitalizing FHIR/RDF
[NEW] ACTION: Harold to review the two links on FHIR RDF spec (from minutes)
 

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2018/09/11 15:59:26 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s|T-minus one minute: https://hangouts.google.com/call/al34mdviyvgahgs2r7z45idmom||
Succeeded: s/Trianetix/Trinetix/

WARNING: No "Present: ... " found!
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy
        <amy> Present+

No ScribeNick specified.  Guessing ScribeNick: dbooth
Inferring Scribes: dbooth

WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: david harold

WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)


[End of scribe.perl diagnostic output]