Page tree

Versions Compared

Key

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

Date of Initial Handover meeting: 11th 9 February 20222023

Date of Final Handover meeting: 15th 14 February 20222023

Attendees


Page properties


statusFINAL HANDOVER COMPLETE 

Handover Status

colourBlue
title



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
  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 -
done
  • MBR - not required as only required in January releases...
  • Process has generated the data - AAT to cross check against report MBH sent:
    1. root synonym - SNOMED Clinical Terms version: 20230228 [R] (February 2023 Release)
    2. MBR - root copyright date - not required
    3. SEP -
    1rXzVqTmMYiN3rwqzEjTdBu-HLsmn-3qzdbfxIGz7Sco
  • Report shows 34 changes - 26 new records + 8 inactivations
  • Association Snapshot in Feb release shows 34 records with 20220228 effectiveTime - 26 new records + 8 inactivations
  • Process has generated the data - AAT to cross check against report MBH sent:
    1rXzVqTmMYiN3rwqzEjTdBu-HLsmn-3qzdbfxIGz7Sco
  • Report shows 342 changes - 9 new records + 9 inactivations + 324 updates
  • SimpleRefset Snapshot in Feb release shows 342 records with 20220228 effectiveTime - 333 new/updated records + 9 inactivations
  • Yong confirmed he will try to follow the deadlines for the monthly releases - 
    1. No expected MRCM changes for the February 2022 release - as confirmed by MBH
  • 1
    2

    Discussion of existing Known Issues from the previous Release

  • MSSP-1357 - Peter fixing in a task branch on 11/2/22, Maria to test and promote - AAT to regression test in Prod Release BEFORE VERSIONING
    1. Testing Complete and signed off
  • INFRA-8398 - Traceability failures - MCH confirming if they’re all false positives…BEFORE VERSIONING
    1. Complete - Michael confirmed all false positives
  • INFRA-8402 - RefsetDescriptor - RDA confirmed we should just remove them from scope for now, so I’ve raised Dev ticket to exclude them automatically
    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

    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 -
    MBR confirmed all done and nothing outstanding other than SEP + Laterality issues..
    1. see
      Jira
      serverIHTSDO JIRA
      serverIdb202d822-d767-33be-b234-fec5accd5d8c
      keyFRI-576
       for traceability failures. 
    2. See also https://jira.ihtsdotools.org/browse/INFRA-10334 "Changes that have been made on a branch that was not task level.", - these relate to MRCM changes all have been checked by Chris Swires are expected and no action required. We can expect this same warning at RELEASE TIME...
    3. NEW and CHANGED MRCM report - https://docs.google.com/spreadsheets/d/1KPywRk5bt4uKeAp7IEFa_CXotLgGlc1gfxgP8p1j4R4/edit#gid=0 checked by Yong, changes confirmed as expected and documented here MRCM changes in the February 2023 release see also 

      https://jira.ihtsdotools.org/browse/ATF-1677

    4. Ref set description changes February 2023 release -none found in descriptions file.
    4Mapping schedule

    Donna confirmed she's happy with the schedule, and they're also already up to date with the final content.

    Mapping process delivered ICD-0 + ICD10 files to AAT on time this cycle

    Did mapping process work well this time??   Yes, process was good

    HOWEVER, the counts don't match Donna's manual counts exactly, so we will investigate further:

  • ICD-0 = Manual mapping count = 4 new records, only 3 new records coming through in Delta files
  • 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...
      • Confirmed in final numbers!

    November 2022:

    • ICD-0 - 3 or 4 new record + 10 inactivations expected
    • ICD-10 - expecting 30 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!

    December 2022:

    • ICD-0 - 0 new records + 0 inactivations expected
    • ICD-10 - expecting 890 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!

    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!

    ***** 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 *****

    ICD-10 = Manual mapping count = 477 new records, 485 new records coming through in Delta files
  • Donna sent report:
  • Compared Delta file changes to report:
  • Delta file showed most differences were due to 47 updated records in the Delta, in addition to that there was only one missing concept:
    • 1196866006
  • Confirmed with Rick that this was a concept that was added to the content (therefore came through to mapping in the drip feed), and was then removed from the content before the monthly release! 
  • Therefore should be missing from the Delta files - just should also be removed from Donna's manual counts (based on the drip feed) - she will work with Rick to get visibility of the Mapping QA report to remove these concepts from her counts
  • (see email trail at 16:24 on 15/2/2022)

    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.


    6

    Maria confirmed all tickets complete

    DevOps resource confirmedJoe Schofield
    7
    6
    Versioning and Change Freeze

    Plan is to follow the new processes as now defined:

     
    2022

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

    HIGH LEVEL KEY MILESTONES:

    • 05/01/23 - All content and mapping complete and signed off by close of play
    • 09/01/23  - AAT to
    sign off
    • build PreProduction (unversioned)
    build before 11:00 on 15th February, and then:
    • and sign off by the deadline, otherwise decision made to postpone versioning
    • 11/01/23 -  Versioning to begin first thing
    Versioning
    • + related issues to be completed and resolved
    as of  - DONE!
    • by 17:00
    8
    7
    Stats Report

    Reports run via the reporting platform

    :
  • Concepts moved elsewhere https://docs.google.com/spreadsheets/d/1Qm6pmFH7Fh9zLhNhZGwsotVNAhsasLiF1PLldk7SvSc/edit#gid=1
  • Inactivated concepts https://docs.google.com/spreadsheets/d/1dpTGGc8ijgS-Yokh8xwKGTquCbI8j26gSOHHNVdhKR8/edit#gid=0
  • Inactivated concepts in ref sets https

    :

    //docs.google.com/spreadsheets/d/1mK0Ng5wTDqKTNopSnhJMHzOXFRtRli8zYVAUSHyflGY/edit#gid=2
  • Pre release content validation https://docs.google.com/spreadsheets/d/1Y96Df5aUzvwaOSp7ifozA4oviUCw1pdaI-rRfeQton8/edit#gid=0
  • New and changed components - https://docs.google.com/spreadsheets/d/1h_xcI-U3Ef1FJ5KgRq1F4xT16NB7cwbWlq52jab8XKE/edit#gid=0
  • Release stats https://docs.google.com/spreadsheets/d/1QZ62NQEg5hebps4FiBs9eaKotL2XnBu_3cZYJG7wEI8/edit#gid=0

    Summary Component stats for edition 

    https://docs.google.com/spreadsheets/d/

    1MLfI6yeKbJYDKgES1nGtS97qZuCiaAaXrY93bW5gYHM

    9Risks

    MRCM changes this cycle, just need to keep an eye on them

    10AOB

    Please update release notes page for Feb 2023 with Jan 2023 notes.

    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 into account.

    8Risks

    None raised

    9AOB