SNOMED International Release Management

Page tree

Versions Compared

Old Version 17

changes.mady.by.user Andrew Atkinson

Saved on

compared with

New Version 18

changes.mady.by.user Maria Braithwaite

Saved on

Key

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

Date of Initial 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)
  • Terance Shird (TSH)

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)
  • Terance Shird (TSH)


Apologies


Page properties


Handover Status

Initial Handover - planned



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 - done verified with Yohani by email on 10 May 2021.
  2. MBR - done please see 
    Jira
    serverIHTSDO JIRA
    serverIdb202d822-d767-33be-b234-fec5accd5d8c
    keyINFRA-6257
  3. MBR - NOT NECESSARY FOR JULY RELEASE!

  4. ACTION: Yongsheng Gao to deliver lateralizable refset, as this now comes from the Refset tool ... AAT to receive from Yong on 24th May 2021 (Yong to download from Daily Build to provide provisional files)

  5. ACTION: Yongsheng Gao to deliver SE and SP files, AAT to receive from Yong on 24th May 2021 (Yong to download from Daily Build to provide provisional files)

  6. ACTION:Yongsheng GaoYong to confirm MRCM complete and can be used in current state?

    AAT to then send the confirmed MRCM refsets to Ed Cheetham for external confirmation.... (STILL NEEDED???) - Yes, Rory confirmed this is still a useful step.

2

Discussion of existing Known Issues from the previous Release

 

  1. ISRS-926 - we confirmed that this is a false positive and this concept was therefore whitelisted for this particular assertion, for the Jan 2021 Release cycle.  Is it now resolved? MBR- can be permanently whitelisted.

  2. ISRS-928 - permanently whitelisted, no action required

  3. ISRS-930 - we confirmed that these are false positives, due to the records having been created and then versioned in November 2020, in preparation for the Jan 2021 release.  However, they were then subsequently inactivated within the same release cycle, in order to fix errors in the new content - changes were therefore made to concepts that are brand new to this release and hadn't been Published yet.  These 4 records were therefore temporarily whitelisted for this assertion, as they should not re-occur in the next cycle.  AAT + MBR to verify no re-occurrence during this July 2021 release cycle...
  4. ISRS-931 - we confirmed that these are false positives, due to the records having been created and then versioned in November 2020, in preparation for the Jan 2021 release.  However, they were then subsequently inactivated within the same release cycle, in order to fix errors in the new content - changes were therefore made to concepts that are brand new to this release and hadn't been Published yet.  These 2 records were therefore temporarily whitelisted for this assertion, as they should not re-occur in the next cycle.  AAT + MBR to verify no re-occurrence during this July 2021 release cycle... 
  5. ISRS-933 - These were temporarily whitelisted in Jan 2021, pending further investigation into the classification of these and other concepts, with the aim to resolve any issues for the July 2021 International Edition.  Resolved now? 
    1. No - agreed to carry over as a Known Issue again for July 2021 in ISRS-1023
    2. ACTION: AAT to warn Australia that we're carrying it over again for this cycle, and will be available in a "future" release once work for the Authoring Platform is prioritised...
  6. ISRS-935 - we confirmed that the use of occurrence = 282032007 |Periods of life (qualifier value)| is allowable and not constrained by the MRCM because it might be used as a grouper.  The template has more refined constraints so the inclusion of 282032007 |Periods of life (qualifier value)| as a value for occurrence could be avoided in future through use of the proposed template.  The MRCM will be reviewed to see if it could be refined however this would require thorough analysis as there may be some use cases where this value is acceptable (such as for grouper concepts). The concept 231956007 |Traumatic aniridia (disorder)| will be remodelled for the July 2021 release.  This issue was therefore temporarily whitelisted pending resolution in the July 2021 cycle - resolved? MBR- yes resolved.
  7. ISRS-936 - we confirmed that these are valid issues, but were not critical enough to require action in time for the January 2021 release. A number of the attributes require further discussion regarding changes to the MRCM rules in consultation with the Device project group.  The issue with modelling is of no obvious clinical risk, and therefore all issues were temporarily whitelisted pending resolution in the July 2021 International release with further enhancements to the validation rules requested.  Resolved? MBR- yes resolved, MRCM runs against stated and inferred and no errors for either.
    1. ACTION: AAT to chase up the development of the work to ensure we run MRCM against STATED + INFERRED...


