Using Message Identities

For HL7 messages, the message identity is usually determined using the MSH.9 (Field 9) composite since it contains the Message Code and Trigger Event of the message. For example, an Update Patient message will contain ADT in the message code subfield, and A31 in the trigger event subfield. As a result, the message identity will be ADT^A31.

In this section, you will learn how to use message identities in Chameleon.

Message Identities Treated as Regular Expressions

Each message identity is always treated as a regular expression. For example, if the identity value is "ADT", it can appear anywhere in the field. In order to force it to be an exact match, you must add "^" to the start of the field and "$" to the end of the field (e.g. "^ADT$").

More Information On Message Identities

To learn about message identities, see Message Identities.

General Information About HL7

To learn more about HL7, see What is HL7?

Manually Defining the Message Identity
Defining the Matching Order of Message Definitions
Specifying Default Messages
Using Regular Expression Metacharacters
Filtering Messages Using the Message Identity

iNTERFACEWARE™ Inc.

Using Message Identities