Page tree
Skip to end of metadata
Go to start of metadata


The ART-DECOR tool for the eHDSI project is available:

Release overview

Latest Release (Wave 3 Release Candidate 2)

CDA IG 3.0.0-RC2


Release content can be found here

Release details here

Wave 2 Formal release

CDA IG 2.2.0


Release content can be found here

Release details here

Wave 1 Formal release

CDA IG 2.1.1


Release content can be found here

Release details here

Learn more about software implementation of CDAs and ART DECOR

Templates are context-specific constraints of the generic CDA model as defined in a CDA implementation guide for specific document type and one specific context (e.g. country or project).

Templates could express constraints on the class model itself, on the use of data types, on the values defined by coding systems, or they could be expressions of business rules.

One way to define Templates is as an electronic form supported by template design tools; in the case of the ART-DECOR Templates, they are based on the HL7 Templates DSTU (HL7 Templates Standard: Specification and Use of Reusable Information Constraint Templates Release 1).

The ART-DECOR tool has incorporated the DSTU, it allows the creation, editing, and management of Templates, as well as the creation of schematrons out of the definitions and the validation of instances. It can act as a registry and repository for Templates and accompanying value sets. IHE's testing and validating tool -Gazelle (ObjectsChecker)- can consume ART-DECOR Templates to  allow model driven validation of CDA instances.

To learn more go to:

Recommended reading is:

Historic reading:

CDA Interoperability levels

The CDA document is defined with three different levels of interoperability:

  • Level 1: Includes the CDA Header plus a body consisting of an unstructured blob, such as PDF, DOC, or even a scanned image.
  • Level 2: Includes the CDA Header plus an XML body with narrative blocks. Each section identified with a code.
  • Level 3: Includes the CDA Header plus an XML body with narrative blocks and entries. The section should be encoded with the full power of the RIM with vocabulary such as LOINC, SNOMED, CPT, etc.

For the CEF eHDSI Services -following epSOS and EXPAND Specifications- depending on the document type, any instance of eHDSI pivot CDA shall have a related CDA embedding the PDF representation of the original data from which the eHDSI pivot has been derived (also known as eHDSI PDF). The consumer of the eHDSI services shall be able to access this eHDSI PDF - if existing- any time it seems it is necessary for the document content representation. (SOURCE: epSOS Patient Summary, ePrescription, eDispensation and Common Modules HL7 CDA R2 - Implementation Guide, V1.1, 15-09-2015)

In eHDSI, Level 1 and Level 3 are supported

Following diagram provides an overview of the different layers in the creation process of the Patient Summary templates:

The eHN EU PS guidelines serve as a base for the eHDSI requirements (both business and solution requirements).

The eHDSI PS IGs are based on the eHDSI requirements and international standards like the IHE PCC (Patient Care Coordination) domain and the HL7 CCD (Coordination of Care Document).

eHDSI template stack

Templates (Level 3)
Patient SummaryepSOS-Patient Summary (ART-DECOR)
ePrescriptionepSOS-ePrescription (ART-DECOR)
eDispensationepSOS-eDispensation (ART-DECOR)
Templates for the documents containing the original PDF (Level 1)
Patient Summary: eHDSI-OriginalPSeHDSI-Patient Summary (PDF embedded)

ePrescription: eHDSI-Original-eP

eHDSI-ePrescription (PDF embedded)