Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Is it true that DICOM "Media Storage SOP Instance UID" = "SOP Instance UID"? Why?

Tags:

uid

dicom

I have two questions when I am reading the DICOM standard:

In a DICOM file, (0002 0003)"Media Storage SOP Instance UID" and (0008 0018) "SOP Instance UID", are they the same? What about (0002 0002) and (0008 0016)? and Why ??

like image 945
Sujeeth Damodharan Avatar asked Sep 21 '15 07:09

Sujeeth Damodharan


People also ask

What is Dicom SOP instance UID?

In DICOM, a SOP Instance (e.g. a specific CT image) is the instance of the Class, e.g. a CT Image IOD. Unique Identifiers (UIDs) are used to identify everything in DICOM, from the SOP classes to the individual objects. They are registered by a standards organization to prevent duplication.

What is media storage SOP instance UID?

Media Storage SOP Instance UID (0002,0003) 1 Uniquely identifies the SOP Instance associated with the Data Set placed in the file and following the File Meta Information.

What is referenced SOP Class UID?

The Referenced SOP Class/Instance UID are always items of a sequence, and the sequence defines the meaning of the reference. The Referenced Image Sequence does not refer to Modality Worklist, it refers to images and other objects only.


2 Answers

Chris is correct, they are the same. From the dicom standard section C.12.1.1.1:

The SOP Class UID and SOP Instance UID Attributes are defined for all DICOM IODs. However, they are only encoded in Composite IODs with the Type equal to 1. See Section C.1.2.3. When encoded they shall be equal to their respective Attributes in the DIMSE Services and the File Meta Information header (see PS3.10 Media Storage).

As to the reason why these items are duplicated, I can only speculate, but the File Meta Information Header only exists in dicom files (it is not transmitted by an SCP/SCU). When an SCP writes a file from the DICOM data it receives, it has to get the SOP class and instance UIDs from the dataset, so that is the mechanical reason they are the same. As to why these tags and not some others, I am sure there are many reasons, but note that the File Meta Information Header is always readable by any dicom entity as it is always "Little Endian Explicit" even if the following dataset is some weird transfer syntax. So these two fields are always guaranteed to be readable and usable in any valid dicom file (even if the group 8 versions are in an unreadable transfer syntax).

I also tried to look up the condition:

However, they are only encoded in Composite IODs

Almost every IOD is a Composite IOD when I look at the standard:

Normalized IODs

Composite IODs

like image 59
rkh Avatar answered Sep 24 '22 03:09

rkh


Yes they are the same. Tags with group 0002 are part of the DICOM P10 header, I assume they are duplicated so they can be quickly read without having to parse the entire file.

like image 45
Chris Hafey Avatar answered Sep 23 '22 03:09

Chris Hafey