Source Processing Steps

Mirth® Connect by NextGen Healthcare User Guide

Destination Processing Steps

Note: These steps are repeated for each destination connector that a message flows through. The encoded content from the source connector is used by each destination connector as its raw data. The content is serialized (converted) to the internal representation of the inbound data type (e.g. XML). The content runs through the filter, and the message is either accepted or filtered. If the message gets filtered, flow stops for the current destination here. If there are additional destinations in the current chain, these steps are repeated for the next destination. Otherwise, assuming all other destination chains have finished, flow jumps down to the Final Processing Steps. The content runs through the transformer, where it may be modified. The post-transformer content is stored as the transformed data. The content is deserialized (converted) from the outbound data type's internal representation (e.g. XML) into the actual outbound format (HL7, EDI, etc.). The content is stored as encoded

Mirth® Connect by NextGen Healthcare User Guide

Final Processing Steps

Final Processing Steps Final Processing Steps Note: This point is reached when all destination chains have finished processing the message. If the message was filtered or errored out on the source connector, then flow will immediately jump down to this step. The post processor script is executed. It can return a response that the source connector may use. The source connector decides what response to send back to the originating system, if any. This may be an auto-generated value, the response payload from a destination connector dispatch, a response returned from the post processor script, or a completely custom value residing in the response map. The selected response is stored as the source connector's response data and is sent back to the originating system, if needed. Parent topic: The Message Processing Lifecycle

Mirth® Connect by NextGen Healthcare User Guide

Destination Chains

Destination Chains Destination Chains A channel's destinations are grouped into one or more destination chains. Each destination chain processes simultaneously with respect to each other, however in any particular chain, a message will flow through each destination in order. It looks something like this: In the above example, there are 5 total destinations. However Destination 3 does not wait on Destination 2, so it marks the beginning of a new chain. If each destination takes 1 second to process, then the overall time it takes the message to process through the channel will not be 5 seconds, but rather 3 seconds. When flowing through the destination connectors, a message will take only as long as the longest destination chain. Parent topic: The Message Processing Lifecycle

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

Message Content Types

Content Type Description Raw The inbound message as received and stored by the channel, after the attachment handler has extracted any attachments but before the preprocessor script has modified the message. Processed Raw The altered inbound message after the preprocessor script has executed. Transformed When a message enters a transformer, the raw (or processed raw) data is serialized into an internal representation, which may be XML, JSON, or Raw depending on the inbound data type. The transformer then has a chance to alter this serialized data. This content is the internal representation of the message after the transformer has executed. Encoded After a message leaves the transformer, the Transformed Data (internal representation of the message) is deserialized into the outbound data type. This is referred to as the Encoded Data. The encoded data for a source connector is equivalent to the raw data for a destination connector. Sent A snapshot of the destination connector properties

Mirth® Connect by NextGen Healthcare User Guide

Message Content

Message content is the actual data that gets processed. As a message flows through your channel, different versions of the data are stored for each connector, depending on the modifications your channel needs to make. Source Connector Raw - The state of the message as it enters the connector. Processed Raw - The state of the message after passing through the preprocessor script. Transformed - The serialized internal representation of the message, which exists only if a connector has a filter or transformer configured. Encoded - The state of the message as it exits the transformer (includes changes made to the transformed data). Response - The message sent back to the originating system (at the very end, after all destinations finish). Destination Connector Raw - The state of the message as it enters the connector. For a destination connector, this is the same as the source encoded data. Transformed - The serialized internal representation of the message, which exists only if a connecto

Source Processing Steps

Recommendations

Destination Processing Steps

Final Processing Steps

Destination Chains

The Message Processing Lifecycle

Message Content Types

Message Content

Destination Processing Steps

Final Processing Steps

Destination Chains

The Message Processing Lifecycle

Message Content Types

Message Content