Select Data Types

Mirth® Connect by NextGen Healthcare User Guide

Custom Metadata Columns

Custom Metadata Columns for the current channel also show up in the metadata table. These columns vary depending on the channel. By default the Source and Type columns are added for all new channels, though this can be changed in the Server Settings. Column Description Source Depends on the inbound data type for the connector. For HL7 v2.x messages this will usually be the Sending Facility value in MSH.4.1. Type Depends on the inbound data type for the connector. For HL7 v2.x messages this will usually be the Type and Trigger values in MSH.9.1 and MSH.9.2. Version Depends on the inbound data type for the connector. For HL7 v2.x messages this will usually be the Version value in MSH.12.1. Note that this custom metadata column is not added to new channels by default, though this may be changed in the Server Settings Tab. Note that the above values are only the defaults, and that users can change those values inside of a transformer. Parent topic: Metadata Table

Mirth® Connect by NextGen Healthcare User Guide

Change Data Type Properties

After selecting a connector / response row in the table above, the Inbound Properties and Outbound Properties sections below will show all currently configured properties for the respective data types. Select on the rows in the properties table to view descriptions of categories or specific properties: Depending on the connector row chosen above, the data type itself, and whether the data type is being used as inbound or outbound, the categories of properties shown in the table vary. For additional information on data type properties and options for specific data types, see Data Types. Any properties you have changed or that are not equal to the default value are shown in bold. To revert all changes back to the defaults for the selected data type, select the Restore Defaults button above the Properties tables: Parent topic: Set Data Types Window

Mirth® Connect by NextGen Healthcare User Guide

Bulk Edit Mode

The above instructions so far have assumed that Single Edit is selected at the top-left of the dialog. This means that only a single connector / response row can be modified at a time. However you can also make common changes to multiple connectors all at once. Select the Bulk Edit button on the top-left side of the dialog: After entering Bulk Edit mode, the drop-down menu arrows in the Inbound / Outbound columns disappear, and a new check box column appears at the left of the table. Select the connector / response rows you want to edit by checking the check box in the table next to the name. Once you have selected at least one, the Inbound / Outbound Properties sections below will become activated. For either the Inbound or Outbound Properties section, if the data type is the same across all of the currently selected rows, then you have the option to edit properties. Any changes you make while in this mode will be applied across all of the currently selected connector / response rows.

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

Standard Variables/Templates

Name Description Channel ID The unique ID of the current channel. Channel Name The name of the current channel. Message ID The unique ID of the current message. Raw Data The raw content of the destination connector message (equal to the encoded content of the source connector message). Transformed Data The serialized internal representation of the post-transformer message data. Encoded Data The state of the message data as it exists in the transformer. Message Source Depends on the inbound data type for the connector. For HL7 v2.x messages this will usually be the Sending Facility value in MSH.4.1. Message Type Depends on the inbound data type for the connector. For HL7 v2.x messages this will usually be the Type and Trigger values in MSH.9.1 and MSH.9.2. Message Version Depends on the inbound data type for the connector. For HL7 v2.x messages this will usually be the Version value in MSH.12.1. Message Hash The SHA-256 hash of the encoded data of the destination connector message. If n

Mirth® Connect by NextGen Healthcare User Guide

MLLP Transmission Mode

This transmission mode implements the Minimal Lower Layer Protocol (MLLP) specified by HL7, and is often used when transmitting HL7 v2.x messages. There are two versions of MLLP, v1 and v2. The first version is similar to the Basic TCP Transmission Mode in that it only specifies sequences for the start/end message bytes. The second version builds on the first with "reliable delivery assurance", by having each system send a protocol-level ACK or NAK immediately after every received frame. By default only MLLPv1 is enabled, as it is the most common use-case. Item Name Default Value Description A Start of Message Bytes 0x0B <VT>) The MLLP Start Block bytes before the beginning of the actual message. Only valid hexadecimal characters (0-9, A-F) are allowed. B End of Message Bytes 0x1C0D (<FS><CR>) The MLLP End Data/Block bytes after the end of the actual message. Only valid hexadecimal characters (0-9, A-F) are allowed. C Use MLLPv2 No Select Yes to use the MLLPv2 bi-directional transport

Select Data Types

Recommendations

Custom Metadata Columns

Change Data Type Properties

Bulk Edit Mode

Outbound Properties

Standard Variables/Templates

MLLP Transmission Mode

Custom Metadata Columns

Change Data Type Properties

Bulk Edit Mode

Outbound Properties

Standard Variables/Templates

MLLP Transmission Mode