Материал: part03

3.​An example of an Attribute that might be included in the Unassigned Shared Converted Attributes Macro is Series​ Number (0020,0011), which typically would be the same for all Classic CT images in a set (but is not required to be),​ and will be replaced with a different value in the top-level Data Set, and hence if the original is to be preserved, needs​ to be recorded.​

4.​An example of an Attribute that might be included in the Unassigned Per-Frame Converted Attributes Macro is Instance​ Number (0020,0013), which typically would be different for each Classic CT image in a set, and will be replaced with a​ different value in the top-level Data Set, and hence if the original is to be preserved, needs to be recorded.​

5.​The UIDs of the converted instances are recorded in the Conversion Source Attributes Sequence, and are not included​ in the Unassigned Shared and Per-Frame Converted Attributes Macros.​

For the purpose of comparing values, an Attribute that is not present in a Classic image to be converted is considered the same as​ an Attribute that is present but has no value. Sequence Attributes match when they have the same number of Items and Item contents​ in the same order (irrespective of whether the Sequences or Items are encoded with fixed or variable length).​

The Unassigned Shared Converted Attributes Sequence, and the Unassigned Per-Frame Converted Attributes Sequence may be​ absent, if there are no such Attributes available to be included. E.g., there may be no shared Attributes with the same values, all the​ shared Attributes may be included in the top-level Data Set, there may be no Attributes that vary per-frame or an individual frame​ may have no such Attribute.​

ThenecessaryPrivateCreatorDataElementwithineachSequenceItemaccompaniesPrivateDataElements.Thereisnorequirement​ to preserve the private block of Data Elements used in the Classic images to be converted. Nor is there a requirement that a Private​ Data Element use the same private block in all of the Classic images.​

Matching of Private Attribute Values for the purpose of determining whether they are shared or per-frame may be performed using​ the equivalent meaning if the Value Representation is Explicit and not UN, or known through other means, otherwise, byte matching​ of the UN VR shall be performed.​

C.7.6.16.2.25.1 Unassigned Shared Converted Attributes Macro​

Table C.7.6.16.2.25.1-1 specifies the Attributes of the Unassigned Shared Converted Attributes Functional Group Macro.​

Table C.7.6.16.2.25.1-1. Unassigned Shared Converted Attributes Macro Attributes​

values,thathavethesamevalues,andthatarenotinthetop-levelData​ Set.​

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

Required if any unassigned shared Attributes are present.​

C.7.6.16.2.25.2 Unassigned Per-Frame Converted Attributes Macro​

Table C.7.6.16.2.25.2-1 specifies the Attributes of the Unassigned Per-Frame Converted Attributes Functional Group Macro.​

Table C.7.6.16.2.25.2-1. Unassigned Per-Frame Converted Attributes Macro Attributes​

- Standard -​

C.7.6.16.2.25.3 Image Frame Conversion Source Macro​

Table C.7.6.16.2.25.2-1 specifies the Attributes of the Image Frame Conversion Source Functional Group Macro.​

Table C.7.6.16.2.25.3-1. Image Frame Conversion Source Macro Attributes​

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

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

C.7.6.16.2.26 Stored Value Color Range Macro​

Table C.7.6.16.2.26-1 defines the Attributes of the Stored Value Color Range Functional Group Macro​

Table C.7.6.16.2.26-1. Stored Value Color Range Macro Attributes​

C.7.6.16.2.26.1 Stored Value Color Range Macro Attributes Description​

The voxel values of the Parametric Map shall be mapped to RGB values using the following transformation.​

All values smaller than Minimum Stored Value Mapped (0028,1231) shall be treated as equal to this minimum value.​

All values larger than Maximum Stored Value Mapped (0028,1232) shall be treated as equal to this maximum value.​

The values between Minimum Stored Value Mapped (0028,1231) and Maximum Stored Value Mapped (0028,1232) shall be mapped​ to the Palette Color LUT using a linear interpolation function.​

Note​

The Palette Color LUT can be segmented and interpolation needs to accommodate the segmentation.​

In case of floating point mapping the second value of the Palette Color Lookup Table Descriptor is not used in the mapping as the​ Minimum Stored Value Mapped (0028,1231) is used as start value for the LUT values.​

- Standard -​

Stored Values (floats/doubles)

Color LUT

R G B

