Date | Responsibility | Deliverables |
---|---|---|
| Authoring begins for the July 2020 International Edition editing cycle. | |
| Content team to deliver final MRCM change requests to EPS Team for action | |
| EPS Team delivers MRCM changes to content team for review - Content Team to complete this by | |
| Content team to deliver final reviewed MRCM changes plus any feedback to EPS Team | |
| EPS Team to make any necessary changes (based on feedback from the authors) and verify with Content Team by | |
| 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. | |
| Final MRMC refsets delivered by EPS Team to Release Management team for review | |
| SNOMED International Tech Team to now:
????? NO LONGER REQUIRED due to MRCM Tool???????? | |
| NO FURTHER CRS REQUESTS ACCEPTED | |
|
| |
|
| |
| Andrew Atkinson | Pre close of release full validation of the initial exported content |
| Content team review, rebase and finalise all content | |
| Content team promote to MAIN final content for all projects to be released in the current editing cycle (weekend contingency) | |
| 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 - 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 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 2020 | |
| Andrew Atkinson | Full validation of the initial exported content |
|
| |
|
| |
|
| |
Handover of Release Notes to technical team Release manager | ||
|
| |
| PLANNED Alpha Release date Restart the mapping Drip Feed - this can actually be done earlier than the final Alpha if required, as the only pre-requisite is to complete the ICD-0/ICD-10 testing in the Alpha build. This is simply to provide confidence that there will not likely be map changes during the Alpha/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 Alpha build to switch the drip feed back on.
| |
| PLANNED Alpha feedback deadline | |
| PLANNED BETA Release date | |
| PLANNED BETA feedback deadline | |
| Member Release date | |
| Public Release date |