SNOMED International Release Management

Page tree

Versions Compared

Old Version 7

changes.mady.by.user Andrew Atkinson

Saved on

compared with

New Version 8

changes.mady.by.user Andrew Atkinson

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date of Initial Handover meeting: 14th 13th October 2022

Date of Final Handover meeting: 18th October 2022

Attendees


Page properties


Handover Status

Status
subtletrue
colourBlue
titleINITIAL Handover COMPLETE



Agenda


 

Items to be discussed

Actions

1

Prerelease Content Management Activities:

  1. Inactivate the root concept synonym referencing previous release, and add synonym to reference current release.
  2. Update copyright date on synonym (January releases only)
  3. Generate + Validate SEP Refsets
  4. Generate + Validate Lateralizable Refset


  1. MBR - done manually in the front end -DONE - 5144464019 SNOMED Clinical Terms version: 20221031 [R] (October 2022 Release)
  2. MBR - not required as only required in January release.
  3. Process has generated the data -  pre close report 13 October 2022

    1. https://docs.google.com/spreadsheets/d/1fxc7AK4waR1oiwZFrbTzhaEc5Qsbw9kOillmNvSIUE0/edit#gid=1

  4. Process has generated the data - pre close report 13 October 2022

    1. https://docs.google.com/spreadsheets/d/1fxc7AK4waR1oiwZFrbTzhaEc5Qsbw9kOillmNvSIUE0/edit#gid=2

2

Discussion of existing Known Issues from the previous Release

  1. Traceability failures 
    Jira
    serverIHTSDO JIRA
    serverIdb202d822-d767-33be-b234-fec5accd5d8c
    keyINFRA-8675
     July 2022 release issues logged here
    Jira
    serverIHTSDO JIRA
    serverIdb202d822-d767-33be-b234-fec5accd5d8c
    keyINFRA-9209
     confirmed by Michael as false positives.
  2. Traceability issues for October 2022 release logged here
    Jira
    serverIHTSDO JIRA
    serverIdb202d822-d767-33be-b234-fec5accd5d8c
    keyINFRA-9628
     all false positives confirmed by Michael.


3

Content Validation 

  1. Instead of usual manual Content validation, we now just need confirmation that all Projects had automated validation run against them, and were clean before promotion.
  2. New Issues identified by the community from the previous Monthly Release.
    1. Decision on whether to fix the issues:
      1. VERY QUICKLY in time for this upcoming release?
      2. In good time for the next monthly release?


  1. Content Release Lead confirms to Release Manager that all Projects had automated validation run against them, and all issues identified were resolved before promotion - DONE
  2. MRCM: Checked with Yong - NO CHANGES for October 2022 release.
  3. Ref set description changes October 2022 release - no new descriptions seen in descriptions file https://docs.google.com/spreadsheets/d/1hUopEa3LjJbJSyGy07lZGqGeKAT9zUtsx3qYKR2_lzM/edit#gid=0


4Mapping schedule

April 2022:

  • Donna ran new report that Rick created to double check no invalid mappings, all clean now
  • Mark/Donna to complete mapping on Monday

June 2022:

  • Rick to confirm whether or not the difference in the Deleted record count (in the new automated mapping stats report) is anything to be concerned about ....

July 2022:

  • ICD-0 - very few changes expected
  • ICD-10 - expecting 1000+ changes due to large number of intentional inactivations this cycle

August 2022:

  • ICD-0 - very few changes expected
  • ICD-10 - expecting 320+ changes due to large number of intentional inactivations this cycle
  • Upload of mapping content to 2x branches planned for Friday 12th this cycle...

September 2022:

  • ICD-0 - no changes expected
  • ICD-10 - expecting 300 ish changes due to large number of intentional inactivations this cycle
  • No expected issues this cycle...

October 2022:

  • ICD-0 - 1 new record + 2 inactivations expected
  • ICD-10 - expecting 478 ish changes (plus tonight's drip feed) due to large number of intentional inactivations this cycle
  • No expected issues this cycle...



***** NOTE:  Make sure that we keep an eye on the upgrade to ICD-0 version 3.2, as it will need to happen at some point in 2023 *****

5Brief 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.



6DevOps resource confirmed
7Versioning and Change Freeze

Plan is to follow the new processes as now defined:

AAT walked through and agreed new process with DevOps already, so unless there are any further questions/issues??

HIGH LEVEL KEY MILESTONES:

  • 14/10/22 - All content and mapping complete and signed off by close of play
  • 18/10/22  - AAT to build PreProduction (unversioned) and sign off before 15:00 on 18th, otherwise decision made to postpone versioning
  • 19/10/22 -  Versioning to begin first thing + related issues to be completed and resolved by 17:00
8Stats Report

Reports run via the reporting platform:

9Risks
  1. NOVEMBER 2022 - Need to ensure that Rick + Terance have resolved the issues from Sept release, whereby the username/password for the auto-jobs were switched around and so failed.  Ensure that this is resolved before 00:01 14th October when next jobs set to run
  2. CLOSE DECEMBER 22 IF NO FURTHER ISSUES...Intermittent problems with the 12am Daily Build have been caught by backup 2am Daily Build run so far, BUT could in theory run into problems with the mapping drip feed that also runs at 2am.  However, this should be mopped up by the Friday drip feed, so shouldn't be a problem - agreed auto-job setup for 2:20am on Friday morning each cycle to catch any stragglers as well...
    1. Another minor issue though with this is moving the auto-job to 3am results in a clash with the drip feed - Rick has submitted a ticket (INFRA-9419) to discuss potential long term options for automation in order to circumvent this issue
    2. STILL AN ISSUE??? NO THIS IS MITIGATED BY THE MOVE OF THE AUTO JOB TO 02:20 on FRIDAY - Can THEREFORE remove from October onwards
10AOB