Stream: Ballot-QA
Topic: STU Update Process
Corey Spears (Apr 20 2021 at 14:39):
Not sure where this question should go, so I will try here first.
Can someone point me to the FHIR IG STU Update process? I have an IG that has no errors and warnings, the Jira Artifacts have been updated, the Sponsoring and Co-sponsoring WGs have approved in scope and to carry on with the process. I have a link to for a publication request, but was wondering if there was any more in the process, particularly around review and approvals.
Melva Peters (Apr 20 2021 at 15:30):
Here is a link to the information on the HL7 Essentials page: https://confluence.hl7.org/download/attachments/86972322/Guidance-to-Work-Groups-on-DSTU-Updates20130819.docx?version=2&modificationDate=1609966428642&api=v2
Melva Peters (Apr 20 2021 at 15:31):
Work group and co-sponsoring WGs have to agree to the scope of the STU Update. The Peer Review has to be announced via the Co-chair list, Zulip, and to stakeholders and be open for a minimum of 2 weeks. All comments must be captured in Jira.
Melva Peters (Apr 20 2021 at 15:32):
After the peer review cycle closes, comments are reviewed and triaged via the same process as for a ballot. Changes are made as agreed and a publication request is approved by the WG the FHIR Management Group and the TSC. The STU update will be published as a dot release.
Corey Spears (Apr 20 2021 at 18:32):
Thanks @Melva Peters, Everything is in place and the FM is ready to go to open the Peer Review on Friday on 4/23. Does FMG need to review and approve before the peer review is open for comment?
Melva Peters (Apr 20 2021 at 21:11):
No requirement for that at this point...that will happen with the publication request. You'll need to get the notifications sent out to the co-chair list, Zulip and stakeholders.
Last updated: Apr 12 2022 at 19:14 UTC
