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

« Previous Version 13 Next »

Date of Initial Handover meeting: 11th August 2022

Date of Final Handover meeting: 16th August 2022

Attendees

Handover Status

INITIAL HANDOVER COMPLETE

Agenda


 

Items to be discussed

Actions

1

Prerelease Content Management Activities:

  1. Inactivate the root concept synonym referencing previous release, and add synonym to reference current release.
  2. Update copyright date on synonym (January releases only)
  3. Generate + Validate SEP Refsets
  4. Generate + Validate Lateralizable Refset


  1. MBR - done manually in the front end -DONE - SNOMED Clinical Terms version: 20220831 [R] (August 2022 Release)
  2. MBR - not required as only required in January release.
  3. Process has generated the data -  pre close report 11 August2022

    1. https://docs.google.com/spreadsheets/d/1VGepsbIeasxOO4yFZdZ_AeOnpE9iUBF-HrFrmaWP7JE/edit#gid=1

  4. Process has generated the data - pre close report 11 August2022

    1. https://docs.google.com/spreadsheets/d/1VGepsbIeasxOO4yFZdZ_AeOnpE9iUBF-HrFrmaWP7JE/edit#gid=2

***** LATERALIZABLE REFSET AUTOMATION IS NO LONGER WORKING - Maria is asking Darryn to run it manually for now, until the problem can be permanently resolved in FRI-477 - Getting issue details... STATUS *****

2

Discussion of existing Known Issues from the previous Release

  1. Traceability failures  INFRA-8675 - Getting issue details... STATUS  July 2022 release issues logged here INFRA-9209 - Getting issue details... STATUS  confirmed by Michael as false positives.
  2. Traceability failures for August 2022 release logged here 

    https://jira.ihtsdotools.org/browse/INFRA-9362

    https://jira.ihtsdotools.org/browse/INFRA-9389

    https://jira.ihtsdotools.org/browse/INFRA-9388 and confirmed as false positives.

3

Content Validation 

  1. Instead of usual manual Content validation, we now just need confirmation that all Projects had automated validation run against them, and were clean before promotion.
  2. New Issues identified by the community from the previous Monthly Release.
    1. Decision on whether to fix the issues:
      1. VERY QUICKLY in time for this upcoming release?
      2. In good time for the next monthly release?


  1. Content Release Lead confirms to Release Manager that all Projects had automated validation run against them, and all issues identified were resolved before promotion. 
  2. MRCM: Checked with Yong - 
  3. Association Records not transferring through to the RF2 files as expected https://jira.ihtsdotools.org/browse/ISRS-1271
    1. AAT to validate all correct in the final AUGUST 2022 release...

 4. Ref set description changes August 2022 release - MBR no changes identified via descriptions file.


4Mapping schedule

April 2022:

  • Donna ran new report that Rick created to double check no invalid mappings, all clean now
  • Mark/Donna to complete mapping on Monday

June 2022:

  • Rick to confirm whether or not the difference in the Deleted record count (in the new automated mapping stats report) is anything to be concerned about ....

July 2022:

  • ICD-0 - very few changes expected
  • ICD-10 - expecting 1000+ changes due to large number of intentional inactivations this cycle

August 2022:

  • ICD-0 - very few changes expected
  • ICD-10 - expecting 320+ changes due to large number of intentional inactivations this cycle
    • Donna flagged up a potential issue where one concept (1231691008) is mapped to two same codes - so it will look like a duplicate to our validation - but we can safely whitelist it as an intentional change within the spec of ICD-10
  • Upload of mapping content to 2x branches planned for Friday 12th this cycle...


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



6DevOps resource confirmedTerance will be the resource for the August release...
7Versioning and Change Freeze

Plan is to follow the new processes as now defined:

AAT walked through and agreed new process with DevOps already, so unless there are any further questions/issues??

AAT to sign off PreProduction (unversioned) build before 09:00 on 17th August, and then:

  • Versioning + related issues to be completed and resolved as of 17:00 on - 
8Stats Report

Reports run via the reporting platform:

9Risks
  1. Intermittent problems with the 12am Daily Build have been caught by backup 2am Daily Build run so far, BUT could in theory run into problems with the mapping drip feed that also runs at 2am.  However, this should be mopped up by the Friday drip feed, so shouldn't be a problem - agreed auto-job setup for 3am on Friday morning each cycle to catch any stragglers as well...
    1. Another minor issue though with this is moving the auto-job to 3am results in a clash with the drip feed - Rick has submitted a ticket (INFRA-9419) to discuss potential long term options for automation in order to circumvent this issue
10AOB




  • No labels