Development of a Visual Editor for the Definition of HL7 CDA Archetypes

Uploaded on

This paper describes the design and implementation of a clinical-oriented tool for the definition of HL7 CDA templates based on the archetype methodology proposed by CEN/ISO 13606 and openEHR. The use …

This paper describes the design and implementation of a clinical-oriented tool for the definition of HL7 CDA templates based on the archetype methodology proposed by CEN/ISO 13606 and openEHR. The use of archetypes together with HL7 CDA brings along new possibilities for clinical model definitions based on CDA. It allows taking profit of the formal nature of archetypes as well as their ability of binding medical knowledge and technical requirements into the same artefact. To achieve this objective, LinkEHR archetype editor has been adapted to support and facilitate the use of the HL7 CDA reference model by clinical users. This paper shows the problems faced and the solutions that have been developed in order to implement a tool that can ease the way HL7 CDA templates are currently defined.

D. Moner, J. A. Maldonado, D. Boscá, A. Mañas, and M. Robles, “Development of a Visual Editor for the Definition of HL7 CDA Archetypes,” in Proceedings of the XIII Mediterranean Conference on Medical and Biological Engineering and Computing 2013, IFMBE Volume 41, 2014, pp. 1258–1261.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. Development of a Visual Editor for the Definition of HL7 CDA Archetypes David Moner, José Alberto Maldonado, Diego Boscá, Alejandro Mañas and Montserrat Robles Grupo de Informática Biomédica, Instituto Universitario ITACA, Universitat Politècnica de València, Spain
  • 2. Introduction HL7 and archetypes in the same sentence? The fight begins? No! We are looking for collaboration, rather than confrontation 2
  • 3. Introduction • Two main standards for EHR data representation in the arena: HL7 CDA is a widely adopted standard for the representation of clinical documents. Templates are a mechanism to define specific schemas or document profiles. It gives instructions for the creation of specific CDA instances. Templates, in the form of implementation guides, are not directly computable, but oriented to human interpretation. ISO EN 13606 is a standard for the semantic interoperability of EHR information. Archetypes are a mechanism for the definition of EHR data structures and their meaning. It gives instructions for the creation of specific ISO EN 13606 instances. Archetypes are based on a computable formal model that can be also used with any other standard. 3 HL7 CDA ISO EN 13606
  • 4. Introduction • The use of archetypes together with HL7 CDA can resolve several weaknesses of the template approach: – To provide a formal framework for the definition of clinical models. – To improve the reuse and governance of those models by taking profit of the specialization and aggregation possibilities of archetypes. – To facilitate the direct involvement of health professionals in the archetype definition process. – To provide a more powerful and expressive definition of the semantics (terminology bindings) and data constraints that define the clinical information model. 4 The main objective of the work was to develop technology and tools to use the archetype methodology as an HL7 CDA template definition format.
  • 5. Methods • A reference model provides the pieces and basic structure to represent any clinical data and its context information (dates, authorship, etc.). 5 • A dual model architecture separates the representation of data structures from their formal definitions. ISO EN 13606HL7 CDA openEHR • An archetype represents the instructions about how to combine those pieces into a data structure schema that also has a clinical defined meaning (e.g. a discharge report or a medication instruction).
  • 6. Methods • LinkEHR Editor is a reference model-independent archetype editor developed by the IBIME group. – It can be used for the definition of archetypes based on any reference model that has been previously imported into the tool. – Additionally to this generic interface, specific and clinical-oriented interfaces can be developed to ease the use of the tool by archetype designers. – It has been already used with ISO EN13606, openEHR, Hl7 CDA, CDISC ODM, ASTM CCR and MML (Japanese standard) 6
  • 7. Results • HL7 reference model XML Schema was imported into LinkEHR • Some problems faced: – XML-oriented vs. Object-oriented methodologies (mixed nodes and choices of mandatory elements) – Preservation of namespaces 7
  • 8. Results • A specific HL7 CDA interface was implemented – Hides the technical HL7 CDA structures and classes that do not add clinical value to the user. – There exists a visualization option to Access to the technical view at any time. 8
  • 9. Results • Forms have been created to simplify the definition od constraints on HL7 CDA attributes. – These forms are associated to each node of the archetype tree. 9
  • 10. Results • HL7 CDA internal terminologies and LOINC codes have been included into the tool to ease access to them. 10
  • 11. Conclusions Constrained node Number of steps (generic editor) Number of steps (simplified editor) Section 16 4 CustodianOrganization 11 6 LabeledDrug 36 10 11 Interactions needed to create a node constraint • A method for measuring the simplification of the modelling process is by analyzing the number of steps or interactions needed to define a constraint.
  • 12. Conclusions • LinkEHR Editor has been used to implement the HL7 CDA template of the Genetic Test Report (GTR) – a 107 pages document. – 4 CDA archetypes were implemented following the indications of the GTR guide: Genetic report, Cytogenetics, Genetic variation and Test result information. – Over 50 different data items (archetype nodes) were defined and constrained, adding the name of the node, its textual description, terminology binding, occurrences, templateId and data type selection. 12 Archetypes can represent faithfully all constraints defined in a CDA template
  • 13. David Moner Cano Grupo de Informática Biomédica (IBIME) Instituto ITACA, Universitat Politècnica de Valencia, Spain Thank you for your attention! Questions?