Traceability matrix (US Edition - September 2025)
September 2025 PREPRODUCTION (Version 2 PRE VERSIONING) to September 2025 PRODUCTION (Version 1 POST VERSIONING)
traceability
MSSP Ticket: MSSP-3951
CONCLUSION: All changes as expected, as no changes observed between PreProd and Prod, versioning only
September 2025 PREPRODUCTION (Version 1 PRE VERSIONING) to September 2025 PREPRODUCTION (Version 2 PRE VERSIONING) traceability
MSSP Ticket: MSSP-3951
CONCLUSION: All changes as expected, as now included Mapping files which now contains expected totals for Extended Map records, as match the Delta file from WCI:
1. The TOTAL of New (12982) + Changed (4269) + Reactivated (864) in the PCR Report = the number of records with “20250901 1“ in the new Map snapshot (18115) = the number of records with “20250901 1 “ in the WCI Delta file (18115)
2. The total of Inactivated (7230) in the PCR Report = the number of records with “20250901 0 “ in the new Map snapshot (7230) = the number of records with “20250901 0 “ in the WCI Delta file (7230)
March 2025 PRODUCTION (PUBLISHED) to September 2025 PREPRODUCTION (Version 1 PRE VERSIONING) traceability
MSSP Ticket: MSSP-3951
CONCLUSION: Changes as expected:
release_package_information.json:
Metadata as expected
ExtendedMap files:
MISSING - NEED TO TRY ANOTHER DELTA FEED TO SEE IF THIS RESOLVES THE ISSUE
ModuleDependency files:
5x updated records, as expected (as other updates are INT Edition content being updated due to this package being an Edition)
Component Annotations files:
Circa. 3218 new records added, but all in International module as expected, as these were changes from the International releases.
AttributeValue files no longer have a record count discrepancy
Concepts:
VERIFY THE 80x "Promoted" record in the PCR Report???
Look good to me:
(eg)
911421000124106 20250301 1 731000124108 900000000000074008
911421000124106 20250501 1 900000000000207008 900000000000074008
Just need to ask them to verify in their validation
Descriptions:
VERIFY THE 1x "Changed Inactive" record in the PCR Report:
Simply removed a double space from the end of the term, so seems valid:
< 182731000119111 20170301 0 731000124108 22851000119107 en 900000000000003001 Pyogenic bacterial arthritis of pelvis (disorder) 900000000000448009
> 182731000119111 20250901 0 731000124108 22851000119107 en 900000000000003001 Pyogenic bacterial arthritis of pelvis (disorder) 900000000000448009
Just need to ask them to verify in their validation
Relationships:
VERIFY THE 177x "New Inactive" record in the PCR Report???
Look invalid, as they all seem to have previous records with Active status! Only difference is thet they seem to have switched modules (from INT to US module )in this release cycle, at the same time as being inactivated (eg)
40565026 20020131 1 900000000000207008 230222003 3168002 0 116680003 900000000000011006 900000000000451002
40565026 20070131 0 900000000000207008 230222003 3168002 0 116680003 900000000000011006 900000000000451002
40565026 20250501 1 900000000000207008 230222003 3168002 0 116680003 900000000000011006 900000000000451002
40565026 20250901 0 731000124108 230222003 3168002 0 116680003 900000000000011006 90000000000045100216346535020 20250501 1 900000000000207008 230222003 18058007 0 116680003 900000000000011006 900000000000451002
16346535020 20250901 0 731000124108 230222003 18058007 0 116680003 900000000000011006 90000000000045100215902164020 20240301 1 900000000000207008 10837221000119107 10958721000119108 0 116680003 900000000000011006 900000000000451002
15902164020 20250901 0 731000124108 10837221000119107 10958721000119108 0 116680003 900000000000011006 900000000000451002
So have raised: https://snomed.atlassian.net/browse/RP-1060
Copyright © 2025, SNOMED International