SNOMED International Release Management

Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »


Date of Preliminary Handover meeting: 

Date of Initial Handover meeting:   

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

Handover Status

FINAL

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. Get SE and SP refset files from Yong



 

  1. MBR - confirmed with Yohani 5 Nov 2019

  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  

    1. YONG confirmed he would complete the refset by cop on ............., so once Maria reviewed as well AAT should receive the completed version by ........... at the latest.

    2. YONG Delivered as requested on

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

    1. YONG confirmed he would complete the refset by cop on ............., so once Maria reviewed as well AAT should receive the completed version by ............. at the latest.

    2. YONG Delivered as requested 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. We just, therefore, need to confirm that the RVF report is now:

a) RVF report being checked on a daily basis with the intention of having it cleared down completely by the handover on 8 Nov 2019

b) To be clean by the Final Handover meeting (before we version the content) to confirm 18 Nov 2019

ACTION: Maria Braithwaite to share the Content report results with the content team - will confirm whether or not any fixes are required before the Alpha release


Maria confirms:

https://jira.ihtsdotools.org/browse/RP-127 - all issues resolved for Jan 2020 release, new report in RP confirms no new issues.

https://jira.ihtsdotools.org/browse/RP-165 - all issues resolved for Jan 2020 release, no new issues in RP report.


 

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, Donna and Yong 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 January 2020 International Edition - SNOMED International Release notes - content team to update with relevant figures for January 2020 content.....

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

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.
  2. ISRS-409- Specific case significance issue - I have asked JCA for an update, no immediate action, requires wider consultation.
  3. ISRS-575 - Getting issue details... STATUS - no action, being resolved over time with template based editing as part of QI project.
  4. ISRS-574 - Getting issue details... STATUS - requires change to RVF report to remove this assertion altogether.
  5. ISRS-582 - Getting issue details... STATUS - checked no author changes required.
  6. MAINT-919 - Getting issue details... STATUS -147,000+ issues, needs change to assertion to allow self grouping, no editing changes needed.
  7. ISRS-562 - Finding with explicit context| concepts using |Associated Procedure| attribute - editing issue resolved.
  8. ISRS-563 - 8 concepts using |Surgical approach| that are not subtypes of |surgical procedure| - editing issue resolved.
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:


7Versioning and Change Freeze

KAI TO RUN ONE FINAL MANUAL OWL DAILY BUILD BEFORE WE VERSION JUST TO DOUBLE CHECK NO UNEXPECTED CONTENT ISSUES....

AAT to then get a clean Alpha package built before we can sign off content for versioning... 

AAT to request Rory/Michael to action after all above confirmed.....

Validation up and running immediately due to no more reliance on the AMI!! - Maria and team to let us know immediately if any issues found in the validation as might be a few initial niggles...

????????Versioning completed and initial successful builds run - will confirm properly once final validation run after mapping files delivered....

8Stats Report

MBR has now been using the Daily Build QA report (which will contain data from the next Release Cycle by the time this Release is published) - https://dailybuild.ihtsdotools.org/qa/

ACTION: Maria Braithwaite will run the spell check and RVF one final time after the cut off is complete -

MBR can also now use this for the stats in the Release Notes, as once content cut off is complete, this Daily Build report will show the static version

ACTION: Maria Braithwaite The only thing we need to be careful of here is large updates during Alpha/Beta release cycle - so MBR to run this again after Beta release is complete and update Release Notes if required - done??

9Risks


10





  • No labels