HL7Connect has support for validating both HL7 v2 Messages and CDA R2 documents. The following methods are supported for validation:

Method HL7 v2 Messages CDA Documents
Simple Yes Yes
Javascript / VBScript Yes Yes
OCL Yes Yes
XSLT Yes Yes
Schema Yes Yes
HL7 V2 Conformance Profile Yes
Eclipse OHF Yes

Simple Validation

This uses the inbuilt facilities of HL7Connect to validate the message or document. Usually the internal parsers run in a forgiving mode where they parse whatever can be parsed, and ignore any content they can ignore. In simple validation mode, the parsers report errors related to this unknown or incorrect content. Generally, if a message or document passes simple validation, it can be assumed that it's content is correct except for vocabulary.

Javascript / VBScript

This validation method uses the scripting infrastructure to execute a javascript or VBScript. Instead of an event, the message or document is passed directly as the parameter. The script can explore the documents as required, and use the kernel infrastructure as desired. If the script raises an exception, then the validation is considered to have failed with the error the script raises. If the script does not raise an exception, then the validation is assumed to pass.

OCL

The validation method takes as input a series of OCL constraints, and verifies that the constraints are met. For futher information, see OCL constraints for further information.

XSLT

The document (either an HL7 v2 message in v2.xml form or the CDA document directly) is passed to an XSLT script. If the transform creates an output message using xsl:message, then the validation is considered to have failed with that message. If the transform does not use xsl:message, then the validation is assumed to pass. Actual output from the transform is ignored. MSXML is used as the transform engine.

Schema

The document (either an HL7 v2 message in v2.xml form or the CDA document directly) is validated against the specified schema. MSXML is used as the transform engine. You can specify either the standard schema or you can provide you own custom schema.

Schema

The document (either an HL7 v2 message in v2.xml form or the CDA document directly) is validated against the specified schema. MSXML is used as the transform engine. You can specify either the standard schema or you can provide you own custom schema.

HL7 V2 Conformance Profile

V2 messages only: Validate against a HL7 v2 conformance profile as specified in chapter 2C of the v2 standard. The easiest way to prepare such conformance profiles is using the HL7 Message Workbench, though as of 2010 the future status of this program is not clear.

Eclipse OHF

CDA documents only: Use the Eclipse OHF CDA validator to validate a CDA document. The Eclipse OHF validator is included as part of HL7Connect. The Eclipse OHF validator provides the best validation of the data types (HL7Connect, The V3 data types, and the Eclipse OHF validator are all developed by the same author).

To Do

We plan to add support for validating CDA documents against the HL7 template registry, perhaps in association with Alschuler Associates.


© Kestral Computing P/L 2000-2010.
Keywords: Validation