Limitations in message variations
Limitations in message variations include:
- The standard C-Service and N-Service DIMSE Headers are included as segment files.
- The standard Data Element is
included as a field.
Any Data Element that is tagged as retired in the 2014a spec is not included as a standard Data Element. If you require using a retired Data Element, then you must use the IDE to add retired fields to the DICOM variant. Otherwise, the retired Data Element cannot be displayed in the IDE and handled by the engine.
- Standard DICOM messages that are ready to use are not provided, because the DICOM message is not defined in the DICOM specification. You must define your own DICOM message in the DICOM variant according to the incoming DICOM message.
A DICOM message should be composed of only two segments in separate groups.
Example
{
C_STORE_RQ_DIMSE <- Group 0 (Standard C STORE Request DIMSE)
}
{
C_STORE_DATASET <- Group 1 (User defined C STORE DATASET)
}
Group 0
should be the DIMSE Header segment. You can
use the standard C-Service or N-Service DIMSE Header segment file.
Group 1
should be the DATASET part of a DICOM message. You can use the
IDE to configure the DATASET segment file or use
hcidicomdefgen
to create the DATASET segment file
based on a DICOM message.