SNOMED International Release Management

Page tree

Versions Compared

Old Version 3

changes.mady.by.user Andrew Atkinson

Saved on

compared with

New Version 4

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:   

Attendees

  • Maria Braithwaite (MBR)
  • Kai Kewley (KKE)
  • Peter Williams (PWI)
  • Monica Harry (MHA)

Date of Final Handover meeting:  

Attendees

  • Andrew Atkinson (AAT)
  • Maria Braithwaite (MBR)
  • Donna Morgan (DMO)
  • Kai Kewley (KKE)
  • Peter Williams (PWI)
  • Rory Davidson (RDA)
  • Monica Harry (MHA)

Apologies


Page properties


Handover Status




Agenda

 

Items to be discussed

Actions

1

Prerelease Content Management Activities:

  1. Verify that all namespace concepts (in the namespace registry) have been added
  2. Inactivate the root concept synonym referencing previous release, and add synonym to reference current release.
  3. Update copyright date on synonym (January releases only; N/A to July 2014)
  4. Send updated laterality indicator spreadsheet to technical team to support qualifier generation.

  5. Content Team to deliver SE and SP refset files to Release Manager

  6. Content Team to deliver 4x MRCM refset files to Release Manager (just needs to confirm they're completed, downloaded + tested, AAT will then pull them out of the termServer during release builds via the termServer Export)

 

  1. MBR - confirmed with Yohani on.....

  2. MBR - ?????????done please see INFRA-3968

  3. MBR - ?????????update root concept and synonym please see INFRA-3968

  4. ACTION: Yongsheng Gao to deliver laterality indicator, as this now comes from the Refset tool ... AAT to receive from Yong on.....


  5. ACTION: Yongsheng Gao to deliver SE and SP files, AAT to receive from Yong on..... 

  6. ACTION:Yongsheng Gao to deliver MRCM files, AAT to receive from Yong on..... 

    ACTION: Linda Bird to deliver final MRCM spreadsheet for cross checking (July 2020 ONLY), AAT to receive from Linda on..... 

2

Content Validation Activities:

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

MBR has been analysing the Daily Build RVF results for the past few weeks, and working with Peter to clear down the failures. Early Alpha run by AAT 30th April 2020:

  1. ISRS-770 - False positives - whitelisted
  2. ISRS-771 - False positives - whitelisted
  3. ISRS-772 - False positives - whitelisted
  4. ISRS-773 - Whitelisted after investigation
  5. ISRS-774 - False positives - whitelisted
  6. ISRS-775 - MRCM Refsets need to be delivered for July 2020 and included in package before re-running validation
  7. ISRS-776 - Requires a backend fix and a ticket is logged 
    Jira
    showSummaryfalse
    serverIHTSDO JIRA
    serverIdb202d822-d767-33be-b234-fec5accd5d8c
    keyINFRA-4998
    - STATUS FROM DEV? Looks like it's resolved now? can close ISRS-776?
  8. ISRS-777 - Resolved - AAT + Maria to regression test in Alpha/Beta/Production to confirm still resolved...
  9. ISRS-778 - Requires back end fix and ticket is already logged for this 
    Jira
    serverIHTSDO JIRA
    serverIdb202d822-d767-33be-b234-fec5accd5d8c
    keyINFRA-5001
    - RESOLVED - can close ISRS-778?
  10. ISRS-779 - Requires back end fix and ticket is already logged for this 
    Jira
    serverIHTSDO JIRA
    serverIdb202d822-d767-33be-b234-fec5accd5d8c
    keyINFRA-5002
    - RESOLVED - can close ISRS-779?
  11. ISRS-780 - Whitelisted after investigation
  12. ISRS-781 - requires back end fix, ticket already logged for this 
    Jira
    serverIHTSDO JIRA
    serverIdb202d822-d767-33be-b234-fec5accd5d8c
    keyINFRA-5030
    -  resolved but not yet promoted to MAIN so still appearing in RVF at this point....RESOLVED - can close ISRS-781? 5/5/2020 - Maria promoted new task to fix everything related to this concept, she will confirm once re-tested...
  13. ISRS-782 - Resolved - AAT + Maria to regression test in Alpha/Beta/Production to confirm still resolved...


MBR will share content report with team when it is ready. 

3

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 + Yong + Donna will all be around to support wherever needed

 

4

Early visibility of Release Notes

 

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

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

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

 

5

Discussion of existing Known Issues from the previous Release

 

  1. ISRS-366 - Long term case significance fixes work has commenced for this, it will be ongoing over subsequent releases. STILL THE CASE??
  2. ISRS-409- Specific case significance issue - I have asked JCA for an update, no immediate action, requires wider consultation.  LOOKS LIKE IT's RESOLVED NOW?
  3. ISRS-575 - no action, being resolved over time with template based editing as part of QI project. STILL THE CASE?? Close this ticket as QI now a permanent feature?
  4. ISRS-582 - checked no author changes required. RESOLVED - AAT + Maria to regression test in Alpha/Beta/Production to confirm still resolved...
  5. ISRS-562 - Finding with explicit context| concepts using |Associated Procedure| attribute - editing issue resolved. STILL THE CASE??
  6. ISRS-563 - 8 concepts using |Surgical approach| that are not subtypes of |surgical procedure| - editing issue resolved. STILL THE CASE??
  7. ISRS-672 - Resolved - AAT + Maria to regression test in Alpha/Beta/Production to confirm still resolved...
  8. ISRS-673 - Resolved - AAT + Maria to regression test in Alpha/Beta/Production to confirm still resolved...
  9. ISRS-668 - Resolved - AAT + Maria to regression test in Alpha/Beta/Production to confirm still resolved...
  10. ISRS-739 - Resolved - AAT + Maria to regression test in Alpha/Beta/Production to confirm still resolved...
  11. ISRS-741 - Resolved - AAT + Maria to regression test in Alpha/Beta/Production to confirm still resolved...
  12. ISRS-720 - Resolved - AAT + Maria to regression test in Alpha/Beta/Production to confirm still resolved...
  13. ISRS-739 - Resolved - AAT + Maria to regression test in Alpha/Beta/Production to confirm still resolved...
  14. ISRS-700 - Yong and Linda confirmed that they were happy with the testing so far, and would complete testing by end of play today.

  15. We will then export the MRCM refsets tomorrow and re-build the early alpha release to confirm all working as expected.

    AAT to then send final MRCM refset to Linda + Yong for final confirmation...

    AAT to then send the confirmed MRCM refsets to Ed Cheetham for external confirmation....

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.

Mapping: Donna?????



7Versioning and Change Freeze

KAI has run some manual checks for missing descriptions - no issues found.

8Stats Report

MBR has been using the Daily Build QA report for stats and has the information needed for release notes, also given access to https://docs.google.com/spreadsheets/d/1hgDBPG5TjarvGpRJD6LBUN1sHLizhWWchzWDXXjpPRk/edit#gid=3 by Peter for further information that will be useful for release notes.


9Risks
  1. Kai - Any SnowStorm risks for this release? Anything to consider from the new Technical Team Release tasks?
10