Outbound Properties

Mirth® Connect by NextGen Healthcare User Guide

About Data Types

A data type tells a filter / transformer how to parse a certain format. The inbound data type serializes the incoming raw data into its internal representation. Then the filter / transformer executes, possibly modifying this internal representation, or even completely overwriting it with a different internal representation. Finally, the outbound data type takes this transformed data and deserializes it into the proper outbound format (the encoded data) . For example, the HL7 v2.x data type serializes ER7 data from this: into this: In this case, the internal representation is XML, because, for HL7 v2.x, the message object you use or manipulate in a filter / transformer is an E4X XML object. However not all data types use XML for their internal representation. The JSON data type uses JSON as you might expect, and the object you use in a filter / transformer is a regular JavaScript Object. The Raw data type does no serialization or deserialization, so its internal representation is identi

Mirth® Connect by NextGen Healthcare User Guide

Frequently Asked Questions

This section addresses the most common questions users have about Mirth® Connect by NextGen Healthcare. What is Mirth® Connect? Mirth® Connect is a versatile, standards-based healthcare integration engine that speeds bi-directional message routing, filtering, and transformation between disparate health-info systems over various messaging protocols (e.g., HL7, X12, EDI, DICOM, XML). Is Mirth® Connect the same as "Mirth"? Yes. Mirth 1.0 was released in 2006 by WebReach, Inc. Based on the success of the Mirth application, WebReach, Inc. was renamed "Mirth Corporation" in 2009. To avoid confusion between the new company name and its products, the Mirth application was renamed Mirth® Connect. As of early 2016, Mirth Corporation, as a business entity, no longer exists, having been absorbed into the Quality Systems, Inc. family of products in Sept. 2013. QSI has since become NextGen Healthcare, and Mirth® Connect lives on with other former Mirth Corporation products as part of the "Mirth Solu

Mirth® Connect by NextGen Healthcare User Guide

HL7 v3.x Data Type

This data type handles HL7 v3.x messages. No actual serialization or deserialization is needed because the data format is the same as the internal representation format (XML), but it still has options to strip namespaces if needed. Serialization / Template Serialization Properties Name Default Value Description Strip Namespaces Enabled Strips namespace definitions from the transformed XML message. Will not remove namespace prefixes. If you do not strip namespaces your default xml namespace will be set to the incoming data namespace. If your outbound template namespace is different, you will have to set "default xml namespace = 'namespace';" via JavaScript before template mappings. Batch Properties Name Default Value Description Split Batch By JavaScript Select the method for splitting the batch message. This option has no effect unless Process Batch is enabled in the Source Settings. The following options are available: JavaScript: Use JavaScript to split messages. For additional infor

Mirth® Connect by NextGen Healthcare User Guide

EDI / X12 Data Type

This data type handles both UN/EDIFACT and ASC X12 data formats, as well as custom formats similar to EDI / X12 that use a segment / element / subelement delimiter. Serialization / Template Serialization / Deserialization Properties Name Default Value Description Segment Delimiter ~ Characters that delimit the segments in the message. Element Delimiter * Characters that delimit the elements in the message. Subelement Delimiter : Characters that delimit the subelements in the message. Infer X12 Delimiters Enabled This property only applies to X12 messages. If checked, the delimiters are inferred from the incoming message and the delimiter properties will not be used. Batch Properties Name Default Value Description Split Batch By JavaScript Select the method for splitting the batch message. This option has no effect unless Process Batch is enabled in the Source Settings. The following options are available: JavaScript: Use JavaScript to split messages. For additional information, see Jav

Mirth® Connect by NextGen Healthcare User Guide

Inbound Properties

Serialization Properties: Determines how to convert data from the raw inbound format to the internal representation (e.g. XML). If a data type doesn't have serialization properties present, it either doesn't need any (DICOM, JSON), or it doesn't actually do any serialization (Raw). Batch Properties: Determines how to split an incoming message into multiple messages. Only supported when Process Batch is enabled in the Source Settings. This will only be displayed for source connectors. Not all data types support batch processing (DICOM). Response Generation Properties: When an auto-generation option is chosen for the response on the Source Settings, these properties determine how to generate an automatic response. This will only be displayed for source connectors. Not all data types support automatic response generation. Response Validation Properties: Determines how to validate responses received by a destination after dispatching a message. Only supported when Validate Response is enab

Mirth® Connect by NextGen Healthcare User Guide

Raw Data Type

This data type allows a channel / connector to process any custom data not handled by any of the other data types. When using it, the msg / tmp variable accessible in the filter/transformer will be a String rather than an E4X XML object which some other data types use. This data type also has the special property that when used as the Response Inbound data type for a destination, the response transformer will always be executed, even if no actual response data was received. No serialization properties are needed since there is no conversion done. Batch Properties Name Default Value Description Split Batch By JavaScript Select the method for splitting the batch message. This option has no effect unless Process Batch is enabled in the Source Settings. The following options are available: JavaScript: Use JavaScript to split messages. For additional information, see JavaScript Batch Script JavaScript Enter JavaScript that splits the batch, and returns the next message. This script has acce

Outbound Properties

Recommendations

About Data Types

Frequently Asked Questions

HL7 v3.x Data Type

EDI / X12 Data Type

Inbound Properties

Raw Data Type

Outbound Properties

About Data Types

Frequently Asked Questions

HL7 v3.x Data Type

EDI / X12 Data Type

Inbound Properties

Raw Data Type