Stream: implementers
Topic: Notfications for tags/security labels
Theo Stolker (Sep 15 2017 at 19:45):
Hi there,
We are implementing FHIR Subscriptions, which work well to notify subscribers of created/updated/deleted resources.
Today we got the question how it would be possible to subscribe for changes to tags and security labels.
Communicating that as an update on the resource would be possible, but not logical given that the resource itself hasn't changed, at least, its version hasn't changed.
Has anyone tried implementing subscriptions / notfications for change to tags and security labels?
Thanks,
Theo
Grahame Grieve (Sep 15 2017 at 23:59):
Hi Theo. In principle, you subscribe to changes to the resource. So anything that changes the content (including, through the rest interface, any update, patch, delete, or create) will trigger a subscription event
Grahame Grieve (Sep 16 2017 at 00:00):
it's possible to use $meta-add and $meta-delete to change just the meta. We have not defined whether or not that triggers subscriptio
Theo Stolker (Sep 18 2017 at 13:02):
Hi @Grahame Grieve,
Thanks for your response/ You said: "it's possible to use $meta-add and $meta-delete to change just the meta. We have not defined whether or not that triggers subscription".
That is exactly the type of clarification that I am looking for. The particular issue being here that the resource doesn't get a new version when only the meta fields change.
How can we resolve this to recommended behavior?
Thanks,
Theo
Theo Stolker (Sep 18 2017 at 13:02):
(deleted)
John Moehrke (Sep 18 2017 at 13:25):
Theo, We have not defined this because it is going to be something that different regions and deployments will want to handle in different ways. Some really want changes to meta to change version, some don't want it to change version, and others only want the version to not change for specific tag changes. I would be interested in your use-case so that I can make sure the security WG addresses it (I am co-chair).
Last updated: Apr 12 2022 at 19:14 UTC
