Channel Destination Components |
A channel's destination component dictates where the data will be going. The complete list of source components that are currently shipped with Iguana are described in the following table:
| Channel Destination Component | Description |
|---|---|
| LLP Client: | The destination end of the channel will be a TCP/IP port at a target IP address. All HL7 messages received from the channel's source component will be sent to the target IP address using LLP over TCP/IP, the defacto standard for delivering HL7 messages over a network. |
| To Database: | The destination end of the channel will be a set of database tables. All HL7 messages received from the channel's source component will be parsed using iNTERFACEWARE's Chameleon messaging engine. A mapping file (VMD file) is used to determine what data is needed from the incoming messages and where it should be placed in the database. |
| To Plugin (called Client Executable in versions of Iguana prior to 4.0): | This component allows users to write an application, in a selected language, that connects to Iguana to receive messages. Iguana can be configured to start the external application and take control of it, or Iguana can start and wait for the external application and wait for its connection. |
| To File: | The destination end of the channel will be a file or files on the local machine. All HL7 messages received from the channel's source component will be written to the file(s). |
| To Message Filter: (Iguana 3.3 and earlier only) | The destination end of the channel will be a message filter. All HL7 messages received from the channel's source component will be stored "as is", and will be picked up by message filter source components in other channels. This component, along with the message filter source component, allows Iguana to route messages to multiple destinations, filter messages and map (graphical transformation or scripted transformation) messages. In Iguana 4.0 or later, you do not need to specify Message Filter as a destination component for a channel, as you can apply a filter to any channel. For details, see Configuring the Filter. |
| To XML File: (Iguana 3.3 and earlier only) | The destination end of the channel will be the XML file(s) on the local machine. All HL7 messages received from the channel's source component will be written to the XML file(s). In Iguana 4.0 or later, you can specify a filter for your channel that transforms messages from HL7 format to XML. For details, see Configuring the Filter. |
| To Channel (Iguana 4.0 or later only): | The destination end of the channel will be another Iguana channel. |
| To HTTPS (Iguana 4.0 or later only): | The destination end of the channel will be an HTTPS connection to a channel defined by another instance of Iguana. The source component of the other channel must be From HTTPS. |
One of the most common configurations is a channel with From Database as the source and LLP Client as the destination. This would involve taking data directly from a database and sending it to a target application in the form of an HL7 message. Conversely, a channel with LLP Listener as the source and To Database as the destination would extract data from incoming HL7 messages and place it into database tables.