Yong to download Daily build and deliver by Friday 20th
Yong to download Daily build and deliver by Friday 20th
Maria confirmed all good + Yong confirmed all requests agreed for next cycle.
2
Discussion of existing Known Issues from the previous Release
Jira
server
IHTSDO JIRA
serverId
b202d822-d767-33be-b234-fec5accd5d8c
key
ISRS-806
- Checked before close of editing, content issue is resolved
Jira
server
IHTSDO JIRA
serverId
b202d822-d767-33be-b234-fec5accd5d8c
key
ISRS-809
- All resolved we have a validation rule in the RVF report for this now, 17 issues found and resolved, no issues in RVF report today.
Jira
server
IHTSDO JIRA
serverId
b202d822-d767-33be-b234-fec5accd5d8c
key
ISRS-688
-https://jira.ihtsdotools.org/browse/ISRS-605 relates to the US extension, the ticket we have relating to the International release is https://jira.ihtsdotools.org/browse/ISRS-575 with a failure count of 1716. I have checked a sample of the attached file, the issue is the same, the concepts are marked fully defined by virtue of their stated IS_A relationships which was in the past acceptable, editorial policy has subsequently changed and we now require a proximal primitive parent and the addition of attribute and value pairs. These modelling issues are being addressed by the QI project in many cases using template based editing, no changes required at present. Can we close this down then?? Yes everyone on the call agreed to resolve the ticket and confirm that the QI project will resolve these outstanding issues over the next few cycles
Jira
server
IHTSDO JIRA
serverId
b202d822-d767-33be-b234-fec5accd5d8c
key
ISRS-807
-As discussed with the technical team, this may require changes to the existing classification service. Further investigation and evaluation are needed before we can implement the changes in production. It is not possible to make the changes for this release. The plan is to address this issue for the July 2021 release. We will update the ticket when the progress has been made. Agreed by everyone on the call to be carried over to July 2021 as too high risk to make classifier changes now - will be planned in for next cycle.
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
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 and Yong will
all
be around
to support wherever needed Donna and Yong on leave at present (8 Nov 2019)
INFRA-4197 - 147,000+ issues, needs change to assertion to allow self grouping, no editing changes needed.
ISRS-562 - Finding with explicit context| concepts using |Associated Procedure| attribute - editing issue resolved.
ISRS-563 - 8 concepts using |Surgical approach| that are not subtypes of |surgical procedure| - editing issue resolved.
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.
Mapping: 8 Nov 2019 Donna is on leave today she sends this update:
Technical QA has started. SNOMED has been reloaded and 1 concept has been identified as needing a map in the ICD-10 project - Drip feed must not have picked it up. The concept 32941000119104 Ingestion of toxic substance (disorder) has been mapped and WCI can re commence the release work. GMDN and ICD-O have been completed and WCI notified. Both projects will need to pass technical QA but nothing to report so far.
7
Versioning and Change Freeze
KAI has run some manual checks for missing descriptions - no issues found.
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 (like
Jira
server
IHTSDO JIRA
serverId
b202d822-d767-33be-b234-fec5accd5d8c
key
ISRS-921
, etc) into account.
9
Risks
Kai - After versioning need to take care when rebasing some projects that still have content on them as never done before on this terminology server and may find strange behaviour - mitigation: Kai will do the rebasing after we have versioned. This will be done before editing reopens.
None raised
10
AOB
Release schedule task for today - Content Release Lead to request (via Infra ticket) the maintenance screen to be raised in Production, to prevent further updates to International content
Jira
server
IHTSDO JIRA
serverId
b202d822-d767-33be-b234-fec5accd5d8c
key
ISRS-921
still needs to be resolved - Maria will implement in a fix branch off RFBJAN21 and AAT will regression test (as feedback_fix release type) once complete.