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 enabled in the Destination Settings . This will only be displayed for destination responses. Not all data types support automatic response generation.
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
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, 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
HTTP Sender This destination connector sends an HTTP request to an external web server. The method, parameters, and headers can all be fully customized. Both Basic and Digest authentication (preemptive or reactive) are supported. Sending requests through a proxy server is also supported, even when using HTTPS. The HTTP payload can be written out as raw bytes, or converted using a specified charset. Responses can be automatically converted to XML, allowing multipart payloads to be parsed in a consistent and easy-to-use way. Additional options are available with the SSL Manager extension. Supported property groups: Destination Settings Item Name Default Value Description A URL The URL of the HTTP server to send each message to. B Use Proxy Server No If enabled, requests are forwarded to the proxy server specified in the address/port fields below. C Proxy Address The domain name or IP address of the proxy server to connect to. D Proxy Port The port on which to connect to the proxy server. E Method PO Mirth® Connect by NextGen Healthcare User Guide
Outbound Properties Deserialization Properties: After a transformer finishes, these properties determine how to convert data from the final internal representation (e.g. XML) into the outbound data format. If a data type doesn't have deserialization properties present, it either doesn't need any (DICOM, EDI/X12, XML, JSON) or it doesn't actually do any deserialization (Raw). Template Serialization: If an outbound template is specified for the transformer, these properties determine how to convert that template to its corresponding internal representation (e.g. XML). Mirth® Connect supports the following data types: Delimited Text Data Type DICOM Data Type EDI / X12 Data Type HL7 v2.x Data Type HL7 v3.x Data Type JSON Data Type NCPDP Data Type Raw Data Type XML Data Type An additional data type is made available as an extension: ASTM E1394 Data Type Also see: Batch Processing Parent topic: Data Types 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 