Stream: fmg
Topic: Process Problem
Grahame Grieve (May 09 2017 at 12:30):
We're having a problem with tasks that were re-opened for R4 after being deferred in the past. The problem is illustrated by the following advice on the wiki:
Grahame Grieve (May 09 2017 at 12:30):
Note: If an item is associated with a ballot, it cannot be re-opened once the final disposition spreadsheet has been prepared for that ballot. (If a WG isn't sure, contact the FHIR Management Group) It's always possible to raise a new tracker item, but that item should reference the original and provide some new argument for re-visiting the decision.
Items that are marked as "deferred" will automatically be re-opened after a new release of the product has been published. (Deferred is never a 'final' resolution.)
Grahame Grieve (May 09 2017 at 12:30):
these two sentences disagree with each other
Grahame Grieve (May 09 2017 at 12:31):
the correct process is far from clear
Grahame Grieve (May 09 2017 at 12:31):
can we please clarify this
Lloyd McKenzie (May 09 2017 at 13:07):
Not being able to update "deferred" items would be very problematic. We could get away with creating new trackers when re-opening other items, though enforcing this will be next to impossible. We have a full history so we can always reconstitute. So my preference is to have guidance that previous resolutions be moved into a comment so they're easily visible/discoverable, but to otherwise allow items to be re-opened/reactivated and changed.
Last updated: Apr 12 2022 at 19:14 UTC
