...
June 2023 PreProduction (Version 5 - Fixes from version 4) traceability vs June 2023
...
Production (Version
...
1) traceability
SUMMARY COMPONENT REPORT: https://docs.google.com/spreadsheets/d/1Q18jq4eHU4-H8hou3U3Pb-4l1jGgqRNSIk-1KvTfrIo/edit#gid=1
MSSP TICKET: https://jira.ihtsdotools.org/browse/MSSP-2072
Differences found in package Comparison | Number of RF2 records impacted | Related JIRA ticket(s) | Rationale |
|---|
...
| Readme file | n/a | All x prefixes removed, and Production naming conventions applied, as expected |
June 2023 PreProduction (Version 4 - COMPLETE RE-START OF SWISS RELEASE, AS IF THIS IS A "FIRST TIME" RELEASE
...
) traceability
vs June 2023 PreProduction (Version 5 - Fixes from version 4) traceability
SUMMARY COMPONENT REPORT: https://docs.google.com/spreadsheets/d/1Q18jq4eHU4-H8hou3U3Pb-4l1jGgqRNSIk-1KvTfrIo/edit#gid=1
MSSP TICKET: https://jira.ihtsdotools.org/browse/MSSP-2072
Differences found in package Comparison | Number of RF2 records impacted | Related JIRA ticket(s) | Rationale |
|---|---|---|---|
| RefsetDescriptor files | 10 | 8 records had their UUID's reverted to December 2022 (plus 2 records that were missing from the PreProd version 4 package) + new effectiveTime of 20230607 (but NO CHANGES TO ACTUAL RECORDS) as expected, due to NEW "FIRST TIME" RELEASE:
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
2 records however, DID NOT GET REPLACED IN NEW JUNE 2023 RELEASE as expected???
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
5 records removed completey, replaced with nothing!!
SO ALL WRONG!! NEED TO REVERT BACK TO EXTERNALLYMAINTAINED INPUT FOR THIS FILE TO SEE IF THIS FIXES IT!!
...
all x prefixes added in, plus PreProduction naming convention applied, as expected.
...
2 new records added/updated for 20230607,
10 records (from all different effectiveTimes) removed
...NOT as expected due to Summary Component Stats report for this cycle (see link above) showing:
2 new records added/updated for 20230607,
0 records inactivated
IS THIS TO BE EXPECTED BECAUSE WE'VE "STARTED FROM SCRATCH" IN THIS RELEASE??????
ALL HISTORY GONE FROM ASSOCIATION FILES - I GUESS THIS IS WHAT WE WERE AIMING FOR WITH A BRAND NEW RELEASE, BUT JUST NEED TO DOUBLE CHECK WITH RORY...
...
6860 new records added/updated for 20230607,
11613 records (from all different effectiveTimes) removed
...NOT as expected due to Summary Component Stats report for this cycle (see link above) showing:
6860 new records added/updated for 20230607,
0 records inactivated
IS THIS TO BE EXPECTED BECAUSE WE'VE "STARTED FROM SCRATCH" IN THIS RELEASE??????
ALL HISTORY GONE FROM ATTRIBUTEVALUE FILES - I GUESS THIS IS WHAT WE WERE AIMING FOR WITH A BRAND NEW RELEASE, BUT JUST NEED TO DOUBLE CHECK WITH RORY...
...
27928 new records added/updated for 20230607 - ***** FOR REFSETID: 2041000195100 *****
1563 records (from all different effectiveTimes) removed
..NOT as expected due to Summary Component Stats report for this cycle (see link above) showing:
27928 new records added/updated for 20230607,
0 records inactivated
IS THIS TO BE EXPECTED BECAUSE WE'VE "STARTED FROM SCRATCH" IN THIS RELEASE??????
DOES THIS MEAN THE SCS REPORT WILL BE INVALID, AS WILL SHOW NOW INACTIVATIONS BECAUSE IT'S A "BRAND NEW RELEASE" WITH NO "PREVIOUSPUBLISHEDPACKAGE" TO COMPARE THE CONTENT TO????
So my manual validation shows:
- All inactive records (99) were removed from the original Language refset file, as expected
...
1292 new records added/updated for 20230607 - ***** FOR REFSETID: 2031000195108 *****
1311 records (from all different effectiveTimes) removed
...as expected ????????????????
due to exact match in Summary Component Stats report for this cycle (see link above)
...
96 new records added/updated for 20230607 - ***** FOR REFSETID: 900000000000508004 + 900000000000509007 *****
86 records (from all different effectiveTimes) removed
...as expected ????????????????
...
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?!!
...
161,454 new records added/updated for 20230607 - ***** FOR REFSETID: 2021000195106 *****
98,834 records (from all different effectiveTimes) removed
...as expected ????????????????
due to exact match in Summary Component Stats report for this cycle (see link above)
...
25 new records added/updated for 20230607,
21 records (from all different effectiveTimes) removed
...NOT as expected due to Summary Component Stats report for this cycle (see link above) showing:
25 new records added/updated for 20230607,
0 records inactivated
IS THIS TO BE EXPECTED BECAUSE WE'VE "STARTED FROM SCRATCH" IN THIS RELEASE??????
DOES THIS MEAN THE SCS REPORT WILL BE INVALID, AS WILL SHOW NOW INACTIVATIONS BECAUSE IT'S A "BRAND NEW RELEASE" WITH NO "PREVIOUSPUBLISHEDPACKAGE" TO COMPARE THE CONTENT TO????
Some of the records removed appear to be absolutely valid, as they are previously inactive records (and therefore there's no need to keep them as "born inactive" records) (eg)
- 394812008 20220607 0 2011000195101 900000000000074008
Many more appear to be valid as they're simply "removing" these records to be replaced with the same record just with new effectiveTimes (eg)
- < 394730007 20211207 1 2011000195101 900000000000074008
- > 394730007 20230607 1 2011000195101 900000000000074008
Yet more appear to be added in validly as brand new concepts for this authoring cycle (eg)
- 62271000195100 20230607 1 2011000195101 900000000000074008
- 62281000195103 20230607 1 2011000195101 900000000000074008
- 62291000195101 20230607 1 2011000195101 900000000000074008
- 72281000195108 20230607 1 2011000195101 900000000000074008
- 72291000195105 20230607 1 2011000195101 900000000000074008
- 82291000195104 20230607 1 2011000195101 900000000000074008
However, that leaves 1 active record that has just been removed for no apparent reason:
- 11000241103 20211207 1 11000241103 900000000000074008
DID RORY PERHAPS INTENTIONALLY MISS OUT ALL CONTENT FOR THIS MODULE (WHEN IMPORTING THE CONTENT INTO THE FRESH NEW CODESYSTEM), BECAUSE THIS IS THE COMMON FRENCH MODULE (11000241103 | SNOMED CT Common French translation module (core metadata concept) |) AND THEREFORE WE'RE NOW GOING FOR AN APPROACH THAT JUST IMPORTS THE COMMON FRENCH CONTENT STRAIGHT INTO THE SWISS MODULE INSTEAD AND THEREFORE THERE IS NO LONGER A DEPENDENCY THERE ON THE COMMON FRENCH MODULE, AND THUS NO REASON TO INCLUDE IT IN THE SWISS PACKAGE????
So when compared to the old December 2022 release, the new Version 5 refsetDescriptor records are identical except for the new effectiveTime of 20230607 for each record, as expected. | |||
| ModuleDependency files | 2 | 2 records added back in as expected, as remaining 3 from December 2022 were all related to the old dependency on the CF module, which no longer exists!
Therefore, when compared to the old December 2022 release, the new Version 5 moduleDependency records are identical (except for the new effectiveTime of 20230607 for each record) for the 2 records that are still applicable in the new world of hosting all CF + CG records in the CH module instead of in the CF + CG modules. However, we've now removed 3 of the old moduleDependency records, as we no longer need to call out the dependencies on those CF + CG modules:
This is all now exactly as expected. | |
| Description-fr FULL + SNAPSHOT files | 7478 | 7478 inactive CF module (11000241103) records have been completely removed from the package. This is exactly as expected, due to the fixes that were applied by Rory after the remaining 7478 CF module records were identified in the Version 4 testing below... | |
| Description-fr-ch FULL + SNAPSHOT files | 7478 | 7478 inactive records (from the -fr file, that were removed because they were still in the CF module (11000241103)) have now been added back into the package in the RIGHT MODULE (the Swiss module 2011000195101) This is exactly as expected, due to the fixes that were applied by Rory after the remaining 7478 CF module records were identified in the Version 4 testing below... |
December 2022 Production (PUBLISHED) vs June 2023 PreProduction (Version 4 - COMPLETE RE-START OF SWISS RELEASE, AS IF THIS IS A "FIRST TIME" RELEASE) traceability
SUMMARY COMPONENT REPORT: https://docs.google.com/spreadsheets/d/1Q18jq4eHU4-H8hou3U3Pb-4l1jGgqRNSIk-1KvTfrIo/edit#gid=1
MSSP TICKET: https://jira.ihtsdotools.org/browse/MSSP-2072
Differences found in package Comparison | Number of RF2 records impacted | Related JIRA ticket(s) | Rationale |
|---|---|---|---|
| RefsetDescriptor files | 10 | 8 records had their UUID's refreshed + new effectiveTime of 20230607 (but NO CHANGES TO ACTUAL RECORDS) as expected, due to NEW "FIRST TIME" RELEASE:
2 records however, DID NOT GET REPLACED IN NEW JUNE 2023 RELEASE as expected???
| |
| ModuleDependency files | 5 | 5 records removed completey, replaced with nothing!! 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. | ||
| Association files | 12 | 2 new records added/updated for 20230607, 10 records (from all different effectiveTimes) removed ...NOT as expected due to Summary Component Stats report for this cycle (see link above) showing:
IS THIS TO BE EXPECTED BECAUSE WE'VE "STARTED FROM SCRATCH" IN THIS RELEASE?????? ALL HISTORY GONE FROM ASSOCIATION FILES - I GUESS THIS IS WHAT WE WERE AIMING FOR WITH A BRAND NEW RELEASE, BUT JUST NEED TO DOUBLE CHECK WITH RORY... Yes, Rory confirmed this is correct during our call at 17:00 on | |
| AttributeValue files | 11613 | 6860 new records added/updated for 20230607, 11613 records (from all different effectiveTimes) removed ...NOT as expected due to Summary Component Stats report for this cycle (see link above) showing:
IS THIS TO BE EXPECTED BECAUSE WE'VE "STARTED FROM SCRATCH" IN THIS RELEASE?????? ALL HISTORY GONE FROM ATTRIBUTEVALUE FILES - I GUESS THIS IS WHAT WE WERE AIMING FOR WITH A BRAND NEW RELEASE, BUT JUST NEED TO DOUBLE CHECK WITH RORY... Yes, Rory confirmed this is correct during our call at 17:00 on | |
| Language Refset (de-ch) files | 29491 | 27928 new records added/updated for 20230607 - ***** FOR REFSETID: 2041000195100 ***** 1563 records (from all different effectiveTimes) removed ..NOT as expected due to Summary Component Stats report for this cycle (see link above) showing:
DOES THIS MEAN THE SCS REPORT WILL BE INVALID, AS WILL SHOW NOW INACTIVATIONS BECAUSE IT'S A "BRAND NEW RELEASE" WITH NO "PREVIOUSPUBLISHEDPACKAGE" TO COMPARE THE CONTENT TO???? So my manual validation shows:
IS THIS TO BE EXPECTED BECAUSE WE'VE "STARTED FROM SCRATCH" IN THIS RELEASE?????? Yes, Rory confirmed this is correct during our call at 17:00 on | |
| Language Refset (it-ch) files | 2603 | 1292 new records added/updated for 20230607 - ***** FOR REFSETID: 2031000195108 ***** 1311 records (from all different effectiveTimes) removed So my manual validation shows:
...as expected ???????????????? Yes, Rory confirmed this is correct during our call at 17:00 on | |
| Language Refset (en) files | 182 | 96 new records added/updated for 20230607 - ***** FOR REFSETID: 900000000000508004 + 900000000000509007 ***** 86 records (from all different effectiveTimes) removed So my manual validation shows:
IS THIS TO BE EXPECTED BECAUSE WE'VE "STARTED FROM SCRATCH" IN THIS RELEASE?????? Yes, Rory confirmed this is correct during our call at 17:00 on | |
| Language Refset (fr) files | 0 | 0 records added/updated, as expected as this is Common French Language file?????? SUMMARY REPORT EXPECTING 0 | |
| Language Refset (fr-ch) files | 260,288 | 161,454 new records added/updated for 20230607 - ***** FOR REFSETID: 2021000195106 ***** 98,834 records (from all different effectiveTimes) removed So my manual validation shows:
IS THIS TO BE EXPECTED BECAUSE WE'VE "STARTED FROM SCRATCH" IN THIS RELEASE?????? Yes, Rory confirmed this is correct during our call at 17:00 on | |
| Concept files | 46 | 25 new records added/updated for 20230607, 21 records (from all different effectiveTimes) removed ...NOT as expected due to Summary Component Stats report for this cycle (see link above) showing:
DOES THIS MEAN THE SCS REPORT WILL BE INVALID, AS WILL SHOW NOW INACTIVATIONS BECAUSE IT'S A "BRAND NEW RELEASE" WITH NO "PREVIOUSPUBLISHEDPACKAGE" TO COMPARE THE CONTENT TO???? Some of the records removed appear to be absolutely valid, as they are previously inactive records (and therefore there's no need to keep them as "born inactive" records) (eg)
Many more appear to be valid as they're simply "removing" these records to be replaced with the same record just with new effectiveTimes (eg)
Yet more appear to be added in validly as brand new concepts for this authoring cycle (eg)
However, that leaves 1 active record that has just been removed for no apparent reason:
DID RORY PERHAPS INTENTIONALLY MISS OUT ALL CONTENT FOR THIS MODULE (WHEN IMPORTING THE CONTENT INTO THE FRESH NEW CODESYSTEM), BECAUSE THIS IS THE COMMON FRENCH MODULE (11000241103 | SNOMED CT Common French translation module (core metadata concept) |) AND THEREFORE WE'RE NOW GOING FOR AN APPROACH THAT JUST IMPORTS THE COMMON FRENCH CONTENT STRAIGHT INTO THE SWISS MODULE INSTEAD AND THEREFORE THERE IS NO LONGER A DEPENDENCY THERE ON THE COMMON FRENCH MODULE, AND THUS NO REASON TO INCLUDE IT IN THE SWISS PACKAGE???? IS THIS TO BE EXPECTED BECAUSE WE'VE "STARTED FROM SCRATCH" IN THIS RELEASE?????? Yes, Rory confirmed this is correct during our call at 17:00 on | |
| Description (de-ch) files | 29593 | 28030 new records added/updated for 20230607 1563 records (from all different effectiveTimes) removed So my manual validation shows:
due to close match with TOTAL DESCRIPTION Counts in Summary Component Stats report for this cycle (see link above) IS THIS TO BE EXPECTED BECAUSE WE'VE "STARTED FROM SCRATCH" IN THIS RELEASE?????? Yes, Rory confirmed this is correct during our call at 17:00 on | |
| Description (en) files | 68 | 40 new records added/updated for 20230607 - 28 records (from all different effectiveTimes) removed So my manual validation shows:
due to close match with TOTAL DESCRIPTION Counts in Summary Component Stats report for this cycle (see link above) IS THIS TO BE EXPECTED BECAUSE WE'VE "STARTED FROM SCRATCH" IN THIS RELEASE?????? Yes, Rory confirmed this is correct during our call at 17:00 on | |
| Description (fr) files | 185,262 | 7479 new records added/updated for 20230607 - 177,783 records (from all different effectiveTimes) removed So my manual validation shows:
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) IS THIS TO BE EXPECTED BECAUSE WE'VE "STARTED FROM SCRATCH" IN THIS RELEASE?????? NO - RORY CONFIRMED (during our call at 17:00 on ) THAT THE 7478 RECORDS STILL LEFT IN THE CF module (11000241103) WERE JUST A MISTAKE WHEN HE WAS DOING THE ORIGINAL UPLOADS | |
| Description (fr-ch) files | 158774 | 158,602 new records added/updated for 20230607 - 147 records (from all different effectiveTimes) removed So my manual validation shows:
...as expected due to close match with TOTAL DESCRIPTION Counts in Summary Component Stats report for this cycle (see link above) IS THIS TO BE EXPECTED BECAUSE WE'VE "STARTED FROM SCRATCH" IN THIS RELEASE?????? NO - RORY CONFIRMED (during our call at 17:00 on ) THAT THE 7478 RECORDS STILL LEFT IN THE CF module (11000241103) in the description-fr file WERE JUST A MISTAKE WHEN HE WAS DOING THE ORIGINAL UPLOADS. They therefore now need to be added back into this description-fr-ch file in the Swiss module (2011000195101). | |
| Description (it-ch) files | 2637 | 1326 new records added/updated for 20230607 - 1311 records (from all different effectiveTimes) removed So my manual validation shows:
|
...
28030 new records added/updated for 20230607
1566 records (from all different effectiveTimes) removed
...as expected ????????????????
due to close match with TOTAL DESCRIPTION Counts in Summary Component Stats report for this cycle (see link above)
...
40 new records added/updated for 20230607 -
28 records (from all different effectiveTimes) removed
...as expected ????????????????
due to close match with TOTAL DESCRIPTION Counts in Summary Component Stats report for this cycle (see link above)
...
7479 new records added/updated for 20230607 -
177,783 records (from all different effectiveTimes) removed
...as expected ????????????????
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)
...
158,623 new records added/updated for 20230607 -
151 records (from all different effectiveTimes) removed
...as expected ????????????????
...as expected due to close match with TOTAL DESCRIPTION Counts in Summary Component Stats report for this cycle (see link above)
...
1326 new records added/updated for 20230607 -
1311 records (from all different effectiveTimes) removed
...
due to close match with TOTAL DESCRIPTION Counts in Summary Component Stats report for this cycle (see link above) IS THIS TO BE EXPECTED BECAUSE WE'VE "STARTED FROM SCRATCH" IN THIS RELEASE?????? Yes, Rory confirmed this is correct during our call at 17:00 on | |||
| Relationship files | 64 | 37 new records added/updated for 20230607 - 27 records (from all different effectiveTimes) removed ...NOT as expected due to Summary Component Stats report for this cycle (see link above) showing:
|
...
0 records inactivated
...
Some of the records removed appear to be absolutely valid, as they are previously inactive records (and therefore there's no need to keep them as "born inactive" records) (eg)
Many more appear to be valid as they're simply "removing" these records to be replaced with the same record just with new effectiveTimes (eg)
Yet more appear to be added in validly as brand new concepts for this authoring cycle (eg)
The good news here is that the only record related to the now unnecessary Common French module (11000241103) was already inactive, and therefore gets removed anyway:
IS THIS TO BE EXPECTED BECAUSE WE'VE "STARTED FROM SCRATCH" IN THIS RELEASE?????? Yes, Rory confirmed this is correct during our call at 17:00 on | |||
| 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 | 46 | 25 new records added/updated for 20230607 - 21 records (from all different effectiveTimes) removed ...as expected ???????????????? Some of the records removed appear to be absolutely valid, as they are previously inactive records (and therefore there's no need to keep them as "born inactive" records) (eg)
Many more appear to be valid as they're simply "removing" these records to be replaced with the same record just with new effectiveTimes (eg)
The good news here is that one of the records related to the now unnecessary Common French module (11000241103) was already inactive, and therefore gets removed anyway:
The other one relating to this module also gets removed, as expected:
Yet more appear to be added in validly as brand new concepts for this authoring cycle (eg)
|
...
IS THIS TO BE EXPECTED BECAUSE WE'VE "STARTED FROM SCRATCH" IN THIS RELEASE?????? Yes, Rory confirmed this is correct during our call at 17:00 on | |||
| TextDefinition (de-ch) files | 0 | 0 new records added/updated for 20230607 - 0 records (from all different effectiveTimes) removed ...as expected as this file was empty in the previous releases. | |
| TextDefinition (en) files | 0 | 0 new records added/updated for 20230607 - 0 records (from all different effectiveTimes) removed ...as expected as this file was empty in the previous releases. | |
| TextDefinition (fr) files | 1 | 0 new records added/updated for 20230607 - 1 records (from all different effectiveTimes) removed |
...as expected ????????????????
1 record related to the now unnecessary Common French module (11000241103) was removed as expected: 1020231000241112 20220331 1 11000241103 77386006 fr 900000000000550004 Patiente enceinte actuellement 900000000000017005 IS THIS TO BE EXPECTED BECAUSE WE'VE "STARTED FROM SCRATCH" IN THIS RELEASE?????? Yes, Rory confirmed this is correct during our call at 17:00 on | |||
| TextDefinition (fr-ch) files | 0 | 0 new records added/updated for 20230607 - 0 records (from all different effectiveTimes) removed ...as expected as this file was empty in the previous releases. | |
| TextDefinition (it-ch) files | 0 | 0 new records added/updated for 20230607 - 0 records (from all different effectiveTimes) removed ...as expected as this file was empty in the previous releases. |