The N-CREATE-RQ Message contains fields as defined in Table 10.3-9. Each field shall conform to DICOM encoding and Value Representation as defined in PS 3.5. Fields are required as specified in the N-CREATE service definition unless otherwise noted in Table 10.3-9. Fields not specified in the N-CREATE service definition but present in Table 10.3-9 are required by the DIMSE-N protocol.
Table 10.3-9N-CREATE-RQ MESSAGE FIELDS
|Message Field||Tag||VR||VM||Description of Field|
|Command Group Length||(0000,0000)||UL||1||The even number of bytes from the end of the value field to the beginning of the next group.|
|Affected SOP Class UID||(0000,0002)||UI||1||SOP Class UID of the SOP Instance to be created.|
|Command Field||(0000,0100)||US||1||This field distinguishes the DIMSE-N operation conveyed by this Message. The value of this field shall be set to 0140H for the N-CREATE-RQ Message.|
|Message ID||(0000,0110)||US||1||Implementation-specific value which distinguishes this Message from other Messages.|
|Command Data Set Type||(0000,0800)||US||1||This field indicates that if a Data Set is present in the Message. This field shall be set to the value of 0101H if no Data Set is present; any other value indicates a Data Set is included in the Message.|
|Affected SOP Instance UID||(0000,1000)||UI||1||Contains the UID of the SOP Instance to be created.|
|Attribute List||(no tag)||⎯||⎯||This field is encoded as a Data Set. One Data Element is encoded for each Attribute and Attribute Value applicable to the operation.|
Note: The permitted contents of Attribute List, encoded as a series of Data Elements, are defined in the Information Object Definition (PS 3.3) and Service Class Specifications (PS 3.4).