Minimum Stored Value Mapped (0028,1231)

Palette Color

Number of Entries

Maximum Stored Value Mapped (0028,1232)

Figure C.7.6.16.2.26.2-1. Stored Value Color Range​

C.7.6.16.2.27 Frame Usefulness Macro​

Table C.7.6.16.2.27-1 specifies the Attributes of the Frame Usefulness Functional Group Macro, related to the clinical usefulness of​ the current frame.​

Table C.7.6.16.2.27-1. Frame Usefulness Functional Group Macro Attributes​

Enumerated Values:​

YES​

NO​

C.7.6.16.2.28 Camera Position Macro​

Table C.7.6.16.2.28-1 specifies the Attributes of the Camera Position Functional Group Macro, related to the position of the camera​ or the acquisition device for the current frame, with regards to the patient.​

- Standard -​

DICOM PS3.3 2020a - Information Object Definitions​ Page 589​

Table C.7.6.16.2.28-1. Camera Position Functional Group Macro Attributes​

See Section C.11.30.1.​

C.7.6.16.2.29 Time of Frame Macro​

Table C.7.6.16.2.29-1 specifies the Attributes of the Time of Frame Functional Group Macro, related to the time of frame.​

Table C.7.6.16.2.29-1. Time of Frame Functional Group Macro Attributes​

C.7.6.17 Multi-frame Dimension Module​

The Multi-frame Dimension Module contains a Sequence with Items pointing to Attributes defining a set of dimensions that are usually​ known prior to the acquisition commencing. It is up to the generating applications to decide what Attributes are important to describe​ the multi-frame dimensions.​

The application that generates the Concatenation or SOP Instances may use the order of Dimension Index Pointers (0020,9165) in​ the Dimension Index Sequence (0020,9222) to guide the receiving application in determining the order of the presentation of image​ frames. The first index has the highest ranking, the next index has a lower ranking, etc. Frames with higher values for the dimension​ with the highest ranking would only be presented after all frames that have values for Dimension Index Pointers (0020,9165) of the​ lower rankings have been presented.​

If the set of Dimension Index Pointers does not provide an Attribute set whose values are unique for each frame then the order for​ the frames with the same value set will be incompletely specified. The receiving application could use the logical frame number to​

- Standard -​

resolve this ambiguity. If the Attribute set contains more dimensions than are needed to specify a unique ordering, the lower order​ ranking Attribute(s) will have no effect on the ordering.​

Note​

For example if there were the following indices in the following order:​

•​Stack ID (1-3)​

•​In-stack Position Number (1-2 for Stack ID 1, 1-4 for Stack ID 2, 1-3 for Stack ID 3)​

•​Effective Echo Time (1-2), i.e., every slice has been scanned with 2 different effective echo's​

Then the frames could be presented in the following order:​

(Stack ID, In-stack Position, Effective Echo Time)​

(1,1,1), (1,1,2), (1,2,1), (1,2,2),​

(2,1,1), (2,1,2), (2,2,1), (2,2,2), (2,3,1), (2,3,2), (2,4,1), (2,4,2)​

(3,1,1), (3,1,2), (3,2,1), (3,2,2), (3,3,1), (3,3,2)​

The actual order of the frames in the object is up to the generating application.​

If the effective echo time was not included in the Dimension Index Pointers in the above example then the order of sorting​ for the frames with the same indices will be undefined - in this case there would be 2 frames with the index set (Stack ID,​ In-stack Position) = (1,1) and the order of these frames is not specified.​

If there were another Attribute appended to the Dimension Index Pointers, for example TR, then the TR index would not be​ usedindeterminingtheorderoftheframes.SotheIndexFramePointerswouldcontain(StackID,In-stackPosition,Effective​ Echo Time, TR) but the TR index would be irrelevant for frame ordering purposes.​

Table C.7.6.17-1 specifies the Attributes of the Multi-frame Dimension Module.​

Table C.7.6.17-1. Multi-frame Dimension Module Attributes​

TILED_FULL​ Tiled image in which each frame represents a single tile​ and the spatial positions of the tiles are implicitly defined​ as per Section C.7.6.17.3.​

TILED_SPARSE​Tiled image in which each frame represents a single tile​ and the spatial positions of tiles are explicitly defined by​ per-frame Functional Group Macro entries.​

- Standard -​