SNOMED International Release Management

Page tree

Versions Compared

Old Version 7

changes.mady.by.user Maria Braithwaite

Saved on

compared with

New Version 8

changes.mady.by.user Maria Braithwaite

Saved on

Key

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


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)
  • Yongsheng Gao (YGA)

Apologies


Page properties


Handover Status

Status
colourRed
titleINITIAL



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 on 29 April 2019.

  2. MBR -done please see JIRA ticket INFRA-3278

  3. MBR - not required for July 2019 release.

  4. ACTION: Yongsheng Gao to deliver this, as this now comes from the Refset tool ... AAT to receive from Yong w/c ???????

    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 them, AAT to receive from Yong w/c .............

    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) In the Preliminary Handover meeting it is being cleaned on a daily basis, with the intention of having it cleared down completely by the handover on ..........................

b) Clean in the Final Handover meeting (before we version the content)???????? to confirm next week...

ACTION: Maria Braithwaite to share the Content report results with the content team - she will confirm whether or not any fixes are required before the Alpha release - ??????????? Maria confirmed all clean now and no further issues requiring action

Final issue found by UK (

Jira
serverIHTSDO JIRA
serverIdb202d822-d767-33be-b234-fec5accd5d8c
keyISRS-464
) was confirmed by content team as planned for fix in July 2019 (and agreed to be carried over by Elaine and Jeremy), so team to just confirm this was resolved in the July 2019 editing branch. MBR new concept added 782715005 |Infection caused by Bordetella (disorder)| no other changes required.


 

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 July 2019 International Edition - SNOMED International Release notes - content team to update with relevant figures for July 2019 content.....

ACTION: Maria Braithwaite and Donna Morgan will kindly aim to get them to Andrew Atkinson by ??????? 15th May 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-365 - Long term "part of" fixes - current status - May 2019 update has dependency on the implementation of DL enhancements.
  2. ISRS-366 - Long term case significance fixes - May 2019 review work completed, requires implementation into editing environment, meeting planned to discuss 8 May 2019.
  3. ISRS-409- Specific case significance issue - have we decided whether or not to fix this?I have asked JCA for an update.
  4. ISRS-414- Non breaking spaces - fixed, just need to validate in this release cycle
  5. ISRS-459 - resolved by Maria in
    Jira
    showSummarytrue
    serverIHTSDO JIRA
    serverIdb202d822-d767-33be-b234-fec5accd5d8c
    keyINFRA-2984
    ? Ready to validate in this cycle?
  6. ISRS-464 - Veterinary inactivation issues - fixed??, just need to validate in this release cycle
  7. ISRS-487 - MRCM domain issues - fixed, just need to validate in this release cycle
  8. ISRS-489- MRCM updates - part two of the changes we implemented in Jan 2019 - Maria completed the warning, Linda to finalise....
  9. ISRS-491 - MRCM constraint issues - fixed, just need to validate in this release cycle

Brief 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: ??????? Clean after initial meeting - how are we looking for meeting the planned delivery timelines??


7Versioning and Change Freeze

AAT to raise ticket after all above confirmed.....

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


Stats 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... done??

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 for the July 2018 International Edition.

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

9Risks

No known risks! Everyone comfortable so far...






...