FHIR Chat · Version-specific operations · implementers

Stream: implementers

Topic: Version-specific operations


view this post on Zulip Lloyd McKenzie (Aug 01 2017 at 22:51):

Is it legitimate to invoke an operation that can be invoked on an instance on a specific version? E.g. is this legal: [base]/ValueSet/[id]/_version/[version]$expand ?

view this post on Zulip Lloyd McKenzie (Aug 01 2017 at 22:52):

And for that matter, is this legal? [base]/ValueSet/[id]|[busVersion]$expand

view this post on Zulip Cesar Farell (Aug 02 2017 at 18:25):

Is it legitimate to invoke an operation that can be invoked on an instance on a specific version? E.g. is this legal: [base]/ValueSet/[id]/_version/[version]$expand ?

Consider that the $expand operation has an optional date input parameter for filtering to which version of the ValueSet the operation should be applied. Having both a date and a version together would likely produce an overdetermined and incoherent request: what if the requested version was not effective at the specified date?

view this post on Zulip Lloyd McKenzie (Aug 02 2017 at 20:13):

date isn't the way we identify value set versions, though it could incidentally determine the version, it would also determine code system versions

view this post on Zulip Lloyd McKenzie (Aug 02 2017 at 20:13):

(and versions of referenced value sets)

view this post on Zulip Grahame Grieve (Aug 02 2017 at 20:58):

at present only the metadata operations are described as being able to apply to past versions

view this post on Zulip Grahame Grieve (Aug 02 2017 at 20:59):

and it's not legal to apply the operation to the canonical URL directly. You need to resolve the canonical URL direct, and then do the operation


Last updated: Apr 12 2022 at 19:14 UTC