The outcome of a response to sending/processing the document. The document 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 document 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.

If the document is rejected, some text description is expected to explain why the document is rejected. HL7Connect will always populate the text message; if a sending script chooses not to send a document, it *should* populate this field.


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

Other values are droAccepted, droTimeout, or droRejected.

-- List of possible document responses





TDocumentResponseRejectionCause Cause;
   If a document is rejected, it may be unclear why - in particular, is it worth sending again? the cause is an optional property that may assist a sender to decide whether to resend the document. Note that not all transports report the case back to the sender.

Possible values: drrcUnknown, drrcTransient, drrcDocument, drrcPolicy

-- List of possible rejection causes





string Reason;
   Text explanation for a failure or timeout.


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: Outcome, TextSummary, Reason, Cause, HL7Connect.Exchange.DocumentResponse, DocumentResponse