Construction_Transition Phase Criteria
Developed by Group 1 of the 2014 CTP cohort. Version imported: 2.0 with minor updates given new tooling. Source document: CTP_Construction Transition Phase Completion Criteria2.0.docx
1 Introduction
This document outlines the criteria for completion of the construction phase of content development/improvement projects for SNOMED CT, according to the IHTSDO Content Development Process.
To enter the final, transition or publication, phase the following criteria must be completed. Doing so ensures that the output from the project does not cause adverse impact to the publication process. Upon entering the transition phase the content must be in a state regarded as complete. All that remains is for the standard publication process to be followed. The criteria for evaluating the transition phase and closure the project is out of the scope for this document.
2 Construction/Transition criteria for assessing completion of project
Subject | Criteria for assessing completion |
Editorial guide | The editorial guide is updated to properly reflect the editorial decisions made as part of the project. |
Release note | A draft wording for inclusion in the release note in the SNOMED distribution is completed. |
Quality assurance | The changes must have passed routine content quality assurance rules for SNOMED CT available at TBA Any agreed exceptions should be noted in the Construction Log Book. |
Proposed project specific quality assurance metrics and technical QA rules in elaboration have been measured and achieved. Any unachievable targets need to push the project back to elaboration phase for revision of solution. | |
Visual inspection of expected results after changes specified in elaboration have been performed and checked by authoring team. | |
Risk control | The risks identified in the elaboration phase have been managed appropriately. The new potential impact beyond the main scope of the project has been assessed. |
Conformance to proposed solution | Recommended design and solution proposed in elaboration has been followed in construction phase. |
| The completeness of changes have been checked against the scope of project. The changes should have included the existing content in SNOMED CT, the pending requests in SIRS, and the tracker item. |
The completed changes to concepts/descriptions/relationships in scope specified in elaboration have been indicated in the Construction Log Book.
Where the solution requires modification or is rejected or deferred, then the rationale for this needs to be documented in the Construction Log Book and the project returned to the relevant phase (inception or elaboration) of development. If only simple modification or rejection is required the recording of the changes and rationale may enable the construction phase to continue, though consultation with the document author should occur. | |
Stakeholder engagement | Stakeholder engagement has been sought for determining acceptance that can be different for production and technical preview. The additional and unmet requirements should be updated in elaboration document, or inception if that is deemed necessary. |
Resource assessment | The project has been completed within the specified and deadline. If the resource specified in elaboration was not sufficient for the project, the adjustment of resource and project plan has been made and documented. |
Maintenance plan | The maintenance plan for current and future content in scope of the project has been documented in the Construction Log Book. |
3 Construction/Transition approval process – Outline
The artifact in the content tracker should be assigned to the editor responsible for editing after elaboration phase document has been signed off. The Project Lifecycle Phase should be updated to “Construction phase”. The tracker can be changed to “Transition phase” when content is ready for release and the listed criteria have been met.
The solution described in the elaboration document should be followed as closely as possible, developing content in the scope described by the document. A Construction Log Book should be kept noting progress and, particularly, noting any deviations from the solution as described in the elaboration document. If there is uncertainty about the interpretation of the elaboration document, the document author should be consulted. Significant deviations from the elaboration document must generate a new elaboration or inception cycle. Deviations indicating that a step back to elaboration or inception phase is necessary include for example:
The quality criteria targets are not met,
A principle of the elaboration solution is not applicable,
Resources specified in elaboration are not sufficient for applying solution,
Shifting requirements, e.g. as stated by stakeholders during construction or during alpha testing.
When the content has been edited and/or new content is created, the criteria above are checked and noted in the logbook. These criteria apply to both “fast track” and full inception/elaboration processes.
Appendix A Construction Log Book
JIRA item number | IHTSDO-xxxx |
Log date | YYYYMMDD - the date this log is created |
Completed changes | Percentage of the most recent elaboration or count of total (excludes modification to solution). Either percentage or count should be used according to the elaboration document, but not a mix. For example: Elaboration criteria = 70% Change 1 - name, brief description of changes, complete, 100% Change 2 - name, brief description of changes, complete, 70% |
Modification to solution | Percentage of the total changes or count with reason and description of modification. For example: Modification name, 10% Description of modification and rationale |
Declined changes | Percentage of the total changes or count with justification |
Deferred construction tasks | deferred tasks for future project/s If it is needed, new tracker item(s) should be raised and provide the links to the track items in this section. |
Stakeholder engagement note | The recommendation for update elaboration document for additional and unmet requirements |
Resource assessment note | Describe the resource requirement if the estimate resource is not sufficient for the project |
Maintenance plan |
|
- Anticipated requests | number of new concept requests |
| foreseeable change requests |
- Risk mitigation strategies | risk mitigation strategies has been followed or additional actions have been taken to minimise the identified risks under “Risks of addressing the problem” or new risks identified during construction phase. |
- Resource | resource requirements for maintenance |
References
CTP Project Inception Completion Criteria CTP Project Inception - completion criteria.docx
CTP Project Elaboration Completion Criteria 20120314 CTP Project Elaboration - completion criteria.doc
Copyright © 2025, SNOMED International