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

Version 1 Next »

Date of Preliminary Handover meeting:   

Date of Final Handover meeting:  

Attendees

Apologies

  • Rory Davidson (RDA)
  • Michael Chu (MCH)

Handover Status

ALPHA

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.

 

  1. MHA to verify in the Final handover meeting - DONE

  2. Michael to ask technical team to call the TS API direct in order to update the Root concept directly. Michael to confirm complete as of the final handover meeting. -DONE

  3. Michael to ask technical team to call the TS API direct in order to update the Root concept directly. Michael to confirm complete as of the final handover meeting. -DONE 

  4. MHA verified that as of this point there are only 2 remaining outstanding – these will be resolved on the back end (JIRA ticket ATF1052)

    1. MHA to verify that this has been complete in the final handover meeting. DONE

  5. MHA to verify in the Final handover meeting -DONE

  6. AAT to speak to Peter and Yong about this, as we may not need this item any more given the introduction of the new Laterality refset in the Jan 2017 release. - Yongsheng Gao will confirm with Andrew

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
  16. Verify that the daily build is extracting the correct Workbench path

 

MHA has been analysing the Daily Build RVF results for the past few weeks (since 23rd October 2016), and working with Michael 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 10th November 2016

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

MICHAEL to therefore run Content Validation through on the final cut-off content from 11th November 2016 onwards, in order to identify any outstanding issues and resolve them before 15th November when the mapping cut off takes place. -DONE


MHA - no notifications have come through, Michael will do Alpha release and run through validation and assertions and send Root description task.

 

LMA - Waiting on Term Server restore - Monica will manually check and correct any that are not in the RVF - this will happen after the versioning - Main content done external refsets to be done after Nov 15th


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.

Monica and Yong will all be around to support wherever needed.

Confirmed Monica is available

4

Early visibility of Release Notes

 

AAT to provide template to update on Confluence - MHA will kindly aim to get them to me by 10th November 2016.

******* Section 2.1 to be enhanced by MHA for the high level Changes, per Project that have happened in each Project. So for example, 1000 concepts were updated for Observables for this good reason, and this is the benefit to the users. The number of concepts can be pulled from JIRA reports, and should eventually total the total number of changes in the release (AAT can then use this for traceability matrix from July 2016 to Alpha release for Jan 2017 which is currently a gap...)

5

Discussion of existing Known Issues from the previous Release

 

Issue ID: 20160131-002

Part-of relationships need to be included in the Jan 2017 release - Michael and Peter to confirm that this has happened and has been included in the content for this Release. -

LMA -This did not go for Jan 2017. Two pointers is the issue and waiting bug fix - the future plan assigning as part of a stated -The work of moving part of relationships into the stated file is another question and that’s going to take a bit of working out for how we form the Distribution Normal Form." may July 2107 Andrew/YGA to confirm.

 

6

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.

 

Pending Term Server Restore There are only a few known outstanding issues here - MHA to confirm that these are all closed down in time for the Final handover meeting

7VersioningMonica and Yong will all be around to support wherever needed. And no promotion to main once authoring commences until notified.
8Stats Report

From July 2017 onwards, Rory will kindly create a new, separate version of the http://qa.snomed.org/ stats site, that includes only the data up to and including the Content Cut Off date.

Monica can then use this link in the Release Notes, instead of using the Daily Build QA report (which will contain data from the next Release Cycle by the time this Release is published)

  • No labels