| | Items to be discussed | Actions |
|---|
| 1 | Prerelease Content Management Activities: - Verify that all namespace concepts (in the namespace registry) have been added
- Inactivate the root concept synonym referencing previous release, and add synonym to reference current release.
- Update copyright date on synonym (January releases only; N/A to July 2014)
- Send updated laterality indicator spreadsheet to technical team to support qualifier generation.
Content Team to deliver SE and SP refset files to Release Manager Content Team to deliver 4x MRCM refset files to Release Manager (just needs to confirm they're completed, downloaded + tested, AAT will then pull them out of the termServer during release builds via the termServer Export)
| - MBR - done verified with Yohani by email on.....
- MBR - done please see https://jira.ihtsdotools.org/browse/INFRA-5402
| Jira |
|---|
| server | IHTSDO JIRA |
|---|
| serverId | b202d822-d767-33be-b234-fec5accd5d8c |
|---|
| key | INFRA-6257 |
|---|
|
- MBR - NOT NECESSARY FOR JULY RELEASE!
ACTION: Yongsheng Gao to deliver lateralizable refset, as this now comes from the Refset tool ... AAT to receive from Yong on 24th May 2021 (Yong to download from Daily Build to provide provisional files) ACTION: Yongsheng Gao to deliver SE and SP files, AAT to receive from Yong on 24th May 2021 (Yong to download from Daily Build to provide provisional files) ACTION:Yongsheng GaoYong to confirm MRCM complete and can be used in current state?
AAT to then send the confirmed MRCM refsets to Ed Cheetham for external confirmation.... (STILL NEEDED???)
|
| 2 | Discussion of existing Known Issues from the previous Release | - ISRS-926 - we confirmed that this is a false positive and this concept was therefore whitelisted for this particular assertion, for the Jan 2021 Release cycle. Is it now resolved?
ISRS-928 - permanently whitelisted, no action required
- ISRS-930 - we confirmed that these are false positives, due to the records having been created and then versioned in November 2020, in preparation for the Jan 2021 release. However, they were then subsequently inactivated within the same release cycle, in order to fix errors in the new content - changes were therefore made to concepts that are brand new to this release and hadn't been Published yet. These 4 records were therefore temporarily whitelisted for this assertion, as they should not re-occur in the next cycle. AAT + MBR to verify no re-occurrence during this July 2021 release cycle...
- ISRS-931 - we confirmed that these are false positives, due to the records having been created and then versioned in November 2020, in preparation for the Jan 2021 release. However, they were then subsequently inactivated within the same release cycle, in order to fix errors in the new content - changes were therefore made to concepts that are brand new to this release and hadn't been Published yet. These 2 records were therefore temporarily whitelisted for this assertion, as they should not re-occur in the next cycle. AAT + MBR to verify no re-occurrence during this July 2021 release cycle...
- ISRS-933 - These were temporarily whitelisted in Jan 2021, pending further investigation into the classification of these and other concepts, with the aim to resolve any issues for the July 2021 International Edition. Resolved now?
- ISRS-935 - we confirmed that the use of occurrence = 282032007 |Periods of life (qualifier value)| is allowable and not constrained by the MRCM because it might be used as a grouper. The template has more refined constraints so the inclusion of 282032007 |Periods of life (qualifier value)| as a value for occurrence could be avoided in future through use of the proposed template. The MRCM will be reviewed to see if it could be refined however this would require thorough analysis as there may be some use cases where this value is acceptable (such as for grouper concepts). The concept 231956007 |Traumatic aniridia (disorder)| will be remodelled for the July 2021 release. This issue was therefore temporarily whitelisted pending resolution in the July 2021 cycle - resolved?
- ISRS-936 - we confirmed that these are valid issues, but were not critical enough to require action in time for the January 2021 release. A number of the attributes require further discussion regarding changes to the MRCM rules in consultation with the Device project group. The issue with modelling is of no obvious clinical risk, and therefore all issues were temporarily whitelisted pending resolution in the July 2021 International release with further enhancements to the validation rules requested. Resolved?
|
| 3 | Content Validation Activities in the Current Release cycle: - Concepts that have changed its high level hierarchy ancestor since last release
- Concepts with FSNs with changed semantic tags
- Active concepts with changed FSNs (check for shifts in meaning)
- Concepts *in*-activated since the last release
- Concepts *re*-activated since the last release
- Concepts that changed from fully defined to primitive
- Concepts that changed from primitive to fully defined
- New FSNs: Check for adherence to naming conventions, no acronyms, etc.
- Spell checking for new descriptions and/or manual inspection
- Review all new and changed text definitions
- Additions/removals of members of VMP refset (Inactive concepts still in the VMP refsets are removed during release extraction)
- Additions/removals of members of VTM refset (Inactive concepts still in the VTM refsets are removed during release extraction)
- Verify that there have been no changes to the Non-human refset in the Workbench.
- Additions/removals of members of ICD-O simple map refset (Inactive concept still in the ICDO map are removed during release extraction)
- Active concepts having active historical associations and reasons for inactivation
| MBR has been analysing the Daily Build RVF results for the past few weeks, and working with Peter to clear down the failures. Early Alpha run by AAT 11th May 2021: MBR will share content report with team when it is ready. |
| 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. | Maria + Yong + Donna will all be around to support wherever needed |
| 5 | Early visibility of Release Notes
| Andrew Atkinson has created the template to update on Confluence: SNOMED CT July 2021 International Edition - SNOMED International Release notes - content team to update with relevant data for July 2021 content..... ACTION: Maria Braithwaite and Donna Morgan will kindly aim to get them to Andrew Atkinson by 24th May 2021 ACTION: Monica Harry and Paul Amos to review and approve once complete |
| 6 | 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. | Content (Maria): Concrete Domains: |
| 7 | Versioning and Change Freeze | Plan is to follow the new process as defined last cycle: Technical Team Release tasks - July 2021
|
| 8 | Stats Report | MBR has been using the Daily Build QA report for stats and has the information needed for release notes. Release Reports run via the reporting platform: Concepts changed : Concepts inactivated : New components : Release stats : HOWEVER, should we focus on the Summary Component stats report now, as with MS products, in order o ascertain Intention of the authoring cycle vs real data actually contained in the Release files? |
| 9 | Risks | - Concrete Domains?
- VACCINE WORK COMING IN LATE AGAIN?
|
| 10 |
|
|