Page tree

Versions Compared

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)
  • Lesley MacNeil (LMA)
  • Michael Chu (MCH)

Apologies

  • Rory Davidson (RDA)


Page properties


Handover Status

Status
colourRed
titlein progress



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. 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.................. - again to verify in the Final handover meeting.

  2. MBR and MCH confirmed...

  3. MBR and MCH confirmed...

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

  7. 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 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 9th May 2018

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

ACTION: Andrew Atkinson to therefore run the Content Validation report through on the final cut-off content from 10th May 2018 onwards, in order to identify any outstanding issues and resolve them before 16th May 2018 when the mapping cut off takes place. 

 

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

ACTION: Maria Braithwaite and Donna Morgan will kindly aim to get them to Andrew Atkinson by ?????????????????17th May 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. Fix is still in Dev, so likely only be fixed for July 2018 - only a technical issue though not content
    2. MCH confirmed that fix is still in Dev, so likely only be fixed for July 2018 - only a technical issue though not content

    3. MCH confirmed that we can ignore this until hunter code in and this is a warning already...

  2. ISRS-225 -Descriptions that are incompatible with related concepts (RF1)
    1. RF1 issue for UKTC to confirm during upcoming Alpha/Beta testing
    2. Peter confirmed he's actioning this today, so will confirm once complete...
  3. ISRS-316 (tracking for ISRS-302)
    1. Should be resolved, just need to confirm nothing outstanding to action?
    2. Peter confirmed this ticket can be closed down, with some case sensitivty still to be completed under other tickets for Jan 2019
  4. ISRS-323 - CaseSignificance changes to be implemented for July 2018 International Edition
    1. Should be resolved, just need to confirm nothing outstanding to action?
    2. Andrew and Maria to test in this cycle and close down...
  5. ISRS-324 - Clinical finding 404684003 only approved defining attributes used - planned for July 2018 International Edition
    1. Should be resolved, just need to confirm nothing outstanding to action?
    2. Monica to confirm when completed....
  6. ISRS-327 - Minor issues in the MRCM Domain file - planned for resolution in July 2018 International Edition
    1. Linda Bird to confirm that she has completed the next step...
  7. ISRS-362 - Association Reference records
    1. Should be resolved, just need to confirm nothing outstanding to action?
    2. Andrew and Maria to regression test and close down...
  8. ISRS-366 (tracking for ISRS-206) - CaseSignificance changes that have yet to be implemented
    1. Peter's confirmed fixes now applied in Prod - Maria confirmed she's happy, so Andrew Atkinson to spot check in Int Edition validation
    2. Remainder logged as Known Issue for future release cycles
    3. Andrew to catch up with Yong and confirm if complete as yet?
  9. ISRS-367 (tracking for ISRS-145) - AttributeValue records with both and Active and Inactive record for the same content
    1. Michael Chu confirmed no fix implemented...can be implemented as published content we'll verify no new issues in regression testing for this cycle.
  10. ISRS-368 (tracking for ISRS-298) - Clinical finding 404684003 only approved defining attributes used
    1. Maria expecting to fix this for Jan 2019 - still the case or will this now make it into the July 2018 release?
      1. Monica to confirm when completed....

  11. ISRS-369 (tracking for ISRS-319) - Minor issues in the MRCM Domain file
    1. Linda Bird to confirm that she has completed the next step..
  12. ISRS-370
    1. Peter to confirm if this is resolved in https://jira.ihtsdotools.org/browse/DRUGS-510?

      If so, was this a recent fix as this assertion was still failing as of yesterday lunch time?

    2. Peter confirmed fix now gone into Main today, so Andrew to re-build and verify no further failures in RVF....

  13. ISRS-371
    1. Maria to confirm statusonce fixed today...
  14. ISRS-376
    1. Front end fix required to prevent future issues
    2. Historical issues require back end fix - Kai to pick this one up and resolveMaria to confirm status...
  15. ISRS-377
    1. Maria to confirm status...Historical issues require back end fix - Michael to pick this one up and resolve
  16. ISRS-378
    1. Peter and Michael working on this - proposal to create new Identifiers for July 2018 release...
    2. Also need to verify assertion is correct, otherwise may need an RVF updaet as wellMaria to confirm status...
  17. ISRS-380
    1. Michael logged ticket for this - see linked ticket

      This linked ticket is marked complete - can we therefore close this down as resolved? (if so why is RVF assertion still failing?)

    2. Michael to investigate and confirm what action is required...

  18. ISRS-381
      Maria to confirm status
      1. Peter confirmed fix now gone into Main today, so Andrew to re-build and verify no further failures in RVF....

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.

ACTION: EVERYONE to confirm if we need any further RVF assertions to cover potential known issues caused by new Drugs modelling ??????????????????????????

ACTION: We need to complete the traceability analysis for the TermServer export, to ensure that everything is being exported as expected. Andrew to raise a ticket track it and assign to Kai to keep us updated.

ACTION: We need to verify the new OWLAxiom refset - either we need to get the new assertions into Production RVF asap, or we need to create and run the validation in a manual script that we need to run this release. Andrew to raise ticket to track...

See section 2 for remaining current known issues...


7Versioning and Change Freeze

Everyone still fine with all dates on this...


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