Stream: implementers
Topic: Resource versioning for subscription status
Da Huang (Nov 27 2018 at 15:42):
For regular resources, resource versioning (https://www.hl7.org/fhir/http.html#versioning) is useful since it allows related systems to track the correct version of information, and to keep integrity in clinical records. However, for subscription resource, since the subscription status (https://www.hl7.org/fhir/subscription-definitions.html#Subscription.status) could flip between “active” and “error” thousands times, does it make sense to store all the versions? Do you think it’s reasonable to ignore the subscription resource versions caused by status change only?
Grahame Grieve (Nov 29 2018 at 02:17):
it depends whether you have storage constraints, and what your requirements are
Last updated: Apr 12 2022 at 19:14 UTC
