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.
"1.2.840.xxxxx.3.152.235.2.12.187636473"
\___________/ \______________________/
root . suffix
In this example, the root is:
In this example the first two components of the suffix relate to the identification of the device:
The remaining four components of the suffix relate to the identification of the image:
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.
Original: https://www.cnblogs.com/h2zZhou/p/13496122.html
Author: h2z
Title: StudyUID命名规则
原创文章受到原创版权保护。转载请注明出处：https://www.johngo689.com/546715/
转载文章受原作者版权保护。转载请注明原作者出处！