Материал: part21

Внимание! Если размещение файла нарушает Ваши авторские права, то обязательно сообщите нам

Page 96​

DICOM PS3.21 2020a - Transformations between DICOM and other Representations​

SR Tree​

Nesting​

Attribute​

Tag​

VR​ VL (hex)​

Value​

Depth​

 

 

 

 

 

 

 

1.6.1.8​ >>>​

Observation UID​(0040,a171)​UI​

002c​

2.25.70160252080234577167847509948368893276​

1.6.1.8​ >>>​

Measured Value​(0040,a300)​SQ​

ffffffff​

 

 

 

 

Sequence​

 

 

 

 

 

%item​

 

 

 

 

 

 

1.6.1.8​ >>>>​

Measurement​

(0040,08ea)​SQ​

ffffffff​

 

 

 

 

Units Code​

 

 

 

 

 

 

 

Sequence​

 

 

 

 

 

%item​

 

 

 

 

 

 

1.6.1.8​ >>>>>​

Code Value​

(0008,0100)​SH​

000c​

g/ml{SUVbw}​

 

1.6.1.8​ >>>>>​

Coding Scheme​(0008,0102)​SH​

0004​

UCUM​

 

 

 

Designator​

 

 

 

 

 

1.6.1.8​ >>>>>​

Code Meaning​

(0008,0104)​LO​

000c​

g/ml{SUVbw}​

 

%enditem​

 

 

 

 

 

 

%endseq​

 

 

 

 

 

 

1.6.1.8​ >>>>​

Numeric Value​

(0040,a30a)​DS​

000e​

2.329186593407​

 

%enditem​

 

 

 

 

 

 

%endseq​

 

 

 

 

 

 

1.6.1.8​ >>>​

Content​

(0040,a730)​SQ​

ffffffff​

 

 

 

 

Sequence​

 

 

 

 

 

%item​

 

 

 

 

 

 

1.6.1.8.1​>>>>​

RelationshipType​(0040,a010)​CS​

0010​

HAS CONCEPT MOD​

1.6.1.8.1​>>>>​

Value Type​

(0040,a040)​CS​

0004​

CODE​

 

1.6.1.8.1​>>>>​

Concept Name​ (0040,a043)​SQ​

ffffffff​

 

 

 

 

Code Sequence​

 

 

 

 

 

%item​

 

 

 

 

 

 

1.6.1.8.1​>>>>>​

Code Value​

(0008,0100)​SH​

0006​

121401​

 

1.6.1.8.1​>>>>>​

Coding Scheme​(0008,0102)​SH​

0004​

DCM​

 

 

 

Designator​

 

 

 

 

 

1.6.1.8.1​>>>>>​

Code Meaning​

(0008,0104)​LO​

000a​

Derivation​

 

%enditem​

 

 

 

 

 

 

%endseq​

 

 

 

 

 

 

1.6.1.8.1​>>>>​

Concept Code​

(0040,a168)​SQ​

ffffffff​

 

 

 

 

Sequence​

 

 

 

 

 

%item​

 

 

 

 

 

 

1.6.1.8.1​>>>>>​

Code Value​

(0008,0100)​SH​

000a​

373098007​

 

1.6.1.8.1​>>>>>​

Coding Scheme​(0008,0102)​SH​

0004​

SCT​

 

 

 

Designator​

 

 

 

 

 

1.6.1.8.1​>>>>>​

Code Meaning​

(0008,0104)​LO​

0004​

Mean​

 

%enditem​

 

 

 

 

 

 

%endseq​

%enditem​

%endseq​ %enditem​

- Standard -​

DICOM PS3.21 2020a - Transformations between DICOM and other Representations​

Page 97​

SR Tree​ Nesting​

Attribute​

Tag​

VR​ VL (hex)​

Value​

 

Depth​

 

 

 

 

 

 

 

%item​

 

 

 

 

 

 

 

1.6.1.9​ >>>​

RelationshipType​(0040,a010)​CS​

0008​

CONTAINS​

 

 

1.6.1.9​ >>>​

Value Type​

(0040,a040)​CS​

0004​

NUM​

 

 

1.6.1.9​ >>>​

Concept Name​ (0040,a043)​SQ​

