JavaScript Attachment Handler Properties

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

Mirth® Connect by NextGen Healthcare User Guide

JavaScript HTTP Authentication

Allows you to authenticate users with a custom JavaScript script. With this script you have access to source map variables, and can choose whether to send a challenged or failure response back to the client. The default script simply allows all requests to pass. The Script field will show <Default Script Set> if the default script is currently being used. If you have made any modification to the script, the Script field will show <Custom Script Set>. Select the Script field to edit the JavaScript: This script expects either a boolean ( true to accept the request, false to send back a failure response) or an AuthenticationResult object to be returned (for additional information, see User API) . There are three types of results you can return: AuthenticationResult.Success(): The request will be accepted and processed through the channel. AuthenticationResult.Challenged(authenticateHeader): The request will not be processed through the channel. A 401 response will be sent back to the clie

Mirth® Connect by NextGen Healthcare User Guide

Custom Attachment Handler Properties

This attachment handler gives you full control over the attachment extraction process by allowing you to provide a custom Java implementation of MirthAttachmentHandlerProvider. In the properties you specify the class name, and any properties you want to pass in. Properties Parent topic: Attachment Handler Properties

Mirth® Connect by NextGen Healthcare User Guide

Regex Attachment Handler Properties

This attachment handler extracts data from the incoming message using regular expressions. You can specify multiple expressions, each with their own MIME type. There are also options to replace certain values on the extracted attachment data before storing it in the database, and replace values in the attachment data right before reinserting it into the message for outbound dispatching. Regular Expressions Table String Replacement Tables Parent topic: Attachment Handler Properties

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

DICOM Attachment Handler Properties

The DICOM Attachment Handler does not have properties to configure. When used, the handler automatically takes the incoming DICOM data and extract all pixel data into one or more attachments. The resulting raw data will not have an attachment replacement token, but instead will be the Base64 encoded representation of the DICOM message without the pixel data. If the DICOM Data Type is used in a filter / transformer, it will automatically serialize this Base64 data into an XML message containing all header / tag data. Because there is no attachment replacement token, to reattach DICOM messages on the destination connector side, a special token is used: ${DICOMMESSAGE} This indicates to the destination connector that the encoded data should be merged with any pixel data attachments into a final binary representation before being dispatched to the external system. Parent topic: Attachment Handler Properties

JavaScript Attachment Handler Properties

Recommendations

Attachment Handlers

JavaScript HTTP Authentication

Custom Attachment Handler Properties

Regex Attachment Handler Properties

Attachment JavaScript Functions

DICOM Attachment Handler Properties

Attachment Handlers

JavaScript HTTP Authentication

Custom Attachment Handler Properties

Regex Attachment Handler Properties

Attachment JavaScript Functions

DICOM Attachment Handler Properties