Resources Table Columns

Column	Description
Name	The name of the resource. Double-click this column to edit the name. Note that the [Default Resource] cannot be renamed or removed.
Type	The type of resource / service. The [Default Resource] type cannot be changed.
Global Scripts	If selected, any libraries included with the resource will automatically be made available for use in the Global Scripts.
Load Parent-First	If selected, classes already included in the overall server classpath will not be able to be overwritten. Classes will attempt to be loaded from the parent ClassLoader first. Also, if this resource is included on a channel with other resources that have this option disabled, you will still not be able to overwrite classes in the parent classpath.

Mirth® Connect by NextGen Healthcare User Guide

Channel Tasks

The following context-specific tasks for channels are available from the Channels View: Task Icon Task Name Description Refresh Updates the channel table. Redeploy All Undeploys all channels, then deploys all currently enabled channels. Debug Channel Displays the Debug Channel dialog that allows you to deploy the currently selected channel while debugging specific scripts within the channel. Deploy Channel Deploys the currently selected channel(s). If a group is selected, deploys all channels underneath that group. Note that the Channel Dependencies workflow may apply to this task. Edit Global Scripts Enters the Edit Global Scripts View. Edit Code Templates Enters the Edit Channel View. New Channel Creates a newchannel and enters the Edit Channel View. The channel is not yet saved. Import Channel Imports a channel from an XML file and enters the Edit Channel View. The channel is not yet saved. For additional information, see Import Channel. Export All Channels Exports all of the channe

Mirth® Connect by NextGen Healthcare User Guide

Code Template Contexts

Similar to how a code template library can be included only on specific channels, code templates can further be isolated to specific scripts. This can be helpful for ensuring that there are no conflicts between function names, and also for better memory usage, since not all code templates need to be compiled in with all scripts across your entire server. The script contexts are organized into groups, allowing you to easily include a code template in, for example, all global scripts, in a single select. The following groups are displayed: Global Scripts: The global deploy/undeploy/preprocessor/postprocessor scripts, not specific to any particular channel. For additional information, see Edit Global Scripts View. Channel Scripts: The channel-level deploy/undeploy/preprocessor/postprocessor scripts (more info here) , as well as the JavaScript Attachment Handler and JavaScript Batch Adapter (for additional information, see Data Types) . Source Connector: The source filter/transformer scrip

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

Global Map

This map is available across your entire server, across all channels and all messages. That means you can store a value during message processing in one channel, and use that value from a different channel, or somewhere else like an Alert. You can also store global map values in the global scripts. Like the global channel map, this map is useful for storing stateful, non-serializable objects like a database Connection. It is in-memory only, meaning that if Mirth® Connect is restarted, the entries in this map are not preserved anywhere. It is also a concurrent map, which means that "null" values cannot be stored in it. Get global map value: var value = globalMap.get('key'); var value = $g('key'); Put global map value: globalMap.put('key', 'value'); $g('key', 'value'); Note: By default the "Clear global map on redeploy" option is enabled on the Server Settings Tab. You may want to disable this if you want the global map to remain unchanged when you redeploy all channels. Parent topic: Va

Mirth® Connect by NextGen Healthcare User Guide

Edit Views

This section is separated into the following topics: Edit Channel View Edit Filter / Transformer Views Edit Global Scripts View Edit Code Templates View Edit Alert View Edit Channel View Edit Filter / Transformer Views You can use the Edit Filter view or the Transformer view to configure filter rules and transformer steps. Edit Global Scripts View The Edit Global Scripts view provides global scripts across all channels. Edit Code Templates View This view is where code templates and libraries are configured for your Mirth® Connect server. Edit Alert View Use the Edit Alert view to configure and modfiy alerts. Parent topic: Mirth Connect Administrator

Mirth® Connect by NextGen Healthcare User Guide

Scripts Tab

The Scripts tab is where channel-level scripts are configured. Select a script type from the drop-down list and edit the script in the text area.Select a script type from the drop-down and edit the script in the text area below. If a number appears next to "Scripts" in the tab, that number represents how many scripts have been edited from the default values. There is also a Reference List to the right for easy drag-and-drop of common helper methods / code templates. The following channel-level script types can be edited: Deploy Script: This script executes once when the channel is deployed. You have access to the global / global channel / configuration maps here. Typically this script is used to perform a one-time operation for the given channel, such as loading a properties file from disk, or instantiating a database connection. Undeploy Script: This script executes once when the channel is undeployed. You have access to the global / global channel / configuration maps here. Typically

Resources Table Columns

Recommendations

Channel Tasks

Code Template Contexts

The Variable Map Lookup Sequence

Global Map

Edit Views

Scripts Tab

Resources Table Columns

Channel Tasks

Code Template Contexts

The Variable Map Lookup Sequence

Global Map

Edit Views

Scripts Tab