SNOMED International Release Management

Page tree

Versions Compared

Old Version 6

changes.mady.by.user Maria Braithwaite

Saved on

compared with

New Version 7

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: 18 November 2020

Attendees

Date of Final Handover meeting: 25 November 2020

Attendees

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

  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)

 

2

Discussion of existing Known Issues from the previous Release

Jira
serverIHTSDO JIRA
serverIdb202d822-d767-33be-b234-fec5accd5d8c
keyISRS-806
 - Checked before close of editing, content issue is resolved

Jira
serverIHTSDO JIRA
serverIdb202d822-d767-33be-b234-fec5accd5d8c
keyISRS-809
 - All resolved we have a validation rule in the RVF report for this now, 17 issues found and resolved, no issues in RVF report today.

Jira
serverIHTSDO JIRA
serverIdb202d822-d767-33be-b234-fec5accd5d8c
keyISRS-688
 - https://jira.ihtsdotools.org/browse/ISRS-605 relates to the US extension, the ticket we have relating to the International release is https://jira.ihtsdotools.org/browse/ISRS-575 with a failure count of 1716.
I have checked a sample of the attached file, the issue is the same, the concepts are marked fully defined by virtue of their stated IS_A relationships which was in the past acceptable, editorial policy has subsequently changed and we now require a proximal primitive parent and the addition of attribute and value pairs. These modelling issues are being addressed by the QI project in many cases using template based editing, no changes required at present.  Can we close this down then??

Jira
serverIHTSDO JIRA
serverIdb202d822-d767-33be-b234-fec5accd5d8c
keyISRS-807
 - As discussed with the technical team, this may require changes to the existing classification service. Further investigation and evaluation are needed before we can implement the changes in production. It is not possible to make the changes for this release. The plan is to address this issue for the July 2021 release. We will update the ticket when the progress has been made. 


 

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

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.


 

5

Early visibility of Release Notes


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

ACTION: Maria Braithwaite and Donna Morgan will kindly aim to get them to Andrew Atkinson by 25 November 2020.

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.


Any?


7Versioning and Change Freeze


8Stats Report


9Risks