Built-In Code Templates

Mirth® Connect by NextGen Healthcare User Guide

Adding Segments to a Message

Segments are a group of fields that can contain varying types of data. Each segment exists independently and can be used in multiple messages. To add a segment to a message, create a new XML object with a segment code, then add it after the segment it should follow: var seg = new XML("<ZZZ><ZZZ.1><ZZZ.1.1>My Value</ZZZ.1.1></ZZZ.1></ZZZ>");msg['QRF'] += seg; Insert the += operator into a message after a particular segment or at the end of the message. Mirth® Connect has four global functions by which you can create segments for messages: Function Function Description Example Create Segment (individual) Creates an XML object for the segment that has not been inserted into a message. var newSeg = createSegment('ZYX');newSeg ['ZYX']['ZYX.1']['ZYX.1.1'] = "My Value";msg += newSeg; Create Segment (in message) Creates an XML object for the segment at the end of a specified message. createSegment ('ZYX', msg);msg ['ZYX']['ZYX.1']['ZYX.1.1'] = "My Value"; Create Segment (in message, index) Cre

Mirth® Connect by NextGen Healthcare User Guide

Edit Global Scripts

Select a script type from the drop-down menu and edit the script in the text area below. There is also a Reference List to the right for easy drag-and-drop of common helper methods / code templates. The following global script types can be edited: Deploy Script: This script executes once whenever any channel or set of channels deploys. You have access to the global / configuration maps here. Typically this script is used to perform a one-time operation, such as loading a properties file from disk, or instantiate a database connection. Undeploy Script: This script executes once whenever any channel or set of channels is undeployed. You have access to the global / configuration maps here. Typically this script is used to cleanup any data created from the deploy script, such as closing a database connection. Preprocessor Script: This script applies across all channels, and executes once for every message, after the attachment handler has run but before the message reaches the source filte

Mirth® Connect by NextGen Healthcare User Guide

Reference List

The Reference List contains code templates (both built-in and custom) that you can drag into your filter rules and transformer steps. These include common operations like serializing to/from XML, performing a manual database query, or generating a unique ID. For additional information on code templates, see . An image of the reference list on the Reference tab. Use the Category and Filter components at the top of the area to quickly find the template you are looking for. For custom code templates, choose the User Defined Functions or User Defined Code options. Hover your mouse over an item in the list to view its description. Image displaying hover pop-up text. To use an item, simply drag it from the table into your rule/step properties window. Image showing the process drag and drop an item. The corresponding code template/function call is automatically pasted into the field/text area. An image of the ccode function pasted into the text area. Parent topic: Reference Tab Related concep

Mirth® Connect by NextGen Healthcare User Guide

Message Variables

There are a wide variety of different JavaScript contexts throughout Mirth® Connect, and each have various variables automatically available from the local scope. Here are some common examples: message: A string that represents a raw inbound message in native format. msg: An XML object that represents a transformed version of the inbound message. tmp: An XML object that represents an outbound message template; available only if an outbound template is defined. connectorMessage: An instance of the ImmutableConnectorMessage Java class; an internal representation of the message and its attributes. Parent topic: Using JavaScript in Mirth Connect

Mirth® Connect by NextGen Healthcare User Guide

Using Java Classes

You can access any Java class in any JavaScript context: var map = new Packages.java.util.LinkedHashMap(); The "Packages." at the beginning may be omitted for common top-level package domains, like "com", "net", "org", and "java". To avoid having to type out the fully-qualified class name every time, you can import the package: importPackage(org.apache.commons.io);FileUtils.getUserDirectory(); For classes in custom or non-standard libraries, create a resource (see Resources Settings Tab) containing your .jar file. Then include it on the channel in the Library Resources dependencies tab. Parent topic: Using JavaScript in Mirth Connect

Mirth® Connect by NextGen Healthcare User Guide

Logging with JavaScript

Use logger.info() and logger.error() to log information in JavaScript contexts: logger.info("The value of x =" + x); You can view the output of this method in the Mirth® Connect Dashboard's Server Log. The default logging level, ERROR, is the quickest, having the least amount of overhead. INFO and DEBUG levels give more details but have more overhead, so are somewhat slower. You can change the logging level via the Mirth® Connect Server Manager for users who run the latest version of Mirth® Connect on a Mac ( Applications > Mirth Connect > mcmanager) or PC: Note: Mirth Appliance users can change the logging level from the Mirth® Connect Settings page via Applications > Mirth Connect > Manage from the Appliance UI. Parent topic: Using JavaScript in Mirth Connect

Built-In Code Templates

Recommendations

Adding Segments to a Message

Edit Global Scripts

Reference List

Message Variables

Using Java Classes

Logging with JavaScript

Adding Segments to a Message

Edit Global Scripts

Reference List

Message Variables

Using Java Classes

Logging with JavaScript