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
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
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
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
XML Data Type This data type handles XML 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 Disabled Identifies the 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 Element Name 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: Element Name: Use the element name to split messages. Mirth® Connect by NextGen Healthcare User Guide
DICOM Data Type This data type works in conjunction with the DICOM Listener / DICOM Sender and the DICOM Attachment Handler to consume and transformer DICOM messages. It has no configurable data type properties, but will automatically convert binary DICOM data to and from an XML format specified by the dcm4che parser library. Example XML snippet: <dicom> <tag00020000 len="4" tag="00020000" vr="UL">212</tag00020000> <tag00020001 len="2" tag="00020001" vr="OB">00\01</tag00020001> <tag00020002 len="26" tag="00020002" vr="UI">1.2.840.10008.5.1.4.1.1.4</tag00020002> <tag00020003 len="60" tag="00020003" vr="UI">1.3.46.670589.11.30.9.1062531302827752870602.13.1.1.1.0.0.1</tag00020003> <tag00020010 len="18" tag="00020010" vr="UI">1.2.840.10008.1.2</tag00020010> <tag00020012 len="18" tag="00020012" vr="UI">1.3.46.670589.17.1</tag00020012> <tag00020013 len="14" tag="00020013" vr="SH">ARCVTS04NOV99</tag00020013> <tag00020016 len="14" tag="00020016" vr="AE">VTS_DCM_STORE</tag00020016> <tag00080005 len="10" tag="0 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 