March 2019 Pre-Production (Version3) vs March 2019 Pre-Production (Version7) traceability
Differences found in package Comparison | Number of RF2 records impacted | Related JIRA ticket(s) | Rationale |
|---|---|---|---|
| Language files (FR) | 1 | 1 record inactviated as expected to resolve ISRS-519: < 225ae415-f160-45c5-ba98-8d6c6add9140 20180315 1 11000172109 31000172101 644911000172119 900000000000549004 | |
| Language files (NL) | 1 | ISRS-519 | 1 inactivation record removed as expected to resolve ISRS-519 < 225ae415-f160-45c5-ba98-8d6c6add9140 20190315 0 11000172109 31000172101 644911000172119 900000000000549004 |
| OWLExpression files | 1 record updated with just new UUID as expected due to this being a new record for this release, therefore UUID updates with every new build: < 11f18fc2-114d-4c75-82a5-5e4f535ef8cb 20190315 1 11000172109 762103008 734147008 Ontology(<http://snomed.info/sct/11000172109>) |
March 2019 Pre-Production (Version3) vs March 2019 Pre-Production (Version5) traceability
Differences found in package Comparison | Number of RF2 records impacted | Related JIRA ticket(s) | Rationale |
|---|---|---|---|
| Language files (FR) | 1 | 1 record inactviated as expected to resolve ISRS-519: < 225ae415-f160-45c5-ba98-8d6c6add9140 20180315 1 11000172109 31000172101 644911000172119 900000000000549004 | |
| Language files (NL) | 1 | ISRS-519 | 1 inactivation record removed as expected to resolve ISRS-519 < 225ae415-f160-45c5-ba98-8d6c6add9140 20190315 0 11000172109 31000172101 644911000172119 900000000000549004 |
| Relationship files | 3 records reverted from inactviations since the pre-prod release as NOT expected: < 41641000172127 20190315 0 11000172109 398971002 768687001 0 116680003 900000000000011006 900000000000451002 < 47081000172122 20190315 0 11000172109 421953007 768459000 0 116680003 900000000000011006 900000000000451002 < 47471000172128 20190315 0 11000172109 424039006 768626007 0 116680003 900000000000011006 900000000000451002 Have double checked these and they were active in September 2018, then inactivated in the March 2019 Pre-Prod release on 25/02/2019, but have then had those inactivations reverted in this latest build of the March 2019 release! Sending to Zoli to investigate, as he can't think of a good reason for these to be doing this either! | ||
| OWLExpression files | 1 record updated with just new UUID as expected due to this being a new record for this release, therefore UUID updates with every new build: < 11f18fc2-114d-4c75-82a5-5e4f535ef8cb 20190315 1 11000172109 762103008 734147008 Ontology(<http://snomed.info/sct/11000172109>) |
March 2019 Pre-Production (Version3) vs March 2019 Pre-Production (Version4) traceability
Differences found in package Comparison | Number of RF2 records impacted | Related JIRA ticket(s) | Rationale |
|---|---|---|---|
| Language files (FR) | 1 | 1 inactivation record added XXXXXXNOT as expected because the UUID has changed, so old active record is still in Snapshot!!XXXXXXXX > b2d54bb1-9c5b-4e1a-a14f-1e35966acb75 20190315 0 11000172109 21000172104 644911000172119 900000000000549004 | |
| Language files (NL) | 1 | 1 inactivation record removed ?????????as expected??????????? < 225ae415-f160-45c5-ba98-8d6c6add9140 20190315 0 11000172109 31000172101 644911000172119 900000000000549004 | |
| Relationship files | 3 records added ?????????as NOT expected???????????: > 20180915 1 11000172109 398971002 768687001 116680003 900000000000011006 900000000000451002 | ||
| OWLExpression files | 1 record updated with just new UUID ?????????as NOT expected???????????: < 11f18fc2-114d-4c75-82a5-5e4f535ef8cb 20190315 1 11000172109 762103008 734147008 Ontology(<http://snomed.info/sct/11000172109>) |
September 2018 (PUBLISHED) vs March 2019 Pre-Production (Version2) traceability
Differences found in package Comparison | Number of RF2 records impacted | Related JIRA ticket(s) | Rationale |
|---|---|---|---|
| ModuleDependency files | 2 | Changes to add 2 new records for March 2019 as expected | |
| AttributeValue files | 213 | 213 new records, as expected from 209 NL descriptions inactivated + 4 FR inactivations | |
| Description files (FR) | 8 | 3 new records added, plus 4 records inactivated, plus 1 record updated ??????????????? as expected from BE editing ??????????????? | |
| Description files (NL) | 544 | 332 new records added, as expected from 331 NL bulk import records + a few records manually authored by BE, plus 209 records inactivated, as expected from 205 NL bulk import records + a few records manually authored by BE, plus 3 records updated as expected from 80 NL bulk import records + a few records manually authored by BE | |
| Language files (FR) | 7 | 3 new records added, plus 3 records inactivated, plus 1 record updated ??????????????? as expected from BE editing ??????????????? | |
| Language files (NL) | 626 | 336 new records added,as expected from 331 NL bulk import records + a few records manually authored by BE, plus 210 records inactivated,as expected from 205 NL bulk import records + a few records manually authored by BE, plus 80 records updated as expected from 80 NL bulk import records + a few records manually authored by BE, | |
| Inferred Relationship files | 6843 | 135 new records added, plus 6688 active records removed (including 6708 inactivated), as expected as a result of the automatic reversion of the issue from Sept 2018 (SNOMED CT Managed Service - Belgium Extension Critical Incident Response Plan - March 2019), in which 6708 inferred relationships were incorrectly added (and therefore correctly inactivated in this release), and 2736 inferred relationships were incorrectly inactivated. Obviously the 2736 records that were incorrectly inactivated in the last release do not match the 135 records that were added back into this release! However, both Kai and Yong confirmed that this is the expected result, due to a mathematical coincidence in this release cycle, whereby nearly all of those records (2601 of them) just happened to get inactivated in the latest Jan 2019 International Edition! See Yong's email from 09:02 on 26/2/2019: I checked the inactivated inferred relationships. 1,934 product concepts have been classified to more accurate parent concepts. Therefore, we see a large number of inactivation of the IS A relationships. I randomly checked some and they are correct inactivations. The rest results of inactivation of concepts in either sourceId or destinationId or both. These inactivations involved different hierarchies, e.g. findings, procedures etc. So, the good news is that all of these are expected inactivations in the inferred relationships. Plus Kai's email from 21:52 on 25/2/2019: Attached is a zip of the 2,601 inactive inferred relationships from the Jan 2019 International release which match the active, source, destination and group of the relationships mistakenly made inactive in the Sept 2018 Belgian release. This explains why we only have 135 active relationships when we classify the March 2019 Belgian release. | |
| Readme file | Expected changes to date and file naming convention |
September 2018 (PUBLISHED) vs March 2019 Pre-Production (Version1) traceability
Differences found in package Comparison | Number of RF2 records impacted | Related JIRA ticket(s) | Rationale |
|---|---|---|---|
| ModuleDependency files | 2 | Changes to add 2 new records for March 2019 as expected | |
| Description files (FR) | 0 | 0 records updated, ??????????????? as expected from BE editing ??????????????? | |
| Description files (NL) | 0 | 0 records updated, ??????????????? as expected from BE editing ??????????????? | |
| Language files (FR) | 0 | 0 records updated, ??????????????? as expected from BE editing ??????????????? | |
| Language files (NL) | 0 | 0 records updated, ??????????????? as expected from BE editing ??????????????? | |
| Inferred Relationship files | 6843 | 135 new records added, plus 6708 records inactivated, ??????????????? as expected from BE editing ??????????????? | |
| Readme file | Expected changes to date and file naming convention |