Source Map Variables

Key	Description
sourceChannelId	The unique ID of the channel that dispatched a message to the current channel.
sourceMessageId	The ID of the message from which the current message dispatch originated.
sourceChannelIds	If there are more than two channels in a Channel Writer -> Reader chain, this will be a List containing the IDs of all channels in the chain.
sourceMessageIds	If there are more than two channels in a Channel Writer -> Reader chain, this will be a List containing the IDs of all messages in the chain.

Mirth® Connect by NextGen Healthcare User Guide

Channel Writer

The Channel Writer is a connector that simply dispatches messages to other internal channels. This can be useful if you split your message workflow into multiple channels, where one sends to another. If no target channel is specified, the connector acts as a "sink" where no message dispatching is done. Note that a channel does not need to use a Channel Reader source for a Channel Writer to be able to send messages to it. The connector also has options to inject source map variables into the downstream message of the target channel. Supported property groups: Destination Settings Item Name Default Value Description A Channel Id <None> The unique ID of the target channel to send messages to. This may be a hard-coded ID, or may be a Velocity Variable Replacement. Use the drop-down menu to the right to quickly select a particular channel. If <None> is selected, the destination will act as a "sink" where messages are not dispatched anywhere. B Message Metadata The map variables entered here

Mirth® Connect by NextGen Healthcare User Guide

Source Map Variables

If this connector receives a message from a Channel Writer, the following source map variables will be available: Key Description sourceChannelId The unique ID of the channel that dispatched a message to the current channel. sourceMessageId The ID of the message from which the current message dispatch originated. sourceChannelIds If there are more than two channels in a Channel Writer -> Reader chain, this will be a List containing the IDs of all channels in the chain. sourceMessageIds If there are more than two channels in a Channel Writer -> Reader chain, this will be a List containing the IDs of all messages in the chain. Parent topic: Channel Reader

Mirth® Connect by NextGen Healthcare User Guide

The Variable Map Lookup Sequence

In many cases when referencing map variables in Mirth® Connect, you do not call out to a specific map, but instead use the generic lookup function: var value = $('variableName'); Or, you might reference a variable using Velocity Variable Replacement: ${variableName} When you do this, Mirth® Connect will automatically look that key up in all available maps. That may only be the configuration/global map (in the case of the global scripts) , or it may be all maps (in the case of a filter / transformer script) . This sequence is followed: Response Map Connector Map Channel Map Source Map Global Channel Map Global Map Configuration Map For example, if you have stored a variable called "dataSource" in both the Connector Map and the Global Channel Map, the one from the Connector Map will be used. If you want the value specifically from the Global Channel Map instead, you can use the map-specific get function shown in the Variable Maps section: var dataSource = globalChannelMap.get('dataSource

Mirth® Connect by NextGen Healthcare User Guide

Message Content

Message content is the actual data that gets processed. As a message flows through your channel, different versions of the data are stored for each connector, depending on the modifications your channel needs to make. Source Connector Raw - The state of the message as it enters the connector. Processed Raw - The state of the message after passing through the preprocessor script. Transformed - The serialized internal representation of the message, which exists only if a connector has a filter or transformer configured. Encoded - The state of the message as it exits the transformer (includes changes made to the transformed data). Response - The message sent back to the originating system (at the very end, after all destinations finish). Destination Connector Raw - The state of the message as it enters the connector. For a destination connector, this is the same as the source encoded data. Transformed - The serialized internal representation of the message, which exists only if a connecto

Mirth® Connect by NextGen Healthcare User Guide

Batch Processing

Batch Processing allows a channel to receive a single message, but split it into multiple messages that each get processed through the channel. When using this along with a source connector that supports streaming (File Reader, TCP Listener in MLLP mode), batch processing has the added benefit of not having to read the entire file into memory all at once, but instead only one message at a time. For example with the File Reader and batch processing you can read in files that are gigabytes in size, without causing any memory issues for your Mirth Connect server. Data types that support batch processing will have a Batch Properties section in the source inbound data type properties. To enable batch processing, set Process Batch to Yes in the Source Settings. To change how an incoming message is split into multiple messages, look at the Batch Properties section of the source inbound data type you are using. For example, the Delimited Text Data Type has options to split by record delimiter,

Mirth® Connect by NextGen Healthcare User Guide

Variable Maps

Throughout the Message Processing Lifecycle, your channels and messages have access to various maps. Depending on the scope, the map may only be available in the current channel/connector, or may be globally available across your entire system. These variable maps allow you to store a piece of information that can be used later (in a downstream channel, connector, or somewhere else). A common use for these variables is to provide easy drag-and-drop for connector properties. The Destination Mappings list will display all available connector/channel map variables for example. They are also used in other ways, such as populating Custom Metadata Columns. The following variable maps exist throughout Mirth® Connect: Name JavaScript Variable Get/Put Shortcut Variable Response Map responseMap $r Connector Map connectorMap $co Channel Map channelMap $c Source Map sourceMap $s Global Channel Map globalChannelMap $gc Global Map globalMap $g Configuration Map configurationMap $cfg The table above

Source Map Variables

Recommendations

Channel Writer

Source Map Variables

The Variable Map Lookup Sequence

Message Content

Batch Processing

Variable Maps

Channel Writer

Source Map Variables

The Variable Map Lookup Sequence

Message Content

Batch Processing

Variable Maps