Edit Channel View

Mirth® Connect by NextGen Healthcare User Guide

Navigation

Select the Channels link in the Mirth® Connect task pane at the top-left to enter the Channels View. In the Channel Table, s select the channel you would like to edit, then select the Edit Channel task to the left. You can also double-click the channel row in the table to access the Edit Channel This section contains the following topics: Source Tab Edit Channel View Destinations Tab Scripts Tab Edit Channel Tasks Parent topic: Edit Channel View

Mirth® Connect by NextGen Healthcare User Guide

Navigation

Select the Channels link in the Mirth® Connect task pane at the top-left to enter the Channels View: In the Channel Table, select the channel you wish to edit, and select the Edit Channel task to the left: You can also double-click the channel row in the table. Once in the Edit Channel View, select either the Source Tab or Destinations Tab. Select a destination if necessary. Then, select on the Edit Filter, Edit Transformer, or Edit Response tasks to the left. The Edit Response task (for editing the response transformer) is only visible for destination connectors. This section is separated into the following topics: Message Templates Tab Message Trees Tab Reference Tab Create New Rules/Steps Rule/Step Table Filter Rule Properties Transformer Step Properties Response Transformers Working With Iterators View Generated Script Filter Tasks Transformer Tasks Parent topic: Edit Filter / Transformer Views

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

Source Connector

Every channel has exactly one source connector which gets data into Mirth® Connect from an external system. The source connector is configured on the Source Tab within the Edit Channel View. In addition to the standard Connector Components, source connectors include: A Source Queue that can be enabled or disabled. When enabled, the channel acts as a store-and-forward service that can receive messages and send acknowledgements immediately to the originating system, without having to wait for the message to process through the entire channel. A Batch Processor that can be enabled or disabled. When enabled, the channel takes any incoming data and splits it into multiple messages that each proceed discretely through the channel. See Batch Processing for additional information. A Response Selector that determines what response to send back to the originating system, if applicable. You can choose to auto-generate a response based on the inbound data type of the source transformer. You can al

Mirth® Connect by NextGen Healthcare User Guide

Channel Scripts

Channel Scripts can be configured on the Scripts Tab within the Edit Channel View. There are four special scripts associated with a channel: Deploy Script: This runs once right before a channel is deployed. Preprocessor Script: This runs once for every message, after the source connector sends a message to the channel and after the Attachment Handler Properties has optionally extracted data, but before the message has reached the source filter/transformer. The job of the preprocessor is to modify the incoming message. Post Processor Script: This runs once for every message, after the source connector and all destinations have completed (excluding asynchronous processes like the destination queue), but before the source connector sends a response back to the originating system. The postprocessor script has access to responses from all executed destination, and can return custom response that the source connector can use. Undeploy Script: This runs once right before a channel is undeploy

Mirth® Connect by NextGen Healthcare User Guide

Destination Connectors

Every channel has at least one destination connector that sends data out to an external system. Destination connectors are configured on the Destinations Tab within the Edit Channel View. In addition to the standard Connector Components, destination connectors include: An Enabled flag that determines whether the destination is currently being used. A channel must have at least one destination enabled at any given time. A Wait for previous destination setting that determines what chain a destination connector belongs to. (For additional information, see Destination Chains. ) A Response Transformer. This is like a regular transformer, except it has its own response inbound data type and response outbound data type, and does the job of modifying the response that an external system returned to a destination connector. It also allows you to decide when to queue / force-error a message. See Response Transformers for additional information. Parent topic: Channel Components

Edit Channel View

Recommendations

Navigation

Navigation

Code Template Contexts

Source Connector

Channel Scripts

Destination Connectors

Edit Channel View

Navigation

Navigation

Code Template Contexts

Source Connector

Channel Scripts

Destination Connectors