Stream: implementers
Topic: Reference with version
Ardon Toonstra (Mar 13 2020 at 12:14):
Just a double check: could the Reference.reference include the target reference resource's version so the receiving system can perform a vread?
So for example, would the below reference be valid?
<reference value="Task/234234/_history/3be72cfc-267a-450e-bb74-275b9785298e"/>
Grahame Grieve (Mar 13 2020 at 12:37):
yes though it's not widely supported well
Paul Church (Mar 13 2020 at 16:06):
related to that, does it make sense for _include or Patient $everything to follow versioned refs and retrieve the specified version?
Rik Smithies (Mar 13 2020 at 16:58):
A specification I am working on has considered this.
You want to be able to pull a set of resources that link to a historic version of a resource. Medicinal products definitions are made of several resources and we want to be able to get the whole set as it was at a given point.
To allow it to work we wondered about storing the resources in the first place using references with specific history versions. Otherwise when you follow a reference you always get the newest version of the pointed at resource, not the one as it was at the time.
Clinical data doesn't tend to update, or if it does you want the latest. But definitional things tend to go through versions, which are all useful.
Paul Church (Mar 13 2020 at 17:02):
That case could also use canonical references, I think?
Rik Smithies (Mar 13 2020 at 17:10):
you mean by appending a "|version" to the url? That would work if the pieces were all versioned with numbers. Presumably the resolver needs to look into the resource.version attribute. Not sure if any servers can do that. And that would need the version attribute to exist and be populated of course. We don't have numbers on the parts currently, they just all come in together.
Last updated: Apr 12 2022 at 19:14 UTC
