Loading...

Recommendations

©2025 NXGN Management, LLC. All Rights Reserved.Legal notices Privacy Policy

Deleting a Segment

To delete a segment, use the JavaScript delete keyword: delete msg['ZZZ'];

In repeating segments, the above code deletes all instances of that segment. When you delete a segment, all subsequent segments move up.

Deleting a Segment

Mirth® Connect by NextGen Healthcare User Guide

Adding a New Repeating Field

To add a new repeating field, you need to create an XML object at the segment's field level. Populate the fields, then link to the message at the repeating field level: var newDr = new XML ("<PV1.7/>");newDr ["PV1.7.1"] = "C3333";newDr ["PV1.7.2"] = "Jones";msg ['PV1']['PV1.7'] += newDr; Parent topic: Using JavaScript in Mirth Connect

Mirth® Connect by NextGen Healthcare User Guide

Iterating Over Message Segments

To iterate over all segments, follow this example: for each (segment in msg.children()) { if (segment.name().toString() == "ORC") { // Do something… }} To iterate through specifically named segments, use this formula: for each (segment in msg..OBX) { // Do something…} Note that although JavaScript can be used to iterate through message segments, you may find it easier to use the Iterator Rule / Step instead. Parent topic: Using JavaScript in Mirth Connect

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) Crea

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

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

Accessing Message Data with E4X

<?xml version="1.0"?><HL7Message> <MSH> <MSH.1>|</MSH.1> <MSH.2>|^~\&</MSH.2> <MSH.3> <MSH.3.1>SENDAPP</MSH.3.1> </MSH.3> <MSH.4> <MSH.4.1>General Hospital</MSH.4.1> </MSH.4> <MSH.5> <MSH.5.1>RECAPP</MSH.5.1> </MSH.5> <MSH.6/>… </MSH>…</HL7Message> The XML variables msg and tmp represent root-level elements. Use JavaScript bracket notation for each element level in the document below the root (this works with any message data, not only HL7): var sendingFacility = msg ['MSH']['MSH.4'][MSH.4.1'].toString(); Most values in an HL7 message go three levels deep. The first level is a segment; the second level is a field within the segment; the third level is a component within a segment field. If a field or component does not exist, it is created automatically. Examples for repeating segments and fields include using bracket notation to index: var obx = msg['OBX'];var obx5 = obx['OBX.5'];var obx5_1 = obx5['OBX.5.1'].toString(); All E4X methods available on the msg and tmp variables can be