Restructuring

Duplicate instance removal

Detect and drop duplicate instances that share a SOP Instance UID.

Problem

Your dataset contains duplicate DICOM instances: the same SOP Instance UID appears in two different files. This happens when files are copied between folders, when a PACS export includes redundant copies, or when a CD import brings in files already archived. Duplicate SOP Instance UIDs violate DICOM uniqueness constraints and cause PACS import errors.

Steps

  1. Open the files (⌘O). Load the same file twice to simulate duplicates (e.g. test.dcm loaded twice).

  2. Switch to the Files tab in the right rail.

  3. Check the Dedupe button. Dedupe (1) means one duplicate was found.

  4. Click Dedupe. The duplicate instance is removed. The button updates to Dedupe (0) and becomes disabled.

  5. Verify. Only unique instances remain. The files tree shows the correct count.

When No Duplicates Exist

  • Load a single file with no duplicates.
  • The Dedupe button shows Dedupe (0) and is disabled.

Result

Dedupe keeps the first-loaded copy of each duplicate SOP Instance UID and removes the rest. An instance with no SOP Instance UID counts as a duplicate when an earlier instance, also without one, has the same Series Instance UID and Instance Number. Dedupe works on whole instances: it does not compare or remove frames inside a multi-frame object.