Error Content Types

Content Type	Description
Processing Error	An error occurred during a user-script, such as the preprocessor or the filter / transformer.
Response Error	An error occurred generating the response, or sending the response from the source connector to its point of origin.
Post Processor Error	An error occurred during the .

Mirth® Connect by NextGen Healthcare User Guide

View Message Errors

Select a connector message in the Metadata Table. Select the Errors tab (located below the Metadata Table). Note that this tab is only available if the connector message actually has error content. Select the radio button corresponding to the content type you want to view. Parent topic: Errors Tab

Mirth® Connect by NextGen Healthcare User Guide

Errors Tab

If any error content exists for a connector message, a separate Errors tab will be present in the message browser when you select that row in the Metadata Table. You can tell beforehand whether a connector message has error content by looking at the Errors column in the metadata table. For additional information, see Metadata Table. View Message Errors Error Content Types Parent topic: Message Browser View

Mirth® Connect by NextGen Healthcare User Guide

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 (e.g. XML), or deserializing the message to the outbound data type format. Filter: An error that originated from a source or destination filter rule. Transformer: An error that originated from a source or destination transformer step. User Defined Transformer: An error that originated from a user-defined call to AlertSender (alerts.sendAlert) from any script. For additional information, see The User API (Javadoc). Response Validation: An error that originated from a destination connector

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 User Guide

Message Content Types

Content Type Description Raw The inbound message as received and stored by the channel, after the attachment handler has extracted any attachments but before the preprocessor script has modified the message. Processed Raw The altered inbound message after the preprocessor script has executed. Transformed When a message enters a transformer, the raw (or processed raw) data is serialized into an internal representation, which may be XML, JSON, or Raw depending on the inbound data type. The transformer then has a chance to alter this serialized data. This content is the internal representation of the message after the transformer has executed. Encoded After a message leaves the transformer, the Transformed Data (internal representation of the message) is deserialized into the outbound data type. This is referred to as the Encoded Data. The encoded data for a source connector is equivalent to the raw data for a destination connector. Sent A snapshot of the destination connector properties

Mirth® Connect by NextGen Healthcare User Guide

Final Processing Steps

Final Processing Steps Final Processing Steps Note: This point is reached when all destination chains have finished processing the message. If the message was filtered or errored out on the source connector, then flow will immediately jump down to this step. The post processor script is executed. It can return a response that the source connector may use. The source connector decides what response to send back to the originating system, if any. This may be an auto-generated value, the response payload from a destination connector dispatch, a response returned from the post processor script, or a completely custom value residing in the response map. The selected response is stored as the source connector's response data and is sent back to the originating system, if needed. Parent topic: The Message Processing Lifecycle

Error Content Types

Recommendations

View Message Errors

Errors Tab

Alert Error Categories

Channel Error

Message Content Types

Final Processing Steps

View Message Errors

Errors Tab

Alert Error Categories

Channel Error

Message Content Types

Final Processing Steps