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
Result
The derived copy gets its own non-empty SOP Instance UID — 2.25., UUID-v5 and therefore deterministic for the same input — while the original’s UID is unchanged. Related Series and Study UIDs are regenerated on the copy to keep references consistent.