Difference between revisions of "Category:Standards Governance Board Precepts"

From HL7Wiki
Jump to navigation Jump to search
Line 43: Line 43:
 
*'''Precepts - Tooling:'''
 
*'''Precepts - Tooling:'''
 
**In order to ensure sustainable tooling, the organization needs a reasonable and rational vetting process on any new tool that becomes a dependency of the efficient and effective generation of standards. '''[http://wiki.hl7.org/index.php?title=2018-02-02_SGB_WGM_Agenda Minutes]'''
 
**In order to ensure sustainable tooling, the organization needs a reasonable and rational vetting process on any new tool that becomes a dependency of the efficient and effective generation of standards. '''[http://wiki.hl7.org/index.php?title=2018-02-02_SGB_WGM_Agenda Minutes]'''
 +
 +
*'''Precepts - Substantive Change:'''
 +
**Each product family shall define what substantive change means for the product family artifacts conformant to the parent definition of substantive change.

Revision as of 14:54, 5 February 2019


  • Precept: Standards related GOM materials should be backed up by formal precepts.
    • Given that there has been substantial work in the development of the materials in the GOM, we'll accept the GOM as the set of rules that we operate under; SGB will formally document the precepts to support those rules as the need arises. Minutes
  • Precepts - Documentation:
    • WGs must post minutes documenting committee decisions to initiate standards development projects and decisions to ballot, reconcile and publish specifications. Minutes
      • The SGB recommends to the TSC that the way the precept is measured is through recording the WG's decision in published minutes and providing either the date of the minutes or a link to the published minutes in documents such as a PSS or publication request. The NIB may use a check box to assert that the WG decision has been recorded in minutes and those minutes have or will be published. Minutes
  • Precepts - Separation of Concerns:
    • WGs should be organized where practical to separate the work items with respect to concerns. Minutes
    • An artifact’s scope should be determined to support separation of concerns. Minutes
    • Where separation of concerns have been implemented in a product family, an individual should not be a cochair of more than one of the appropriate governance, management, or methodology groups. Exceptions can be granted on a case-by-case basis by the TSC. Minutes
  • Precepts - Balloting:
    • Any artifact which must have its own ballot level must be balloted with the scope of content clearly designated.Minutes
    • In order to submit a ballot, the submitter must have a documented understanding of the roles and responsibilities of managing and reconciling a ballot. Effective date: TBD Minutes
    • Ballot management tooling must by default support best practices and rules Minutes
    • A ballot package must clearly identify the Individual Ballots within the package which will be progressed or not as a standard. Minutes
  • Precept - Handling Multiple Level Ballots:
    • This precept supports HL7 ballots where content within the balloted specification is to be assessed at different ballot levels, including normative, STU, informative and comment (draft). Under ANSI requirements, a change in scope for a normative ballot is a substantive change; therefore, all artifacts within a normative ballot pass and fail together.
      • Ballot materials and the included elements must be clearly identified as to whether they are included in the ballot pool, and if so, the ballot level of each.
      • One or more ballot pools may be established for each ballot level as needed. Each of the ballot pools may refer to common material under ballot. The ballot level must be clearly indicated on each element of the specification. Minutes
  • Precepts - Quality:
    • For each family, methodology determines what the quality critera are, and the management groups establish a plan to ensure the criteria are applied. Minutes
  • Precepts - Product Family Management Groups:
    • Scope of Product Family MGs:
      • Product Family Management Groups are responsible for the management of specifications which are wholly contained within or are assigned to the product family;
      • They may develop IGs or guidance on Cross-Paradigm technologies which are used within the Product Family; and
      • They may represent the needs and concerns of the work groups within the Product Family to the Work Group which is responsible for the Cross Paradigm Specification. Minutes
  • Precepts - Tooling:
    • In order to ensure sustainable tooling, the organization needs a reasonable and rational vetting process on any new tool that becomes a dependency of the efficient and effective generation of standards. Minutes
  • Precepts - Substantive Change:
    • Each product family shall define what substantive change means for the product family artifacts conformant to the parent definition of substantive change.

This category currently contains no pages or media.