iNTERFACEWARE Products Manual > Installing and Using Iguana > Using Iguana > Working With the Logs > Viewing the Logs > Viewing Log Message Details > Viewing Table Data Generated From a Message |
|
Looking for Iguana v.5 or v.6? Learn More or see the Help Center.
If an HL7 message has been logged for a channel that has To Database as its destination component, you can parse the message and examine the database table entries that have been generated for it. These table entries can be displayed in graphical or text format. To view table data generated from an HL7 message:
When you select this view mode, Iguana uses the VMD file that you defined when you configured the To Database component of the channel to parse the message and determine which message definition was matched. The left panel of the Logs screen displays this matched message definition, along with the table grammar for the message definition. In this example, the message definition is named PatientObservationMsg, and its table grammar consists of two tables, Patient and PatientObservation. To view the data generated for a table, click its name. The data is then displayed in the right panel of the Logs screen. If more than one row of table data has been generated from a message, you can view the row location of a specific row. To view this information, click a Row Location link. For example: In the example shown above, the second Row Location link has been clicked. The Grammar Information window indicates that this line of data is the second PatientObservation table row generated from the message.
When you have finished viewing the table data, click Close to revert to displaying the list of log messages. You can also parse any message sent through a channel if another channel uses this channel as a source and has To Database as its destination component. For example, suppose that an image is sent through a channel named inputrecord. Now, suppose that a channel named outputrecord is created, with To Database as its destination component and From Channel as its source component. If outputrecord's source channel is inputrecord, you will be able to use the database table specified in outputrecord to parse the message sent through inputrecord: Now, suppose that two channels named outputrecord1 and outputrecord2 are created. Each specifies To Database as its destination component and From Channel as its source component, and each specifies inputrecord as its source channel. In this case, when you display a message sent through inputrecord and parse the message, a list box appears enabling you to select which output channel's data tables you want to use when parsing: |