Additional information in message metadata
The engine saves other information in message metadata to help the DICOM protocol work.
Information that is saved to DriverControl
includes:
CallingAET
: The modality sending the request.CalledAET
: The modality expected to reply the request.ReplyAET
. The modality replies the request. This is appended only to the reply message.AbstractSyntax
: Used to construct the TRXID.TransferSyntax
: Used to parse and encode the DICOM message.
Examples
Data message (DICOM request)
msgDriverControl : {CallingAET FINDSCU} {CalledAET DICOMTEST} {AbstractSyntax 1.2.840.10008.5.1.4.31}
{TransferSyntax 1.2.840.10008.1.2}
Reply message (DICOM response)
msgDriverControl : {CallingAET FINDSCU} {CalledAET DICOMTEST} {AbstractSyntax 1.2.840.10008.5.1.4.31}
{TransferSyntax 1.2.840.10008.1.2} {ReplyAET DICOMTEST}