Difference between revisions of "Category:OO Change Requests"
| Line 32: | Line 32: | ||
*Copy the contents of one of the following templates into your new page: | *Copy the contents of one of the following templates into your new page: | ||
**[[OO Change Request Template]] (Make sure when copying the contents that the first line is <nowiki>"{{OO Open Change Requests}}"</nowiki>, which will automatically make your page show up in the Table of Contents below). | **[[OO Change Request Template]] (Make sure when copying the contents that the first line is <nowiki>"{{OO 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:ord@lists.hl7.org|OO list]] alerting the work group so that agenda and discussion time can be arranged. | + | *Send an e-mail to the [[mailto:ord@lists.hl7.org| OO list]] alerting the work group so that agenda and discussion time can be arranged. |
'''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 shange request, its status will change from Open to Closed. | *Once a committee decision has been reached on a shange request, its status will change from Open to Closed. | ||
Revision as of 16:39, 8 May 2009
ContentsOO Change RequestsChange Requests are proposals that will or have been formally submitted to OO for consideration for incorporation into normative V3 standards supported by the OO 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 OO 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 OO DSTU standards. The same applies to HL7 2.x change requests, use the existing 2.x change request process. |
O&O Wiki Content
|
OO Standards Accepting Change Requests
- Lab CMETs Release 10 (as part of HL7 CMET Release 10)
- Specimen CMETs Release 10 (as part of HL7 CMET Release 10)
- Lab Result Release 2
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:
- OO Change Request Template (Make sure when copying the contents that the first line is "{{OO Open Change Requests}}", which will automatically make your page show up in the Table of Contents below).
- Send an e-mail to the [OO list] alerting the work group so that agenda and discussion time can be arranged.
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 shange request, its status will change from Open to Closed.
This category currently contains no pages or media.
