Looking for Iguana v.5 or v.6? Learn More or see the Help Center.
Full Tree Validation Errors |
Full Tree Validation Errors are only thrown when you enable the Validate Data for XML -> HL7 option and translate a message from XML to HL7. A XML to HL7 translation can be performed when:
- Clicking Translate in the XML Translation window.
- Using the translateXmlToMessage API call.
The following table provides brief descriptions of the Full Tree Validation errors:
| Error Code | Error Type | Description |
|---|---|---|
| XML00001 | General error | Typically this will be any error that is not covered by any other error code. |
| XML00002 | Invalid XML error | This error occurs when the XML is not well-formed. |
| XML00003 | Undefined HL7 message | This error occurs when the XML provides the name of a message that is not defined in the VMD file. |
| XML00004 | Unexpected data or element was found | This error occurs when Chameleon finds an unexpected tag, or when it finds an unexpected element when it is expecting a single contiguous string. If applicable, the line number is the parent group that is missing the segment or group. |
| XML00005 | Required segment or group is missing | This error occurs when a required group or segment is missing from the XML. |
| XML00006 | Number of repeats exceeded | This error occurs when a segment or group exceeded the number of allowed repetitions. The line number is the first segment or group that caused the error. |
| XML00007 | Segment error caused by Strict Grammar Checking | This error occurs when the strict grammar checking option is enabled. When Strict Grammar Checking is on, Chameleon will reject messages that do not have compulsory fields present in their segments. The line number is the field/subfield/sub-subfield that caused the error. |