ffffffff​

 

 

 

 

Code Sequence​

 

 

 

 

 

 

%item​

 

 

 

 

 

 

 

1.6.1.9​ >>>>​

Code Value​

(0008,0100)​SH​

0006​

126401​

 

 

1.6.1.9​ >>>>​

Coding Scheme​(0008,0102)​SH​

0004​

DCM​

 

 

 

Designator​

 

 

 

 

 

 

1.6.1.9​ >>>>​

Code Meaning​

(0008,0104)​LO​

0006​

SUVbw​

 

 

%enditem​

 

 

 

 

 

 

 

%endseq​

 

 

 

 

 

 

 

1.6.1.9​ >>>​

Observation UID​(0040,a171)​UI​

002c​

2.25.140657026119469861895824082767088344984​

1.6.1.9​ >>>​

Measured Value​(0040,a300)​SQ​

ffffffff​

 

 

 

 

Sequence​

 

 

 

 

 

 

%item​

 

 

 

 

 

 

 

1.6.1.9​ >>>>​

Measurement​

(0040,08ea)​SQ​

ffffffff​

 

 

 

 

Units Code​

 

 

 

 

 

 

 

Sequence​

 

 

 

 

 

 

%item​

 

 

 

 

 

 

 

1.6.1.9​ >>>>>​

Code Value​

(0008,0100)​SH​

000c​

g/ml{SUVbw}​

 

 

1.6.1.9​ >>>>>​

Coding Scheme​(0008,0102)​SH​

0004​

UCUM​

 

 

 

Designator​

 

 

 

 

 

 

1.6.1.9​ >>>>>​

Code Meaning​

(0008,0104)​LO​

000c​

g/ml{SUVbw}​

 

 

%enditem​

 

 

 

 

 

 

 

%endseq​

 

 

 

 

 

 

 

1.6.1.9​ >>>>​

Numeric Value​

(0040,a30a)​DS​

0010​

1.8828952323684​

 

 

%enditem​

 

 

 

 

 

 

 

%endseq​

 

 

 

 

 

 

 

1.6.1.9​ >>>​

Content​

(0040,a730)​SQ​

ffffffff​

 

 

 

 

Sequence​

 

 

 

 

 

 

%item​

 

 

 

 

 

 

 

1.6.1.9.1​>>>>​

RelationshipType​(0040,a010)​CS​

0010​

HAS CONCEPT MOD​

 

1.6.1.9.1​>>>>​

Value Type​

(0040,a040)​CS​

0004​

CODE​

 

 

1.6.1.9.1​>>>>​

Concept Name​ (0040,a043)​SQ​

ffffffff​

 

 

 

 

Code Sequence​

 

 

 

 

 

 

%item​

 

 

 

 

 

 

 

1.6.1.9.1​>>>>>​

Code Value​

(0008,0100)​SH​

0006​

121401​

 

 

1.6.1.9.1​>>>>>​

Coding Scheme​(0008,0102)​SH​

0004​

DCM​

 

 

 

Designator​

 

 

 

 

 

 

1.6.1.9.1​>>>>>​

Code Meaning​

(0008,0104)​LO​

000a​

Derivation​

 

 

%enditem​

 

 

 

 

 

 

 

%endseq​

 

 

 

 

 

 

 

- Standard -​

Page 98​

DICOM PS3.21 2020a - Transformations between DICOM and other Representations​

SR Tree​

Nesting​

Attribute​

Tag​

VR​ VL (hex)​

Value​

Depth​

 

 

 

 

 

 

 

1.6.1.9.1​>>>>​

Concept Code​

(0040,a168)​SQ​

ffffffff​

 

 

 

 

Sequence​

 

 

 

 

 

%item​

 

 

 

 

 

 

1.6.1.9.1​>>>>>​

Code Value​

(0008,0100)​SH​

000a​

386136009​

 

1.6.1.9.1​>>>>>​

Coding Scheme​(0008,0102)​SH​

0004​

SCT​

 

 

 

Designator​

 

 

 

 

 

1.6.1.9.1​>>>>>​

Code Meaning​

(0008,0104)​LO​

0012​

Standard Deviation​

 

%enditem​

 

 

 

 

 

 

%endseq​

 

 

 

 

