Page tree

Versions Compared

Key

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

Date of Initial Handover meeting: 5 October 2023

Date of Final Handover meeting: 10 October 2023

Attendees


Page properties


Handover Status

Status
subtletrue
colourBlue
titleINITIAL Handover COMPLETE



Agenda

FRI-533January 2023 release - NONE.
  • Traceability issues for February 2023 release - https://jira.ihtsdotools.org/browse/FRI-576 2 failures both confirmed as false positives by Michael.
  • 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)
  • Traceability for April 2023 release - 8 failures on main checked and false positives, ticket is here Image AddedINFRA-10712 - MF1, All components in the branch traceability summary must also be in the RF2 export, TRACEABILITY, f68c761b-3b5c-4223-bc00-6e181e7f68c3 CLOSED
  • Traceability for May 2023 release - NONE
  • Traceability for June 2023 release - https://jira.ihtsdotools.org/browse/INFRA-11004 these are valid warnings relating to the MRCM changes.
  • Traceability for July 2023 release - 2 failures

    https://jira.ihtsdotools.org/browse/INFRA-11186 checked and false positives

  • Traceability for September 2023 release - 3 failures false positives Image AddedINFRA-11323 - CMTTWO, All components in the RF2 export must also be in the branch traceability summary, TRACEABILITY, b7f727d7-9226-4eef-9a7e-47a8580f6e7a CLOSED Image AddedINFRA-11339 - QIJCA, All components in the RF2 export must also be in the branch traceability summary, TRACEABILITY, b7f727d7-9226-4eef-9a7e-47a8580f6e7a CLOSED Image AddedINFRA-11347 - RVF daily build - assertionText": "All components in the branch traceability summary must also be in the RF2 export." CLOSED Image AddedINFRA-11351 - QIKLI: Assertion Failure: All components in the RF2 export must also be in the branch traceability summary. CLOSED Also MRCM traceability expected changes checked here Image AddedINFRA-11294 - MRCM change request : 1142142004 |Has pack size (attribute)| change from Integer to Decimal CLOSED
  • Traceability for October 2023 release -
    1. MRCM traceability failures https://jira.ihtsdotools.org/browse/ATF-1678
    2. MRCM traceability failures https://jira.ihtsdotools.org/browse/INFRA-11496
      1. (both standard, expected warnings when MRCM changes are promoted)
    3. Traceability false positives https://jira.ihtsdotools.org/browse/INFRA-11526
    4. Traceability valid issues resolved https://jira.ihtsdotools.org/browse/INFRA-11549
      1. Unexpected issues with inferred records - fixed in a RELVAL task and promoted to MAIN, so just need to watch out for similar issues in Release Val

  •  

    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 -
    1. root synonym - 5268601017 SNOMED Clinical Terms version:
    20221130
    1. 20231001 [R] (
    November 2022 Release)Process has generated the data -   post close report 11 November 2022
    1. October 2023 Release) https://authoring.ihtsdotools.org/#/tasks/task/DAILYPROMO/DAILYPROMO-5382/edit
    2. MBR -
    not required as only required in January release.
    1. root copyright date - not required
    2. SEP - 
    Process has generated the data - post close report 11 November 2022
    1. https://docs.google.com/spreadsheets/d/
    1-u-8pAsQaI2fkER4XbK4ogtxjc65rPnM0NcYZZAAeYk/edit#gid=1
    1. 1so8UKIB_5lNK06fgrMRGoadTT3oaKQnyfnvV9VzvYTY/edit?usp=sharing
    2. Laterality - 
    1. https://docs.google.com/spreadsheets/d/
    1-u-8pAsQaI2fkER4XbK4ogtxjc65rPnM0NcYZZAAeYk/edit#gid=2

    NOTE: report of missing concept from laterality reference set see

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

    Darryn McGaw - investigating this concept, and also any other missing concepts from the Laterality automation...
    1. 1so8UKIB_5lNK06fgrMRGoadTT3oaKQnyfnvV9VzvYTY/edit?usp=sharing
    2

    Discussion of existing Known Issues from the previous Release

    1. Traceability issues for November 2022 release logged here
      Jira
      serverIHTSDO JIRA
      serverIdb202d822-d767-33be-b234-fec5accd5d8c
      keyINFRA-9804
       all false positives confirmed by Michael. NOTE no failures in the AP validation or the daily build validation, there is a ticket remaining to resolve issues with traceability
    Jira
    serverIHTSDO JIRA
    serverIdb202d822-d767-33be-b234-fec5accd5d8c
    key
    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 - DONE
  • MRCM: Checked with Yong - NO CHANGES for November 2022 release.
    1. RVF failures - Image AddedINFRA-11526 - ANCRJAN22, All components in the RF2 export must also be in the branch traceability summary, TRACEABILITY, b7f727d7-9226-4eef-9a7e-47a8580f6e7a CLOSED false positives
    2. Ref set description changes
    November 2022
    1. October 2023 release -
    no new descriptions seen
    1. none found in descriptions
    file
    1. report https://docs.google.com/spreadsheets/d/
    1GR4ttlSWQfmo7dln81cnCWu
    1. 1Bl5hKo-
    Js_9ztD6dENYC0Qoh9I
    1. ZXhWwixCiU8FKDK2LHLVWjCpkBBYjPr6hhwY/edit#gid=0
    2. NEW and CHANGED MRCM report -https://docs.google.com/spreadsheets/d/114B51X8HokMEX-5ZW-0-9bPwQSi1MTkU8g6M5l-1tRY/edit?usp=sharing sent to Yong for review- There is one issue with the proximal primitive refinement. It has existed for a while. We can fix it in the next release, as we discussed. The rest of the changes are expected. - will wait for November release to resolve.
    3. MRCM changes for October 2023 - https://jira.ihtsdotools.org/browse/ATF-167 and https://jira.ihtsdotools.org/browse/INFRA-11496


    4Mapping schedule

    January 2023:

    • ICD-0 - 1 new records + 0 inactivations
    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
    • 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

    August 2022

    :

    • ICD-0 -
    very few changes
    • 1 new records + 0 inactivations expected
    • ICD-10 - expecting
    320+ changes
    • 500 ish changes (plus tonight's drip feed) due to large number of intentional inactivations this cycle
  • Donna flagged up a potential issue where one concept (1231691008) is mapped to two same codes - so it will look like a duplicate to our validation - but we can safely whitelist it as an intentional change within the spec of ICD-10
    Jira
    serverIHTSDO JIRA
    serverIdb202d822-d767-33be-b234-fec5accd5d8c
    keyISRS-1302
    • No expected issues this cycle...
      • Confirmed in final numbers!

    March 2023

  • Upload of mapping content to 2x branches planned for Friday 12th this cycle...
  • September 2022

    :

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

    April 2023:

    • ICD-0 -
    1
    • 6 new
    record
    • 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
    478
    • 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!
    November 2022

    May 2023:

    • ICD-0 - 3
    or 4
    • new
    record
    • records +
    10
    • 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
    30
    • 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

    will need to

    "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

    June 2023 release - ICD-O no new maps for June.  

    New content was added, promoted to main and has since been deleted, the content was mapped, 16 concepts:

    • Postpartum acute cystitis (disorder) 10752111000119109
    • Postpartum anxiety (finding) 10756431000119109
    • Postpartum bacterial vaginosis (disorder) 10752211000119104
    • Postpartum calculus of gallbladder (disorder) 10754741000119103
    • Postpartum cellulitis of breast (disorder) 10751991000119105
    • Postpartum cholestasis (disorder) 10753141000119100
    • Postpartum disorder of lactation (disorder) 15755591000119106
    • Postpartum edema (disorder) 16737621000119100
    • Postpartum heart murmur (finding) 10755991000119107
    • Postpartum hyperthyroidism (disorder) 10754961000119101
    • Postpartum hypothyroidism (disorder) 10753681000119101
    • Postpartum inflammation of cervix uteri (disorder) 10752031000119100
    • Postpartum iron deficiency anemia (disorder) 10755381000119108
    • Postpartum mood disorder (disorder) 10755001000119102
    • Postpartum thyroid disease (disorder) 10757711000119106
    • Pain during postpartum period due to and following cesarean section (finding) 10756061000119109

    These concepts may impact mapping numbers for June release.

    July 2023 release - Donna is on leave but sent these notes:

    • GMDN is complete and ready for the July release to progress.
    • ICD-10 has no unmapped concepts but final few tomorrow to map/review before 12:00 noon.
    • Mapped 3 concepts in the ICD-O map waiting for Nicki to review.
    • Estimated numbers for ICD-10 roughly 335 and ICD-O 4 new concepts but potentially only 2 are classifiable.
    • No problems I can see with completing ready for the release to progress

    Chris will contact Rick via slack to schedule timing for Rundeck.

    September 2023 release - 

    • GMDN is complete and ready for the July release to progress.
    • ICD-10 has no unmapped concepts but final few tomorrow to map/review before 12:00 noon.
    • Mapped 1 concepts in the ICD-O map waiting for Nicki to review.
    • Estimated numbers for ICD-10 roughly 540 and ICD-O 1 new concepts but potentially only 0 are classifiable
      • *This means it won't show up in the stats! *
    • No problems I can see with completing ready for the release to progress

    Rick raised a risk that the 0901 date could cause issues with map scripts - Chris Morris already aware and has made pre-emptive changes, but could still be an issue... we will find out tomorrow (Friday) when the email comes out with the Map stats reports - if they have the right date then it'll be fine...  If not, RICK will go in and manually fix it...

    October 2023 release   

    Invalid New content was added (authored by 3M but promoted by internal authors), promoted to main and has since been deleted, the content was mapped, 18 concepts:

    • 1290139003|Reactive arthritis of hip joint (disorder)
    • 104671000119108|Reactive arthritis of joint of ankle (disorder)
    • 1290146007|Reactive arthritis of joint of elbow (disorder)
    • 1290138006|Reactive arthritis of knee joint (disorder)
    • 1290145006|Reactive arthritis of glenohumeral joint (disorder)
    • 16047151000119104 |Hydroxyapatite deposition disease of bilateral hip joints (disorder)|
    • 16046311000119104 |Hydroxyapatite deposition disease of left hip joint (disorder)|
    • 16047191000119109 |Hydroxyapatite deposition disease of right hip joint (disorder)|
    • 16046431000119103 |Hydroxyapatite deposition disease of joint of bilateral ankles (disorder)|
    • 16046551000119105 |Hydroxyapatite deposition disease of joint of right ankle (disorder)|
    • 16046871000119103 |Hydroxyapatite deposition disease of joint of left ankle (disorder)|
    • 16046511000119109 |Hydroxyapatite deposition disease of joint of bilateral hands (disorder)|
    • 16046711000119103 |Hydroxyapatite deposition disease of joint of left hand (disorder)|
    • 16047071000119107 |Hydroxyapatite deposition disease of joint of right hand (disorder)|
    • 16046831000119101 |Hydroxyapatite deposition disease of joint of bilateral feet (disorder)|
    • 1288004000 |Hydroxyapatite deposition disease of joint of hand (disorder)|
    • 16046791000119107 |Hydroxyapatite deposition disease of joint of right foot (disorder)|
    • 16047231000119100 |Hydroxyapatite deposition disease of joint of left foot (disorder)|

    So we need to ensure that:

    1. None of the above maps are actually propagated through to the Release content, plus
      1. AAT spot checked in PreProd release on 11/9/23 - could not find any of the concepts above in the final Map files
    2. The predicted figures from Mapping are adjusted accordingly to remove these 18 changes (which are no longer part of MAIN)
      1. However, Rick is going to reload the DailyBuild from tonight, and therefore the Mapping Stats Report should (in theory) take account of their removal from MAIN, but the time they're run tomorrow (Friday 8th)
      2. AAT checked final Map tool figures against PreProd release on 11/9/23 - all Reported figures match final Map files as expected

    1x ICD0 Map record showing as Non-classifiable so the counts again will need to be readjusted.

    Donna to confirm final figures tomorrow...

    1. AAT checked final Map tool figures against PreProd release on 11/9/23 - all Reported figures match final Map files as expected


    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:

    • 10/11/22 - All content and mapping complete and signed off by close of play
    • 15/11/22  - AAT to build PreProduction (unversioned) and sign off before 15:00 on 18th, otherwise decision made to postpone versioning
    • 16/11/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 11th November 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