Variable Maps

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

Mirth® Connect by NextGen Healthcare User Guide

Channel Map

This map is isolated to the current message as it processes through a channel. If you store a connector map variable in the source connector, you will have access to that value in all subsequent destinations. However when the current message finishes and the next one begins, that next message will not have access to the value you stored for the previous message. The channel map is useful for anything that needs to be shared among multiple destinations, or the source connector and all destinations. For example, you might have one HTTP Sender destination that makes a request to a remote service, and then in the Response Transformer you store a particular response HTTP header in the channel map. As long as the next destination connector is in the same chain, it will have access to that channel map variable, and can do something else with it, like include it on a subsequent HTTP request. Get channel map value: var value = channelMap.get('key'); var value = $c('key'); Put channel map value:

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

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');

Mirth® Connect by NextGen Healthcare User Guide

General Channel Properties

General Channel properties are configured on the Summary Tab within the Edit Channel View and include: Unique ID, name, and description. Links to Code Template Libraries: These let the channel know which custom functions are available in specific JavaScript contexts. Links to Library Resources: These let the channel know which custom Java classes are available in specific connectors and/or JavaScript contexts. Deploy/Start Dependencies: These determine which channels are dependent on this one, and also which channels are dependencies for this one. This way you can have some channels deploy and start before others. Attachment Handler: This allows you to extract pieces of any incoming message and store them separately. As a message processes through a channel, multiple copies of it will be held in memory at once (for the raw / transformed / encoded versions of a message). Attachments are stored only once, so by using them you can greatly reduce your channels' memory footprint. Message St

Mirth® Connect by NextGen Healthcare User Guide

Destination Mappings

This section is to the right of the destination connector properties, and allows you to easily drag-and-drop common variables/templates into fields of the connector properties. Standard variables/templates are available across all destination connectors. Custom mapper variables come from the Mapper Steps you have added in the current destination or in any previous destinations. For additional information on Velocity replacement, see Velocity Variable Replacement. Standard Variables/Templates Parent topic: Destinations Tab

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

Variable Maps

Recommendations

Channel Map

The Variable Map Lookup Sequence

Configuration Map

General Channel Properties

Destination Mappings

Channel Writer

Variable Maps

Channel Map

The Variable Map Lookup Sequence

Configuration Map

General Channel Properties

Destination Mappings

Channel Writer