This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "SDWG Process"

From HL7Wiki
Jump to navigation Jump to search
 
Line 1: Line 1:
 
Return to [[Structured Documents TC|SDWG]] page.
 
Return to [[Structured Documents TC|SDWG]] page.
  
Ballot steps
+
===Ballot Steps===
 +
(for Unballoted DSTU Updates See below)
  
 
* Scope Statement [new for new project, revise existing when taking DSTU to normative]
 
* Scope Statement [new for new project, revise existing when taking DSTU to normative]
Line 31: Line 32:
 
* Update "revised package" to "pre-publication package" based on feedback;
 
* Update "revised package" to "pre-publication package" based on feedback;
 
* SDWG request for publication (vs. move to reballot);
 
* SDWG request for publication (vs. move to reballot);
 +
** Send request for publication to TSC;
 +
** Send "pre-publication package" to HQ;
 +
* TSC approval;
 +
* HQ creates "final" publication draft;
 +
* Verify publication;
 +
 +
===Unballoted DSTU Update Steps===
 +
* Reference: [http://gforge.hl7.org/gf/download/docmanfileversion/7482/10824/Guidance-to-Work-Groups-on-DSTU-Updates20130819.docx TSC Unballoted DSTU Update document]
 +
* Identify appropriate Scope Statement [new for new project, revised if existing scope doesn't cover scope of update, or use existing unmodified PSS if appropriate]
 +
** Committee approval (draft is posted to SDWG >= 3 days before the vote)
 +
** Steering division approval
 +
** TSC approval
 +
 +
* ... develop update content ...
 +
 +
* SDWG approves moving forward with unballoted DSTU update
 +
* SDWG determines which review process to use from the following:
 +
** Informal wiki comment process (1-2 week comment period)
 +
*** Setup wiki page to gather comments
 +
*** Send "draft package" (aka tracked change version) privately to SDWG co-chairs.
 +
*** SDWG co-chair posts posts the "draft package" to the "Documents" section of the main HL7 SDWG website as a "members" only document.
 +
*** Announce wiki comment period open for draft document with links to draft document package and link to wiki comment page;
 +
** Project Services peer review process (1-2 week peer review process)
 +
*** Send "draft package" (aka tracked change version) privately to SDWG co-chairs.
 +
*** SDWG co-chair posts posts the "draft package" to the "Documents" section of the main HL7 SDWG website as a "members" only document.
 +
*** Announce peer review period open for draft document with link to draft document package and including peer review comment spreadsheet with instructions on submitting spreadsheet to co-chairs.
 +
** Draft for Comment ballot
 +
*** Follow the '''Ballot Step''' process above
 +
 +
* ... comment or peer review period ...
 +
* ... consolidate comments ...
 +
* ... comment reconciliation ...
 +
** ... post comment reconciliation spreadsheet to SDWG list ...
 +
 +
* SDWG votes to approve comment reconciliation spreadsheet;
 +
* Comment reconciliation spreadsheet posted to SDWG WG documents page;
 +
* Revise specification per comment reconciliation agreements;
 +
* Send "revised package" (aka tracked change version) privately to SDWG co-chairs.
 +
* SDWG co-chair posts posts the "revised package" to the "Documents" section of the main HL7 SDWG website as a "members" only document.
 +
* Post notification that "revised package" (aka tracked change version) is available along with link to package to SDWG list;
 +
* SDWG approval;
 +
** preconditions: due diligence with comments; "revised package" posted >= 3d;
 +
* Update "revised package" to "pre-publication package" based on feedback;
 +
* SDWG request for publication (vs. move to ballot);
 
** Send request for publication to TSC;
 
** Send request for publication to TSC;
 
** Send "pre-publication package" to HQ;
 
** Send "pre-publication package" to HQ;

Latest revision as of 16:57, 16 January 2014

Return to SDWG page.

Ballot Steps

(for Unballoted DSTU Updates See below)

  • Scope Statement [new for new project, revise existing when taking DSTU to normative]
    • Committee approval (draft is posted to SDWG >= 3 days before the vote)
    • Steering division approval
    • TSC approval
  • ... develop ballot ...
  • NIB approved by SDWG and submitted to HQ
  • SDWG approves going to ballot (committee vote, based on meeting quality criteria)
    • A draft meeting the quality criteria is posted to SDWG >= 3 days before the vote
  • ... ballot ...
  • ... consolidate comments ...
  • ... ballot reconciliation ...
    • ... post reconciliation spreadsheet to SDWG list ...
  • SDWG votes to approve ballot reconciliation spreadsheet;
  • Ballot reconciliation spreadsheet posted to ballot site;
  • Seek withdrawal of negatives via ballot site;
  • Revise specification per reconciliation agreements;
  • Send "revised package" (aka tracked change version) privately to SDWG co-chairs.
  • SDWG co-chair posts posts the "revised package" to the "Documents" section of the main HL7 SDWG website as a "members" only document.
  • Post notification that "revised package" (aka tracked change version) is available along with link to package to SDWG list;
  • SDWG approval;
    • preconditions: due diligence with negatives; "revised package" posted >= 3d;
  • Update "revised package" to "pre-publication package" based on feedback;
  • SDWG request for publication (vs. move to reballot);
    • Send request for publication to TSC;
    • Send "pre-publication package" to HQ;
  • TSC approval;
  • HQ creates "final" publication draft;
  • Verify publication;

Unballoted DSTU Update Steps

  • Reference: TSC Unballoted DSTU Update document
  • Identify appropriate Scope Statement [new for new project, revised if existing scope doesn't cover scope of update, or use existing unmodified PSS if appropriate]
    • Committee approval (draft is posted to SDWG >= 3 days before the vote)
    • Steering division approval
    • TSC approval
  • ... develop update content ...
  • SDWG approves moving forward with unballoted DSTU update
  • SDWG determines which review process to use from the following:
    • Informal wiki comment process (1-2 week comment period)
      • Setup wiki page to gather comments
      • Send "draft package" (aka tracked change version) privately to SDWG co-chairs.
      • SDWG co-chair posts posts the "draft package" to the "Documents" section of the main HL7 SDWG website as a "members" only document.
      • Announce wiki comment period open for draft document with links to draft document package and link to wiki comment page;
    • Project Services peer review process (1-2 week peer review process)
      • Send "draft package" (aka tracked change version) privately to SDWG co-chairs.
      • SDWG co-chair posts posts the "draft package" to the "Documents" section of the main HL7 SDWG website as a "members" only document.
      • Announce peer review period open for draft document with link to draft document package and including peer review comment spreadsheet with instructions on submitting spreadsheet to co-chairs.
    • Draft for Comment ballot
      • Follow the Ballot Step process above
  • ... comment or peer review period ...
  • ... consolidate comments ...
  • ... comment reconciliation ...
    • ... post comment reconciliation spreadsheet to SDWG list ...
  • SDWG votes to approve comment reconciliation spreadsheet;
  • Comment reconciliation spreadsheet posted to SDWG WG documents page;
  • Revise specification per comment reconciliation agreements;
  • Send "revised package" (aka tracked change version) privately to SDWG co-chairs.
  • SDWG co-chair posts posts the "revised package" to the "Documents" section of the main HL7 SDWG website as a "members" only document.
  • Post notification that "revised package" (aka tracked change version) is available along with link to package to SDWG list;
  • SDWG approval;
    • preconditions: due diligence with comments; "revised package" posted >= 3d;
  • Update "revised package" to "pre-publication package" based on feedback;
  • SDWG request for publication (vs. move to ballot);
    • Send request for publication to TSC;
    • Send "pre-publication package" to HQ;
  • TSC approval;
  • HQ creates "final" publication draft;
  • Verify publication;