Stream: implementers
Topic: Version Specific Resference Resolution in Transaction-Bundle
Pooja Adhikari (Jan 24 2020 at 22:54):
The fhir spec says " Version-specific references should remain as version-specific references after the references have been updated". Can I get more clarification on this? Does this mean when a resource is updated, then all the version specific reference should update their version to the updated version of that resource?
Lloyd McKenzie (Jan 25 2020 at 00:53):
It means that after you execute the create or update for the resource and know what the id and version is on the new system, you change the reference to point to that specific version
Pooja Adhikari (Jan 25 2020 at 05:22):
Spec also specifies the transaction processing rules.
Process any DELETE interactions
Process any POST interactions
Process any PUT or PATCH interaction.
I am trying to address the following situation. I have a resource within a bundle that needs to be created and has a versioned reference that is pointing to a resource that needs to be updated. Here, the resource that needs to created cannot obtain a updated version of referenced resource within a transaction due to the processing rules stated above, as POST is always executing before PUT. Are these two rules contradicting with each other?
Lloyd McKenzie (Jan 25 2020 at 05:35):
Nope. You're going to have to do the create, then the update, then fix the reference.
Last updated: Apr 12 2022 at 19:14 UTC
