Channel Writer

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 will be included in the source map of the destination channel's message. Note: This table expects only variable names, not Velocity replacement tokens. For example, do not use ${varName}, instead use varName. The value will be extracted from all available Variable Maps.
C	Template	${message.encodedData}	The actual payload to send to the target channel. By default the encoded data of this destination will be used. Velocity Variable Replacement is supported here.

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

JavaScript Writer

This destination connector executes a custom user-defined JavaScript script. This can be used in a wide variety of ways, such as calling out to external Java libraries or invoking a local OS shell script. You can return custom values that determine what response data to store, and what status to put the destination connector message into. Or simply use the script as a generic job that doesn't necessarily produce responses. For example, you can use tools like ChannelUtil to programmatically start/stop/deploy channels from within the script. Supported property groups: Destination Settings JavaScript Writer Return Values Parent topic: Destination Connectors

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

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

Mirth® Connect by NextGen Healthcare User Guide

Source Map Variables

When this connector sends a message to another channel, the following source map variables will be available on the downstream message: 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 Writer

Mirth® Connect by NextGen Healthcare User Guide

Configuration Map

This map is also available across your entire server, across all channels and all messages. Like the global map, that means you can use the values from the configuration map in any channel, or somewhere else like an Alert. Unlike the global map however, this map is editable only from the Configuration Map Settings Tab, and is read-only from the perspective of channels / messages. The values are also String key/values only. This map is useful for global, static settings you want to persist across restarts of Mirth Connect. For example, you could store a variable like "clientAdtPort" and then use Velocity to reference that variable ("${clientAdtPort}") in a TCP Listener. That way you can export the channel on one Mirth® Connect installation, import it into a completely different installation, and then you would not have to edit anything in the channel settings as long as the configuration map is set on both instances. Get configuration map value: var value = configurationMap.get('key');

Channel Writer

Recommendations

The Variable Map Lookup Sequence

JavaScript Writer

Source Map Variables

Variable Maps

Source Map Variables

Configuration Map

Channel Writer

The Variable Map Lookup Sequence

JavaScript Writer

Source Map Variables

Variable Maps

Source Map Variables

Configuration Map