Select one of the first three entries to indicate whether the Message Analyzer will perform that type of validation. If a menu line ends with "[ ]", the item will not be used in validation. If a menu line ends with "[X]", the item will be used in validation. When you have selected one or more entries, enter 4 to start validation.
Field validation checks whether the segments in the messages conform to segment definitions in the specified document structure. Component validation checks whether the data structures in the messages conform to the data structure definitions in the document structure. Code table validation checks whether the code tables in the messages match the code tables in the document structure.
Fixing the Custom Schema
After validation, the Message Analyzer prompts you whether you want to make the possible fixes it has identified. If there is more than one possible fix, you are prompted to drill down to individually choose which fixes you want to make. When you choose a fix, it is not executed immediately, but rather is added to a queue. When you are done selecting fixes, you are prompted whether you want to accept all the fixes in the queue.
If you want to accept a subset of the possible fixes, use the prompts to identify the fixes you want to make, then enter ^ until you are prompted to apply the fixes.
Selecting a Category of Fixes
If you ran more than one type of validation (field, component, and code table), it is possible that the Message Analyzer found potential fixes for more than one category. In this case, you are prompted to specify what type of fixes you want to make. If the Message Analyzer found possible fixes in only one category (segment, data structure, or code table), this prompt is skipped.
Select a category of fixes to process
 70 code table(s)
 7 data structure(s)
 28 segment structure(s)
Enter one of the above options, ^ to go back a level:
Selecting a Structure, Segment, or Table
If there are possible fixes for multiple segments, data structures or code tables, you are prompted to select which fix you want to make. Once you select one of the fixes, it is removed from the list and you can select another fix. If you are done selecting fixes and do not want to accept them all, enter ^ until you are prompted to accept the fixes.
For example, suppose there are fixes for more than one data structure. You might see a prompt like:
Select a data structure to process
 2.4:CE coded element (1)
 2.4:HD hierarchic designator (1)
 2.4:ID coded value for HL7 defined tables (1)
 2.4:IS coded value for user-defined tables (1)
 2.4:MSG Message Type (1)
 2.4:PL person location (1)
 2.4:ST string data (1)
Enter one of the above options, ^ to go back a level:
Adding Fixes to the Queue
In most cases, each time you select a segment, data structure or code table, you are prompted whether you want to accept the fix. When you enter Y, the fix is not applied immediately; it is added to a queue of fixes that will be applied when you give a final confirmation. If there is more than one fix to the same code table, segment, or data structure, you are prompted to select which fix you want to make before adding it to the queue.
Making the Fixes
When you have added all the possible fixes to the queue or have indicated you are done adding fixes by using ^, you are prompted whether you want to apply the queued fixes to the custom schema. Items that are not already in the custom schema will be copied from the built-in library schema before the changes are made.
For example, you might be prompted to apply the following queue of changes to the custom schema:
Items queued for fixes to HL7 configuration:
*Do you want to add code 'Z' to code table 2.4:1 (Administrative sex)
*Do you want to add code 'EC' to code table 2.4:131 (!Copied from 2.5 - Contact Role)
*Do you want to add 3 dummy components to data structure 2.4:CE (coded element)
*Do you want to add 1 dummy components to data structure 2.4:IS (coded value for user-defined tables)
*Do you want to increase the maximum size for field 2 (EncodingCharacters) in segment structure 2.4:MSH (Message Header) from 4 to 5
*Do you want to make field 7 (DateTimeOfMessage) in segment structure 2.4:MSH (Message Header) optional
Fixes marked with a '*' apply to library items, which cannot be updated directly
Do you want to apply these fixes? (Y/N):
Understanding the Changes
Before the relevant fix can be made (for example, adding a new code to a code table), the Message Analyzer might need to:
Copy items (for example, code tables) to the custom schema.
Update custom items to reference other custom items instead of the library items they formerly referenced.
These changes are detailed in the update report which follows your confirmation that the fixes should be applied. Each copy, reference-update or principal change is detailed on its own line.
Lines beginning with Path: summarize updates to document structures, segment structures, data structures and code tables. In such a line, a + means that the item was copied to the custom schema; a * means that the given reference was updated.
For example, a path of ORU_R01 --> PID -*-> XTN+ -*-> 202+ means:
custom document structure ORU_R01
custom segment PID: reference to XTN was updated
data structure XTN: copied to custom schema, reference to 202 was updated
code table 202: copied to custom schema
The path does not describe the principal update target identified by the validation - in the example above this would be the adding of a code to the code table.