Justification and Objectives
To date, FHIR RDF ITS Specification has not been widely implemented or adopted. The current FHIR RDF ITS Specification was "hand crafted" and requires the development of FHIR specific software to implement. The W3C JSON LD working group is in the process of releasing a released a new Committee Draft (CD) of the JSON LD 1.1 specification, which has the potential to merge the FHIR JSON and RDF specifications and to simplify the RDF and JSON transformations.This new proposal and approach, however, re-opens some of the issues that had been addressed in the current FHIR RDF specification, includingwill allow a significant portion of the FHIR RDF specification to be represented as JSON-LD 1.1 contexts. There are still portions of the FHIR specification, however, that cannot be represented using JSON-LD. This gives us an opportunity to revisit some of the earlier decisions wrt. RDF and to take into account some of the feedback and issues that have been received with respect to usability. These decisions include:
- Extensibility – the current RDF specification makes extensibility easy and straightforward, but at the cost of making commonplace RDF/SPARQL operations difficult and non-intuitive.
- Concept URI's – the RDF specification allows concept URI's but the transformation between the FHIR Coding to the URI's is non-trivial
- List ordering – the current RDF specification requires the addition of an "index" attribute to maintain list ordering
- Node root – JSON and XML represent trees, where the "root" is the outermost element. RDF requires an additional identifier to identify the starting point within an arbitrary directed (potentially cyclic) graph
2) To start with bespoke RDF representations of FHIR to determine how the JSON-LD Framing Language, ShEx and other tools can be used to transform and valid validate the RDF as a collection of FHIR resources.
A webinar will be hosted on Tuesday, December 17 10:00 AM EEST to share further participation information about this track.
Any system that needs to consume or emit FHIR as RDF. This includes FHIR Servers, DL and NLP modules.
Role Scenario 1 Name
Goal: Transform FHIR JSON representation into the current FHIR R4 RDF target using proposed FHIR JSON-LD 1.1 contexts.
1) Create a transformation process that takes FHIR JSON, the supplied contexts and produces a "minimal" R4 output
2) Develop strategies to extend the input JSON and/or the generated RDF to produce a fully conformant R5 output.
Test scripts: https://github.com/fhircat/fhir_rdf_validator can be used to compare RDF output to expected and/or run ShEx evaluation
Security and Privacy Considerations