SNOMED International Release Management

Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »


Date of Preliminary Handover meeting: 

Date of Initial Handover meeting: 18 November 2020

Attendees

Date of Final Handover meeting: 25 November 2020

Attendees

Apologies

Handover Status


Agenda

 

Items to be discussed

Actions

1

Prerelease Content Management Activities:

  1. Verify that all namespace concepts (in the namespace registry) have been added
  2. Inactivate the root concept synonym referencing previous release, and add synonym to reference current release.
  3. Update copyright date on synonym (January releases only; N/A to July 2014)
  4. Send updated laterality indicator spreadsheet to technical team to support qualifier generation.

  5. Get SE and SP refset files from Yong

  6. Content Team to deliver 4x MRCM refset files to Release Manager (just needs to confirm they're completed, downloaded + tested, AAT will then pull them out of the termServer during release builds via the termServer Export)

 

2

Discussion of existing Known Issues from the previous Release

ISRS-806 - Getting issue details... STATUS

ISRS-809 - Getting issue details... STATUS

ISRS-688 - Getting issue details... STATUS

ISRS-807 - Getting issue details... STATUS


 

3

Content Team Support availability - Confirm which members of the content team will remain on stand-by until clean database milestone is achieved after release build file QA and post-release assertions are validated.

Maria will all be around to support wherever needed Donna and Yong on leave at present (8 Nov 2019)

 

4

Early visibility of Release Notes


Andrew Atkinson has created the template to update on Confluence: SNOMED CT January 2021 International Edition - SNOMED International Release notes - content team to update with relevant figures for January 2020 content.....

ACTION: Maria Braithwaite and Donna Morgan will kindly aim to get them to Andrew Atkinson by 15 November 2019

ACTION: Monica Harry and Paul Amos to review and approve once complete

 

5

Discussion of existing Known Issues from the previous Release

 

  1. ISRS-366 - Long term case significance fixes work has commenced for this, it will be ongoing over subsequent releases.
  2. ISRS-409- Specific case significance issue - I have asked JCA for an update, no immediate action, requires wider consultation. 
  3. ISRS-575 - no action, being resolved over time with template based editing as part of QI project.
  4. ISRS-574 - requires change to RVF report to remove this assertion altogether.
  5. ISRS-582checked no author changes required.
  6. INFRA-4197 - 147,000+ issues, needs change to assertion to allow self grouping, no editing changes needed.
  7. ISRS-562 - Finding with explicit context| concepts using |Associated Procedure| attribute - editing issue resolved.
  8. ISRS-563 - 8 concepts using |Surgical approach| that are not subtypes of |surgical procedure| - editing issue resolved.
6Brief run through of the known issues already identified by the content team during the QA batch process, to ensure that technical team are aware of them, and can either resolve them in time for the release, or confirm as known issues.

Mapping: 8 Nov 2019 Donna is on leave today she sends this update:

Technical QA has started. SNOMED has been reloaded and 1 concept has been identified as needing a map in the ICD-10 project - Drip feed must not have picked it up. The concept  32941000119104 Ingestion of toxic substance (disorder) has been mapped and WCI can re commence the release work. GMDN and ICD-O have been completed and WCI notified. Both projects will need to pass technical QA but nothing to report so far.



7Versioning and Change Freeze

KAI has run some manual checks for missing descriptions - no issues found.

8Stats Report

MBR has been using the Daily Build QA report for stats and has the information needed for release notes, also given access to https://docs.google.com/spreadsheets/d/1hgDBPG5TjarvGpRJD6LBUN1sHLizhWWchzWDXXjpPRk/edit#gid=3 by Peter for further information that will be useful for release notes.


9Risks
  1. Kai - After versioning need to take care when rebasing some projects that still have content on them as never done before on this terminology server and may find strange behaviour - mitigation: Kai will do the rebasing after we have versioned. This will be done before editing reopens.
10





  • No labels