API for declarative purposes, DICOM is not supported, and the API should be expected to change without notice ***

The outcome of processing a Dicom Message. The Dicom Message may be accepted or rejected.

If rejected, then the rejection *may* indicate whether the rejection is believed to be due to internal transient conditions, whether the condition is related to the content of the Dicom message itself, or whether it is caused by some business rules (policy). Note that it can be very hard to tell these conditions apart in the presence of an unexpected error, so the value should never be taken as gospel.

Some text description is expected to explain why the Dicom is rejected (Explanation). This won't make it into an actual DICOM Abort PDU, but it will appear in various HL7Connect records and logs. If a sending script chooses not to fill the response out, it *should* populate this field.


TDocumentResponseOutcome Outcome;
   The result of processing the Dicom. Before the script executes, this is set to droUnknown. If the script doesn't change this value, the Dicom will be processed as expected (either received or sent).

Other values are droAccepted, droTimeout, or droRejected. If a script sets the value to droRejected, it should populate the code and comment too.

-- List of possible document responses





int Code;
   An optional application-specific error code with value 1 - 65535 (0 is no error)

Goes in Dicom Element (0000,0903)

string Comment;
   Text explanation for a failure or timeout.

Goes in Dicom Element (0000,0902)


string TextSummary();
   One line string suitable for inclusion in logs etc that sumamrises the response

© Kestral Computing P/L 2000 - 2003. HL7Connect v2.00-063 generated on 30-Nov 2015.
Keywords: Code, Comment, Outcome, TextSummary, HL7Connect.Exchange.DicomResponse, DicomResponse