iNTERFACEWARE Products Manual > Learning Center > Tutorials and Sample Scenarios > Routing and Processing Messages > Ignoring Messages > Step 2 - Setting Up the VMD File > Creating the Patient Message Definition |
|
Looking for Iguana v.5 or v.6? Learn More or see the Help Center.
In the previous section, you imported the segment definitions for your message. The next step is to create a message definition to match the message types that you want to process. 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:
The message is re-parsed automatically and is now recognized: The Create Message Definition Wizard adds the new message definition 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 Identity window appears: 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. Since you want to use this message definition to match messages of type ADT^A03, ADT^A05, ADT^A06 and ADT^A08 in addition to ADT^A04, you must update the message identity. To do this:
This tells Chameleon that the Trigger Event field must be one of A03, A04, A05, A06 or A08 to match the message.
|