DICOM PS3.5 2017b - Data Structures and Encoding

B Creating a Privately Defined Unique Identifier (Informative)

Privately defined Unique Identifiers (UIDs) are used in DICOM to uniquely identify items such as Specialized or Private SOP Classes, Image SOP Instances, Study SOP Instances, etc.

B.1 Organizationally Derived UID

A UID may be formed using a registered root (see Annex C) and an organization specific suffix. The manner in which the suffix of such an organizationally derived UID is defined is not constrained by the DICOM Standard. Only the guarantee of its uniqueness by the defining organization is required by DICOM.

The following example presents a particular choice made by a specific organization in defining its suffix to guarantee uniqueness of a SOP Instance UID.

   \___________/ \______________________/
       root     .         suffix

In this example, the root is:

  • 1 Identifies ISO

  • 2 Identifies ANSI Member Body

  • 840 Country code of a specific Member Body (U.S. for ANSI)

  • xxxxx Identifies a specific Organization.(assigned by ANSI)

In this example the first two components of the suffix relate to the identification of the device:

  • 3 Manufacturer defined device type

  • 152 Manufacturer defined serial number

The remaining four components of the suffix relate to the identification of the image:

  • 235 Study number

  • 2 Series number

  • 12 Image number

  • 187636473 Encoded date and time stamp of image acquisition

In this example, the organization has chosen these components to guarantee uniqueness. Other organizations may choose an entirely different series of components to uniquely identify its images. For example it may have been perfectly valid to omit the Study Number, Series Number and Image Number if the time stamp had a sufficient precision to ensure that no two images might have the same date and time stamp.

Because of the flexibility allowed by the DICOM Standard in creating organizationally derived UIDs, implementations should not depend on any assumed structure of UIDs and should not attempt to parse UIDs to extract the semantics of some of its components.

DICOM PS3.5 2017b - Data Structures and Encoding