June 2022 PreProduction (Version 20) vs June 2022 Production (Version 2) traceability
Differences found in package Comparison | Number of RF2 records impacted | Related JIRA ticket(s) | Rationale |
---|---|---|---|
Language files (EN) | 0 | 0 Changes AS EXPECTED!!! Fixed in ISRS-1267 | |
Description files (EN) | 0 | ISRS-1267 | 0 Changes AS EXPECTED!!! Fixed in ISRS-1267 |
Description files (fr_ch) | 0 | ISRS-1267 | 0 Changes AS EXPECTED!!! Fixed in ISRS-1267 |
June 2022 PreProduction (Version 20) vs June 2022 Production (Version 1) traceability
Differences found in package Comparison | Number of RF2 records impacted | Related JIRA ticket(s) | Rationale |
---|---|---|---|
Language files (EN) | 7 | 7 new records added - NOT AS EXPECTED!!! Fixed in ISRS-1267 | |
Description files (EN) | 4 | ISRS-1267 | 4 new records added - NOT AS EXPECTED!!! Fixed in ISRS-1267 |
Description files (fr_ch) | 2 | ISRS-1267 | 2 new records added - NOT AS EXPECTED!!! Fixed in ISRS-1267 |
June 2022 PreProduction (Version 18) vs June 2022 PreProduction (Version 20) traceability
Differences found in package Comparison | Number of RF2 records impacted | Related JIRA ticket(s) | Rationale |
---|---|---|---|
ModuleDependency files | 3 | 3 records had their effectiveTimes updated to the new 20220331 version of the Common French release, which this June 2022 CH release was based upon: < 7321d59a-986d-4496-9cf8-874022470ad5 20220607 1 11000241103 900000000000534007 900000000000012004 20220607 20220331 < b3c09a5c-496c-48d7-808a-166f2b6a3c97 20220607 1 11000241103 900000000000534007 900000000000207008 20220607 20220331 < dc968531-82da-4aeb-bf59-3ae96cf71dd7 20220607 1 2011000195101 900000000000534007 11000241103 20220607 20210930 |
June 2022 PreProduction (Version 9) vs June 2022 PreProduction (Version 18) traceability
Differences found in package Comparison | Number of RF2 records impacted | Related JIRA ticket(s) | Rationale |
---|---|---|---|
AttributeValue files | 29 | ISRS-1257 | 29 records updated from 1217318005 | Grammatical description error (foundation metadata concept) | to 900000000000485001 | Erroneous component (foundation metadata concept) | ...as expected due to the fixes made in ISRS-1257 |
Language Refset (fr-ch) files | 2634 | ISRS-1264 | 52 records updated from 900000000000548007 | Preferred (foundation metadata concept) | to 900000000000549004 | Acceptable (foundation metadata concept) | + 2558 records added into the Full + Snapshot files, as expected due to fixes in ISRS-1264 to include ALL fr-ch records in the new release package (by spoofing the previousPublishedPackage) |
Description (fr) files | 3435 | ISRS-1263 | 3435 records added into the Full + Snapshot files, as expected due to fixes in ISRS-1263 to include ALL fr-ch records in the new release package (by spoofing the previousPublishedPackage) |
Relationship files | 1 | 1 new record added in: > 11000241126 20220331 0 11000241103 11000241103 900000000000443000 0 116680003 900000000000011006 900000000000451002 On investigation and manual comparison of the files, the Snapshot files are fine. It's just the latest Full file which contains an extra record where this relationship is first inactivated in the Common French module, before the Swiss module: 11000241126 20211207 1 11000241103 11000241103 900000000000443000 0 116680003 900000000000011006 900000000000451002 This isn't a critical issue (as the correct final Swiss inactivation still takes priority due to the effectiveTimes), this can be safely ignored. | |
TextDefinition files | 1 | 1 new record added in: > 1020231000241112 20220331 1 11000241103 77386006 fr 900000000000550004 Patiente enceinte actuellement 900000000000017005 Confirmed that this is definitely a new record added into both Full/Snapshot files for version 18. This is a Common French term, and so must have been added when we changed the dependency of this June 2022 Swiss release from the 20210930 Common French release, to the 20220331 Common French release package. |
June 2022 PreProduction (Version 8 PLUS MSSP-1519) vs June 2022 PreProduction (Version 9) traceability
Differences found in package Comparison | Number of RF2 records impacted | Related JIRA ticket(s) | Rationale |
---|---|---|---|
ModuleDependency files | 2 | 2 records updated: < b3c09a5c-496c-48d7-808a-166f2b6a3c97 20211207 1 11000241103 900000000000534007 900000000000207008 20211207 20210731 < dc968531-82da-4aeb-bf59-3ae96cf71dd7 20211207 1 2011000195101 900000000000534007 11000241103 20211207 20210930 However, no mention of removing the previous invalid records, so running comparison of ModuleDependency file from Version 9 against original December 2021 release: < 36ddb438-742a-4c97-9dca-b95489b6a08a 20211207 1 2011000195101 900000000000534007 900000000000207008 20211207 20210731 < 7321d59a-986d-4496-9cf8-874022470ad5 20211207 1 11000241103 900000000000534007 900000000000012004 20211207 20210731 < a4fbf40a-73ae-4e51-80da-cddc448d3a32 20211207 1 2011000195101 900000000000534007 900000000000012004 20211207 20210731 < b3c09a5c-496c-48d7-808a-166f2b6a3c97 20211207 1 11000241103 900000000000534007 900000000000207008 20211207 20210731 < dc968531-82da-4aeb-bf59-3ae96cf71dd7 20211207 1 2011000195101 900000000000534007 11000241103 20211207 20210930 LOOKS GOOD! Manual checks of SNapshot + Full also look good! Looks like the previous comparison was actually to Version 8 (NOT Version 8 plus MSSP-1519) and so most of these issues were already fixed! However, the Version 8 plus MSSP-1519 was also flawed, as the following 2 lines were not correctly updated by the automation code: b3c09a5c-496c-48d7-808a-166f2b6a3c97 20211207 1 11000241103 900000000000534007 900000000000207008 20211207 20210731 So I still needed to manually update the ModuleDependency file this cycle, as I did from version 9 onwards... |
December 2021 Production (PUBLISHED) vs June 2022 PreProduction (Version 8 PLUS MSSP-1519) traceability
Differences found in package Comparison | Number of RF2 records impacted | Related JIRA ticket(s) | Rationale |
---|---|---|---|
RefsetDescriptor files | 2 | MSSP-1518 | 2 records added, denoting 1 new refset as expected ???? > 1ca3e72a-71ee-436d-9c06-e47e0db53185 20220607 1 2011000195101 900000000000456007 22241000195100 900000000000510002 900000000000462002 0 Checking with Pero in MSSP-1518 that this language refset addition is expected... |
ModuleDependency files | 5 | 3 records had their UUID's replaced, BUT ALSO HAD DUPLICATE RECORDS ADDED (presumably by the automated ModuleDependency code): < 36ddb438-742a-4c97-9dca-b95489b6a08a 20211207 1 2011000195101 900000000000534007 900000000000207008 20211207 20210731 < 7321d59a-986d-4496-9cf8-874022470ad5 20211207 1 11000241103 900000000000534007 900000000000012004 20211207 20210731 < a4fbf40a-73ae-4e51-80da-cddc448d3a32 20211207 1 2011000195101 900000000000534007 900000000000012004 20211207 20210731 Also 2 records had their UUID's replaced unnecessarily: < b3c09a5c-496c-48d7-808a-166f2b6a3c97 20211207 1 11000241103 900000000000534007 900000000000207008 20211207 20210731 < dc968531-82da-4aeb-bf59-3ae96cf71dd7 20211207 1 2011000195101 900000000000534007 11000241103 20211207 20210930 SO ALL WRONG!! NEED TO REVERT BACK TO EXTERNALLYMAINTAINED INPUT FOR THIS FILE TO SEE IF THIS FIXES IT!! | |
Readme file | all x prefixes added in, plus PreProduction naming convention applied, as expected. ALL Delta files removed as well, as expected. PLUS 2x new file types added in as planned, meaning 4x new files in total added:
| ||
Concept files | 2 | MSSP-1518 | 1 new record added for new "Romansh [International Organization for Standardization 639-1 code rm] language reference set (foundation metadata concept)" concept: > 22241000195100 20220607 1 2011000195101 900000000000074008 VERIFYING THIS WITH PERO IN MSSP-1518, as although all of the relevant components are here as expected (concepts, descriptions in all languages, etc) - there's NO new actual language refset file?!! Plus 1 inactivated record: < 394812008 20211207 1 2011000195101 900000000000074008 ...as expected due to exact match in Summary Component Stats report for this cycle (see link above) |
Association files | 5 | 5 new records added/updated ...as expected due to exact match in Summary Component Stats report for this cycle (see link above) | |
AttributeValue files | 10843 | 10840 added/updated??!!! NOT AS EXPECTED!!! SUMMARY COMPONENT REPORT SHOWS 88 ADDED EXPECTED, WHICH IS MUCH CLOSER TO EXPECTED THAN 10000+!!!!! 10753 records have been added here for the Common French descriptions (11000241103) - question is why?!! The snapshot of this file had only 20 records in it for the December 2021 release! However when I run the June 2022 release, it now has over 10000 records! (there’s only been 200 odd Description changes in this cycle!) The attributeValue config in the manifest is still the same as it was in December 2021: <file Name=“xder2_cRefset_AttributeValueSnapshot_CH1000195_20220607.txt”> To be fair, looking at the Common French Description file (https://prod-release.ihtsdotools.org/api/centers/ch/products/snomed_ct_switzerland_releases[…]s/xsct2_Description_Snapshot-fr_CH1000195_20220607.txt), it looks like there were about 10254 records inactivated in the December release - however these were Born Inactive (in the first time release) and so I wouldn’t expect the system to create new attributeValue records for these? But perhaps it has to if it can’t find existing attributeValue records for the old inactive records?? CHECKING WITH QUYEN...Quyen thinks it's a snowstorm bug, so I've raised ticket: - ISRS-1254Getting issue details... STATUS Michael confirmed them to be all valid in ISRS-1254 | |
Description (de-ch) files | 115 | 74 added/updated records + 41 inactivated records ...as expected due to close match with TOTAL DESCRIPTION Counts in Summary Component Stats report for this cycle (see link above) | |
Description (en) files | 2 | 2 new records added/updated ...as expected due to close match with TOTAL DESCRIPTION Counts in Summary Component Stats report for this cycle (see link above) | |
Description (fr) files | 110 | 110 Swiss French records removed, as planned in INFRA-8967 in order to correctly split out the Swiss French records into their own "fr-ch" Description file, leaving ONLY the Common French records in this "fr" Description file. ...as expected due to close match with TOTAL DESCRIPTION Counts in Summary Component Stats report for this cycle (see link above) | |
Description (fr-ch) files | 140 | Original 110 Swiss French records added, as planned in INFRA-8967 in order to correctly split out the Swiss French records into their own "fr-ch" Description file, leaving ONLY the Common French records in this "fr" Description file. + 21 records inactivated in the new June 2022 content + 30 new records added in the new June 2022 content ...as expected due to close match with TOTAL DESCRIPTION Counts in Summary Component Stats report for this cycle (see link above) | |
Description (it-ch) files | 83 | 61 added/updated records + 22 inactivated records ...as expected due to close match with TOTAL DESCRIPTION Counts in Summary Component Stats report for this cycle (see link above) | |
Language Refset (de-ch) files | 112 | 71 records added/updated + 41 records inactivated ...as expected due to exact match in Summary Component Stats report for this cycle (see link above) | |
Language Refset (it-ch) files | 90 | 68 records added/updated + 22 records inactivated ...as expected due to exact match in Summary Component Stats report for this cycle (see link above) | |
Language Refset (en) files | 67 | 67 records added/updated ...NOT as expected due to Summary Component Stats report for this cycle (see link above) expecting 40???? Double checked and this looks like a problem with the Summary Component Report - possibly just because we're comparing to a DIFFERENT previous published package though, because we've generated the new one?!! | |
Language Refset (fr) files | 0 | 0 records added/updated, as expected as this is Common French Language file?????? (but then shouldn't we be moving some into fr-ch, or were these already in December - no they weren't there, they requested no preferences for Common French, just Swiss French) SUMMARY REPORT EXPECTING 11 - this looks like a problem with the Summary Component Report - possibly just because we're comparing to a DIFFERENT previous published package though, because we've generated the new one?!! | |
Language Refset (fr-ch) files | 156 | 67 records added/updated + 89 records inactivated ...as expected due to exact match in Summary Component Stats report for this cycle (see link above) | |
Relationship files | 3 | 1 new records added: > 43341000195128 20220607 1 2011000195101 22241000195100 900000000000506000 0 116680003 900000000000011006 900000000000451002 plus 2 records inactivated, related to newly re-activated Concepts: < 11000241126 20211207 1 11000241103 11000241103 900000000000443000 0 116680003 900000000000011006 900000000000451002 < 2026638020 20211207 1 2011000195101 394812008 394733009 0 116680003 900000000000011006 900000000000451002 NOT AS EXPECTED - THE SUMMARY COMPONENT REPORT (linked) SHOWS 2 new and 1 inactivated expected????) Maybe because it's comparing to a DIFFERENT previous published package though, because we've generated the new one?!! Yes, manual checks show 2 inactivations + 1 addition since previous publication... | |
Relationship Concrete Values files | 0 | 0 records added/updated ...as expected due to exact match in Summary Component Stats report for this cycle (see link above) | |
OWL Expression files | 2 | 1 new records added: > 5a9f6ee1-5e4a-4e6d-b740-e123946cfef6 20220607 1 2011000195101 733073007 22241000195100 SubClassOf(:22241000195100 :900000000000506000) plus 1 records inactivated, related to newly re-activated Concepts: < 1ed01c6c-26ea-4b1f-a59e-c79fd882fc51 20211207 1 2011000195101 733073007 394812008 SubClassOf(:394812008 :394733009) NOT AS EXPECTED - THE SUMMARY COMPONENT REPORT (linked) SHOWS 2 new and 1 inactivated expected????) Maybe because it's comparing to a DIFFERENT previous published package though, because we've generated the new one?!! Yes, manual checks show 1 inactivations + 1 addition since previous publication... |