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- please see
MBR - not required as only required in January releases...
Process has generated the data - AAT to cross check against report MBH sent:
Report shows 342 changes - 9 new records + 9 inactivations + 324 updates
SimpleRefset Snapshot in Feb release shows 342 records with 20220228 effectiveTime - 333 new/updated records + 9 inactivations
Peter G. Williams to generate + Yong to also create it the old way + compare to ensure valid...
????Yong/Peter to generate Daily build and deliver by ????
Yong confirmed he will try to follow the deadlines for the monthly releases -
No expected MRCM changes for the January February 2022 release ...- as confirmed by MBH
2
Discussion of existing Known Issues from the previous Release
ISRSMSSP-1112 - 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.
ISRS-1120 - SEP issues - resolved now? 32 issues remain, exception listing requested for 26 of these issues see
Jira
server
IHTSDO JIRA
serverId
b202d822-d767-33be-b234-fec5accd5d8c
key
INFRA-8057
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
1357 - Peter fixing in a task branch on 11/2/22, Maria to test and promote - AAT to regression test in Prod ReleaseBEFORE VERSIONING
Testing Complete and signed off
INFRA-8398 - Traceability failures - MCH confirming if they’re all false positives…BEFORE VERSIONING
Complete - Michael confirmed all false positives
INFRA-8402 - RefsetDescriptor - RDA confirmed we should just remove them from scope for now, so I’ve raised Dev ticket to exclude them automatically
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?
4
Mapping schedule
Donna confirmed she's happy with the schedule, and they're also already up to date with the final content.
Mapping process delivered ICD-0 + ICD10 files to AAT on time this cycle
Did mapping process work well this time?? Yes, process was good
HOWEVER, the counts don't match Donna's manual counts exactly, so we will investigate further:
ICD-0 = Manual mapping count = 4 new records, only 3 new records coming through in Delta files
ICD-10 = Manual mapping count = 477 new records, 485 new records coming through in Delta files
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)
5
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).
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.
86
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.