You can play with an example of this scenario in the Getting Started section.
When you open a data file containing HL7 messages the file is analyzed and 1 of 3 things will happen.
1.HL7 messages are detected in the file, parsed, and loaded into your message store.
2.NO HL7 messages detected (for example the file actually contains a recipe for chicken soup).
3.And finally, #3 is where some HL7 messages are detected and parsed correctly but some are not. We call these 'Malformed' messages.
This section only applies to scenario #3. You will be prompted and asked if you want to view the errors and if you choose Yes you will be brought into the HL7 File Analysis Results window (shown below) with the first error automatically selected.
HL7 File Exceptions (Text View)
You can alternated between the Exception View [Raw Text] Tab (shown above) or the Hex View Tab (shown below). In the example shown above you can see that the top of the Exception View will show the error encountered. You can tell by looking at the text in the screenshot that something is obviously wrong with the PV1 Segment. It seems to suddenly break off into a new line before the segment data is completed. To verify we look at the Hex View (below)
HL7 File Exceptions (Hex View)
In the Hex View if we scroll down (using the plain text right column as a guide) to the place in the message where the error occurred we can see that, sure enough, there is a HEX value 0D (a carriage return and also the HL7 ANSI Standard Segment Delimiter) right in the middle of the PV1 Segment.
