A testable rule to which HL7 messages (at least certain specific message) should conform. This is the central interface of the new HAPI validation model (as of HAPI 0.4). Previously, the only run-time message validation HAPI performs is within the setValue() methods of the Primitive datatype classes. For example when you called setValue() on a DT an exception was thrown if the String arg was not in the correct DT format. This method served well initially but left us with the following limitations:
- Sometimes validation is inappropriate (e.g. some of the standard rules, like phone number format, don't make sense in some regions).
- Couldn't add further optional constraints (such as all timestamps must have a time zone).
- Couldn't turn off validation to improve performance.
- Other forms of validation (e.g. conformance profiles, standard DTDs) were not covered.
Thus the new validation model is broader in scope, and is based on validation rules implemented as Rule objects, which can be configured to run or not, as needed, depending on run-time configuration.
There are three kinds of rules:
- PrimitiveTypeRule: Called when the values of simple datatypes are set, like the existing hard-coded datatype validations (e.g. TNFollowsNorthAmericanFormat).
- MessageRule: Called when complete message content is to be checked on a parsed message (e.g. conformance profile).
- EncodingRule: Applied to an encoded message (e.g. validation against a 2.xml Schema, a rule that prohibits empty tags, etc.).
@author Bryan Tripp