Loading...
Recommendations
Explore
Mappings Table Columns
Column
Description
Scope
The type of map the entry is stored in. For additional information, see
Variable Maps
.
Variable
The unique key identifying the entry within the given map.
Value
The actual value of the entry.
Mappings Table Columns
Mirth® Connect by NextGen Healthcare User Guide
Mappings Tab
The Mappings tab shows all entries stored in variable maps for the selected connector message. View Mappings Mappings Table Columns Parent topic: Message Browser View
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
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:
Mirth® Connect by NextGen Healthcare User Guide
View Mappings
Select a connector message in the Metadata Table. Select the Mappings tab (located below the Metadata Table). Double-click entries in the table to view the values in a separate dialog. Parent topic: Mappings Tab
Mirth® Connect by NextGen Healthcare User Guide
Global Maps
The Global Maps tab allows you to view the current state of the Global Map and the Global Channel Maps specific to particular channels. For additional information on these maps, see Variable Maps. The Global Maps table shows all current global map entries, and all current global channel map entries for the channels that are currently selected in the dashboard table. You can multi-select channels to view global channel map entries across multiple channels at once. Global Maps Table Columns Parent topic: Dashboard View
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
