EN 13606-2:2007

Foreword
0 Introduction
  0.1 Archetypes
  0.2 Archetype Repositories
  0.3 Communicating Archetypes
  0.4 Overview of the Archetype Model
  0.5 Overview of ADL
  0.6 Clinical examples of archetypes
1 Scope
2 Conformance
3 Normative references
4 Terms and definitions
5 Symbols and abbreviations
6 Archetype Representation Requirements
  6.1 General
  6.2 Archetype definition, description and publication
       information
  6.3 Archetype node constraints
  6.4 Data Value constraints
  6.5 Profile in relation to EN 13606-1 Reference Model
7 Archetype Model
  7.1 Introduction
  7.2 Overview
  7.3 The Archetype Package
  7.4 The Archetype Description Package
  7.5 The Constraint Model Package
  7.6 The Assertion Package
  7.7 The Primitive Package
  7.8 The Ontology Package
  7.9 The Domain Extensions Package
  7.10 The Support Package
  7.11 Generic Types Package
  7.12 Domain-specific Extensions (Informative)
8 Archetype Definition Language (ADL)
  8.1 dADL - Data ADL
  8.2 cADL - Constraint ADL
  8.3 Assertions
  8.4 ADL Paths
  8.5 ADL - Archetype Definition Language
Bibliography

This work item consists of the revision of the four part standard ENV 13606 to a full European standard (EN). This standard specifies the information architecture required for interoperable communications between systems and services that need or provide EHR data. This standard is not intended to specify the internal architecture or database design of such systems. The subject of the record or record extract to be communicated is an individual person, and the scope of the communication is predominantly with respect to that person’s care. Uses of healthcare records for other purposes such as administration, management, research and epidemiology, which require aggregations of individual people’s records, are not the focus of this standard but such secondary uses could also find the standard useful. Part 2 of this standard defines an Archetype Model to be used to represent Archetypes when communicated between repositories, and between archetype services. It defines an optional serialised representation, which may be used as an exchange format for communicating individual archetypes. Such communication might, for example, be between archetype libraries or between an archetype service and an EHR persistence or validation service.