In the previous steps, the incoming messages were transformed into the HL7 message format. The next step is to create a message definition that processes these transformed messages.

To create the message definition:

• In the Chameleon toolbar, click Message. A new message, named Message1, appears in the Workspace panel at the left.
• In the Workspace panel, right-click Message1 and select Rename. Change the name to Default.
• In the Default message definition, double-click Identity. The Identity window appears.
• In the Description field, type SurgeryFromFile.
• In the first empty row in the table, in the Segment column, select MSH.
• In this row, in the Field column, click the ... (ellipsis) button. In the Pick Identity Field window, expand 3 - Sending Application and select 1 - Namespace ID.
• In the Value column, type SURGFILE.
• In another empty row, in the Segment column, select MSH. In the Field column, click .... In the Pick Identity Field window, expand 5 - Receiving Application and select 1 - Namespace ID. In the Value field, select VLFILEIMP.
• In the next empty row, in the Segment column, select MSH. In the Field column, click .... In the Pick Identity Field window, expand 9 - Message Type and select 1 - Message Code. In the Value field, select ZZZ.
• In the next empty row, in the Segment column, select MSH. In the Field column, click .... In the Pick Identity Field window, expand 9 - Message Type and select 2 - Trigger Event. In the Value field, select 001.

When you have finished, the Identity window should look like this:

The fields and values in the Identity window are the fields and values that must be matched in an incoming message if the message is to be processed by this message definition. If you examine the sample message after it has been transformed by the Global Inbound Script, you will notice that the MSH segment that was added to the message is a match for these fields and values. This means that the sample message will be processed by this message definition.