FHIR-RDF questions of interest regarding JSON-LD @context & the FHIR Prov Resource

Here are two questions of interest regarding FHIR-RDF stemming from our
UMich + CAMH Toronto project team.
Thanks,
- Allen Flynn, Adeel Ansari, Avanti Paturkur, Marisa Conte


QUESTION 1

Context:  This question arose while creating examples of FHIR-RDF
ServiceRequest, FHIR-RDF Library, and FHIR-RDF Observation resources.

With respect to JSON-LD, is it advisable OR NOT, and why so, to form
an @context clause that points to multiple different pages with
relevant term definitions in the overall FHIR online WWW ecosystem?  Here's
an example of what we've been doing in an @context clause to have triples
relating terms with their definitions, definitions which are found at
various URI/URLs:

{
  "@context": {
    "fhir": "http://hl7.org/fhir/",
    "fhirSRD":"http://hl7.org/fhir/servicerequest-definitions.html#
<http://hl7.org/fhir/servicerequest-definitions.html>",
    "fhirDTP" : "http://hl7.org/fhir/datatypes.html#
<http://hl7.org/fhir/datatypes.html>",
    "fhirPROV": "https://hl7.org/fhir/r4/provenance.html#",
    "xmlSM" : "http://www.w3.org/2001/XMLSchema#
<http://www.w3.org/2001/XMLSchema>"
  },


QUESTION 2:

Context:  This question arose as we began working with the FHIR Provenance
resource as a way of representing and serializing provenance information
about computations that are done to generate additional patient data (e.g.,
computation of a risk score)

Regarding the (seemingly new) FHIR page describing a "Provenance Resource",
what are the pros and cons of having a FHIR resource modeled directly after
the PROV-O ontology?  Put another way, in a linked data world, when is it
advisable to serialize data in RDF schema that exist (PROV-O) rather than
create new schema (FHIR Provenance Resource) that are based on RDF schema
that exist?

SEE:
1)   https://www.hl7.org/fhir/provenance.html
2).  https://www.w3.org/TR/prov-o/



ReplyReply allForward