One standard Composite Instance Root Retrieve Information Model is defined in this Annex. The Composite Instance Root Retrieve Information Model is associated with a number of SOP Classes. The following hierarchical Composite Instance Root Retrieve Information Model is defined:
Composite Instance Root
The Composite Instance Root Information Model is based upon a two level hierarchy:
Composite Instance
Frame
The Composite Instance level is the top level and contains only the SOP Instance UID. The Frame level is below the Composite Instance level and contains only the Attributes that refer to a selection of the frames from a single multi-frame image object.
The following rules for the use of Frame Range Keys apply to both an SCU creating such keys and to an SCP interpreting them.
The selection of frames to be included in a new created SOP Instance made in response to a FRAME level Composite Instance Root Retrieve request shall be defined by one of the mechanisms defined in this section, and the list of frames so specified shall be referred to as the "Frame List".
Re-ordering of frames is not supported, and order of the frames in the Frame List will always be the same as in the original SOP Instance.
New allowable frame selection mechanisms may be defined in the future by the addition of new SOP classes
Simple Frame List (0008,1161) is a multi-valued Attribute containing a list of frame numbers, each specifying a frame to be included in the returned object. The first frame of the source instance shall be denoted as frame number 1.
The frame numbers in the list shall not contain any duplicates, and shall increase monotonically.
Due to the use of UL for this element, a maximum of 16383 values may be specified, as only a 2 byte length is available when an explicit VR Transfer Syntax is used.
Calculated Frame List (0008,1162) is a multi-valued Attribute containing a list of 3-tuples, each representing a sub-range of frames to be included in the returned object. The first frame of the source instance shall be denoted as frame number 1.For each 3-tuple: .
The first number shall be the frame number of the first frame of the sub-range.
The second number shall be the upper limit of the sub-range, and shall be greater than or equal to the first number.
The third number shall be the increment between requested frames of the sub-range. This shall be greater than zero.
The difference between the first and second numbers is not required to be an exact multiple of the increment.
If the difference between the first and second numbers is an exact multiple of the increment, then the last frame of the sub-range shall be the second number.
If the first number is greater than the number of frames in the referenced SOP Instance then that sub-range shall be ignored.
The sub-ranges shall be non-overlapping such that the sequence of frame numbers determined by concatenating all the sub-ranges shall not contain any duplicates, and shall increase monotonically. A value of FFFFFFFFH or any value greater than the number of frames in the referenced SOP Instance as the second value shall denote the end of the set of frames in the referenced SOP Instance, and may only occur in the last 3-tuple.
For example, if the Calculated Frame List contains 6 values, 2, 9, 3, 12, FFFFFFFFH, 5 and is applied to an Instance containing 25 frames. The resulting Frame List will contain the values 2, 5, 8, 12, 17 and 22.
Time Range (0008,1163) contains the start and end times to be included in the returned object. Times are in seconds, relative to the value of the Content Time (0008,0033) in the parent object.
The range shall include all frames between the specified times including any frames at the specified times.
The range may be expanded as a consequence of the format in which the information is stored. Where such expansion occurs, any embedded audio data shall be similarly selected. Under all circumstances, the returned Composite SOP Instance shall retain the relationship between image and audio data.
For MPEG-2 this would be to the nearest surrounding Key Frames
For JPEG 2000 Part 2, this would be to nearest surrounding precinct or tile boundary
Time Range shall only be used to specify extraction from SOP instances where the times of frames can be ascertained using one or more of the following Attributes:
Frame Time (0018,1063)
Frame Time Vector (0018,1065)
Frame Reference DateTime (0018,9151) in the Frame Content Sequence (0020,9111)
When a C-MOVE or C-GET operation is performed on a source Composite Instance at the FRAME level then the SCP shall create a new Composite Instance according to the following rules:
The new Composite Instance shall be extracted from the source Composite Instance specified by the SOP Instance UID Unique Key present at the Composite Instance Level.
The new Composite Instance shall be an instance of the same SOP Class as the source Composite Instance.
The new Composite Instance shall have a new SOP Instance UID.
The new Composite Instance shall be a valid SOP Instance.
The new Composite Instance is required to be internally consistent and valid. This may require the SCP to make consistent modification of any Attributes that reference frames or the relationship between them such as start time, time offsets, and modifying the Per-frame Functional Group Sequence (5200,9230).
The new Composite Instance shall contain the frames from the source Composite Object as requested in the Requested Frame List. The Requested Frame List shall be interpreted according to the rules in Section Y.3.2. The frames shall be in the same order as in the source Composite Instance.
The new Composite Instance shall include the Frame Extraction Module, which shall contain appropriate Attributes from the identifier of the C-GET or C-MOVE request that caused this instance to be created. If the Frame Extraction Module already exists in the source Composite Instance, then a new item shall be appended as an additional item into the Frame Extraction Sequence.
The new Composite Instance shall contain the Contributing Equipment Sequence (0018,A001). If the source Composite Object contains the Contributing Equipment Sequence, then a new Item shall be appended to the copy of the sequence in the new Composite Instance, and if the source Composite Object does not contain the Contributing Equipment Sequence, then it shall be created, containing one new Item. In either case, the new Item shall describe the equipment that is extracting the frames, and the Purpose of Reference Code Sequence (0040,A170) within the Item shall be (109105, DCM, "Frame Extracting Equipment").
The existing General Equipment Module cannot be used to hold details of the creating equipment, as it is a Series level Module. The new Composite Instance is part of the same Series as the source Instance, and therefore the Series level information cannot be altered.
The new Composite Instance shall have the same Patient, Study and Series level information as the source Instance, including Study and Series Instance UIDs.
The new Composite Instance shall have the same values for the Attributes of the Image Pixel Module of the source Composite Instance except that the Pixel Data Provider URL (0028,7FE0) Attribute shall not be present,Pixel Data (7FE0,0010) shall be replaced by the subset of frames, as specified in section Section Y.3.3, and Number of Frames (0028,0008) shall contain the number of frames in the new Composite Instance.
The new Composite Instance shall have the same values for other Type 1 and Type 2 Image level Attributes that are not otherwise specified. Other Attributes may be included in the new Composite Instance if consistent with the new Composite Instance.
In most cases private Attributes should not be copied unless their full significance is known. See Annex ZZ “Implant Template Description”for more guidance.
The new Composite Instance shall not be contained in a Concatenation. This means that it shall not contain a Concatenation UID (0020,9161) Attribute or other Concatenation Attributes. If the existing Composite Instance contains such Attributes, they shall not be included in the new Composite Instance.