Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
SNOMED Spaces
/
Content Handover Meeting minutes - July 2025 International Edition
For info only https://jira.ihtsdotools.org/browse/INFRA-15212 After the Q2 deployment, start a new authoring cycle for each CodeSystem on the Authoring Platform. This is to have their MDRS entries updated to prevent any false positive validation failures.
Lateralizable ref set https://jira.ihtsdotools.org/browse/INFRA-15220Delta import to fix 723264001 Lateralizable body structure reference set| data out of sync with published release file in authoring platform.
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.
New Issues identified by the community from the previous Monthly Release.
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).
Rick will also free up 1x final concept in Donna's workflow.
.
GMDN:
Previously we were working towardsmapping 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!
We've got a couple of potential ways forward:
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?
Or we can just revert back to our previous dependencies of Jan(INT)+Dec(GMDN) / July(INT)+June(GMDN) ?
(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)
We'd then have to update Release Notes and possibly the MDRS file in the GMDN package as well?
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.
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...