About Message Data

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

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

About Channels and Connectors

A Mirth® Connect channel consists of multiple connectors. A connector is a piece of a channel that pulls data into Mirth® Connect (a source connector) , or sends data to an external system (a destination connector). Every channel has exactly one source connector, and at least one destination connector. Because a channel may have multiple destination connectors, think of it as a process that obtains data from a particular source, and sends it out to many different destinations. For example, you may receive data over HTTP, then write the data out to a file, and also insert pieces of the data into your custom database. Channel Components Connector Components Parent topic: The Fundamentals of Mirth Connect

Mirth® Connect by NextGen Healthcare User Guide

The Message Processing Lifecycle

As explained in the About Message Data section, each source and destination connector has various versions of the message data as it flows through the channel. The raw inbound message enters Mirth® Connect, is received by the source connector, is filtered and transformed, then encoded and sent to the destination connector. From the source connector, the raw inbound message can be passed through multiple destination connectors where it can again be influenced by filters and transformers before it is processed, encoded, and sent on. Source Processing Steps Destination Processing Steps Final Processing Steps Destination Chains Parent topic: The Fundamentals of Mirth Connect

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

About Message Data

Recommendations

Message Metadata

From the Channels View

General Channel Properties

About Channels and Connectors

The Message Processing Lifecycle

Custom Metadata Columns

Message Metadata

From the Channels View

General Channel Properties

About Channels and Connectors

The Message Processing Lifecycle

Custom Metadata Columns