SNOMED International Release Management

Page tree

Versions Compared

Old Version 1

changes.mady.by.user Andrew Atkinson

Saved on

compared with

New Version Current

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: 13 11 May 2023

Date of Final Handover meeting: 17 16 May 2023

Attendees


Page properties


Handover Status

Final Handover Complete



Agenda

  1. logged here https://jira.ihtsdotools.org/browse/INFRA-10848 and here https://jira.ihtsdotools.org/browse/INFRA-10902
    1. Maria confirmed not significant enough need to include these in the Known Issues in the Release Notes
INFRA-10756
  2. NEW and CHANGED MRCM report - no changes for
April
  1. May 2023 release confirmed with Yong https://docs.google.com/spreadsheets/d/
1sl4tXNnyvg6iRn8Nyi7j6nLNW4HAb7NrfPL1s9TpCrc
  1. 1c5UdyD_dLsbc_eH5kE3kwkiW5GXkcShr2Mr8sL7VRcI/edit#gid=0
  2. Ref set description changes
April
  1. May 2023 release - none found in descriptions file
https://docs
  1. .
google.com/spreadsheets/d/1Ki57tAoA-w4oMh3WNliAWt1DXfsQgiO0vbQnaDUjAd4/edit#gid=0


 

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
  5. Content Team to confirm to Release Manager that 4x MRCM refset files are complete and ready to be released (they are then extracted from the termServer during release builds via the termServer Export)
  1. MBR - root synonym - 5223416010 5244022012 - SNOMED Clinical Terms version: 20230430 20230531 [R] (April May 2023 Release) https://authoring.ihtsdotools.org/#/tasks/task/DAILYPROMO/DAILYPROMO-43144568/edit
  2. MBR - root copyright date - not required
  3. SEP - https://docs.google.com/spreadsheets/d/1s6S_tnpC2ZpWoOLxnTfCKOeEQRiAD2moMnumn3xLpBY1OqJ7lzsWJone4Ie7W9x5YhpriTD1qV3sQ9YaT9uzxJ4/edit#gid=1
  4. Laterality - https://docs.google.com/spreadsheets/d/1s6S_tnpC2ZpWoOLxnTfCKOeEQRiAD2moMnumn3xLpBY1OqJ7lzsWJone4Ie7W9x5YhpriTD1qV3sQ9YaT9uzxJ4/edit#gid=2
2

Discussion of existing Known Issues from the previous Release

  1. Traceability issues for January 2023 release - NONE.
  2. Traceability issues for February 2023 release - https://jira.ihtsdotools.org/browse/FRI-576 2 failures both confirmed as false positives by Michael.
  3. Traceability March 2023 release - NONE on MAIN (2 failures found on project confirmed false positives not seen in daily build after promotion https://jira.ihtsdotools.org/browse/INFRA-10533)
  4. Traceability for April 2023 release - 8 failures on main checked and false positives, ticket is here
    Jira
    serverIHTSDO JIRA
    serverIdb202d822-d767-33be-b234-fec5accd5d8c
    keyINFRA-10712
  5. Traceability for May 2023 release - NONE


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?
Content Release Lead confirms to Release Manager that all Projects had automated validation run against them, and all issues identified were resolved before promotion - failures
  1. Failures for lateralizable reference set all false positives
Jira
serverIHTSDO JIRA
serverIdb202d822-d767-33be-b234-fec5accd5d8c
key
4Mapping schedule

January 2023:

  • ICD-0 - 1 new records + 0 inactivations expected
  • ICD-10 - expecting 550 ish changes (plus tonight's drip feed) due to large number of intentional inactivations this cycle
  • No expected issues this cycle...
    • Confirmed in final numbers!

February 2023:

  • ICD-0 - 1 new records + 0 inactivations expected
  • ICD-10 - expecting 500 ish changes (plus tonight's drip feed) due to large number of intentional inactivations this cycle
  • No expected issues this cycle...
    • Confirmed in final numbers!

March 2023:

  • ICD-0 - 2 new records + 0 inactivations expected
  • ICD-10 - expecting 315 ish changes (plus tonight's drip feed) due to large number of intentional inactivations this cycle
  • No expected issues this cycle...
    • Confirmed in final numbers!

April 2023:

  • ICD-0 - 6 new records + 2 inactivations expected
    • + for the specific fixes for this cycle we're expecting 7 records that should have been inactivated in March but were not, but should be now
    • + Rick is going to tweak the Mapping Dashboard to give Donna more visibility of the final expected map figures (EXCLUDING "no target" maps which she would normally include in her figures but which we wouldn't see coming out of the Delta files)
  • ICD-10 - expecting 537 ish changes (plus tonight's drip feed) due to large number of intentional inactivations this cycle
  • No expected issues this cycle...
    • Confirmed in final numbers!

May 2023:

  • ICD-0 - 3 new records + 0 inactivations expected
    • + Rick is going to tweak the Mapping Dashboard to give Donna more visibility of the final expected map figures (EXCLUDING "no target" maps which she would normally include in her figures but which we wouldn't see coming out of the Delta files)
  • ICD-10 - expecting 150 ish changes (plus tonight's drip feed) due to large number of intentional inactivations this cycle
  • No expected issues this cycle...
    • Confirmed in final numbers!

***** NOTE:  Make sure that we keep an eye on the upgrade to ICD-0 version 3.2/3.4/4.0, as it "MAY" happen at some point in 2023 (though unlikely now) *****

  • Hi @Andrew @WCI support This is the comment I was referring to so lets say any deprecation or new map to 3.2 is "unlikely" ICD-O-3.2 is out of numbers. So, multiple histologies that are different entities are being lumped together at the moment.
  • ICD-O-4 should address this many-to-one lumping and the comment version should be available by the end of the year.
  • The Blue Book 5th edition is still in Beta, and the ICD-3.2 codes assigned to each morphology by chapter are not completely correct and subject to change.
  • We decided on our call yesterday with Jim Case's comments taken into consideration that we will focus on the map to 4 along with the histology quality work. A reverse map to 3.2 will be possible at that point and be straight forward to complete. So, we will not be spending much, if any, time on further 3.2 work
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 confirmedJoe
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:

  • 1312/0405/23 - All content and mapping complete and signed off by close of play
  • 1816/0405/23  - AAT to build PreProduction (unversioned) and sign off by the deadline, otherwise decision made to postpone versioning
  • 1917/0405/23 -  Versioning to begin first thing (START AT 08:30 IF POSSIBLE - yes Maria agreed) + related issues to be completed and resolved by 17:00
8Stats Report

Reports run via the reporting platform:

Summary Component stats for edition 14 April 12 May 2023:


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


9Risks


10AOB

Inappropriate content being included in the lateralizable body structure reference set.

Reported to us by NLM. Requires an update to the validation rules, the ticket is logged For information - there has been a P1 issue with validation in the authoring platform, this has meant that there have been no project promotions with content since 6 April 2023, the patch deployment was made today, details here

Jira
serverIHTSDO JIRA
serverIdb202d822-d767-33be-b234-fec5accd5d8c
keyFRI-641
 I had to promote a project this morning to fix a content issue and the validation ran without a problem, the daily build RVF report has also been run this morning and has completed, no issues (other than known issues) found.
VAL-334