Материал: part03

Note​

1.​This is intended for use by the radiologist, technologist and/or​ physicist during management of the Protocol to understand the​ purpose the Protocol Element serves in the Protocol.​

2.​It is not intended to be copied into the Series Description. Rather​ there is an Attribute in the Performed Storage Module called​ RequestedSeriesDescription(0018,9937)thatisintendedtobe​ copied into the Series Description of the stored instances.​

Protocol Element​ (0018,9923)​ 3​ Summary description of characteristics of this element.​

Characteristics Summary​

Note​

1.​This is intended for use by the radiologist, technologist and/or​ physicist during management of the Protocol to understand the​ characteristics of the Protocol Element.​

2.​It is not intended to be copied into the Series Description. Rather​ there is an Attribute in the Performed Storage Module called​ RequestedSeriesDescription(0018,9937)thatisintendedtobe​ copied into the Series Description of the stored instances.​

10.29 UDI Macro​

This Macro records details associated with a Unique Device Identifier (UDI).​

Table 10.29-1. UDI Macro Attributes​

10.29.1 Unique Device Identifier​

The UDI is a combination of the Device Identifier and the Production Identifier.​

The format of the string is defined by a corresponding Issuing Agency, such as:​

•​GS1 - http://www.gs1.org​

•​HIBCC - http://www.hibcc.org​

•​ICCBBA - http://www.iccbba.org​

Details for encoding a valid device identifier are managed by the Issuing Agency. For full documentation, refer to issuer materials.​

The United States FDA requires the Issuing Agency to use only characters and numbers from the invariant character set of ISO/IEC​ 646 (ISO 7-bit coded character set also known as ISO IR 6). DICOM puts no constraints on the length of the string or the character​ sets beyond the UT Value Representation. Implementations should be prepared to handle very large strings and unusual characters.​

- Standard -​

10.30 Assertion Macro​

This Macro is used to record Assertions made by a person or device about the content of a SOP Instance. The nature of the Assertion​ is defined by the Assertion Code.​

The scope of the Assertion (e.g., whether it applies to the whole instance, to a specific Item in a Sequence, etc.) is described at the​ point where the Macro is included. It is also expected that when this Macro is included, the Baseline CID for the Assertion Code Se-​ quence (0044,0101) will be constrained.​

Table 10.30-1. Assertion Macro Attributes​

- Standard -​

One or more Items are permitted in this Sequence.​

Note​

For example, an Assertion that overrides a previous​ Assertion or disapproves a previously approved​ protocol, could reference the prior approval instance​ making it easier to find/correlate/confirm.​

10.31 Entity Labeling Macro​

The Entity Labeling Macro provides identification of an entity to a user.​

This information is intended for display to human readers. Shall not be used for structured processing.​

Table 10.31-1. Entity Labeling Macro Attributes​

10.31.1 Entity Labeling Macro Attribute Descriptions​

10.31.1.1 Entity Label​

The Entity Label (3010,0035) Attribute represents a user-defined short free text providing the primary identification of this entity to​ other users.​

10.31.1.2 Entity Name and Entity Description​

The optional Attribute Entity Name (3010,0036) allows a longer string containing additional descriptive identifying text. The optional​ Attribute Entity Description (3010,0037) provides additional information when needed.​

10.32 Entity Long Labeling Macro​

The Entity Long Labeling Macro provides identification of an entity to a user.​

This information is intended for display to human readers. Shall not be used for structured processing.​

Table 10.32-1. Entity Long Labeling Macro Attributes​

- Standard -​

10.32.2 Entity Long Labeling Macro Attribute Descriptions​

10.32.2.1 Entity Long Label​

The Entity Long Label (3010,0038) Attribute represents a user-defined free text providing the primary identification of this entity to​ other users.​

10.33 Conceptual Volume Macro​

A Conceptual Volume is an abstract entity used to identify an anatomic region (such as a planning target volume or a combination of​ multiple anatomic volumes) or non-anatomic volumes such as a bolus or a marker. A Conceptual Volume can be established without​ necessarily defining its spatial extent (for example a Conceptual Volume for a tumor can be established prior to segmenting it). The​ spatial extent of a Conceptual Volume may change over time (for example as treatment proceeds the tumor volume corresponding​ to the Conceptual Volume will change).​

The spatial extent of a Conceptual Volume may be defined by any general-purpose entity that represents geometric information (such​ as Segmentation, Surface Segmentation, RT Structure Set SOP Instance and alike) or a combination thereof, although the Concep-​ tual Volume does exist independently of a specific definition of its spatial extent.​

A Conceptual Volume may also be defined as a combination of other Conceptual Volumes.​

Examples for Conceptual Volumes:​

1.​A Conceptual Volume (with a Conceptual Volume UID (3010,0006) can be used to represent the treatment target in an RT​ Physician Intent SOP Instance based upon a diagnostic image set, although the actual delineation of a specific target volume​ has not yet taken place. Later, the target volume is contoured. The RT Segment Annotation SOP Instance references the volume​ contours and associates it with the Conceptual Volume via the Conceptual Volume UID (3010,0006).​

2.​Inanadaptiveworkflow,theanatomicvolumemaychangeovertime.TheConceptualVolumeontheotherhanddoesnotchange.​ Multiple RT Segment Annotation SOP Instances, each referencing different Segmentation instances, can be associated with the​ same Conceptual Volume via the Conceptual Volume UID (3010,0006) , making it possible to track the volume over time.​

3.​AConceptualVolumemayrepresenttargetsand/oranatomicregionsforwhichmanuallycalculateddosesaretracked(forexample,​ in emergency treatments). In this case, Conceptual Volumes may be instantiated first in an RT Physician Intent SOP instance​ andsubsequentlyusedinRTRadiationSOPinstances,ormaybefirstinstantiatedintheRadiationSOPinstances.Aftertreatment,​ these Conceptual Volumes will be used in RT Radiation Records to track the delivered dose. Such Conceptual Volumes may​ neverreferenceasegmentation,butserveasakeyforreferencingtheConceptualVolumeacrossthesedifferentSOPinstances.​

Table 10.33-1. Conceptual Volume Macro Attributes​

Required when Conceptual Volume UID (3010,0006) was​ notissuedinthecurrentSOPInstance,butreadfromanother​ SOP instance.​

Only a single Item shall be included in this Sequence.​

>Include Table 10-11 “SOP Instance Reference Macro Attributes”​

- Standard -​

Shall reference only segment Items that contain the Direct​

Segment Reference Sequence (3010,0023).​

- Standard -​