FHIR Chat · resource versions · implementers

Stream: implementers

Topic: resource versions


view this post on Zulip Jose Costa Teixeira (Jan 10 2020 at 10:10):

For those working with versions: we have /ResourceType/id123/_history/v2 to get a specific version,
but from my current perspective, the use case that is more common is not "Get me this specific version of a the record" but rather "get me the version of this record as it was on this date"

view this post on Zulip Jose Costa Teixeira (Jan 10 2020 at 10:13):

The functionality can be achieved e.g. by having the client get all versions and then find which version they want from the dates.
Is that the way to do it?
If so, is that a good idea?
If not, could we have an alternative?

view this post on Zulip Jose Costa Teixeira (Jan 10 2020 at 10:16):

I'm thinking it could be interesting to have an operation that provides whatever version was active at a given time.
something like /ResourceType/id123/$validAt?date=2019-01-19

view this post on Zulip Jose Costa Teixeira (Jan 10 2020 at 10:16):

comments?

view this post on Zulip Paul Church (Jan 10 2020 at 14:33):

Parameters to the _history operation include _at, which does what you want

view this post on Zulip Lloyd McKenzie (Jan 10 2020 at 15:55):

The specific version id is much easier for the server, so if you want to point to a known version, do it by id. If you don't know the version id, then _at is fine (though you can't use that in a reference).

view this post on Zulip Jose Costa Teixeira (Jan 10 2020 at 20:54):

Thanks. I'll test the _at in a few uses.


Last updated: Apr 12 2022 at 19:14 UTC