%enditem​

 

 

 

 

%endseq​

 

 

 

 

%enditem​

 

 

 

 

%item​

 

 

 

 

1.6.1.10​>>>​

RelationshipType​(0040,a010)​CS​

0008​

CONTAINS​

1.6.1.10​>>>​

Value Type​

(0040,a040)​CS​

0004​

TEXT​

1.6.1.10​>>>​

Concept Name​ (0040,a043)​SQ​

ffffffff​

 

 

Code Sequence​

 

 

 

%item​

 

 

 

 

1.6.1.10​>>>>​

Code Value​

(0008,0100)​SH​

0006​

121106​

1.6.1.10​>>>>​

Coding Scheme​(0008,0102)​SH​

0004​

DCM​

 

Designator​

 

 

 

1.6.1.10​>>>>​

Code Meaning​

(0008,0104)​LO​

0008​

Comment​

%enditem​

 

 

 

 

%endseq​

 

 

 

 

1.6.1.10​>>>​

Text Value​

(0040,a160)​UT​

0014​ PT / WB NAC P600 / 0​

%enditem​

 

 

 

 

%endseq​

%enditem​

%endseq​ %enditem​ %endseq​

A.8 Overview of Data Types​

DICOM data types are specified in PS3.5 of the Standard (PS3.5).​

TheAIMV4datatypesareasubsetof[ISO21090],whichareinturnbasedon[V3DTR1].TheAIMV4datatypesusedaredocumented​ in [AIM v3 v4 changes] and [Extending AIM].​

While a complete comparison of DICOM and [ISO 21090] data types, cardinality and optionality is beyond the scope of this mapping​ guide, some hints are given on topics that are relevant for transforming AIM instances and DICOM SR Measurement Reports.​

The AIM V4 model uses the data types as specified in Table A.8-2 from [ISO 21090], of which only a subset are encountered in use​ cases described by this mapping. In XML encoded AIM instances, the data type is not explicitly encoded, though it is defined in the​ UML model.​

- Standard -​

DICOM PS3.21 2020a - Transformations between DICOM and other Representations​

Page 99​

 

Table A.8-1. ISO 21090 Data Types used in AIM V4​

 

ISO 21090 Data Types​

Description​

 

BL​

Boolean (two-valued logic). A BL value can be either true or false, or may have a nullFlavor.​

 

CD​

ConceptDescriptor.Areferencetoaconceptdefinedinanexternalcodesystem,terminologyorontology,​

 

or an expression in some syntax defined by the referenced code system.​

 

II​

Instance Identifier. An identifier that uniquely identifies a thing or object. Instance identifiers are usually​

 

defined based on ISO object identifiers.​

 

INT​

Integer. No arbitrary limit is imposed on the range of integer numbers.​

 

REAL​

Fractional numbers. The typical representation is decimal.​

 

ST​

Character string. Shall have at least one character or else have a nullFlavor.​

 

TS​

Point in time. A quantity specifying a point on the axis of natural time. Most often represented as a​

 

calendar expression.​

 

Additional data type mapping considerations include:​

a.​Optionality and nullFlavor​

If the original AIM instance does not include values that are required or mandatory in DICOM SR TID 1500, fixed values are​ specifiedsinceemptyvaluesarenotpermittedinDICOMSRTEXTandCODEentriesandomittingtheContentItemwouldviolate​ the template constraints. All nullFlavor values are treated as empty, except for numeric values.​

b.​Character Sets​

DICOM provides information on the interpretation of text data types by specifying a default character set (ISO-IR 6) and "Specific​ Character Set" (0008,0005) values that are used if the Basic Graphic Set is expanded or replaced. For AIM, the XML declaration​ attribute "encoding" (overall document) and the attribute "charset" (for ST data type values) may be used to provide information​ oncharactersets.SeethedescriptionofSpecificCharacterSetinSectionA.6.1.1.11“MappingofDICOMSOPCommonModule”.​

c.​Character strings​

In general, ST text value attributes in AIM XML elements are mapped to DICOM Text Value (0040,A160) of value type TEXT​ (with a VR of Unlimited Text (UT)) in the SR Content Tree. No maximum length is specified for AIM elements and attributes.​

