Date | Responsibility | Deliverables |
---|---|---|
| Authoring begins for the July 2021 International Edition editing cycle. | |
| Jane Millar | Cut off for external collaboration partner CRS Requests (IHE, HL7, etc) - set date of 15th March + 15th September each cycle for clarity. |
| NO FURTHER MRCM CHANGES ACCEPTED - everyone has agreed this, with the caveat that any critical changes can be reviewed by all of us in order to analyse impact vs business case and allow a change if absolutely necessary. The final state of all MRCM resets will then automatically be included in both authoring validation + release. | |
| NO FURTHER CRS REQUESTS ACCEPTED https://www.snomed.org/snomed-ct/Use-SNOMED-CT/change-or-add | |
|
| |
|
| |
Andrew Atkinson | Pre-close of release full validation of the initial exported content. | |
| Content team review, rebase and finalise all content for July 2021 release. | |
| Content team promote to MAIN final content for all projects for the July 2021 release. | |
| Content Release Lead to request (via Infra ticket) formal lock down of all Projects (i.e. no promotions allowed), except for the Internal QA Project (INTQA) - which needs to remain open until from CONTENT CUTOFF DATE in order to allow Content Release Lead to promote all final QA fixes before handover. | |
| Final content review (2 days). Request vet extension report. Request QI project content changes report. Review of new observable entity and evaluation procedure concepts for conflicts with the LOINC agreement. | |
|
| |
| Planned Initial Handover meeting. | |
|
| |
| termServer branching and Release versioning - Technical Team Release tasks - July 2021 | |
| Andrew Atkinson | Full validation of the initial exported content. |
|
| |
|
| |
|
| |
|
| |
Handover of Release Notes to technical team Release manager (note: recheck final figures for concepts changes/ additions etc before member release and public release to take into account changes made after close of editing. | ||
| PLANNED BETA Release date. Restart the mapping Drip Feed - this can actually be done earlier than the final Beta if required, as the only pre-requisite is to complete the ICD-0/ICD-10 testing in the Beta build. This is simply to provide confidence that there will not likely be map changes during the Beta stage, which could in theory create re-work for the teams. This risk should be balanced against the growing backlog of map changes, and a decision made whether to use an early Beta build to switch the drip feed back on. | |
| PLANNED BETA feedback deadline. Last day for addition of COVID-19 related vaccine concepts (critical content only). | |
| Member Release date. | |
| PRODUCTION Public Release date. |