Destination Mappings

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

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

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

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

Destination Table

This table shows you all currently configured destinations for your channel. You can see at a glance the type of each destination, whether it is enabled, what chain it belongs to, and more. Column Description Status Indicates whether the destination is enabled or disabled. Only enabled destinations process messages. A channel must have at least one destination enabled. Destination Double-click this cell to edit the name of the destination. Note that while a destination may be renamed, its metadata ID will remain the same. Id The metadata ID that uniquely identifies this destination within the current channel. Connector Type The type of destination connector. To change this, select the destination from the table and choose a new type from the drop-down menu directly below the table. Chain The chain this destination connector belongs to. The first destination in the table is automatically placed into chain #1. To start a new chain, select a subsequent destination from the table, and unch

Mirth® Connect by NextGen Healthcare User Guide

Mapper Transformer Step

This step extracts data from a field in the message (or an expression) and places it into one of the available Variable Maps. Depending on the scope of the map, this variable will be available in subsequent steps, in the destination connector properties, or even in subsequent connectors. Item Name Description Variable The variable name / key to use when inserting into the map. The Add to drop-down menu to the right determines which map to place the variable in. For additional information, see Variable Maps. Mapping The value to place into the map. This may be a field from the message, or any JavaScript expression. Default Value If the Mapping is not found or evaluates to an empty string, this value / expression will be used instead. String Replacement This table allows you to perform replacements on the value before it gets inserted into the map. Regular Expression: A Java-style regular expression to test against the value. This will implicitly set the global regex flag. Replace With:

Destination Mappings

Recommendations

Variable Maps

Configuration Map

Channel Writer

The Variable Map Lookup Sequence

Destination Table

Mapper Transformer Step

Destination Mappings

Variable Maps

Configuration Map

Channel Writer

The Variable Map Lookup Sequence

Destination Table

Mapper Transformer Step