This COM interface is defined and implemented by HL7Connect for use by other applications.

Called by an incoming scripted message interface basis. If the script determines that a message is to be generated, then it should create one (using Kernel.CreateHL7Message or one of it's variants) and send it using the Event's SendMessage method

The script is called under two different circumstances (as configured). Either it is called on a regular schedule, or it is called when there are items in the virtual queue to be processed. If the event is called because there is a message or document in a virtual queue, then one of the IncomingMessage, IncomingDocument or IncomingDicom properties will be non-null, and the script must set IncomingHandled to true - or else the same item will be processed repeatedly

Note that this is the one place in HL7Connect where documents, messages and DICOM Images can mix - this event requires an outgoing message, but one of documents, messages or images will come in, depending on the configuration of the interface

KScript: the generated content is sent to the kernel as a v2.xml message (One message per execution). IncomingHandled is set to true if the script executes and the message is accepted. Note: KScript is not configured to work usefully with incoming dicom messages at this time.


IncomingMessage : IHL7ConnectMessage
IncomingDocument : IHL7ConnectDocument
IncomingDicom : IHL7ConnectDicomMessage
IncomingHandled : Boolean
EventName : String
IsTestCase : Boolean
Parameter : String


SendMessage(AMessage : IHL7Message) : IHL7Message
SendMessageEx(AMessage : IHL7Message, ASourceParameter : String) : IHL7Message

© Kestral Computing P/L 2000 - 2003. HL7Connect v2.00-063 generated on 30-Nov 2015.
Keywords: ICheckMessageEvent, TCheckMessageEvent