Built-In Attachment Functions

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

The Attachment Object

When using these methods, you will likely be working with a special class called Attachment. This class is documented in the User API. A few of the available methods are documented here: Create a new Attachment new Attachment() new Attachment(id, content, type) new Attachment(id, content, charset, type) id The unique ID of the attachment. content The content (String or byte array) to store for the attachment. charset If the content passed in is a string, this is the charset encoding to convert the string to bytes with. If the content is a String and a charset is not used, UTF-8 will be used as the charset. type The MIME type of the attachment. Retrieve Attachment Content Note: When you retrieve an attachment using the Built-In Attachment Functions or The AttachmentUtil Class, you may want to pass in true for the base64Decode argument so that the attachment content is already decoded. getContent() Retrieves the raw byte array content of the attachment. Note that this may be the actual r

Mirth® Connect by NextGen Healthcare User Guide

Extract Attachments

Use the following method to extract and store attachments from the attachment script: The resulting Attachment object contains the ID you need to inject back into the message. For more information, look at the User API. The return value for the JavaScript attachment script should be the final message string, with any attachments extracted out and replaced with attachment replacement tokens. addAttachment(data, type) Creates and stores an attachment for the current message. Table 1. Parameters Name Type Description data String or Byte array The actual attachment data to insert. Man be either a String or a byte array. If a string is used, it is assumed to be a Base64 encoded representation of the actual attachment data. type String The MIME type of the attachment. For additional information see Attachment Handlers. <Return Value> Attachment The inserted Attachment object. The resulting Attachment object contains the ID you need to inject back into the message. For more information, look

Mirth® Connect by NextGen Healthcare User Guide

Advanced Search Filter

Select the Advanced... button in the message browser search pane to view the Advanced Search Filter. (See Option E in Message Search Options) Item Name Description A Connectors Table Use this table to include only certain connectors in the search criteria. The Id column refers to the metadata ID of the connector, where the Source connector is always 0, and destination connectors have metadata IDs greater than zero. The Current Connector Name column shows the current name of each connector. Even if a destination is renamed, the metadata ID remains static, and is used for the search. The Deleted Connectors row refers to historical connector messages associated with destinations that were deleted. B Select/Deselect All Select this checkbox to select/deselect all connectors in the Connectors Table. C Message Id Enter the minimum and maximum message IDs to include in the search. This could refer to the current ID (Message Id), the original ID of a reprocessed message (Original Id), or the o

Mirth® Connect by NextGen Healthcare User Guide

Scripts Tab

The Scripts tab is where channel-level scripts are configured. Select a script type from the drop-down list and edit the script in the text area.Select a script type from the drop-down and edit the script in the text area below. If a number appears next to "Scripts" in the tab, that number represents how many scripts have been edited from the default values. There is also a Reference List to the right for easy drag-and-drop of common helper methods / code templates. The following channel-level script types can be edited: Deploy Script: This script executes once when the channel is deployed. You have access to the global / global channel / configuration maps here. Typically this script is used to perform a one-time operation for the given channel, such as loading a properties file from disk, or instantiating a database connection. Undeploy Script: This script executes once when the channel is undeployed. You have access to the global / global channel / configuration maps here. Typically

Interoperability Connector Suite User Guide

Source Connectors - Sending Attachments

All of the Interoperability Suite source connectors (PIX/PDQ/XCA/XCPD/XDS.b) support sending attachments back with the SOAP response payload as a multipart response. To do this, you add a MultipartResponseSettings object into the response map (or channel map) with the key "responseMultipartSettings". For example: var bodyHeaders = Maps.map(); bodyHeaders.put( "X-Custom-Body-Header" , Lists.list( "testing" )); bodyHeaders.put( "X-Custom-Body-Header2" , Lists.list( "testing2" )); var attachments = Lists.list();// Create message attachment here in channel and use that var attachmentId = addAttachment( "testing" , "text/plain" , true ).getId(); var attachment1 = new ResponseMultipartAttachment(attachmentId); attachments.add(attachment1); // Set custom attachment content var attachment2 = new ResponseMultipartAttachment(); attachment2.setContent(FileUtil.decode( "iVBORw0KGgoAAAANSUhEUgAAACAAAAAgCAYAAABzenr0AAAAAXNSR0IArs4c6QAAAAZiS0dEAP8A/wD/oL2nkwAAAAlwSFlzAAALEwAACxMBAJqcGAAAAAd0SU1FB9kFD

channelId	The ID of the channel associated with the attachments.
messageId	The ID of the message associated with the attachments.

channelId	The ID of the channel to retrieve the attachment from.
messageId	The ID of the message to retrieve the attachment from.
attachmentId	The ID of the attachment to retrieve.
base64Decode	If true, the content of the attachment will first be Base64 decoded for convenience.

attachment	The The Attachment Object to update.
attachmentId	The unique ID of the attachment to update.
channelId	The ID of the channel the attachment is associated with.
messageId	The ID of the message the attachment is associated with.
data	The attachment content (must be a string or byte array).
type	The MIME type of the attachment.
base64Encode	If true, the content will be Base64 encoded for convenience. If the content you are passing in is not already Base64 encoded, you should pass in true for this argument.

data	The data to insert as an attachment. May be a string or byte array.
type	The MIME type of the attachment.
base64Encode	If true, the content will be Base64 encoded for convenience. If the content you are passing in is not already Base64 encoded, you should pass in true for this argument.

Built-In Attachment Functions

Recommendations

Attachment JavaScript Functions

The Attachment Object

Extract Attachments

Advanced Search Filter

Scripts Tab

Source Connectors - Sending Attachments