March 2025 PreProduction (version 2) vs March 2025 Production (version 1) traceability 

MSSP TICKET:   MSSP-3602

CONCLUSION:  Zero changes as expected, as only change is versioning of the content

March 2025 PreProduction (version 1) vs March 2025 PreProduction (version 2) traceability 

MSSP TICKET:   MSSP-3602

CONCLUSION:  2x "born-inactive" records removed

September 2024 (PUBLISHED) vs March 2025 PreProduction (version 1) traceability 

MSSP TICKET:   MSSP-3602

CONCLUSION:  Changes as expected:

• MDRS files:
  • 2 records updated as expected
• RefsetDescriptor files:
  • 3x new records - NOT AS EXPECTED, AS THEY HAVE NOT PUBLISHED THEIR NEW REFSETS AS YET!!

    • > 1b6fd4d5-7614-4e57-80a7-9a454d039a05 20250331 1 554471000005108 900000000000456007 2923051000005100 449608002 900000000000461009 0

    • > 1ff2d40a-6a88-465a-af0d-5351e8670c2e 20250331 1 554471000005108 900000000000456007 2923031000005105 449608002 900000000000461009 0

    • > 36e2299a-6c2e-4600-a04f-5ef0e8ab02d9 20250331 1 554471000005108 900000000000456007 2923041000005102 449608002 900000000000461009 0

  • On investigation, these are linked to new refsets added by DK:
    • 2923051000005100 = enhedstyper i Sundhedsvæsenets Organisationsregister simple reference set
    • 2923031000005105 = kliniske specialer i Sundhedsvæsenets Organisationsregister simple reference set
    • 2923041000005102 = Graviditetsmappen simple reference set
  • Asked DK NRC in MSSP Ticket if these are valid new refsets??
    • YES, AS EXPECTED THEY ARE IN PREP OF FUTURE REFSET DEPLOYMENTS:  
      • "We have created the three simple reference set descriptors for our 3 new local reference sets created in the new refset tool. For now we have chosen not to publish them, but to keep them as local reference sets which we have also discussed with Terance Shird."
• Association Refset files:
  • Changes as expected in PCR report
• AttributeValue files:
  • 2x "New Inactive" records not matching SCS report...

    • > 4dca6968-0ebf-4086-8eaf-cf4157e39cc3 20250331 0 554471000005108 900000000000490003 492968017 900000000000485001

    • > f40babb8-bd96-4dbc-87f3-8fa7c86e586f 20250331 0 554471000005108 900000000000490003 8381017 900000000000485001

  • These are valid "born-inactive" issues, as checking the Full file these records have never existed before.
    • In addition to this, I checked the input files and confirmed that the records existed in the Delta file exported from the termServer, and they did - so this isn't an SRS problem:  
      • https://prod-release.ihtsdotools.org/api/centers/dk/products/snomed_ct_dk_releases/builds/2025-03-03T16:27:22/inputfiles/rel2_cRefset_AttributeValueDelta_DK1000005_20250331.txt 
    • Therefore raised  to investigate why snowstorm is generating born-inactive AttributeValue records....
• Concept files:
  • Changes as expected in PCR report
• Description files:
  • Changes as expected in PCR report
• Relationship files:
  • Changes as expected in PCR report
• OWL files:
  • Changes as expected in PCR report