Page tree
Skip to end of metadata
Go to start of metadata


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)
  • Michael Chu (MCH)
  • Peter Williams (PWI)

Apologies

  • Rory Davidson (RDA)
  • Lesley MacNeil (LMA)
  • Kai Kewley (KKE)

Handover Status

COMPLETE

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 - 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 ... 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 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.  Complete and results sent to Maria for verification....

ACTION: Maria has shared the 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, via email at 16:51 on  

 

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 - done, Lesley signed off on 5/6/2018

ACTION: Lesley MacNeil and Paul Amos to review and approve once complete... - AAT already addressed some of Paul's feedback on the technical sections - Maria has also addressed his feedback on the content sections

 

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

  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 G. Williams confirmed he's actioning this today, so will confirm once complete...
    3. Peter G. Williams conifrmed that he has resolved and closed the ticket
  3. ISRS-316 (tracking for ISRS-302)
    1. Peter confirmed this ticket can be closed down, with some case sensitivty still to be completed under other tickets for Jan 2019
  4. ISRS-321 -
    1. Need to re-run the report and verify pre-versioning, to ensure no further issues - Kai Kewley agreed to action
    2. Maria confirmed resolved - any further action required? No
  5. 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. Maria Braithwaite to verify in this cycle and confirm to AAT, who will then double check in final package testing

    3. Yong confirmed no action to be taken until January 2019 cycle - we need to create a new report to be run throughout next cycle to continue cleanup...

  6. 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 Harry to confirm when completed....
    3. Peter confirming now all sorted...
    4. AAT to regrssion test and close
  7. 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...
    2. Maria Braithwaite to incorporate the new HRCM testing into all future Release cycles, to ensure that going forward any similar issues are picked up much earlier in the cycle.
    3. Andrew and Maria to agree the plan for testing... (AAT to setup a call with David to discuss whether or not he's updated the HRCM)...
    4. Maria to confirm if she can now use HRCM to validate these type of issues...
  8. ISRS-362 - Association Reference records
    1. Should be resolved, just need to confirm nothing outstanding to action?
    2. Maria Braithwaite has confirmed resolved, so AAT to double check in final package testing
  9. 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. Yong confirmed no action to be taken until January 2019 cycle - we need to create a new report to be run throughout next cycle to continue cleanup...

  10. 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 can be implemented as published content we'll verify no new issues in regression testing for this cycle.
    2. Michael Chu to confirm which RVF assertion would be failing if new instances of the issue were failing, so AAT can verify in final testing...
    3. AAT found the assertion, and confirmed no new failures in this cycle!
    4. Therefore just need to set the 193 pairs as a permanent Known Issue on the Release Management site
  11. 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 Harry to confirm when completed....
      2. Peter confirming now all sorted...
        1. AAT to regrssion test and close
  12. ISRS-369 (tracking for ISRS-319) - Minor issues in the MRCM Domain file
    1. Linda Bird confirmed that she has completed
    2. AAT to verify in Alpha/Beta testing...
  13. 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 Atkinson to re-build and verify no further failures in RVF....

  14. ISRS-371
    1. Maria Braithwaite to confirm once fixed today...
    2. Resolved
  15. ISRS-376
    1. Front end fix required to prevent future issues
    2. Historical issues require back end fix - Michael Chu to pick this one up and resolve, Maria to review to ensure corect
    3. AAT to regrssion test and close
  16. ISRS-377
    1. Historical issues require back end fix - Michael Chu to pick this one up and resolve, Maria to review to ensure corect
    2. AAT to regrssion test and close

  17. ISRS-378
    1. Peter G. Williams and Michael Chu working on this - proposal to create new Identifiers for July 2018 release...
    2. Peter G. Williams will verify assertion is correct, otherwise may need an RVF update as well...
    3. Confirmed resolved, ready to test in Alpha/Beta...
  18. 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 Chu to investigate and confirm what action is required...

    3. Confirmed resolved, ready to test in Alpha/Beta...

  19. ISRS-381 - New inactive states follow active states in the CONCEPT snapshot.
      1. Peter confirmed fix now gone into Main today, so Andrew Atkinson to re-build and verify no further failures in RVF....

      2. Resolved

  20. ISRS-382 - Complete the traceability analysis for the TermServer export

    1. Ticket assigned to Kai, who will add all info and assign to relevant developer

    2. Rory confirmed complete and all fine

  21. ISRS-350/ISRS-383 - Verification of the new OWLAxiom refset

    1. Kai to write the assertion in DROOLS and pass the standalone DROOLS validation over to Andrew to run on desktop for this release until Huy can automate for next release.

    2. ANY PROGRESS ON DROOLS??

    3. Still no autmoated way to run the DROOLS validation, so...

    4. AAT to ask Kai to run the DROOLS validation manually against the final Alpha build on Monday 21st...

    5. Deferred to Jan 2019 - will continue to run manually for July 2018

  22. ISRS-384 - DROOLS assertion failure: Active concept parents should not belong to more than one top-level hierarchy.

    1. Ticket assigned to Toni, who will resolve the issues shortly...

    2. Maria confirmed Toni resolved this issue

      AAT to regression test in final Alpha/Beta builds...


  23. ISRS-385 - DROOLS assertion failure: An active concept must not have two relationships with the same type, target and group. The duplicate can be an inactive relationship that should be reactivated, or an unreleased new relationship that should be deleted.

    1. Ticket assigned to Maria, who is resolving the issues now...

    2. AAT to verify in final builds...

    3. Awaiting confirmation of actual changes made by Maria/Toni......


  24. INFRA-2320 - Getting issue details... STATUS - Michael Chu to pickup and run report for Maria

    1. Maria confirmed resolved

  25. ISRS-286 - Andrew Atkinson to run DROOLS standalone validation against Snapshot once Kai has provided updated version - this will give Maria historical report against this issue

    1. ANY PROGRESS ON DROOLS??

    2. Maria confirmed resolved due to new DROOLS rule to find any new issues, plus Kai's report covering off any historical issues

  26. ISRS-260 - Andrew Atkinson to run DROOLS standalone validation against Snapshot once Kai has provided updated version - this will give Maria historical report against this issue

    1. ANY PROGRESS ON DROOLS??

    2. Maria confirmed resolved due to new DROOLS rule to find any new issues, plus Kai's report covering off any historical issues

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.
  1. ACTION: Peter G. Williams to confirm if we need any further RVF assertions to cover potential known issues caused by new Drugs modelling?
    1. NO - SO ANDREW TO KEEP IN TOUCH WITH Peter G. Williams, WHO WILL CONTINUE TO RUN MANUAL VALIDATION REPORTS AGAINST THE DRUGS BRANCH UP UNTIL THE CUT OFF AND VERSIOING ON 9th May, AND THEN WE MAY NEED TO RUN THEM AGAIN AGAINST THE RELEASE BRANCH FROM THAT POINT ONWARDS IF ANY DRUGS FIXES NEED TO BE IMPLEMENTED DURING HTE ALPHA/BETA CYCLE...


    2. AAT to ask Peter to run the final validation manually against the final Alpha build on Monday 21st... done, Peter confirmed clean

    3. AAT also sent Beta to Peter for final testing at 18:38 on 5/6/2018 - Peter confirmed no further testing required


  2. ACTION: Maria Braithwaite to confirm with Farzaneh/Suzanne whether or not any LOINC issues need to be resolved before versioning, depending on volume and complexity/....


    1. They responded yes, but Michael confirmed report all clear and therefore no issues to resolve for LOINC

  3. ACTION: Peter G. Williams to run one off DROOLS run for case sensitivity to ensure all historical records validated as well as new ones - Peter will confirm ,to Maria if anything needs resolving....Maria has resolved all new issues, and does not believe there's any point in running historical issues as we know they're there and can't be fixed until we have confirmation on the final direction for case sensitivty...

  4. ACTION: Maria Braithwaite would like to disable all project on Friday 4th May - She will ask Rory when ready to disable... done


To keep an eye on as we proceed:

  1. Rory found a concept that had been unintentionally inactivated - it looked at first as if this was an automation issue, in the sense that SnowOwl had inactivated a concept off the back of a merge without having been instructed to do so. However, on investigation this was proven to not be the case, with user error being cited as the rot cause. It's worth keeping an eye on all inactivations throughout the cycle however, and myself and Maria will continue to run some spot checks at various points to ensure nothing looks wrong.


See section 2 for remaining current known issues...

Mapping:

  • Hi Andrew, Quick update for tomorrow as discussed. The drip feed has now been inactivated and all maps for the July 2018 release have been mapped and reviewed and pushed to publication. I have raised a JIRA ticket MAP-1578 for Rick WCI to commence the validation with a view to handover to delivery services when completed. If I have anything further I will keep you updated.


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. Maria confirmed all re-tested and passed, via email at 15:30 on 6/6/2018.

9Risks

No known risks! Everyone comfortable so far...





  • No labels