Date of Initial Handover meeting: 10 July 2025

Date of Final Handover meeting: 15 July 2025

Attendees



Handover Status



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. SNOMED Clinical Terms version: 
  2. Copyright date on synonym - not required for August release.
  3. SEP - 
  4. Laterality - 
2

Known issues

SP ref set missing members, needs change to rule  

3.

New validation/traceability 


4.

MRCM changes

No new changes for August 2025 release.

New and changed MRCM report 

Requested update to New and Changed MRCM report

5.

Content Validation Reports

  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?
6.Mapping schedule

June 2025 Release

  • ICD-10
    • 167 New concepts in release cycle as of 8th May
    • 2 Reactivated concepts in release 
    • 985 Published concepts QA'd in total
  • ICD-O
    • No new activity in the ICD-O map this month

July 2025 Release

  • ICD-10
    • 815 New concepts in release cycle as of 8th May
    • 3 Reactivated concepts in release 
    • 3671 Published concepts QA'd in total
  • ICD-O
    • No new activity in the ICD-O map this month

Other Mapping Business

  1. Rick to pull out report of 950 odd final QI changes still need to be reviewed - Donna will complete this in the next editing cycle (August 2025).
  2. Rick will also free up 1x final concept in Donna's workflow.
  3. .
  4. GMDN:
    1. Previously we were working towards mapping dependencies of Jan(INT)+Jan(GMDN) / July(INT)+July(GMDN).  However, the transition to publishing the INT Edition on 1st of the month means that the mapping team can no longer get the GMDN Jan/July releases mapped in time for the new 1st of the month INT Edition releases, as they only have a couple of days between the GMDN file dropping and the cut off for the INT Edition!
    2. We've got a couple of potential ways forward:
      1. We can start talking about pushing back the INT Edition timelines slightly, to work in the 3rd week of the month instead of the 2nd week.  This might give the mappers enough time to map the latest GMDN release and still aim for a Jan+Jan / July+July dependency?
      2. Or we can just revert back to our previous dependencies of Jan(INT)+Dec(GMDN) / July(INT)+June(GMDN) ? 
        1. (in which case we just need to discuss the naming conventions that GMDNA use for their releases, as it's not clear if the file they give us at the start of June for example, is what they call their "May" or "June" release) 
        2. We'd then have to update Release Notes and possibly the MDRS file in the GMDN package as well?
    3. AAT to discuss with Suzy and revert...
7.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.

Annotation inactivated for the first time 20250605 Inactivated annotation.tsv

AAT to cross check still inactive in final PROD release...


8.DevOps resource confirmed

Joe

9.Versioning and Change Freeze

Release schedule

July 2025 International Edition Release Schedule - Production Monthly Release - INTERNAL

10.Stats Report

Summary Component Stats Report

https://docs.google.com/spreadsheets/d/10EaHem3GdkZxIRia49LOSkKKVj5RUp0HUm3gFxPmjpU/edit?usp=sharing

11.Risks

RICK STILL HAVING TO MANUALLY BOUNCE MYSQL DUE TO THE SWAP SPACE STILL FILLING UP DURING THE OVERNIGHT JOBS...

Chris is going to increase the SWAP space in the meantime, and open a ticket to investigate root cause in the long term...  Some changes made in May 2025...

5th June 2025 - SWAP size still creeping up, so we'll check it again this cycle and see if any other action required...

6th June 2025 - System came back online around 8:30am, so job seems to be back to running at roughly the normal time, so we will just continue to keep an eye on it for now...

12.AOB

Release notes

SNOMED CT July 2025 International Edition - SNOMED International Release notes

Timescale for transition to using RNMS.