Channel Tasks

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 channels to their own respective XML files. For additional information, see Export Channel.
	Export Channel	Exports the selected channel(s) to their own respective XML files. For additional information, see Export Channel.
	Delete Channel	Removes the selected channel(s) from the server. All message / attachment data is also deleted.
	Clone Channel	Copies the channel and enters the Edit Channel View. The channel is not yet saved. Note that you will be prompted to give the channel a new unique name first.
	Edit Channel	Enters the Edit Channel View for the selected channel. This can also be accessed by double-clicking the channel row.
	Enable Channel	Mark this channel as ready to be deployed. Enabled channels are automatically deployed when the server starts up or when the Redeploy All task is performed.
	Disable Channel	Marks this channel as not ready to be deployed. The channel may not be deployed until it is re-enabled. However, if the channel was already deployed, then disabling it will not automatically undeploy it.
	View Messages	Enters the Message Browser View for the selected channel.
	View History	Opens the Channel Historydialog, which allows you to view the history of the selected channel. This task is only available when the Channel History extension has been installed.

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

Channel Properties

Item Name Description A Name The name of the channel. Only alphanumeric (a-z / 0-9) characters, spaces, hyphens, and underscores are allowed. B Enabled Indicates whether the channel is ready to be deployed. All enabled channels will automatically be deployed with the Mirth® Connect by NextGen Healthcare server starts up. If there is an error in your channel configuration, this will automatically be unchecked. C Set Data Types Dialog Configure data types across your entire channel, from the source connector to each of your destination connectors. Allows easy bulk editing of data type properties. For additional information, see Set Data Types. D Clear global channel map on deploy If checked, the global channel map for this channel will be cleared out whenever the channel is redeployed. E Set Dependencies Configures Code Template Libraries, Library Resources, and Deploy/Start Dependencies for this channel. For more information, see Set Dependencies Window. F Initial State Determines what

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

Edit Channel Tasks

The following context-specific tasks are available throughout the Edit Channel View: Task Icon Task Name Description Save Changes Saves a new revision of the current channel, if anything was actually changed. Validate Connector Validates the currently viewed connector, ensuring that all connector properties are valid and able to be saved. Edit Filter Enters the Edit Filter View for the currently viewed connector. Edit Transformer Enters the Edit Transformer View for the currently viewed connector. Import Connector Imports a connector from an XML file into the current channel. For source connectors, this completely overrides all source connector properties and the source filter/transformer. For destination connectors a new destination is added to the table. Export Connector Exports the currently viewed connector to an XML file. This includes all connector properties and the connector's filter / transformer. Export Channel Exports the current channel to an XML file. The channel must be s

Mirth® Connect by NextGen Healthcare User Guide

Group Tasks

The following context-specific tasks for channel groups are available from the Channels View. Task Icon Task Name Description Save Group Changes Saves all changes made to channel groups and refreshes the Channels view. Assign To Group Moves the selected channel(s) into a specific group. New Group Creates a new channel group and adds it to the table. The user is prompted for the group name and description as described in the Edit Group Details task. This task appears after the channels view fully loads. Edit Group Details Allows the user to edit the group name and description. This can also be accessed by double-clicking the group row. For additional information, see Edit Group Details. Import Group Imports a channel group from an XML file. For additional information, see Import Group. Export All Groups Exports all channel groups in the table to their respective XML files. For additional information, see Export Group. Export Group Exports the selected channel group(s) to their respectiv

Mirth® Connect by NextGen Healthcare User Guide

Message Metadata

Metadata typically refers to important information about the message, but not the actual message content. Message Metadata includes: Message ID: Every message for any given channel has a unique integer ID, the Message ID. The Message ID is used to organize data in the message browser and join connector messages together. Connector Metadata ID: Each connector has its own ID, referred to as the connector metadata ID. The source connector always has a metadata ID of zero (0). Destination connector metadata IDs start at one (1) and increment for each new destination you add to the channel. Status: Each connector message has a status, which tells the channel the current processing state. For example, the status could be RECEIVED, which means the raw data has been committed to the database, but the message is in the middle of being processed. It could be QUEUED, which may mean it is sitting in a queue waiting to be processed, or one or more attempts have been made to process the message, but

Channel Tasks

Recommendations

General Channel Properties

Channel Properties

Code Template Contexts

Edit Channel Tasks

Group Tasks

Message Metadata

Channel Tasks

General Channel Properties

Channel Properties

Code Template Contexts

Edit Channel Tasks

Group Tasks

Message Metadata