3

Content Validation Activities in the Current Release cycle:

  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 12th May 2021 was mostly clean - we've since resolved all issues found:

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


4

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

 

5

Early visibility of Release Notes


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

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

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

 

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.

Release:

  • None identified so far - pre-Alpha is now clean

Mapping (Donna):

  • Already locked down last weekend, so ahead of the timelines so far...
  • Maria confirmed she had to re-activate a couple of concepts yesterday which might impact the maps
    • ACTION: She will send them to Donna to discuss with Rick and see if this needs changes to the maps...

Content (Maria): 

  • INFRA-6858
    • Maria only found this issue an hour ago!
    • All agreed that this needs fixing before we version - Peter kindly agreed to jump on this today as he already knows what needs fixing, and so he will resolve by close of play today. 
    • ACTION: Versioning will not be green-lit until this ticket is complete.- ticket is resolved.


Concrete Domains:

  • INFRA-6780
    • Resolved with no known issues
    • ACTION: MCH to add confirmation to ticket of planned number of changes coming through in new Concrete Relationship file for this cycle...
7Versioning and Change Freeze

Plan is to follow the new process as defined last cycle: Technical Team Release tasks - July 2021

  • Terance confirmed ready to go, no identified issues so far...
8Stats Report

MBR has been using the Daily Build QA report for stats and has the information needed for release notes.

Release Reports run via the reporting platform:

Spell checks: https://docs.google.com/spreadsheets/d/1gQhfVFmoq3_nn0jn36NxUl3Zr_EnORCi5guqt2OZniQ/edit#gid=0

Concepts changed : https://docs.google.com/spreadsheets/d/1yNsemZdWhjl9G69c3Gyhe8FyA9KdrZbVFHGAl8dEJ54/edit#gid=1

Concepts inactivated  : https://docs.google.com/spreadsheets/d/1HCdH8JU3td67Sejb3ecS8dQjzkjpma2qqJOKNFmEpoo/edit#gid=0

New components : https://docs.google.com/spreadsheets/d/1NhBWtyu1AYpwmZbuaZaHpM0PtevzT1H6ChpeBY6gc1o/edit#gid=0

Release stats : https://docs.google.com/spreadsheets/d/1tgeiHFIj2BCw4nFMYvlLqmqWN7F0rC8fTs9Y0w31ooc/edit#gid=0

Summary component stats: https://docs.google.com/spreadsheets/d/1jHr_xHWlfkWppwnfK5HZfI6pcSo6Dqx6X_gy7BhVBpE/edit#gid=0


HOWEVER, should we focus on the Summary Component stats report now, as with MS products, in order o ascertain Intention of the authoring cycle vs real data actually contained in the Release files?

  • yes, Peter confirmed that the Summary Component stats report is now the best source of truth for INT as well as MS
9Risks
  • Concrete Domains?
  • VACCINE WORK COMING IN LATE AGAIN - MBR: yes very likely, given provisional deadline for content addition of 16 June 2021 to align with beta release feedback deadline.
    • Monica confirmed that the likely scope of changes is only 1-2 concepts
    • ACTION:  Maria to discuss with Toni and re-confirm over the next week - TMO Best guess is that it will be less than 25 concepts.
    • ACTION:  AAT to then include a note in the BETA Release Notes to confirm to users that we are planning x number of vaccine-related component changes after the BETA release, but BEFORE the Member release.  So anyone interested should ensure to re-validate the Member release even if they've already checked the BETA release.
10