Page tree
Skip to end of metadata
Go to start of metadata
DateResponsibilityDeliverables

 

Authoring begins for the July 2019 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 MillarCut 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:

  1. add UUIDs to the MRCM google sheet for all new MRCM rules, and
  2. update the MRCM in the SCA to ensure remaining new cycle content validated against the latest version.

 

NO FURTHER CRS REQUESTS ACCEPTED (Single content request cut off)

 

  • NO FURTHER DRUGS BATCH LOADS TO termServer
  • NO FURTHER PROMOTION FOR PROJECTS THAT HAVE LARGE SCALE CHANGES - For example this would include large scale changes to foundational hierarchies such as anatomy or substances, or changes that are likely to have impact to reports such as the pattern report (e.g. redundant relationships) or MRCM (e.g. cardinality issues in legacy content where edits have been made to that content without resolving the pre-existing cardinality issue).

 

  • Last day for authors to launch new tasks in SCA - no more new tasks launched after this date, +
  • Early Visibility Handover meeting (if complexity of Release requires)

 

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 - BEWARE OF BANK HOLIDAY ON 6th May 2019!)

Review of new observable entity and evaluation procedure concepts for conflicts with the LOINC agreement

 

  • CONTENT CUTOFF DATE (10:00 UTC), +
  • Handover of content to technical team Release manager
  • Content Release Lead to request (via Infra ticket) the maintenance screen to be raised in Production, to prevent further updates to International content

 

Planned Initial Handover meeting

 

  • Mapping Team to notify WCI mapping/review ready for QA
  • ****** Simultaneously to cloning ICD-0/ICD-10, please ask WCI to clone GMDN data across to Release server as well, to prevent GMDN issues in derivative cycle
  • QA of mapping (Mapping Team + WCI)

 

Transition from Stated Relationships to OWL refsets +

Validation of the new complete OWL refsets

 

termServer branching and Release versioning

 

Andrew AtkinsonFull validation of the initial exported content, including the new OWL refsets

 

  • Content Team to confirm that Lateralizable refset is complete in Production refset tool (Release manager to then action the refset tool release to get the delta files), +
  • Content Team to deliver the SEP refsets (x2) to Release manager

 

  • Mapping/Review/Technical QA complete
  • Authors and mappers - Preparation of release notes content 

 

  • MAPPING CUTOFF DATE (12:00 UTC), +

  • Handover of ICD-0 + ICD-10 maps to technical team Release manager (Andrew Atkinson)

 

  • Planned Final Handover meeting, +

  • PLANNED Early Alpha Release date
  • Provisional date for Content authoring starts for next editing cycle

Handover of Release Notes to technical team Release manager

 

PLANNED Alpha Release date

Restart validation in SCA (no longer relevant - new process should allow validation to re-start immediately when Content authoring starts for next editing cycle)

 

PLANNED Alpha feedback deadline

 

PLANNED BETA Release date

 

PLANNED BETA feedback deadline

 

Member Release date

 

Public Release date

































































  • No labels