FHIR Chat · docs / Issue #196 Clarify the update action type · cds hooks/github

Stream: cds hooks/github

Topic: docs / Issue #196 Clarify the update action type


view this post on Zulip Github Notifications (Apr 16 2018 at 17:29):

kpshek opened Issue #196

I do not think there is enough clarity around the update action type. For instance, when a CDS Service wants to suggestion the user add an additional attribute to a resource, should the resource be the complete FHIR resource (with the additional attribute) or just the single additional attribute?

The same questions can be asked when attributes about the FHIR resource need to be modified or removed entirely.

view this post on Zulip Github Notifications (Apr 16 2018 at 17:29):

kpshek labeled Issue #196

view this post on Zulip Github Notifications (Apr 19 2018 at 00:31):

AlexTatiyants commented on Issue #196

Not requiring a complete resource for updates makes a lot of sense to me. For more complex resources (like orders), it's unlikely that the CDS service will have all of the details necessary to fully update the resource properly. The EMR is in the best position to "merge" changes proposed by the CDS service with the existing resource.

view this post on Zulip Github Notifications (Jun 13 2018 at 15:53):

kpshek milestoned Issue #196

view this post on Zulip Github Notifications (Jun 13 2018 at 15:54):

kpshek unlabeled Issue #196

view this post on Zulip Github Notifications (Dec 12 2018 at 16:24):

kpshek assigned Issue #196

view this post on Zulip Github Notifications (Dec 12 2018 at 16:25):

isaacvetter commented on Issue #196

From discussion with @kpshek , @brynrhodes , @brettmarquard -

When FHIR PUTs or POSTs a resource, the client provides the entire resource. We should remain consistent with FHIR.
The consuming system could compare and only update the things that are different (and perhaps should as part of their concurrency checking).
When the CDS client provides an update, it should provide the entire resource.

view this post on Zulip Github Notifications (Dec 12 2018 at 16:32):

kpshek commented on Issue #196

In addition to what @isaacvetter said, we can evaluate a FHIR PATCH action in a future version of the specification.

view this post on Zulip Github Notifications (Dec 12 2018 at 16:34):

kpshek closed Issue #196


Last updated: Apr 12 2022 at 19:14 UTC