FHIR Chat · Version-specific references for _include, _revinclude, and $ · implementers

Stream: implementers

Topic: Version-specific references for _include, _revinclude, and $


view this post on Zulip Rick Geimer (Mar 30 2020 at 20:04):

We have a couple JIRA issues
https://jira.hl7.org/browse/FHIR-26637
https://jira.hl7.org/browse/FHIR-26638
Asking if _include, _revinclude, and $everything should follow version specific references. The spec is currently silent about this. FHIR-I would like to gather feedback on how we should clarify this in the spec.

view this post on Zulip Paul Church (Mar 30 2020 at 20:07):

As the submitter of those issues, I propose that the answer should be an explicit yes for _include and $everything.

view this post on Zulip Grahame Grieve (Mar 30 2020 at 20:09):

SHOULD not SHALL

view this post on Zulip Paul Church (Mar 30 2020 at 20:09):

_revinclude is a bit different, I don't have an example of what it might do with versioned references. I don't think many implementations are going to index version-specific references anyway.

view this post on Zulip Sean McIlvenna (Mar 30 2020 at 20:17):

I agree. It would be good to be able store multiple versions of an IG on a single FHIR server. To support this, at a minimum, we would need to be able to use _history to store multiple versions of the resources. Part of the use of _history would be having _include respect references to specific versions.

view this post on Zulip Sean McIlvenna (Mar 30 2020 at 20:23):

Also, would be good for this to also apply to _has

view this post on Zulip Sean McIlvenna (Mar 30 2020 at 20:23):

Would like to be able to search for any Observation resources that are part of a specific version of an ImplementationGuide

view this post on Zulip Paul Church (Mar 30 2020 at 20:29):

I feel like canonical refs are going to end up being a better solution for that search though, you want to search by the business version of the IG, not the version ID that is opaque and server-dependent

view this post on Zulip Michael Lawley (Mar 30 2020 at 23:04):

Support for multiple versions is a key reason for using URIs (from Resource.url) (or associated canonical with business version) to reference things rather than logical URLs that tie to the specific Resource.id. _history is similarly the wrong thing to use for managing multiple versions.


Last updated: Apr 12 2022 at 19:14 UTC