Ancestor: HL7Connect.Events.InterfaceBase

This event is called immediately before a Dicom Message is sent. If the script chooses, it can abort further message sending by setting the Response.Outcome to either droAccepted or droRejected.

The script is able to modify the message as it chooses but it should maintain a valid Dicom message.

The logs are written after this event

XSLT: the input is the message to be sent (in XML format used in the development environment), the output replaces the document to be sent

Properties

HL7Connect.Exchange.DicomMessage Message;
   A handle to the actual Dicom Messages to be sent

HL7Connect.Dicom.DicomMessageList Replies;
   A list of replies to the message. For this event, the list will be empty. The script can fill out the replies as required.

Note that this event has both Replies and Response. The Response controls the behaviour of the HL7Connect kernel when it comes to re-sending, etc. The contents of the replies are ignored for this purpose. If the message is being passed through from an incoming interface, and it sets the response.outcome to a value other than droUnknown, then if it defines one or more reply messages, these will be sent to the original SCU. If no messages are defined, and the response.outcome is set to a value other than droUnknown, then HL7Connect will build the appropriate reply message based on the information in the response

HL7Connect.Exchange.DicomResponse Response;
   Response for this message. Leave the Response.Outcome as drcUnknown, and the document will be sent to the transport layer

If the script sets the response to droRejected, then the kernel will handle the error as configured. If the script sets the response to droAccepted, the kernel will assume that the script has processed the message.

Note that this event has both Replies and Response. The Response controls the behaviour of the HL7Connect kernel when it comes to re-sending, etc. The contents of the replies are ignored for this purpose. If the message is being passed through from an incoming interface, and it sets the response.outcome to a value other than droUnknown, then if it defines one or more reply messages, these will be sent to the original SCU. If no messages are defined, and the response.outcome is set to a value other than droUnknown, then HL7Connect will build the appropriate reply message based on the information in the response

HL7Connect.Kernel.Interface SourceInterface;
   Handle the source interface that received the Document. It is possible that the source interface is no longer valid, in which case the value will be null


Methods

void SendToInterface(string Name);
   Send the message to the named (dicom) interface

Note that this is not immediate; instead, the message will be added to the queue after the script finishes executing kernel after the script executes.

void SendToInterfaceWithParams(string Name, string OutTranslationParam, string InTranslationParam);
   Send the message to the named (dicom) interface with translation parameters for the scripts.

Note that this is not immediate; instead, the message will be added to the queue after the script finishes executing kernel after the script executes.

void SendToVirtualQueue(string Name);
   Send the message to the named virtual queue.

Note that this is not immediate; instead, the message will be added to the queue after the script finishes executing

void SendToVirtualQueueWithPartition(string Name, string Partition);
   Send the message to the named virtual queue with a specified partition.

Note that this is not immediate; instead, the message will be added to the queue after the script finishes executing


© Kestral Computing P/L 2000 - 2003. HL7Connect v2.00-063 generated on 30-Nov 2015.
Keywords: Response, Message, SendToInterface, SendToInterfaceWithParams, SendToVirtualQueue, SendToVirtualQueueWithPartition, SourceInterface, Replies, SendDicomMessage, HL7Connect.Events.SendDicomMessage