Inactivate the root concept synonym referencing previous release, and add synonym to reference current release.
Update copyright date on synonym (January releases only)
Generate + Validate SEP Refsets
Generate + Validate Lateralizable Refset
Content Team to confirm to Release Manager that 4x MRCM refset files are complete and ready to be released (they are then extracted from the termServer during release builds via the termServer Export)
MBR - done manually in the front end - SNOMED Clinical Terms version: 20220630 [R] (June 2022 Release)
MBR - not required as only required in January releases...
Process has generated the data - post close report 19June2022
- Have the devops processes been updated to either run before versioning, or to run against 2 packages (as per Peter's note in the ticket)?
Maria is now running this report along with the others pre-versioning (but AFTER content cut off yesterday), so no need for devops to run this report anymore, as AAT will just use the report that Maria ran this morning.
FRI-376 - RefsetDescriptor - RDA confirmed we should just remove them from scope for now, so we’ve raised Dev ticket to fix automated process whilst we continue to generate them manually in the interim...
Traceability failures
Jira
server
IHTSDO JIRA
serverId
b202d822-d767-33be-b234-fec5accd5d8c
key
INFRA-8675
June 2022 release issues logged here
Jira
server
IHTSDO JIRA
serverId
b202d822-d767-33be-b234-fec5accd5d8c
key
INFRA-
8057
9168
NEEDS CONFIRMATION FROM Maria ON WHETHER FIXES HAVE BEEN APPLIED/ARE REQUIRED BEFORE PROCEEDING WITH THE VERSIONING NEXT WEEK - DONE
Latest run is closer than before - Peter now creating a manual block list for exceptions.
See where we are in tomorrow's Final Handover call
Lateralisable refset also being run through one last time as we speak - again will check back on that tomorrow
3
Content Validation
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.
Decision on whether to fix the issues:
VERY QUICKLY in time for this upcoming release?
In good time for the next monthly release?
Content Release Lead confirms to Release Manager that all Projects had automated validation run against them, and all issues identified were resolved before promotion - MBR confirmed all
done and nothing outstanding other than SEP + Laterality issues...
Feedback from Spain:
2 active descriptionshavebeenidentified as FSN but do notincludethesemantic tag in theterm:idtypeIdTerm590999016900000000000003001(Congenital) nipple: [small (& acquired)] or [hypoplasia]661545019900000000000003001Dependence: [cannabis (including marihuana)] or [hallucinogen]
Checked by MBR: The above concepts are both inactive with effective time 20020131, we will not amend the FSN on inactive concepts to include a semantic tag, please exclude active descriptions on inactive concepts from the validation feedback.
In thisedition210conceptshavebeendeactivatedwitheffectiveTime = 2021-10-31. In 5concepts, no correspondencewith alternative conceptsisreported in therefsetAssociation.ideffectiveTimeactiveterm216280052021-10-310Anesthesiaforprocedureson perineal integumentarysystem (procedure)318330012021-10-310Anesthesiaforprocedureson seminal vesicles (procedure)428710052021-10-310Anesthesiaforprocedureson labia, vagina, cervixorendometrium (procedure)4421540082021-10-310Dehiscenceofinternalsurgicalwound (disorder)4498630062021-10-310Insertionofpacemakerfor control of atrial fibrillation (procedure)
Checked by MBR:
Non conformance to editorial policy is a valid inactivation reason and does not require a historical association target, please see
Non-conformance to editorial policy No association required
Applies to a concept which does not adhere to the Editorial guidelines
AAT has responded to the Spanish NRC accordingly on 16/11/21
4
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.
November holidays?
done
MBR: Checked with Yong, no changes to MRCM for June 2022.
Still have traceability failures: All components in the branch traceability summary must also be in the RF2 export. All components in the RF2 export must also be in the branch traceability summary. confirmed false positives seeImage Added
Jira
server
IHTSDO JIRA
serverId
b202d822-d767-33be-b234-fec5accd5d8c
key
INFRA-8675
June 2022 traceability issues see above
Jira
server
IHTSDO JIRA
serverId
b202d822-d767-33be-b234-fec5accd5d8c
key
INFRA-9168
4
Mapping schedule
Chris confirmed today that we would not be able to get the new automated process up and running for this release cycle - therefore need to confirm that everyone is ready to continue with the old manual process for one more cycle?
Ready for testing but no need to rush this cycle - will be ready for May release...
1. First rundeck job will pickup the right date from the Release schedule, and then run the data import
2. Second rundeck job will be run by Maria (once Mapping tasks are complete), to add 2x new task id's into the job and generate the maps
5
Early visibility of Release Notes
NOVEMBER ONLY ACTION:Maria BraithwaiteandDonna Morganconfirmed we don't need these for the November release - instead they'll just log the change notes in their Trello board and add them into the Jan 2022 release when we get to it in December (Member Release).
Delta file showed most differences were due to 47 updated records in the Delta, in addition to that there was only one missing concept:
1196866006
Confirmed with Rick that this was a concept that was added to the content (therefore came through to mapping in the drip feed), and was then removed from the content before the monthly release!
Therefore should be missing from the Delta files - just should also be removed from Donna's manual counts (based on the drip feed) - she will work with Rick to get visibility of the Mapping QA report to remove these concepts from her counts
(see email trail at 16:24 on 15/2/2022)
Maria confirmed manual process went well again this month
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 ....
New Detailed Stats report (eg) ICD-10:
Total Changed mapped concepts this release 5 Total Changed mapped entries (new) this release 5 Total Changed mapped entries (retired) this release 4 Total New mapped concepts this release 341 Total New mapped entries this release 389 Total Retired mapped concepts this release 77 Total Retired mapped entries this release 78
So this "should" translate" to the following diff's in our Diff report:
Inactivations = 78 + 4 = 82
New/updated = 389 + 5 = 394
AAT to check real figures from PROD build on Sunday/Monday to confirm figures now all match up...
5
However, the new mapping schedule didn't work!
When WCI tried to upload the maps to the termServer, we hit a wall:
WCI do not have permissions to run swagger! Should we show Maria how to do it?
OR, CAN WE SET Authoring permissions on JUST THIS PROJECT for WCI each cycle??
Files MUST BE IMPORTED WITH BLANK EFFECTIVETIMES!! Otherwise we can't then export them from the termserver!
AAT has raised ticket to provide WCI with the relevant permissions from next release onwards for RMUP prohect ONLY - is this feasible?
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.
Maria confirmed all tickets complete
6
DevOps resource confirmed
Joe will be the resource for the June release...
8
7
Versioning and Change Freeze
Plan is to follow the new processes as now defined:
Peter confirmed reports will not be updated now, as most are based on Delta's, and once we've versioned the Delta files will be empty! So we need to check the original reports run by Maria (above) straight after her authoring checks were complete, and just manually take all of the latest fixes into account.
10
Risks
None raised
9
Risks
Timing of the Release validation on 21st in order to allow enough time after sign off to complete re-opening tasks for the AP before 5pm on 21st April as planned - meeting moved to 9:30am on 21st to give us as much time as possible...
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 Saturday drip feed, so shouldn't be a problem - agreed auto-job setup for 3am on Monday morning to catch any stragglers as well...
If we find issues during pre-versioning validation this has a knock on effect on the timing of DevOps' versioning
The main concern here is the visibility for the Content Team if we can't get them back up within the same day as planned
Therefore, if we get to 15:00 on the day of versioning and still cannot sign off the PreProd content, we need to let Maria know so that she can give the team plenty of notice that they won't be back in the tool until tomorrow at the earliest.