Stream: cds hooks/github
Topic: docs / Issue #452 Managing resource contention when sugge...
Github Notifications (Dec 13 2018 at 19:48):
dennispatterson opened Issue #452
FHIR manages resource contention by the inclusion of an If-Match request header on a PUT to indicate that an update should only be applied if the current version of the resource matches what that caller received when it was read. Otherwise, two "simultaneous" updates could trample one another.
When a CDS service returns a card with a suggested update to a FHIR resource, there is no concept of supplying something like an If-Match. However, if another workflow makes an update before the action is accepted, loss of data could result. Semantics/documentation need to be added for handling this scenario.
Github Notifications (Dec 13 2018 at 19:59):
dennispatterson commented on Issue #452
Note that this is referring to scenarios where the suggested update is to a persisted resource, not a scratch pad or otherwise in-memory resource that is not yet persisted.
Last updated: Apr 12 2022 at 19:14 UTC
