FHIR Chat · Clarification on versioned vs versioned-update · implementers

Stream: implementers

Topic: Clarification on versioned vs versioned-update


view this post on Zulip Lee Surprenant (Oct 27 2021 at 11:59):

https://www.hl7.org/fhir/http.html#versions lists 3 possible values for CapabilityStatement.rest.resource.versioning.

Unfortunately, I'm not sure that I understand the description of versioned-update.

Versioning and meta.version is supported, and version aware updates are used - Version ID must be correct for updates (server) or will be specified (If-match header) for updates (client)

We have a server that supports version-aware updates (via the If-Match header).
However, if that is not supplied then we do not check Resource.meta.versionId ... we will always update that to whatever the proper versionId will be (similar to how we ignore Resource.id on a POST).

Is that versioned or versioned-update?
I guess specifically my question is what does the spec mean by

version aware updates are used - Version ID must be correct for updates (server)

view this post on Zulip Lee Surprenant (Oct 27 2021 at 12:01):

should it just say "supports version-aware updates (server)" instead?

view this post on Zulip Lloyd McKenzie (Oct 27 2021 at 13:25):

@Grahame Grieve

view this post on Zulip Grahame Grieve (Oct 28 2021 at 02:44):

I think the intent is that you would say versioned-update but we might need to finesse the definition a little?

view this post on Zulip Lee Surprenant (Oct 28 2021 at 12:05):

thanks grahame, I'll set it to versioned-update on our server and open a low-priority JIRA ticket for clarifying the language

view this post on Zulip Lee Surprenant (Oct 28 2021 at 12:13):

opened FHIR#34193


Last updated: Apr 12 2022 at 19:14 UTC