Sample Scenario

To help you gain a true understanding of this feature, let's consider the following real-world scenario. Let's assume that your interface is expecting a stream of ADT^A04 and ADT messages similar to the ones shown below:

MSH|^~\&||.|||199908180016||ADT^A04|ADT.1.1698593|P|2.5
PID|1||000395122||LEVERKUHN^ADRIAN^C^^^||19880517180606|M|^^^^^||6 66TH AVE NE^^WEIMAR^DL^98052||(157)983-3296|||S||12354768|87654321
NK1|1|TALLIS^THOMAS^C|GRANDFATHER|12914 SPEM ST^^ALIUM^IN^98052|(157)883-6176
NK1|2|WEBERN^ANTON|SON|12 STRASSE MUSIK^^VIENNA^AUS^11212|(123)456-7890
PV1|1|E|EMG-W^^|1||||||||||ER||||ER||H|||||||||||||||||||OVL||REG|||199908180015
GT1|1||SMITH^JAMES^M||12914 164TH AVE NE^^RICHMOND^ON^98052|(157)883-6176|||||F|535-52-9776||||WEISS JENSON|.^^WELLINGTON^ON^.|
IN1|1|PRE2||LIFE PRUDENT BUYER|PO BOX 23523^WELLINGTON^ON^98111|||19601||||||||THOMAS^JAMES^M|F|||||||||||||||||||ZKA535529776

ADT^A04 Message

MSH|^~\&||.|||199908180016||ADT^A03|ADT.1.1698593|P|2.5
PID|1||000395122||GUTIERREZ^TYLER^T^^^||19880517180606|M|^^^^^||6 66TH AVE NE^^WEIMAR^DL^98052||(157)983-3296|||S||12354768|87654321
NK1|1|GUTIERREZ^JOHN^C|GRANDFATHER|12914 SPEM ST^^ALIUM^IN^98052|(157)883-6176
PV1|1|E|EMG-W^^|1||||||||||ER||||ER||H|||||||||||||||||||OVL||REG|||199908180015

ADT^A03 Message

In your application, you always want the ADT^A04 messages to be identified and parsed first using its specific grammar. Since both message types contain ADT in their identities, the ADT^A04 message must be the first matching message; otherwise, all your messages will be parsed using the ADT message grammar.

By specifying the matching order of your message definitions, you can ensure that ADT^A04 messages are always identified and parsed first in your application.

iNTERFACEWARE™ Inc.

Sample Scenario