Expanded Replacement Tokens

Mirth® Connect by NextGen Healthcare User Guide

Reattachment

Right before a destination connector dispatches a message to the external system, it scans the outbound message for attachment replacement tokens and automatically re-inserts the actual attachment data. You can prevent a destination from reattaching data by disabling the Reattach Attachments option in the Destination Settings. Parent topic: Attachment Handlers

Mirth® Connect by NextGen Healthcare User Guide

Channel Writer

The Channel Writer is a connector that simply dispatches messages to other internal channels. This can be useful if you split your message workflow into multiple channels, where one sends to another. If no target channel is specified, the connector acts as a "sink" where no message dispatching is done. Note that a channel does not need to use a Channel Reader source for a Channel Writer to be able to send messages to it. The connector also has options to inject source map variables into the downstream message of the target channel. Supported property groups: Destination Settings Item Name Default Value Description A Channel Id <None> The unique ID of the target channel to send messages to. This may be a hard-coded ID, or may be a Velocity Variable Replacement. Use the drop-down menu to the right to quickly select a particular channel. If <None> is selected, the destination will act as a "sink" where messages are not dispatched anywhere. B Message Metadata The map variables entered here

Mirth® Connect by NextGen Healthcare User Guide

Attachment JavaScript Functions

Attachment Handlers are used to extract a portion of a message (or the entire message) and store it separately as an attachment. The portion of the message that was extracted is replaced with an attachment replacement token. When you use a destination connector to send a message downstream, Mirth® Connect will automatically take the message and replace any attachment tokens with the actual attachment data (unless you have Reattach Attachments turned off in the Destination Settings) . Throughout the message lifecycle you can retrieve, modify, and add new attachments with built-in helper functions. Built-In Attachment Functions The AttachmentUtil Class The Attachment Object Examples Built-In Attachment Functions The AttachmentUtil Class The Attachment Object Examples Parent topic: Mirth Connect and JavaScript

Mirth® Connect by NextGen Healthcare User Guide

Extraction

When an attachment handler extracts data from a message, it leaves behind an attachment replacement token like this: This value tells the destination connector where in your message the attachment should be re-inserted right before dispatching to an outbound system. If multiple attachments were extracted for a message, then there will be multiple replacement tokens in the raw data. Parent topic: Attachment Handlers

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

Mirth® Connect by NextGen Healthcare User Guide

Attachment Handlers

An Attachment Handler allows you to extract pieces of any incoming message and store them separately. As a message processes through a channel, multiple copies of it will be held in memory at once (for the raw / transformed / encoded versions of a message, etc.). Attachments are stored only once, so by using them you can greatly reduce your channels' memory footprint. These are configured in the Channel Properties section of the Summary Tab within the Edit Channel View. Note: See Attachment JavaScript Functions for more information. By default the attachment handler is set to None, meaning no attachments will be extracted. To extract attachments choose an attachment handler type from the drop-down menu, and select the Properties button to configure the handler. Note: If Store Attachments next to the Attachment menu is unchecked, then attachments will be extracted from the incoming message data, but not actually stored anywhere. Extraction Reattachment Expanded Replacement Tokens Attach

Expanded Replacement Tokens

Recommendations

Reattachment

Channel Writer

Attachment JavaScript Functions

Extraction

Destination Settings

Attachment Handlers

Reattachment

Channel Writer

Attachment JavaScript Functions

Extraction

Destination Settings

Attachment Handlers