Alert Error Categories

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

Destination Set Filter Transformer Step

Destination Set Filtering is a powerful feature of the source transformer that allows you to decide in advance which destinations to exclude from message processing. Using each individual destination's filter to control where a message goes is still a valid workflow, but when you have many destinations all with mutually exclusive filters, the performance of the channel can be affected because message data will be stored to the database for each destination connector. Also filtered connector messages can clutter up the message browser, making it harder to find what you are looking for. The advantage to using Destination Set Filtering in this case is that filtered destinations will not have any message data stored, and will not show up in the message browser. This can greatly increase message throughput. Destination Set Filtering can be done manually with JavaScript (look at DestinationSet in the User API) . However this step allows easier access to the feature without having to write an

Mirth® Connect by NextGen Healthcare User Guide

Destination Settings

These are general settings that apply to all destination connectors. They include configuring the destination queue, whether to validate responses, and whether to re-attach attachments on outbound messages. Item Name Description A Queue Messages Never: Disable the destination queue. On Failure: Attempt to send the message first before queuing it. This will allow subsequent destinations and the Postprocessor to use the response from this destination if it successfully sends before queuing. Always: Immediately queue the message. Subsequent destinations and the Postprocessor will always see this destination's response as QUEUED. B Advanced Queue Settings Configure how often to re-attempt queued messages, increase queue threads, and more. C Validate Response Select Yes to validate the response. Responses can only be validated if the response transformer's inbound properties contains a Response Validation section. If validation fails, the message will be marked as queued or errored. For add

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

Advanced Alerting User Guide

Channel Error

The Channel Error type triggers whenever a channel encounters an error. You can 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. An image of the Errors section. Alert Error Categories Any: Select this option to trigger on all error categories. Source Connector: An error that originated from the source connector during deploy/start, receiving a message, or sending a response. Destination Connector: An error that originated from a destination connector during deploy/start, dispatching a message, or receiving a response. Serializer: An error that originated from the source or destination filter/transformer script, specifically when serializing the message to the internal representation (such as XML), or deserializing the message to the outbound data type format. Filter: An error that origi

Mirth® Connect by NextGen Healthcare Advanced Clustering User Guide

Advanced Alerting

With the Advanced Alerting plugin installed, there will also be a new trigger type available, Clustering Channel Synchronization: When the channel synchronization process detects that an action should be taken, it will first send a Submitted event that can be triggered on. When that action finishes, it will send one of these two triggerable events: Succeeded: The task finished without any errors. Failed: The task finished with errors. This usually means that the channel was not able to be deployed/started/etc. With this event, the "exception" variable containing the full error stacktrace will be available in the template context. In addition to all of the regular template variables that are available in alert template contexts, this trigger also adds the following variables: Variable Description action The channel or connector action being taken. Will be one of: Deploy, Undeploy, Start, Stop, Pause, Resume event The stage of the current task. Will be one of: Submitted, Succeeded, Faile

Alert Error Categories

Recommendations

Edit Global Scripts

Destination Set Filter Transformer Step

Destination Settings

Extract Attachments

Channel Error

Advanced Alerting

Edit Global Scripts

Destination Set Filter Transformer Step

Destination Settings

Extract Attachments

Channel Error

Advanced Alerting