EN 13606-2:2007
(Main)Health informatics - Electronic health record communication - Part 2: Archetypes interchange specification
Health informatics - Electronic health record communication - Part 2: Archetypes interchange specification
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.
Medizinische Informatik - Kommunikation von Patientendaten in elektronischer Form - Teil 2: Spezifikation für den Austausch von Archetypen
Le présent document constitue une révision de la prénorme ENV 13606 en quatre parties en vue d'établir une Norme européenne de plein statut (EN).
La présente norme spécifie l'architecture d'informations nécessaire aux communications interopérables entre des systèmes et des services utilisant ou fournissant des données de DIS. Elle n'a pas pour objet de spécifier l'architecture interne ou la conception des bases de données de tels systèmes.
Le sujet du dossier ou de l'extrait de dossier à communiquer est une personne individuelle et le domaine d'application de la communication porte principalement sur les soins qui lui sont apportés.
L'utilisation des dossiers de santé à d'autres fins (comme l'administration, la gestion, la recherche et l'épidémiologie, par exemple), qui nécessitent un regroupement (une agrégation) des dossiers de personnes individuelles, ne constituent pas le sujet central de la présente norme bien que celle-ci puisse s'avérer utile à de tels usages secondaires.
La partie 2 de la présente norme définit un modèle d'archétype à utiliser pour représenter les archétypes lorsqu'ils sont communiqués entre référentiels et entre services d'archétypes. Elle définit une représentation sérialisée facultative, qui peut être utilisée comme format d'échange pour la communication d'archétypes individuels. Ce type de communication peut, par exemple, survenir entre des bibliothèques d'archétypes ou un service d'archétypes et un service de conservation de DIS ou un service de validation.
Informatique de la santé - Communication des dossiers de santé informatisés - Partie 2 : Spécification d'échange d'archétypes
Zdravstvena informatika - Komunikacija z elektronskimi zapisi v zdravstvenem varstvu - 2. del: Arhetipi
General Information
Relations
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Health informatics - Electronic health record communication - Part 2: Archetypes interchange specificationZdravstvena informatika - Komunikacija z elektronskimi zapisi v zdravstvenem varstvu - 2. del: ArhetipiInformatique de santé - Dossier de santé informatisé communicant - Spécification des échanges des archétypesMedizinische Informatik - Kommunikation von Patientendaten in elektronischer Form - Teil 2: ArchetypenTa slovenski standard je istoveten z:EN 13606-2:2007SIST EN 13606-2:2008en35.240.80Uporabniške rešitve IT v zdravstveni tehnikiIT applications in health care technologyICS:SIST ENV 13606-2:20031DGRPHãþDSLOVENSKI
STANDARDSIST EN 13606-2:200801-februar-2008
EUROPEAN STANDARDNORME EUROPÉENNEEUROPÄISCHE NORMEN 13606-2August 2007ICS 35.240.80 English VersionHealth informatics - Electronic health record communication -Part 2: Archetypes interchange specificationInformatique de santé - Dossier de santé informatisécommunicant - Spécification des échanges des archétypesMedizinische Informatik - Kommunikation vonPatientendaten in elektronischer Form - Teil 2:Spezifikation für den Austausch von ArchetypenThis European Standard was approved by CEN on 21 June 2007.CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this EuropeanStandard the status of a national standard without any alteration. Up-to-date lists and bibliographical references concerning such nationalstandards may be obtained on application to the CEN Management Centre or to any CEN member.This European Standard exists in three official versions (English, French, German). A version in any other language made by translationunder the responsibility of a CEN member into its own language and notified to the CEN Management Centre has the same status as theofficial versions.CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Cyprus, Czech Republic, Denmark, Estonia, Finland,France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal,Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom.EUROPEAN COMMITTEE FOR STANDARDIZATIONCOMITÉ EUROPÉEN DE NORMALISATIONEUROPÄISCHES KOMITEE FÜR NORMUNGManagement Centre: rue de Stassart, 36
B-1050 Brussels© 2007 CENAll rights of exploitation in any form and by any means reservedworldwide for CEN national Members.Ref. No. EN 13606-2:2007: E
Figures Figure 1 — ADL Archetype Structure.14 Figure 2 — Package structure.28 Figure 3 — Overview of the main part of the Archetype Model – Part 1.29 Figure 4 — Overview of the Archetype Model - Part 2.30 Figure 5 — Archetype Package.33 Figure 6 — Archetype Description Package.35 Figure 7 — Constraint Model Package.39 Figure 8 — Assertion Package.46 Figure 9 — Primitive Package.50 Figure 10 — Ontology Package.56 Figure 11 — Domain Extensions Package.58 Figure 12 — Support Package.60 Figure 13 — Generic Types Package.69 Figure 14 — Example Domain-specific package.70
This document will supersede ENV 13606-2:2000. This multipart standard under the general heading Health informatics – Electronic health record communication consists of the following parts: Part 1: Reference model Part 2: Archetypes interchange specification Part 3: Reference archetypes and term lists Part 4: Security Part 5: Exchange models According to the CEN/CENELEC Internal Regulations, the national standards organizations of the following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom. 4
This requires that EHR data from diverse systems be capable of being mapped to and from a single comprehensive representation, which is used to underpin interfaces and messages within a distributed network (federation) of EHR systems and services. This common representation has to be sufficiently generic and rich to represent any conceivable health record data, comprising part or all of an EHR (or a set of EHRs) being communicated.
The approach adopted in this standard, underpinned by international research on the EHR, has been to define a rigorous and generic Reference Model that is suitable for all kinds of data and data structures within an EHR, and in which all labelling and context information is an integral part of each construct. An EHR Extract will contain all of the names, structure and context required for it to be interpreted faithfully on receipt even if its organisation and the nature of the clinical content have not been “agreed” in advance.
However the wide-scale sharing of health records, and their meaningful analysis across distributed sites, also requires that a consistent approach is used for the clinical (semantic) data structures that will be communicated via the Reference Model, so that equivalent clinical information is represented consistently. This is necessary in order for clinical applications and analysis tools safely to process EHR data that have come from heterogeneous sources.
0.1 Archetypes The challenge for EHR interoperability is therefore to devise a generalised approach to representing every conceivable kind of health record data structure in a consistent way. This needs to cater for records arising from any profession, speciality or service, whilst recognising that the clinical data sets, value sets, templates etc. required by different health care domains will be diverse, complex and will change frequently as clinical practice and medical knowledge advance. This requirement is part of the widely acknowledged health informatics challenge of semantic interoperability. The approach adopted by this standard distinguishes a Reference Model, used to represent the generic properties of health record information, and Archetypes (conforming to an Archetype Model), which are meta-data used to define patterns for the specific characteristics of the clinical data that represent the requirements of each particular profession, speciality or service. The Reference Model is specified as an ODP Information Viewpoint model, representing the global characteristics of health record components, how they are aggregated, and the context information required to meet ethical, legal and provenance requirements. In this standard, the Reference Model is defined in Part 1. This model defines the set of classes that form the generic building blocks of the EHR. It reflects the stable characteristics of an electronic health record, and would be embedded in a distributed (federated) EHR environment as specific messages or interfaces (as specified in Part 5 of this standard). Archet
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.