SNOMED International Release Management

Page tree

Versions Compared

Old Version 1

changes.mady.by.user Andrew Atkinson

Saved on

compared with

New Version 2

changes.mady.by.user Andrew Atkinson

Saved on

Key

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


Date of Preliminary Handover meeting: 

Date of Initial Handover meeting:

18

15 November

2020

2021

Attendees

Date of Final Handover meeting: 25 November 2020

Attendees

Apologies


Page properties


Handover Status

INITIAL HANDOVER COMPLETEPLANNED



Agenda

  • Verify that all namespace concepts (in the namespace registry) have been added
    • ; N/A to July 2014)
  • Send updated laterality indicator spreadsheet to technical team to support qualifier generation.
    • Get SE and SP refset files from Yong verified with Yohani by email 11 Nov 2020MBR - done done please see https://jira.ihtsdotools.org/browse/INFRA-5402
  • Yong to download Daily build and deliver by Friday 20th
  • Yong to download Daily build and deliver by Friday 20th
    • Maria confirmed all good + Yong confirmed all requests agreed for next cycle.key806 Checked before close of editing, content issue is resolved

     

    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
    1. )
    2. Generate + Validate SEP Refsets
    3. Generate + Validate Lateralizable Refset
    2. 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 - done
    1. ? please see https://jira.ihtsdotools.org/browse/INFRA-5402
    2. MBR -
    1.  January releases only
    2. Peter G. Williams to generate + Yong to also create it the old way + compare to ensure valid...
      1. ????Yong/Peter to generate and deliver by ????
    3. Peter G. Williams  to generate + Yong to also create it the old way + compare to ensure valid...
      1. ????Yong/Peter to generate Daily build and deliver by ????
    4. Yong confirmed he will try to follow the deadlines for the monthly releases - 
      1. September 2021 had some Observables changes, BUT they didn't make it in in time for the September deadline, so these will be done for the October 2021 release.
      2. ANY expected MRCM changes for the November 2021 release??
    2

    Discussion of existing Known Issues from the previous Release

    Jira
    serverIHTSDO JIRA
    serverIdb202d822-d767-33be-b234-fec5accd5d8c

    1. ISRS-
    1. 1112 -
    Jira
    serverIHTSDO JIRA
    serverIdb202d822-d767-33be-b234-fec5accd5d8c
    keyISRS-809
     - All resolved we have a validation rule in the RVF report for this now, 17 issues found and resolved, no issues in RVF report today.

    Jira
    serverIHTSDO JIRA
    serverIdb202d822-d767-33be-b234-fec5accd5d8c
    keyISRS-688
     - https://jira.ihtsdotools.org/browse/ISRS-605 relates to the US extension, the ticket we have relating to the International release is https://jira.ihtsdotools.org/browse/ISRS-575 with a failure count of 1716.
    I have checked a sample of the attached file, the issue is the same, the concepts are marked fully defined by virtue of their stated IS_A relationships which was in the past acceptable, editorial policy has subsequently changed and we now require a proximal primitive parent and the addition of attribute and value pairs. These modelling issues are being addressed by the QI project in many cases using template based editing, no changes required at present.  Can we close this down then??  Yes everyone on the call agreed to resolve the ticket and confirm that the QI project will resolve these outstanding issues over the next few cycles

    Jira
    serverIHTSDO JIRA
    serverIdb202d822-d767-33be-b234-fec5accd5d8c
    keyISRS-807
     - As discussed with the technical team, this may require changes to the existing classification service. Further investigation and evaluation are needed before we can implement the changes in production. It is not possible to make the changes for this release. The plan is to address this issue for the July 2021 release. We will update the ticket when the progress has been made.   Agreed by everyone on the call to be carried over to July 2021 as too high risk to make classifier changes now - will be planned in for next cycle.

     

    1. Have the devops processes been updated to either run before versioning, or to run against 2 packages (as per Peter's note in the ticket)?
      1. Or is Maria now running this report along with the others pre-versioning?
    2. ISRS-1120 - SEP issues - resolved now? 
    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.

    2. Feedback from Spain:

      1. 2 active descriptionshavebeenidentified as FSN but do notincludethesemantic tag in theterm:


        1. idtypeIdTerm

          590999016900000000000003001(Congenital) nipple: [small (& acquired)] or [hypoplasia]

          661545019900000000000003001Dependence: [cannabis (including marihuana)] or [hallucinogen]

      2. In thisedition210conceptshavebeendeactivatedwitheffectiveTime = 2021-10-31. In 5concepts, no correspondencewith alternative conceptsisreported in therefsetAssociation.


        1. ideffectiveTimeactiveterm

          216280052021-10-310Anesthesiaforprocedureson perineal integumentarysystem (procedure)

          318330012021-10-310Anesthesiaforprocedureson seminal vesicles (procedure)

          428710052021-10-310Anesthesiaforprocedureson labia, vagina, cervixorendometrium (procedure)

          4421540082021-10-310Dehiscenceofinternalsurgicalwound (disorder)

          4498630062021-10-310Insertionofpacemakerfor control of atrial fibrillation (procedure)

    3

    Content Validation Activities in the Current Release cycle:

  • Concepts that have changed its high level hierarchy ancestor since last release
  • Concepts with FSNs with changed semantic tags
  • Active concepts with changed FSNs (check for shifts in meaning)
  • Concepts *in*-activated since the last release
  • Concepts *re*-activated since the last release
  • Concepts that changed from fully defined to primitive
  • Concepts that changed from primitive to fully defined
  • New FSNs: Check for adherence to naming conventions, no acronyms, etc.
  • Spell checking for new descriptions and/or manual inspection
  • Review all new and changed text definitions
  • Additions/removals of members of VMP refset (Inactive concepts still in the VMP refsets are removed during release extraction)
  • Additions/removals of members of VTM refset (Inactive concepts still in the VTM refsets are removed during release extraction)
  • Verify that there have been no changes to the Non-human refset in the Workbench.
  • Additions/removals of members of ICD-O simple map refset (Inactive concept still in the ICDO map are removed during release extraction)
    • Active concepts having active historical associations and reasons for inactivation

    4

    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 and Yong will be around. 

    November holidays?

     

    5

    Early visibility of Release Notes


    NOVEMBER ONLY ACTION: Maria Braithwaite and Donna Morgan confirmed we don't need these for the November release - instead they'll just log the change notes in their Trello board and add them into the Jan 2022 release when we get to it in December (Member Release).


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

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

    25 November 2020.Yong and Linda to confirm whether or not we need to add info on the new metadata concepts....

    the date on the Release Schedule

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

     

    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.

    Maria confirmed all tickets complete.


    7Versioning and Change Freeze

    Plan is to follow the new

    process

    processes as now defined

    last cycle:  xTechnical

    : 

    August 2021AAT notified Terance accordingly straight after the call on  

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

    Versioning + related issues

    complete

    to be completed and resolved as of

     = 
    Jira
    serverIHTSDO JIRA
    serverIdb202d822-d767-33be-b234-fec5accd5d8c
    keyINFRA-5998
     + 
    Jira
    serverIHTSDO JIRA
    serverIdb202d822-d767-33be-b234-fec5accd5d8c
    keyINFRA-6002

      

    8Stats Report

    Reports run via the reporting platform:

    Concepts changed https://docs.google.com/spreadsheets/d/1QhxK1cja523C8CADBK75wzJ4qeXgIKSOfxgSPCR6E8g/edit#gid=0

    Concepts inactivated  https://docs.google.com/spreadsheets/d/1GkapGLVanHreMH6Si3cEvlNw0w8oalTEFUDJJ0DoE0w/edit#gid=0

    New componentshttps://docs.google.com/spreadsheets/d/1QUsMw39gDeW4lYm0dTVrrWDDlxiV2av7Gqv7NxQmMA4/edit#gid=0

    Release stats https://docs.google.com/spreadsheets/d/1HHKS1ZKsvr9WaDqRbhOirG9qgEKa9lWHwr5lrIeAZWA/edit#gid=0

    Summary Component stats https://docs.google.com/spreadsheets/d/1-XU7byTRnBJUYaDhvlXdzFpHlFxDV746o5F2Msa1Olk/edit#gid=0


    Peter confirmed reports will not be updated now, as most are based on Delta's, and once we've versioned the Delta files will be empty!  So we need to check the original reports run by Maria (above) straight after her authoring checks were complete, and just manually take all of the latest

    fixes (like
    Jira
    serverIHTSDO JIRA
    serverIdb202d822-d767-33be-b234-fec5accd5d8c
    keyISRS-921
    , etc) into

    fixes into account.

    9Risks

    None raised

    10AOB

    Release schedule task for today - Content Release Lead to request (via Infra ticket) the maintenance screen to be raised in Production, to prevent further updates to International content

    Jira
    serverIHTSDO JIRA
    serverIdb202d822-d767-33be-b234-fec5accd5d8c
    keyISRS-921
     still needs to be resolved - Maria will implement in a fix branch off RFBJAN21 and AAT will regression test (as feedback_fix release type) once complete.