MajwareMAJWARE
File Meta

(0002,0003)

Media Storage SOP Instance UID

Keyword: MediaStorageSOPInstanceUID

Uniquely identifies the SOP Instance associated with the Data Set placed in the file and following the File Meta Information.

Tag Attributes

Tag ID
(0002,0003)
Compact
00020003
Keyword
MediaStorageSOPInstanceUID
VR
UI — Unique Identifier (UID)
VM
1
Required
Type 1 — required, with a value
PS3.15
Basic Profile action U
Retired
No

Defined in

File Meta Information

What Media Storage SOP Instance UID contains

It should be identical to SOP Instance UID (0008,0018) in the data set. A tool that replaces SOP Instance UID, for example during de-identification, must put the same new value here.

Group 0002 is the File Meta Information defined in PS3.10. It sits at the start of every DICOM file, is always encoded in Explicit VR Little Endian, and is not part of the data set that is sent over the network.

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

(0002,0003) MediaStorageSOPInstanceUID 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.172045226314590876829360981346738294751

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 MediaStorageSOPInstanceUID appears

Defined inTypeMeaning
File Meta InformationPS3.10 Table 7.1-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.

De-identification (PS3.15)

PS3.15 Table E.1-1 gives Media Storage 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

Group 0002 belongs to the file, not to the data set. A C-STORE sends only the data set, and the receiving system writes its own File Meta header when it saves the object. After a transfer, the File Meta values describe the system that wrote the copy you are looking at, which is not necessarily the system that created the image.

Common errors and how to fix them

Troubleshooting: If it differs from SOP Instance UID (0008,0018), a tool changed only one of the two. Set the File Meta value to the data-set value and keep them in step from then on.

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.

Media Storage SOP Instance UID: frequently asked questions

What is DICOM tag (0002,0003) Media Storage SOP Instance UID?

Uniquely identifies the SOP Instance associated with the Data Set placed in the file and following the File Meta Information.

What VR and VM does Media Storage SOP Instance UID (0002,0003) have?

(0002,0003) MediaStorageSOPInstanceUID 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 Media Storage SOP Instance UID (0002,0003) required?

In the File Meta Information (PS3.10 Table 7.1-1) it is Type 1: required, and it must have a value.

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

PS3.15 Table E.1-1 gives Media Storage 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 Media Storage SOP Instance UID (0002,0003)?

If it differs from SOP Instance UID (0008,0018), a tool changed only one of the two. Set the File Meta value to the data-set value and keep them in step from then on.

Check MediaStorageSOPInstanceUID 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 File Meta tags