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

Difference between revisions of "Category:Change Requests for PHER Standards"

From HL7Wiki
Jump to navigation Jump to search
m
m (add email SD list for SDWG products)
Line 29: Line 29:
 
**[[PHER Change Request Template]] (Make sure when copying the contents that the first line is <nowiki>"{{PHER Open Change Requests}}"</nowiki>, which will automatically make your page show up in the Table of Contents below).
 
**[[PHER Change Request Template]] (Make sure when copying the contents that the first line is <nowiki>"{{PHER Open Change Requests}}"</nowiki>, which will automatically make your page show up in the Table of Contents below).
 
*Send an e-mail to the [[mailto:pher@lists.hl7.org| PHER list]] alerting the work group so that agenda and discussion time can be arranged.
 
*Send an e-mail to the [[mailto:pher@lists.hl7.org| PHER list]] alerting the work group so that agenda and discussion time can be arranged.
 +
**For change requests to SDWG/PHER prodcuts, please also copy the SDWG list at strucdoc@lists.hl7.org
  
 
'''Resolution process:'''
 
'''Resolution process:'''
 
*Change requests will be reviewed in committee. Those that are accepted will be part of the assigned release of the relevant specification when it is ultimately released for formal HL7 balloting.  
 
*Change requests will be reviewed in committee. Those that are accepted will be part of the assigned release of the relevant specification when it is ultimately released for formal HL7 balloting.  
 
*Once a committee decision has been reached on a change request, its status will change from Open to Closed.
 
*Once a committee decision has been reached on a change request, its status will change from Open to Closed.

Revision as of 19:45, 12 April 2012

Return to PHER page

PHER Standards Change Requests are proposals that will or have been formally submitted to PHER for consideration for incorporation into standards supported by the PHER work group. Each of these change requests will be reviewed by work group. Those that have been accepted will be part of a subsequent release of the relevant specification when it is ultimately released for formal HL7 balloting.

Note: The PHER change request process is not intended to replace existing HL7 change management processes. For instance the existing HL7 DSTU comment process will be used to manage requests for changes to PHER DSTU standards.

PHER Standards Accepting Change Requests


SDWG/PHER Standards Accepting Change Requests

Change Request Sub-Lists

Process

A change request may be submitted by anyone.

To raise a change request:

  • Create a new wiki page. (You can create a page from scratch, simply by entering the name of the new page in the search-box on left, which results in a page with the text There is no page titled "your new page name". Select your new page name and the new page will be created).
  • Copy the contents of one of the following templates into your new page:
    • PHER Change Request Template (Make sure when copying the contents that the first line is "{{PHER Open Change Requests}}", which will automatically make your page show up in the Table of Contents below).
  • Send an e-mail to the [PHER list] alerting the work group so that agenda and discussion time can be arranged.
    • For change requests to SDWG/PHER prodcuts, please also copy the SDWG list at strucdoc@lists.hl7.org

Resolution process:

  • Change requests will be reviewed in committee. Those that are accepted will be part of the assigned release of the relevant specification when it is ultimately released for formal HL7 balloting.
  • Once a committee decision has been reached on a change request, its status will change from Open to Closed.