Channel Settings

Item	Name	Description
G	Clear global map on redeploy	Select Yes to clear the global map when redeploying all channels. Yes is the default for this field. Select No to keep global map information when redeploying all channels.
H	Default Queue Buffer Size	The default source/destination queue buffer size to use for new channels. The default is 1000 (messages).
I	Default Metadata Columns	Determines which custom metadata columns is added by default when a user creates a new channel. Options include: Source Type Version The user can also remove these column on the channel's Summary tab. For additional information, see Custom Metadata Columns.

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

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

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

Mirth® Connect by NextGen Healthcare User Guide

From the Channels View

Select the Channels link in the Mirth Connect task panel on the upper-left side of the window. Select a channel where the messages you would like to view reside. Select the View Messages task in the left task list. For additional information, see Channel Tasks. This section is separated into the following topics: Metadata Table Message Content Tab Mappings Tab Errors Tab Attachments Tab Search Messages Message Browser Tasks Parent topic: Navigation

Mirth® Connect by NextGen Healthcare User Guide

About Message Data

In Mirth® Connect, a message refers to a single overall dispatch of data through the source connector and destination connectors within a channel. Messages are further separated into connector messages which are part of the message that flow through a single connector. For example if your channel has two destinations, then a single message will have three connector messages associated with it as it is processed through the channel: One source connector, and two destination connectors. These connector messages correspond to the rows of data you see in the Metadata Table within the Message Browser. Note that messages do not always correspond 1-to-1 with a file that you read in, or a particular stream of data. As explained in the About Channels and Connectors section, the source connector may contain a batch processor which takes a raw inbound stream of data and splits it into multiple messages. So if you have a single file containing 100 HL7 v2.x messages, your channel could read that in

Mirth® Connect by NextGen Healthcare User Guide

View Message Content

Select a connector message in the Metadata Table. Select the Messages tab (located below the Metadata Table). Select the radio button corresponding with the content type you want to view. Parent topic: Message Content Tab

Channel Settings

Recommendations

Custom Metadata Columns

View Mappings

Message Metadata

From the Channels View

About Message Data

View Message Content

Channel Settings

Custom Metadata Columns

View Mappings

Message Metadata

From the Channels View

About Message Data

View Message Content