Some text value attributes in AIM XML elements are mapped to Attributes in the DICOM header, and DICOM length limits may​ apply to character strings such as Long String (LO), e.g., Patient ID.​

d.​Identifiers​

Unique identifiers in AIM V4 are encoded as the root attribute of an XML element (aim:uniqueIdentifier/@root), which has an II​ data type, and are mapped to the DICOM UI VR, which is limited to 64 bytes.​

e.​Codes​

Codes in AIM V4 are encoded as attributes of the aim:typeCode XML element and are mapped as specified in Table A.8-2 below​ for the [ISO 21090] code data type (CD). The code and codeSystemName attributes are encountered as attributes of the​ aim:typeCodeXMLelement,butthedisplayNameisthevalueattributeofachildelement,aim:typeCode/iso:displayName/@value.​ Note that codeSystem (Coding Scheme UID) is usually not sent, even though it is required by [ISO 21090]. DICOM also supports​ other Attributes for encoding code values that exceed 16 characters in length.​

Table A.8-2. Mapping between DICOM Basic Code Attributes and AIM ISO 21090 Code Data Types​ (CD)​

DICOM Attribute and VR​

AIM Element and Attribute and ISO 21090 Data Type​

Code Value (0008,0100)​

SH​

aim:typeCode/@code​

CD.characterstring​

Coding Scheme UID (0008,0x010C)​UI​

aim:typeCode/@codeSystem​

CD.characterstring​

- Standard -​

Page 100​

DICOM PS3.21 2020a - Transformations between DICOM and other Representations​

 

DICOM Attribute and VR​

AIM Element and Attribute and ISO 21090 Data Type​

Coding Scheme Designator​

SH​

aim:typeCode/@codeSystemName​ CD.characterstring​

(0008,0102)​

 

 

Coding Scheme Version (0008,0103)​SH​

aim:typeCode/@codeSystemVersion​ CD.characterstring​

Code Meaning (0008,0104)​

LO​

aim:typeCode/iso:displayName/@value​CD.ST​

f.​ Date and Time​

•​The AIM V4 XML element aim:dateTime/@value attribute corresponds to the ISO 21090 TS data type, and is mapped to the​ DICOM DateTime (DT) VR, or the combination of separate Date (DA) and Time (TM) Attributes.​

•​DICOM DT matches TS except for the number of decimal places of fractional seconds (6 for DT versus 4 for TS).​

•​DICOM DA matches the TS part YYYYMMDD (Y=Year, M=Month, D=Day), except that TS may be missing DD or MMDD.​

•​DICOM TM matches the TS part HHMMSS.UUUUUU (H=Hour, M=Minute, S=Second, U=Fractional Second) except for the​ number of decimal places of fractional seconds (6 for DT versus 4 for TS).​

•​If available, the DICOM Timezone Offset From UTC (0008,0201) used for DA or TM data types may be populated using time​ zone offset values from the ISO 21090 TS value.​

•​ISO TS allows for separators; these need to be removed for conversion to DT, DA and TM.​

g.​Person Names​

•​DICOM Person Name (PN) shall be mapped from [ISO 21090] data type Person Name (PN) as described in Table A.8-3.​

Table A.8-3. Mapping between DICOM Person Name (PN) ans ISO 21090 Data Type Person Name​ (PN)​

DICOM Person Name (PN)​

ISO 21090 Data Type: Person Name (PN)​

<family_name_complex>​

Family Part type​

<given_name_complex>​

Given Part type​

<middle_name>​

Given Part type - order of parts matters​

<name_suffix>​

Suffix Part type​

<name_prefix>​

Prefix Part type​

•​[ISO 21090] PN may contain multiple given names. DICOM PN Middle Name shall be mapped to [ISO 21090] PN Given Name​ Part type.​

Example A.8-1. Person Name Example​

John Robert Morrison, Ph.D. "Morrison^John Robert^^^Ph.D." [One family name; two given names; no middle name; no prefix;​ one suffix] can be represented as a [ISO 21090] Person Name (PN) in the following way:​

<name>

<given>John</given>

<given>Robert</given>

<family>Morrison</family>

<suffix>Ph.D.</suffix>

</name>

- Standard -​

Источник: https://studfile.net/preview/14585774/