Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Differences found in package Comparison

Number of RF2 records impactedRelated JIRA ticket(s)Rationale
RefsetDescriptor files10

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:

  • Dec 22
    • < 174062a5-02eb-4179-899c-741faa68d9a6    20211207    1    2011000195101    900000000000456007    2031000195108    900000000000510002    900000000000462002    0
    • < 1ca3e72a-71ee-436d-9c06-e47e0db53185    20220607    1    2011000195101    900000000000456007    22241000195100    900000000000510002    900000000000462002    0
    • < 1dda242a-587b-4b38-8eff-f86b509afa22    20220607    1    2011000195101    900000000000456007    22241000195100    900000000000511003    900000000000461009    1
    • < 2086b060-a11f-4409-867c-56c308f356ea    20211207    1    2011000195101    900000000000456007    2041000195100    900000000000511003    900000000000461009    1
    • < 31a3a105-910b-4c7f-842d-1b0e7b9b89de    20211207    1    2011000195101    900000000000456007    2021000195106    900000000000510002    900000000000462002    0
    • < 4ae80dc6-2654-4188-85c9-4e5003c96c6f    20211207    1    2011000195101    900000000000456007    2041000195100    900000000000510002    900000000000462002   0
    • < 8afd2ce3-9943-4359-bf0a-18f812ae1bbd    20211207    1    2011000195101    900000000000456007    2031000195108    900000000000511003    900000000000461009    1
    • < ef7acdd0-afcd-416b-8968-358b8d5dfa88    20211207    1    2011000195101    900000000000456007    2021000195106    900000000000511003    900000000000461009    1
  • June 23
    • > 548dc527-855a-476a-9e19-183666f89c8d    20230607    1    2011000195101    900000000000456007    2031000195108    900000000000511003    900000000000461009    1
    • > c1f1334c-9bb0-4149-a2ea-00914853e3cf    20230607    1    2011000195101    900000000000456007    22241000195100    900000000000510002    900000000000462002    0
    • > c6263863-9152-4e93-b229-d8b0243d8e6b    20230607    1    2011000195101    900000000000456007    2021000195106    900000000000511003    900000000000461009    1
    • > d9196a6b-29a1-4dbd-bb6b-9346429d9dfc    20230607    1    2011000195101    900000000000456007    2041000195100    900000000000511003    900000000000461009    1
    • > e654efc1-6113-4eff-acb9-a08ade12dc7e    20230607    1    2011000195101    900000000000456007    2041000195100    900000000000510002    900000000000462002    0
    • > eb71ee49-88b2-4713-950a-4506e714b456    20230607    1    2011000195101    900000000000456007    2031000195108    900000000000510002    900000000000462002    0
    • > eb9f152b-79f1-4d3f-8b8a-6381cb076d45    20230607    1    2011000195101    900000000000456007    22241000195100    900000000000511003    900000000000461009    1
    • > fdf18dfc-59ac-4ef6-a844-9b883e9dc531    20230607    1    2011000195101    900000000000456007    2021000195106    900000000000510002    900000000000462002    0

2 records however, DID NOT GET REPLACED IN NEW JUNE 2023 RELEASE as expected???

  • < 58b37409-0e3b-49ec-9cc4-f2ea835a5789    20211207    1    2011000195101    900000000000456007    722131000    900000000000510002    900000000000462002    0
  • < b9ca50ba-2a5e-4cda-806b-aa313a84dcf9    20211207    1    2011000195101    900000000000456007    722131000    900000000000511003    900000000000461009    1


ModuleDependency files5

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 files12

2 new records added/updated for 20230607, 

10 records (from all different effectiveTimes) removed

...as expected ???????????????? due to exact match in Summary Component Stats report for this cycle (see link above)

AttributeValue files11613

6860 new records added/updated for 20230607, 

11613 records (from all different effectiveTimes) removed

...as expected ????????????????

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”>
<sources>
<source>terminology-server</source>
</sources>
<contains-reference-sets>
<refset id=“900000000000489007" label=“Concept inactivation indicator”/>
<refset id=“900000000000490003" label=“Description inactivation indicator”/>
</contains-reference-sets>
<contains-additional-fields>
<field name =“valueId”/>
</contains-additional-fields>
</file>

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:

Jira
serverIHTSDO JIRA
serverIdb202d822-d767-33be-b234-fec5accd5d8c
keyISRS-1254

Michael confirmed them to be all valid in ISRS-1254

Language Refset (de-ch) files29491

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????

Language Refset (it-ch) files2603

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)

Language Refset (en) files182

96 new records added/updated for 20230607 - ***** FOR REFSETID: 900000000000508004 + 900000000000509007 *****

86 records (from all different effectiveTimes) removed

...as expected ????????????????

Language Refset (fr) files0

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) files260,288

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)

Concept files46

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????


Description (de-ch) files29596

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)

Description (en) files68

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)

Description (fr) files185,262

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)

Description (fr-ch) files158774

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)

Description (it-ch) files2637

1326 new records added/updated for 20230607 - 

1311 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)

Relationship files64

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:

  • 37 new records added/updated for 20230607, 

  • 0 records inactivated

IS THIS TO BE EXPECTED BECAUSE WE'VE "STARTED FROM SCRATCH" IN THIS RELEASE??????

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)

  • 2026638020    20220607    0    2011000195101    394812008    394733009    0    116680003    900000000000011006    900000000000451002
  • 11000241126    20220607    0    2011000195101    11000241103    900000000000443000    0    116680003    900000000000011006    900000000000451002

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)

  • < 33588028    20211207    1    2011000195101    224877003    308912000    0    116680003    900000000000011006    900000000000451002
  • > 33588028    20230607    1    2011000195101    224877003    308912000    0    116680003    900000000000011006    900000000000451002

Yet more appear to be added in validly as brand new concepts for this authoring cycle (eg)

  • > 123431000195124    20230607    1    2011000195101    72281000195108    365996006    0    116680003    900000000000011006    900000000000451002
  • > 123441000195127    20230607    1    2011000195101    72281000195108    225598002    1    363714003    900000000000011006    900000000000451002
  • > 123481000195123    20230607    1    2011000195101    82291000195104    417319006    0    116680003    900000000000011006    900000000000451002
  • > 123501000195126    20230607    1    2011000195101    62271000195100    364830008    1    363702006    900000000000011006    900000000000451002

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:

  • < 11000241126    20220607    0    2011000195101    11000241103    900000000000443000    0    116680003    900000000000011006    900000000000451002
Relationship Concrete Values files0

0 records added/updated

...as expected due to exact match in Summary Component Stats report for this cycle (see link above)

OWL Expression files46

25 new records added/updated for 20230607 - 

21 records (from all different effectiveTimes) removed

...as expected ????????????????

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...

TextDefinition (de-ch) files0

0 new records added/updated for 20230607 - 

0 records (from all different effectiveTimes) removed

...as expected ????????????????

TextDefinition (en) files0

0 new records added/updated for 20230607 - 

0 records (from all different effectiveTimes) removed

...as expected ????????????????

TextDefinition (fr) files1

0 new records added/updated for 20230607 - 

1 records (from all different effectiveTimes) removed

...as expected ????????????????


TextDefinition (fr-ch) files0

0 new records added/updated for 20230607 - 

0 records (from all different effectiveTimes) removed

...as expected ????????????????

TextDefinition (it-ch) files0

0 new records added/updated for 20230607 - 

0 records (from all different effectiveTimes) removed

...as expected ????????????????

...