XML Data Type

Table 1. Serialization / Template Serialization Properties
Name	Default Value	Description
Strip Namespaces	Disabled	Identifies the strip's 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 must set `Default XML namespace = 'namespace';` via JavaScript before template mappings.

Table 2. Batch Properties
Name	Default Value	Description
Split Batch By	Element Name	Determines the method for splitting the batch message. This property has no effect unless Process Batch is enabled in the Source Settings. The following options are available: Element Name: Use the element name to split messages. Does not work with namespaces. Level: Use the element level to split messages. Default is 1. XPath Query: Use a custom XPath Query to split messages. JavaScript: Use JavaScript to split messages.
JavaScript	––-	Contains the JavaScript that splits the batch and returns the next message. This script has access to 'reader', a Java BufferedReader, to read the incoming data stream. The script must return either a string containing the next message or a null/empty string to indicate end of input.

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

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

Mirth® Connect by NextGen Healthcare User Guide

JSON Data Type

This data type allows seamless integration between JSON messages and the filter/transformer scripts which are JavaScript-based. When using the JSON data type, the msg / tmp variables will be a standard JavaScript object, as opposed to an E4X XML object which some other data types use. Since JSON is a very lightweight data format, and the transition from String to JavaScript Object is all handled automatically, no serialization properties are needed. 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 access to 'reader', a Java BufferedReader, to read the incoming data stream. The script must return a

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

JavaScript Batch Script

The JavaScript batch adapter is an option common to almost all data types. When Process Batch is enabled on the Source Settings, you can set this script from the Set Data Types Window to programmatically decide how to split the incoming data into multiple messages. Within the batch script you have access to a variable called "reader", which is a Java BufferedReader object. Use this variable to consume from the underlying character stream and return a String for each message you want to process through the channel. When you decide that no more messages should be processed, or you reach the end of the stream, return null or an empty string. Example 1 This script will simply send a message for every line in the input.return reader.readLine(); Example 2 This script will split the input into multiple messages by assuming that each new message starts with a line break and the characters "MSH". Note that this is already a feature supported by the , but is shown here to illustrate how the batc

Mirth® Connect by NextGen Healthcare User Guide

Batch Processing

Batch Processing allows a channel to receive a single message, but split it into multiple messages that each get processed through the channel. When using this along with a source connector that supports streaming (File Reader, TCP Listener in MLLP mode), batch processing has the added benefit of not having to read the entire file into memory all at once, but instead only one message at a time. For example with the File Reader and batch processing you can read in files that are gigabytes in size, without causing any memory issues for your Mirth Connect server. Data types that support batch processing will have a Batch Properties section in the source inbound data type properties. To enable batch processing, set Process Batch to Yes in the Source Settings. To change how an incoming message is split into multiple messages, look at the Batch Properties section of the source inbound data type you are using. For example, the Delimited Text Data Type has options to split by record delimiter,

XML Data Type

Recommendations

HL7 v3.x Data Type

Raw Data Type

JSON Data Type

EDI / X12 Data Type

JavaScript Batch Script

Batch Processing

HL7 v3.x Data Type

Raw Data Type

JSON Data Type

EDI / X12 Data Type

JavaScript Batch Script

Batch Processing