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: 20221130 [R] (November 2022 Release)

2. MBR - not required as only required in January release.

3. Process has generated the data -   post close report 11 November 2022

   1. https://docs.google.com/spreadsheets/d/1-u-8pAsQaI2fkER4XbK4ogtxjc65rPnM0NcYZZAAeYk/edit#gid=1

4. Process has generated the data - post close report 11 November 2022

   1. https://docs.google.com/spreadsheets/d/1-u-8pAsQaI2fkER4XbK4ogtxjc65rPnM0NcYZZAAeYk/edit#gid=2

NOTE: report of missing concept from laterality reference set see https://snomed.atlassian.net/browse/MAINT-2077

@Darryn McGaw - investigating this concept, and also any other missing concepts from the Laterality automation...

2

Discussion of existing Known Issues from the previous Release

1. Traceability issues for November 2022 release logged here https://snomed.atlassian.net/browse/INFRA-9804 all false positives confirmed by Michael. NOTE no failures in the AP validation or the daily build validation, there is a ticket remaining to resolve issues with traceability https://snomed.atlassian.net/browse/FRI-533

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

2. MRCM: Checked with Yong - NO CHANGES for November 2022 release.

3. Ref set description changes November 2022 release - no new descriptions seen in descriptions file https://docs.google.com/spreadsheets/d/1GR4ttlSWQfmo7dln81cnCWu-Js_9ztD6dENYC0Qoh9I/edit#gid=0

4

Mapping 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 ISRS-1302: Assertion Failure: Active extended maps should not have the same mapTarget and mapRule in different groups for a given referenced componentOn Hold

    • As expected, this was the only mapping failure in the preProd validation :  https://prod-rvf.ihtsdotools.org/api/result/1660553489556?storageLocation=international/international_edition_releases/2022-08-15T08:26:46

• Upload of mapping content to 2x branches planned for Friday 12th this cycle...

September 2022:

• ICD-0 - no changes expected

• ICD-10 - expecting 300 ish changes due to large number of intentional inactivations this cycle

• No expected issues this cycle...

October 2022:

• ICD-0 - 1 new record + 2 inactivations expected

• ICD-10 - expecting 478 ish changes (plus tonight's drip feed) due to large number of intentional inactivations this cycle

• No expected issues this cycle...

  • Confirmed in final numbers!

November 2022:

• ICD-0 - 3 or 4 new record + 10 inactivations expected

• ICD-10 - expecting 30 ish changes (plus tonight's drip feed) due to large number of intentional inactivations this cycle

• No expected issues this cycle...

  • Confirmed in final numbers!

***** NOTE:  Make sure that we keep an eye on the upgrade to ICD-0 version 3.2, as it will need to happen at some point in 2023 *****

5

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.

6

DevOps resource confirmed

7

Versioning and Change Freeze

Plan is to follow the new processes as now defined:

• PROVISIONAL - November 2022 International Edition Release Schedule - Production Monthly Release - INTERNAL

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

HIGH LEVEL KEY MILESTONES:

• 10/11/22 - All content and mapping complete and signed off by close of play

• 15/11/22  - AAT to build PreProduction (unversioned) and sign off before 15:00 on 18th, otherwise decision made to postpone versioning

• 16/11/22 -  Versioning to begin first thing + related issues to be completed and resolved by 17:00

8

Stats Report

Reports run via the reporting platform:

• Summary Component stats for edition post close 11 November 2022

  https://docs.google.com/spreadsheets/d/1k20AnlS_qA3P6lIwDCki47m9XifpNmTBpXSOJtEWFRA/edit#gid=0

9

Risks

1. NOVEMBER 2022 - Need to ensure that Rick + Terance have resolved the issues from Sept release, whereby the username/password for the auto-jobs were switched around and so failed.  Ensure that this is resolved before 00:01 11th November when next jobs set to run

2. CLOSE DECEMBER 22 IF NO FURTHER ISSUES...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 2:20am 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

   2. STILL AN ISSUE??? NO THIS IS MITIGATED BY THE MOVE OF THE AUTO JOB TO 02:20 on FRIDAY - Can THEREFORE remove from October onwards

10

AOB