SNOMED International Release Management

Page tree

Versions Compared

Old Version 8

changes.mady.by.user Andrew Atkinson

Saved on

compared with

New Version 9

changes.mady.by.user Andrew Atkinson

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)

Apologies

  • Rory Davidson (RDA)
  • Lesley MacNeil (LMA)

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. Confirm all conflict adjudications have been resolved
  5. Confirm there are no equivalency conflicts after classification
  6. Send updated laterality indicator spreadsheet to technical team to support qualifier generation.
  7. Get SE and SP refset files from Yong

  8. Donna to confirm with the UKTC (on the weekly call) to confirm they have nothing outstanding in QA status after content cut off for each release - as in July 2017 this started to cause problems in our mapping process...



 

  1. MBR - confirmed with Yohani 31 October 2018

  2. MBR - done please see

    Jira
    serverIHTSDO JIRA
    serverIdb202d822-d767-33be-b234-fec5accd5d8c
    keyINFRA-2719

  3. MBR - done please see

    Jira
    serverIHTSDO JIRA
    serverIdb202d822-d767-33be-b234-fec5accd5d8c
    keyINFRA-2719

  4. MBR confirmed???????

  5. MBR confirmed???????

  6. ACTION: Maria Braithwaite/Andrew Atkinson to speak to Yong about this, as this will now come from the Refset tool ... AAT received from Yong???????

  7. Complete and received from Yong???????

  8. Donna confirmed that this collaborative work has now reached it's conclusion, and so this is no longer an issue as UKTC no longer have access to our tool.???????

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 9th November 2018???????

b) Clean in the Final Handover meeting (before we version the content)????????

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

 

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 2019 International Edition - SNOMED International Release notes - see here with relevant figures replaced with ??????? ready to be replaced with the relevant January 2019 figures

ACTION: Maria Braithwaite and Donna Morgan will kindly aim to get them to Andrew Atkinson by ??????? 2018

ACTION: Lesley MacNeil and Paul Amos to review and approve once complete...

 

5

Discussion of existing Known Issues from the previous Release

 

  1. ISRS-176 - RVF Assertion failure: 19423070-7118-45bd-98ba-6d0dc18bc619

    1. MCH confirmed that fix is still in Dev, so likely only be fixed for July 2018 - only a technical issue though not content...assigned to January 2019


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.
  1. Jira
    serverIHTSDO JIRA
    serverIdb202d822-d767-33be-b234-fec5accd5d8c
    keyINFRA-2965
    1. Concepts should now have been inactivated and promoted - Maria to confirm....
  2. Jira
    serverIHTSDO JIRA
    serverIdb202d822-d767-33be-b234-fec5accd5d8c
    keyINFRA-2723


  3. Jira
    serverIHTSDO JIRA
    serverIdb202d822-d767-33be-b234-fec5accd5d8c
    keyINFRA-2869
  4. Jira
    serverIHTSDO JIRA
    serverIdb202d822-d767-33be-b234-fec5accd5d8c
    keyINFRA-2868


  5. Jira
    serverIHTSDO JIRA
    serverIdb202d822-d767-33be-b234-fec5accd5d8c
    keyMAINT-489
  6. Jira
    serverIHTSDO JIRA
    serverIdb202d822-d767-33be-b234-fec5accd5d8c
    keyINFRA-2792
  7. ACTION: Peter G. Williams to report on relationship issue with Yong, and if it has now been completely resolved and reviewed????????


  8. ACTION: Maria Braithwaite to confirm with Farzaneh/Suzanne whether or not any LOINC issues need to be resolved before versioning, depending on licencing issue??????????????



  10. ACTION: Maria Braithwaite + Andrew Atkinson agreed to formalise the process for disabling projects a few days before content cut off - I've added it into the formal Schedule, so we'll continue to run that for all future releases and see if it continues to have positive effects on lack of impact to Maria's reviews.


Mapping:

7Versioning and Change Freeze

Completed and successful builds run???????


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

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

9Risks

No known risks! Everyone comfortable so far...