Introduction

The following graph based on a slide from René Spronk (Ringholm bv), summarizes the CDA Validation options. 

1. We verify that the CDA is a well-formed XML Document. This corresponds to 1 on the graphic
2. We verify that the CDA document is valid against the CDA Schema  
3. If we have a template specific schema, then we use that one to check the validity of the CDA document.
4. From the CDA implementation guide (IHE technical framework, epSOS specs,...) some business rules are expressed into a schematron document that we use to validate the CDA document.

MIF : Model Interchange Format

René Spronk wrote an excellent white paper on MIF, we recommend its reading in order to better understand the concepts.  The definition extracted from that white paper states : "The Model Interchange Format (MIF) is a set of XML formats used to support the storage and exchange of HL7 version 3 artefacts as part of the HL7 Development Framework. It is the pre-publication format of HL7 v3 artefacts used by tooling. It is also the formal definition of the HL7 metamodel. The MIF can be transformed into derived forms such as UML/XMI or OWL."

CDA Validation

We use the tool H3ET writen by JivaMedical (http://www.jivamedical.com/hl7-v3/h3et-product-overview-2.html). The jar can be downloaded from page Eclipse Instance Editor at the following URL : 

• http://www.jivamedical.com/eclipse_update/InstanceValidator.jar