Mapper Transformer Step

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: The value to replace any matched regions with.

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

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

Custom Metadata Columns

Custom metadata columns are user-created, searchable columns that appear in the Metadata Table in the Message Browser. As messages process through a channel, these columns are populated from the Variable Maps using a configurable map key. Column Description Column Name The name of the actual database column. This name will also be shown in the metadata table when viewing the message browser for the channel. Type The type of column to create. STRING: A textual string value. NUMBER: A numeric value. This may be an integer or floating point value. BOOLEAN: A true/false value. TIMESTAMP: A date/time value. Variable Mapping The key used to look up values in all available variable maps for each connector. As explained in the Variable Maps section, the following maps (if available) will be checked in this order: Response Connector Channel Source Global Channel Global Configuration Modifying Custom Metadata Columns Parent topic: Summary Tab

Mirth® Connect by NextGen Healthcare User Guide

Message Builder Transformer Step

This step extracts data from a field in the message (or an expression) and maps it into a specific field in the inbound or outbound message. This can be used to simply modify a field in the inbound message, copy a field from one place to another, or map data from the inbound message to the outbound message. Item Name Description Message Segment The field/location in the inbound or outbound message to place the value into. Mapping The value to place into the given message segment. 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 is used instead. String Replacement This table allows you to perform replacements on the value before it gets inserted. Regular Expression: A Java-style regular expression to test against the value. This will implicitly set the global regex flag. Replace With: The value to replace any matched regions with. Parent topic: Transformer Step Propertie

Mirth® Connect by NextGen Healthcare User Guide

Destination Set Filter Transformer Step

Destination Set Filtering is a powerful feature of the source transformer that allows you to decide in advance which destinations to exclude from message processing. Using each individual destination's filter to control where a message goes is still a valid workflow, but when you have many destinations all with mutually exclusive filters, the performance of the channel can be affected because message data will be stored to the database for each destination connector. Also filtered connector messages can clutter up the message browser, making it harder to find what you are looking for. The advantage to using Destination Set Filtering in this case is that filtered destinations will not have any message data stored, and will not show up in the message browser. This can greatly increase message throughput. Destination Set Filtering can be done manually with JavaScript (look at DestinationSet in the User API) . However this step allows easier access to the feature without having to write an

Mirth® Connect by NextGen Healthcare User Guide

Iterator Transformer Step

This is a special type of step that allows you to perform extract / transform operations while iterating through an array or list of XML nodes. For additional information, see Working With Iterators . Item Name Description Iterate On The element to iterate on. This may be a list of E4X XML nodes, or a Java / JavaScript array. Index Variable The index variable to use for each iteration. Drag-and-Drop Substitutions When drag-and-dropping values into the children underneath this Iterator, the index variable (e.g. "[i]") will be injected after any of these prefixes. For example if your index variable is i and you have msg['PID'] in the Drag-and-Drop Substitutions table, when you drag the value msg['PID']['PID.3']['PID.3.1'].toString() from the Message Trees Tab into a child step, it will automatically be replaced with msg['PID'][i]['PID.3']['PID.3.1'].toString(). Parent topic: Transformer Step Properties

Mapper Transformer Step

Recommendations

The Variable Map Lookup Sequence

Batch Processing

Custom Metadata Columns

Message Builder Transformer Step

Destination Set Filter Transformer Step

Iterator Transformer Step

Mapper Transformer Step

The Variable Map Lookup Sequence

Batch Processing

Custom Metadata Columns

Message Builder Transformer Step

Destination Set Filter Transformer Step

Iterator Transformer Step