SOPInstanceUID for derived copies
Assign new SOPInstanceUIDs so derived images don't collide with their originals.
Problem
You apply a pixel transformation (Flip, Crop, Resample, Window/Level Bake) to a DICOM image. The resulting output is a derived image — different pixel data — and per the DICOM standard (PS3.15 §E.3.1), it must receive a new SOP Instance UID. Using the original UID on a derived image breaks referential integrity: two different images with the same UID cannot coexist in a PACS.
Steps
-
Open the file (⌘O) and note the original SOP Instance UID (0008,0018) in Edit mode.
-
Open Pixel Operations — ⌘K → “Pixel operations…”.
-
Select a transform (Flip, Crop, Resample, or Bake W/L) and click Apply transform.
-
Verify the new UID — filter for SOP Instance UID in Edit mode. The value should:
- Be different from the original UID
- Start with
2.25.(OID root for UUID-derived identifiers) - Be non-empty
Expected Result
- The derived copy has a distinct, non-empty SOP Instance UID.
- The original instance’s UID is unchanged (the transform produces a derived copy, not an in-place modification).
- The
2.25.prefix indicates UUID-v5 derivation, which is deterministic — the same input always produces the same output UID. - All related UIDs (Series Instance UID, Study Instance UID) are also regenerated on the derived copy to maintain referential integrity.