MajwareMAJWARE
General

(0008,0018)

SOP Instance UID

Keyword: SOPInstanceUID

Uniquely identifies one object: one image, report, presentation state or other instance. It must never be reused for different content.

Tag Attributes

Tag ID
(0008,0018)
Compact
00080018
Keyword
SOPInstanceUID
VR
UI — Unique Identifier (UID)
VM
1
Required
Type 1 — required, with a value
PS3.15
Basic Profile action U
Retired
No

Defined in

SOP Common Module

What SOP Instance UID contains

SOP Instance UID is the identity of one DICOM object. Archives identify stored objects by it, and Storage Commitment, key object selections, presentation states and structured reports all refer to images by it.

The rule is simple: the same object keeps the same UID wherever it is copied, and different content gets a different UID. A lossy-compressed copy, a reprocessed image or a de-identified copy is new content and needs a new SOP Instance UID.

Every copy of the same object keeps the same SOP Instance UID, wherever it is stored. A new or changed object, such as a reprocessed image or a lossy-compressed copy, needs a new one.

Group 0008 holds general identifying information: what kind of object this is, when it was made, and by which equipment and people.

Value format: UI (Unique Identifier (UID)), VM 1

(0008,0018) SOPInstanceUID has Value Representation UI (Unique Identifier (UID)) and Value Multiplicity 1, which means exactly one value.

UI — Unique Identifier (UID)

A globally unique identifier made of numeric components separated by periods, for example 1.2.840.10008.1.2.1. An odd-length value is padded with one trailing NULL byte.

Length
64 bytes maximum
Characters
The digits 0–9 and the period.

Example value

2.25.268434151379112284556391137408731940317

Format mistakes to avoid

  • A component may not start with a zero unless it is the single digit 0, so 1.2.03 is invalid.
  • Letters, spaces and values longer than 64 bytes are invalid.

Where SOPInstanceUID appears

Defined inTypeMeaning
SOP Common ModulePS3.3 C.12.11Required, and it must have a value.

A module lists the attributes an object must or may carry. Many IODs (CT Image, MR Image, Secondary Capture and others) include the same module, and an IOD-specific module can make an attribute stricter than the general one.

In a C-FIND query using the Study Root Query/Retrieve Information Model, it is a IMAGE-level key of type U: a Unique Key: one value identifies a single entity at that level.

De-identification (PS3.15)

PS3.15 Table E.1-1 gives SOP Instance UID the Basic Profile action U: replace it with a new UID that stays consistent across every instance in the de-identified set.

With the Retain UIDs Option, the action is K: keep it unchanged (a sequence is kept but cleaned item by item).

To see how de-identification changes your own files, try the free DICOM Anonymizer, which runs in the browser and uploads nothing.

In archives and migrations

SOP Instance UIDs are the key of every migration check: an object is in the new archive when its SOP Instance UID is found there. Changing them during a move breaks every reference from reports, presentation states and key images.

Common errors and how to fix them

  • Same UID, different image

    The UID generator of a device or tool is not unique. Stop it before more collisions happen, and give the affected objects new UIDs according to the archive vendor's correction procedure.

  • The same object sent twice

    Sending an object again with the same UID is normal, for example after a retry. Whether the archive ignores the copy or replaces the stored object is a configuration choice; check the archive's documentation before resending large volumes.

Troubleshooting: Two different objects with the same SOP Instance UID cannot both be stored correctly: a receiving archive may reject the second or treat it as a replacement of the first. Duplicates come from UID generation that is not unique, for example two devices configured with the same UID root or a cloned configuration. Fix the generator; do not edit UIDs by hand.

Check a file in seconds with the free DICOM Validator: it reads the header in your browser, lists the tags with their values, and flags missing or malformed key attributes.

SOP Instance UID: frequently asked questions

What is DICOM tag (0008,0018) SOP Instance UID?

Uniquely identifies one object: one image, report, presentation state or other instance. It must never be reused for different content. SOP Instance UID is the identity of one DICOM object. Archives identify stored objects by it, and Storage Commitment, key object selections, presentation states and structured reports all refer to images by it.

What VR and VM does SOP Instance UID (0008,0018) have?

(0008,0018) SOPInstanceUID has Value Representation UI (Unique Identifier (UID)) and Value Multiplicity 1, which means exactly one value. A globally unique identifier made of numeric components separated by periods, for example 1.2.840.10008.1.2.1. An odd-length value is padded with one trailing NULL byte. Maximum length: 64 bytes maximum.

Is SOP Instance UID (0008,0018) required?

In the SOP Common Module (PS3.3 C.12.1) it is Type 1: required, and it must have a value.

Can you query a PACS by SOP Instance UID?

In a C-FIND query using the Study Root Query/Retrieve Information Model, it is a IMAGE-level key of type U: a Unique Key: one value identifies a single entity at that level.

How is SOP Instance UID handled when de-identifying DICOM files?

PS3.15 Table E.1-1 gives SOP Instance UID the Basic Profile action U: replace it with a new UID that stays consistent across every instance in the de-identified set. With the Retain UIDs Option, the action is K: keep it unchanged (a sequence is kept but cleaned item by item).

How do I troubleshoot SOP Instance UID (0008,0018)?

Two different objects with the same SOP Instance UID cannot both be stored correctly: a receiving archive may reject the second or treat it as a replacement of the first. Duplicates come from UID generation that is not unique, for example two devices configured with the same UID root or a cloned configuration. Fix the generator; do not edit UIDs by hand.

Check SOPInstanceUID in your files

The free DICOM Validator lists every header tag and flags problems. Files stay in your browser.

Open DICOM Validator →

Remove patient data before sharing

The free DICOM Anonymizer applies a de-identification profile in your browser, with no upload.

Open DICOM Anonymizer →

Sources

Checked against the DICOM standard, release 2026d. Module Types, query keys and de-identification actions come from these tables:

More General tags