– DRAFT –
FHIR RDF

Issue 170 handle semantics of hash ids

w3c/hcls-fhir-rdf#170

jim: SHould contained resources be identified the same way as Bundled resources? Our proposed resolution for issue 170 (contained) differs from how Bundles are handled currently.

tim: https://build.fhir.org/references.html#contained

Contained resources share the same internal id resolution space as the parent resource (for id attributes, see Narrative references).

When resolving references, references are resolved by looking through the 'container' resource - the one that contains the other resources. Since there are no nested contained resources, there is only one container resource.

tim: Fragment-only URL References to contained resources are never resolved outside the container resource. Specifically, resolution stops at the elements Bundle.entry.resource and Parameters.parameter.resource, but not at DomainResource.contained. To reference a contained resource in a different entry within a Parameters or Bundle (or anywhere else), the reference must include the containing resource. E.g. Observation/123#pat.

ericp: We need to make those absolute URIs

jim: For better robustness we have decided to output the hash ID appended to the parent URI, e.g.: <http://hl7.org/fhir/PlanDefinition/KDN5#1111>. Also, the identifiers for contained do not follow exactly the same rules as the bundle examples (https://build.fhir.org/references.html#contained). If no parent URI (blank node?) just output as relative hash URI.

see issue: w3c/hcls-fhir-rdf#170

ADJOURNED