Loading...
Recommendations
Mirth® Connect by NextGen Healthcare User Guide
Select the Channels link in the Mirth Connect task panel on the upper-left side of the window. Select a channel where the messages you would like to view reside. Select the View Messages task in the left task list. For additional information, see Channel Tasks. This section is separated into the following topics: Metadata Table Message Content Tab Mappings Tab Errors Tab Attachments Tab Search Messages Message Browser Tasks Parent topic: NavigationFrom the Channels View
Mirth® Connect by NextGen Healthcare User Guide
Metadata typically refers to important information about the message, but not the actual message content. Message Metadata includes: Message ID: Every message for any given channel has a unique integer ID, the Message ID. The Message ID is used to organize data in the message browser and join connector messages together. Connector Metadata ID: Each connector has its own ID, referred to as the connector metadata ID. The source connector always has a metadata ID of zero (0). Destination connector metadata IDs start at one (1) and increment for each new destination you add to the channel. Status: Each connector message has a status, which tells the channel the current processing state. For example, the status could be RECEIVED, which means the raw data has been committed to the database, but the message is in the middle of being processed. It could be QUEUED, which may mean it is sitting in a queue waiting to be processed, or one or more attempts have been made to process the message, butMessage Metadata
Mirth® Connect by NextGen Healthcare User Guide
The Channel Writer is a connector that simply dispatches messages to other internal channels. This can be useful if you split your message workflow into multiple channels, where one sends to another. If no target channel is specified, the connector acts as a "sink" where no message dispatching is done. Note that a channel does not need to use a Channel Reader source for a Channel Writer to be able to send messages to it. The connector also has options to inject source map variables into the downstream message of the target channel. Supported property groups: Destination Settings Item Name Default Value Description A Channel Id <None> The unique ID of the target channel to send messages to. This may be a hard-coded ID, or may be a Velocity Variable Replacement. Use the drop-down menu to the right to quickly select a particular channel. If <None> is selected, the destination will act as a "sink" where messages are not dispatched anywhere. B Message Metadata The map variables entered hereChannel Writer
Mirth® Connect by NextGen Healthcare User Guide
Select the Advanced... button in the message browser search pane to view the Advanced Search Filter. (See Option E in Message Search Options) Item Name Description A Connectors Table Use this table to include only certain connectors in the search criteria. The Id column refers to the metadata ID of the connector, where the Source connector is always 0, and destination connectors have metadata IDs greater than zero. The Current Connector Name column shows the current name of each connector. Even if a destination is renamed, the metadata ID remains static, and is used for the search. The Deleted Connectors row refers to historical connector messages associated with destinations that were deleted. B Select/Deselect All Select this checkbox to select/deselect all connectors in the Connectors Table. C Message Id Enter the minimum and maximum message IDs to include in the search. This could refer to the current ID (Message Id), the original ID of a reprocessed message (Original Id), or the oAdvanced Search Filter
Mirth® Connect by NextGen Healthcare User Guide
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 propertiesMessage Content Types
Mirth® Connect by NextGen Healthcare User Guide
Note: These steps are repeated for each destination connector that a message flows through. The encoded content from the source connector is used by each destination connector as its raw data. The content is serialized (converted) to the internal representation of the inbound data type (e.g. XML). The content runs through the filter, and the message is either accepted or filtered. If the message gets filtered, flow stops for the current destination here. If there are additional destinations in the current chain, these steps are repeated for the next destination. Otherwise, assuming all other destination chains have finished, flow jumps down to the Final Processing Steps. The content runs through the transformer, where it may be modified. The post-transformer content is stored as the transformed data. The content is deserialized (converted) from the outbound data type's internal representation (e.g. XML) into the actual outbound format (HL7, EDI, etc.). The content is stored as encoded