In the previous section, you imported the segment definitions for your message. The next step is to create a message definition for the message.

This message definition will use the first and second subfields of the ninth field of the MSH segment as its message identity. These subfields are named Message Code and Trigger Event, and are also known as MSH.9.1 and MSH.9.2. Incoming messages will be processed by this message definition if their Message Code and Trigger Event fields match the message identity.

To create a message definition:

• In the Message Browser, click the Message is unrecognized link (in the yellow panel). This displays the Create Message Definition Wizard:

Using the Create Message Definition Wizard

• Leave everything as is, and click Finish.

The message is re-parsed automatically and is now recognized:

Sample Message is Now Recognized

The Create Message Definition Wizard adds the new message definition to the Workspace:

Message Definition Added to the Workspace

The Wizard also creates the message identity for this message definition. To view the message identity, double-click the Identity link that has just been created:

The Message Identity

This indicates that the message identity for this definition is a Message Code of ADT and a Message Type of A04. These were the values defined in the sample message supplied to the Message Browser.

After you have created your message definition, the next step is to define the segment grammar to determine the information to be extracted from the message.