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 immediately before the destination connector attempts to dispatch the message.
Response	The Response object returned by the destination connector after a dispatch has been attempted. This will include the response status, the status message, and the actual response payload (if present).
Response Transformed	This is the same as the Transformed content, except that it is for the response data. This will be the internal representation of the response content, serialized into the response inbound data type.
Processed Response	This is the same as the Encoded content, except that it is for the response data. This will be the internal serialized representation of the response content, deserialized into the response outbound data type.

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

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

Source Processing Steps

A message or stream of data is received by the source connector. The batch processor decides whether to split the message into multiple messages. If so, the below steps are repeated for each message returned by the batch processor. The attachment handler extracts and/or stores all attachment data. The post-attachment-handler content is stored as raw data. The content runs through the preprocessor script and is stored as processed 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 here and 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

Mirth® Connect by NextGen Healthcare User Guide

Response Transformers

The response transformer is a special type of transformer only editable for destination connectors on the Destinations Tab. It works the same as a regular transformer, except that the data being transformed is not the message flowing through the channel, but instead the response payload that the destination connector received from the external system (if applicable). For additional information about transformers, see About Transformers. A destination response is comprised not only of the response data, but also the status (e.g. SENT, ERROR), status message, and error message. Response transformers can be used to modify these latter pieces as well. For example if a message gets set to ERROR by the destination connector, in the response transformer you can choose to override that and set the status to SENT instead based on some custom logic. Note: Response transformers will only execute if there is an actual response payload to transform. For example if you are using an HTTP Sender desti

Mirth® Connect by NextGen Healthcare User Guide

Response Transformers

The Response Transformer is a special type of transformer specific to destination connectors. It works the same as a regular transformer, except that the data being transformed is not the message flowing through the channel, but instead the response payload that the destination connector received from the external system (if applicable). For additional information, see Response Transformers A destination response is comprised not only of the response data, but also the status (e.g. SENT, ERROR), status message, and error message. Response transformers can be used to modify these latter pieces as well. For example if a message gets set to ERROR by the destination connector, in the response transformer you can choose to override that and set the status to SENT instead based on some custom logic. Note: Response transformers will only execute if there is an actual response payload to transform. For example if you are using an HTTP Sender destination and it fails to connect to the remote se

Mirth® Connect by NextGen Healthcare FHIR Connector User Guide

FHIR Data Types

As you may already know, FHIR resources are typically found in either XML or JSON formats. If you are building a FHIR client or server and only need to support one of those formats, then using either the XML or JSON data types will work fine. However, this new FHIR data type is unique in that it allows your channel to accept both XML and JSON, without having to modify your code to handle one or the other. You simply configure what format you're expecting inbound, and what format you want to go outbound, for each connector / transformer. Image of the Set Data Types window On the Inbound side, the Serialization Type is the format you want all inbound data to be converted to. XML: The inbound data will be converted to XML if needed, and your msg variable will be an E4X XML object. JSON: The inbound data will be converted to JSON if needed, and your msg variable will be a JavaScript Object. Raw: The inbound data will not be converted at all, and your msg variable will be a JavaScript Strin

Message Content Types

Recommendations

Message Content

Destination Processing Steps

Source Processing Steps

Response Transformers

Response Transformers

FHIR Data Types

Message Content

Destination Processing Steps

Source Processing Steps

Response Transformers

Response Transformers

FHIR Data Types