*** HAD TO RUN LOCALLY AS PCR DOESN’T WORK WITH VET EXTENSION AT PRESENT ***

March 2026 PreProduction Version 13 package vs March 2026 Production Version 1 Production package

CONCLUSION:  Changes as expected:

• Readme file had changes to remove x prefixes + PreProduction naming conventions ONLY - as expected as versioned ONLY in this update

March 2026 PreProductionVersion 12 vs March 2026 PreProduction Version 13 Production package

CONCLUSION:  Changes as expected:

• Description EN files:

  • 2x records removed from Description_en file as has incorrectly jumped modules to the VET extension (see Julie’s confirmation in the email trail at 19:37 on Mar 25, 2026

    • 2869833013 20260331 0 332351000009108 420824004 en 900000000000003001 Cinnyricinclus leucogaster (organism) 900000000000017005

    • 2870804019 20260331 0 332351000009108 420824004 en 900000000000013009 Cinnyricinclus leucogaster 900000000000017005

  • As per Peter’s fixes, these descriptions weren't removed from the system entirely, they just reverted back to their previous state in the International Edition.  So the VET extension will still see them, but inherited from Int rather than being directly in the VET extension.

• AttributeValue files:

  • 4618 inactivated as per Peter’s fixes to resolve CNC indictor deprecation (to align them with the International Edition (see notes in Slack - Release Management channel)

March 2026 PreProductionVersion 7 vs March 2026 PreProduction Version 12 Production package

CONCLUSION:  Changes as expected:

• Readme file:

  • Copyright statement updated with the new 2026 date

• MDRS files:

  • Old 2025 Records removed as expected:

    • < 78fb8bdd-17dc-403a-bdf5-58aa8bc4c83f 20250930 1 332351000009108 900000000000534007 900000000000012004 20250930 20250201
      < 8128ff42-5d05-41a6-a757-caa9c573b016 20250930 1 332351000009108 900000000000534007 900000000000207008 20250930 20250201

  • Plus invalid new 2026 records (with unreconciled UUID’s) removed as expected

    • < 8926a585-8dba-4e57-9b63-32e496f86cd0 20260331 1 332351000009108 900000000000534007 900000000000012004 20260331 20260101
      < a4b2d96f-ac94-42b3-bdd8-884c6cdceeea 20260331 1 332351000009108 900000000000534007 900000000000207008 20260331 20260101

  • Plus new valid 2026 records (with reconciled UUID’s) added as expected:

    • > 78fb8bdd-17dc-403a-bdf5-58aa8bc4c83f 20260331 1 332351000009108 900000000000534007 900000000000012004 20260331 20260101
      > 8128ff42-5d05-41a6-a757-caa9c573b016 20260331 1 332351000009108 900000000000534007 900000000000207008 20260331 20260101

March 2026 PreProductionVersion 6 vs March 2026 PreProduction Version 7 Production package

CONCLUSION:  Changes as expected:

• MDRS files:

  • Old 2025 Records still there - not fixed yet!

• OWL Axioms - expected as a result of Julie’s fixes in fix branch VET25-50 - confirmed with her that these are valid changes in email at 19:39 on Mar 18, 2026

  • 1x updated record:

    • < 972b8ddf-e0b3-430e-b598-2c316585e09a 20250930 1 332351000009108 733073007 337971000009100 SubClassOf(:337971000009100 ObjectIntersectionOf(:118698009 :387713003 ObjectSomeValuesFrom(:609096000 ObjectIntersectionOf(ObjectSomeValuesFrom(:260686004 :410820007) ObjectSomeValuesFrom(:405813007 :342051000009109)))))

    • > 972b8ddf-e0b3-430e-b598-2c316585e09a 20260331 1 332351000009108 733073007 337971000009100 SubClassOf(:337971000009100 ObjectIntersectionOf(:71388002 ObjectSomeValuesFrom(:609096000 ObjectIntersectionOf(ObjectSomeValuesFrom(:260686004 :129406001) ObjectSomeValuesFrom(:363701004 :345361000009101) ObjectSomeValuesFrom(:405813007 :342051000009109)))))

  •  

• Inferred Relationships - expected as a result of Julie’s fixes in fix branch VET25-50 (see her email at 21:11 on 17/03/2026):

  • 3x new records:

    • 22656091000009124 20260331 1 332351000009108 337971000009100 118830002 0 116680003 900000000000011006 900000000000451002

    • 22656101000009125 20260331 1 332351000009108 337971000009100 129406001 1 260686004 900000000000011006 900000000000451002

    • 22656111000009128 20260331 1 332351000009108 337971000009100 345361000009101 1 363701004 900000000000011006 900000000000451002

       

  • 2x inactivations:

    • < 936541000009122 20250930 1 332351000009108 337971000009100 410820007 1 260686004 900000000000011006 900000000000451002

    • 936541000009122 20260331 0 332351000009108 337971000009100 410820007 1 260686004 900000000000011006 900000000000451002

    • < 22155301000009123 20250930 1 332351000009108 337971000009100 16453004 0 116680003 900000000000011006 900000000000451002

    • 22155301000009123 20260331 0 332351000009108 337971000009100 16453004 0 116680003 900000000000011006 900000000000451002

Sep 2025 Production (Published) to March 2026 PreProduction Version 7 traceability

CONCLUSION:  Changes as expected:

• moduleDependency has 2x records ADDED, NOT as expected - so the SNAPSHOT looks like the FULL file!!

  • id effectiveTime active moduleId refsetId referencedComponentId sourceEffectiveTime targetEffectiveTime
    8128ff42-5d05-41a6-a757-caa9c573b016 20250930 1 332351000009108 900000000000534007 900000000000207008 20250930 20250201
    8926a585-8dba-4e57-9b63-32e496f86cd0 20260331 1 332351000009108 900000000000534007 900000000000012004 20260331 20260101
    a4b2d96f-ac94-42b3-bdd8-884c6cdceeea 20260331 1 332351000009108 900000000000534007 900000000000207008 20260331 20260101
    78fb8bdd-17dc-403a-bdf5-58aa8bc4c83f 20250930 1 332351000009108 900000000000534007 900000000000012004 20250930 20250201

  • THIS IS BECAUSE WE DIDN’T COPY THE PUBLISHED SEPT FILES BACK INTO THE BRANCH AFTER PUBLISHING, AND SO IT DOESN’T HAVE THE SEPT 25 MDRS RECORDS (with their UUID’s) TO RECONCILE AGAINST - IT JUST CREATES 2x NEW ONES!!

  • SO WE NEED TO TRY IMPORTING THE SEPT 25 MDRS RECORDS (ONLY) INTO THE VET25 PROJECT TO TELL IT WHAT THE CORRECT PREVIOUS RECORDS ARE… that way we can always use the “termServer” version of the MDRS records going forward

  • OR we have to use the externallyMaintained repo to feed them in again, but this won’t fix the problem going forward?

• refsetDescriptor files:

  • 0 changes, as expected

• Concept files:

  • 43 added/updated + 7 inactivated, so seems about right

• Description EN files:

  • 138 added/updated + 157 inactivated, so seems about right

• Description ES files:

  • 0 added/updated + 0 inactivated, so seems about right

• Description IT files:

  • 0 added/updated + 0 inactivated, so seems about right

• Relationship files:

  • 502 added/updated + 275 inactivated, so seems about right

• Relationship Concrete files:

  • 13 added/updated + 0 inactivated, so seems about right

• OWLAxiom files:

  • 77 added/updated + 52 inactivated, so seems about right

• Association files:

  • 10 added/updated + 2 inactivated, so seems about right

• AttributeValue files:

  • 206 added/updated + 6 inactivated, so seems about right

• Language EN files:

  • 12661 added/updated + 251 inactivated, so seems about right

• Language ES files:

  • 0 added/updated + 0 inactivated, so seems about right

• Language IT files:

  • 13 added/updated + 0 inactivated, BUT WHY ARE THERE ANY CHANGES IF NO DESCRIPTION IT changes?

• Simple Refset files:

  • 0 added/updated + 0 inactivated, so seems about right

• Component Annotations files:

  • 0 added/updated + 0 inactivated, so seems about right

• Member Annotations files:

  • 0 added/updated + 0 inactivated, so seems about right

• Text Definition EN files:

  • 4 added/updated + 0 inactivated, so seems about right

• Text Definition ES files:

  • 0 added/updated + 0 inactivated, so seems about right

• Text Definition IT files:

  • 0 added/updated + 0 inactivated, so seems about right

• Readme file as expected:

  • All dates changed to new effectiveTime, BUT number of files remains identical , as expected