Annex B(Informative)Creating a privately defined unique identifier

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.

A UID is formed using a registered root (see Annex C) and an organization specific suffix. The manner in which the suffix of a Privately Defined UID is defined is not constrained by the DICOM Standard. Only the guarantee of its uniqueness by the defining organization is required by DICOM. This example presents a particular choice made by a specific organization in defining its suffix to guarantee uniqueness. A variant is discussed.

"1.2.840.xxxxx.3.152.235.2.12.187636473"

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.(provided by ANSI)

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

3 Manufacturer or user defined device type

152 Manufacturer or user 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 Privately Defined 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.