Alert Enabled Channels

Mirth® Connect by NextGen Healthcare User Guide

Alert Actions

This section of the Edit Alert View allows you to decide what actions to take after your alert has been triggered. You can take multiple actions all at once for a single trigger event, which may include sending e-mails to multiple users and dispatching messages to multiple channels. Protocols All protocols also support Velocity Variable Replacement, you can use any of the Alert Variables below, or any Global Map variable. Channel: The template is sent as a message to the channel selected in the Recipient column. The subject is not used for this protocol. Email: The subject and template is used to send an e-mail to the address specified in the Recipient column. User: Same as the Email protocol, the e-mail address used is the one configured for the selected user. Role: E-mails will be sent to all users within a particular Role-Based Access Control role. Only visible when User Authorization is installed. Alert Variables Parent topic: Edit Alert View

Mirth® Connect by NextGen Healthcare User Guide

Alert Error Types and Regex

This section of the Edit Alert View allows you to decide what type of errors you want your alert to trigger on. This includes choosing among categories of error types, and optionally using a regular expression that only allows events whose error source, error message, or exception stacktrace matches to cause an alert trigger to occur. Alert Error Categories Parent topic: Edit Alert View

Mirth® Connect by NextGen Healthcare User Guide

Edit Alert Tasks

The following context-specific tasks are available throughout the Edit Alert View: Task Icon Task Name Description Save Alert Saves all changes made to the current alert. If the alert is enabled, it automatically listens for new events to trigger on. Note that since many alerts rely on dispatching e-mails, you are warned if your global SMTP settings are not configured on the Server Settings Tab. Export Alert Exports the current alert to an XML file. Parent topic: Edit Alert View

Mirth® Connect by NextGen Healthcare User Guide

Edit Views

This section is separated into the following topics: Edit Channel View Edit Filter / Transformer Views Edit Global Scripts View Edit Code Templates View Edit Alert View Edit Channel View Edit Filter / Transformer Views You can use the Edit Filter view or the Transformer view to configure filter rules and transformer steps. Edit Global Scripts View The Edit Global Scripts view provides global scripts across all channels. Edit Code Templates View This view is where code templates and libraries are configured for your Mirth® Connect server. Edit Alert View Use the Edit Alert view to configure and modfiy alerts. Parent topic: Mirth Connect Administrator

Mirth® Connect by NextGen Healthcare User Guide

Navigation

Select the Alerts link in the Mirth® Connect task panel at the upper-left side of the window. Select the alert you want to edit, and select the Edit Alert task in the Alert Tasks panel on the left. You can also double-click the alert from the Alerts Table. This section is separated into the following topics: Alert Error Types and Regex Alert Enabled Channels Alert Actions Edit Alert Tasks Parent topic: Edit Alert View

Mirth® Connect by NextGen Healthcare User Guide

Configuration Map

This map is also available across your entire server, across all channels and all messages. Like the global map, that means you can use the values from the configuration map in any channel, or somewhere else like an Alert. Unlike the global map however, this map is editable only from the Configuration Map Settings Tab, and is read-only from the perspective of channels / messages. The values are also String key/values only. This map is useful for global, static settings you want to persist across restarts of Mirth Connect. For example, you could store a variable like "clientAdtPort" and then use Velocity to reference that variable ("${clientAdtPort}") in a TCP Listener. That way you can export the channel on one Mirth® Connect installation, import it into a completely different installation, and then you would not have to edit anything in the channel settings as long as the configuration map is set on both instances. Get configuration map value: var value = configurationMap.get('key');

Alert Enabled Channels

Recommendations

Alert Actions

Alert Error Types and Regex

Edit Alert Tasks

Edit Views

Navigation

Configuration Map

Alert Actions

Alert Error Types and Regex

Edit Alert Tasks

Edit Views

Navigation

Configuration Map