Change Data Type Properties

Mirth® Connect by NextGen Healthcare User Guide

Edit Data Types

You can edit the properties for the destination transformer's inbound data type. A filter only has access to the inbound data type, while a transformer has access to both inbound and outbound data types. Additionally, when editing the destination transformer the inbound data type may not be changed, since it must remain the same as the source connector's outbound data type. However, you can still edit the properties for the destination transformer's inbound data type. An image of the Message Templates tab editing the inbound data type. When selecting the Properties button, a dialog opens allowing you to edit the various inbound or outbound properties for the data type. This is a subset of the view shown in the Set Data Types Window. For additional information, see About Data Types and Data Types. Parent topic: Message Templates Tab

Mirth® Connect by NextGen Healthcare User Guide

Select Data Types

The table at the top of the dialog shows all currently configured connectors for your channel. Since response transformers have their own inbound / outbound data types, for destination connectors you can expand the node in the tree and view the Response row underneath a particular destination. For a new channel, all data types are set to HL7 v2.x by default. This can be changed in two ways: The Connector table has Inbound and Outbound columns with drop-down menus. Select the drop-down arrow inside of the cell to make a selection: Use the drop-down menu in the Inbound Properties or Outbound Properties sections: Note: Since a message flows from the source connector directly to each destination connector, every destination inbound data type is always equal to the source outbound data type. Therefore, you may notice that the inbound data type is not editable for destination rows. In order to change the destination inbound data type, change the source outbound data type. Parent topic: Set D

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

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

Code Template Contexts

Similar to how a code template library can be included only on specific channels, code templates can further be isolated to specific scripts. This can be helpful for ensuring that there are no conflicts between function names, and also for better memory usage, since not all code templates need to be compiled in with all scripts across your entire server. The script contexts are organized into groups, allowing you to easily include a code template in, for example, all global scripts, in a single select. The following groups are displayed: Global Scripts: The global deploy/undeploy/preprocessor/postprocessor scripts, not specific to any particular channel. For additional information, see Edit Global Scripts View. Channel Scripts: The channel-level deploy/undeploy/preprocessor/postprocessor scripts (more info here) , as well as the JavaScript Attachment Handler and JavaScript Batch Adapter (for additional information, see Data Types) . Source Connector: The source filter/transformer scrip

Mirth® Connect by NextGen Healthcare User Guide

Destination Settings

These are general settings that apply to all destination connectors. They include configuring the destination queue, whether to validate responses, and whether to re-attach attachments on outbound messages. Item Name Description A Queue Messages Never: Disable the destination queue. On Failure: Attempt to send the message first before queuing it. This will allow subsequent destinations and the Postprocessor to use the response from this destination if it successfully sends before queuing. Always: Immediately queue the message. Subsequent destinations and the Postprocessor will always see this destination's response as QUEUED. B Advanced Queue Settings Configure how often to re-attempt queued messages, increase queue threads, and more. C Validate Response Select Yes to validate the response. Responses can only be validated if the response transformer's inbound properties contains a Response Validation section. If validation fails, the message will be marked as queued or errored. For add

Change Data Type Properties

Recommendations

Edit Data Types

Select Data Types

Bulk Edit Mode

Standard Variables/Templates

Code Template Contexts

Destination Settings

Edit Data Types

Select Data Types

Bulk Edit Mode

Standard Variables/Templates

Code Template Contexts

Destination Settings