DICOM“媒体存储SOP实例UID"是否确实存在?="SOP实例UID"?为什么? [英] Is it true that DICOM "Media Storage SOP Instance UID" = "SOP Instance UID"? Why?

查看:79
本文介绍了DICOM“媒体存储SOP实例UID"是否确实存在?="SOP实例UID"?为什么?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我在阅读《纽约时报》时有两个问题DICOM标准:

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

在DICOM文件中,(0002 0003)媒体存储SOP实例UID"和(0008 0018)"SOP实例UID",它们是相同的吗?怎么了(00020002)和(0008 0016)?以及为什么??

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 ??

推荐答案

Chris是正确的,它们是相同的.来自dicom标准部分 C.12.1.1.1 :

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

为所有定义了SOP类UID和SOP实例UID属性DICOM IOD.但是,它们仅在复合IOD中使用类型等于1.请参阅第C.1.2.3节.当编码时,它们应相等到DIMSE Services和 File Meta中的它们各自的属性信息标题(请参阅PS3.10媒体存储).

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).

关于这些项目重复的原因,我只能推测,但是文件元信息标题仅存在于dicom文件中(SCP/SCU不会传输).SCP从接收到的DICOM数据写入文件时,必须从数据集中获取SOP类和实例UID,因此这是机械上相同的原因.至于为什么使用这些标签而不是其他标签,我相信有很多原因,但是请注意,任何dicom实体始终可以读取 File Meta Information Header (文件元信息标题),因为它甚至始终是"Little Endian Explicit"如果以下数据集是一些奇怪的传输语法.因此,始终保证这两个字段在任何有效的dicom文件中都是可读和可用的(即使第8组版本的传输语法不可读).

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).

我还尝试查找条件:

但是,它们仅在复合IOD中编码

However, they are only encoded in Composite IODs

当我查看标准时,几乎每个IOD都是一个复合IOD:

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

归一化IOD

复合IOD

这篇关于DICOM“媒体存储SOP实例UID"是否确实存在?="SOP实例UID"?为什么?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