Use the "Destination Set Filter" feature in your source transformer when you need to route messages to only one (or a subset) of destinations in your channel.

Mirth® Connect by NextGen Healthcare User Guide

Enable destination queuing if you do not need to respond to the originating system from your destination.

All destination connectors support queuing. Queuing is important for re-attempting to send messages if they do not succeed at first, but can also improve channel performance. Without queuing, the message send attempt will occur on the main message processing thread for the channel, which will block any new messages from being processed (unless the Max Processing Threads is increased, see below). This can significantly improve channel performance if the system you are sending to is slow to respond. Parent topic: Channel Performance

Mirth® Connect by NextGen Healthcare User Guide

Clear the "Wait for previous destination" checkbox, unless you need destinations to process messages one after another.

Clearing this box will allow adjacent destinations to execute in parallel, potentially improving performance. When using several destinations, you can configure some to execute in order and others to execute in parallel. Parent topic: Channel Performance

Mirth® Connect by NextGen Healthcare User Guide

Destination Set Filter Transformer Step

Destination Set Filtering is a powerful feature of the source transformer that allows you to decide in advance which destinations to exclude from message processing. Using each individual destination's filter to control where a message goes is still a valid workflow, but when you have many destinations all with mutually exclusive filters, the performance of the channel can be affected because message data will be stored to the database for each destination connector. Also filtered connector messages can clutter up the message browser, making it harder to find what you are looking for. The advantage to using Destination Set Filtering in this case is that filtered destinations will not have any message data stored, and will not show up in the message browser. This can greatly increase message throughput. Destination Set Filtering can be done manually with JavaScript (look at DestinationSet in the User API) . However this step allows easier access to the feature without having to write an

Mirth® Connect by NextGen Healthcare User Guide

Channel Performance

Adjust the Message Storage slider so that the channel only retains the message data that you will actually need. If large messages are expected, use an Attachment Handler to improve throughput and reduce memory and disk usage. Enable source queuing if an auto-generated acknowledgement is sufficient for the upstream system. Enable destination queuing if you do not need to respond to the originating system from your destination. Increase the Max Processing Threads value if message order is not important and you may receive a large number of messages in a short time Increase the Queue Threads value if the downstream system can accept multiple concurrent connections. Clear the "Wait for previous destination" checkbox, unless you need destinations to process messages one after another. Use the "Destination Set Filter" feature in your source transformer when you need to route messages to only one (or a subset) of destinations in your channel. Adjust the Message Storage slider so that the cha

Mirth® Connect by NextGen Healthcare FHIR Connector User Guide

Notes on Implementation

First, note that certain interactions have been selectively enabled for certain resource types. For this example we'll only actually be implementing some interactions, so this is largely for illustration. You can enable or disable interactions as you see fit, so that the generated conformance statement will reflect that support to clients. On the source connector settings, we also have a custom "response" variable selected. This indicates that the FhirResponse object the FHIR Listener uses will be retrieved from the response map. Source Transformer Here we have a single step. We use destination set filtering to decide in advance which destination to send a message to. Each destination is named according to one of the possible FHIR interactions, like "create" or "update". Because the interaction of the request will be in the "fhirInteraction" source map variable, we can use that to directly filter on destinations:var interaction = sourceMap.get('fhirInteraction'); if (interaction == 'op

Mirth® Connect by NextGen Healthcare User Guide

Destination Tasks

In addition to the general Edit Channel Tasks, several context-specific tasks are unique to the Destinations Tab: Task Icon Task Name Description New Destination Creates a new destination and adds it to the table above. Delete Destination Deletes the currently selected destination and removes it from the table above. Note that a channel must have at least one enabled destination. Clone Destination Copies the currently selected destination and adds it to the table above. Enable Destination Marks this destination as ready to process messages at deploy time. Disable Destination Marks this destination as not ready to process messages at deploy time. Note that a channel must have at least one enabled destination. Move Destination Up Moves the currently selected destination one row higher in the table above. Move Destination Down Moves the currently selected destination one row lower in the table above. Edit Response Enters the Edit Transformer View for the currently selected destination's r

Use the "Destination Set Filter" feature in your source transformer when you need to route messages to only one (or a subset) of destinations in your channel.

Recommendations

Enable destination queuing if you do not need to respond to the originating system from your destination.

Clear the "Wait for previous destination" checkbox, unless you need destinations to process messages one after another.

Destination Set Filter Transformer Step

Channel Performance

Notes on Implementation

Destination Tasks

Use the "Destination Set Filter" feature in your source transformer when you need to route messages to only one (or a subset) of destinations in your channel.

Enable destination queuing if you do not need to respond to the originating system from your destination.

Clear the "Wait for previous destination" checkbox, unless you need destinations to process messages one after another.

Destination Set Filter Transformer Step

Channel Performance

Notes on Implementation

Destination Tasks