EN 13606-3:2008
(Main)Health informatics - Electronic health record communication - Part 3: Reference archetypes and term lists
Health informatics - Electronic health record communication - Part 3: Reference archetypes and term lists
This Standard addresses the communication of part or all of electronic health records (EHR) of a single identified subject of care between EHR systems, or between EHR systems and a centralised EHR data repository. It may also be used for EHR communication between an EHR system or repository and clinical applications or middleware components (such as decision support components) that need to access or provide EHR data, or as the representation of EHR data within a distributed (federated) record system.
This Standard, Part 3 of the 13606 EHR Communications Standard Series, defines term lists that each specify the set of values that particular attributes of the Reference Model defined in Part 1 of this Series may take. It also defines informative Reference Archetypes that correspond to ENTRY-level compound data structures within the Reference Models of openEHR and HL7 Version 3, to enable those instances to be represented within a consistent structure when communicated using this standard.
Medizinische Informatik - Kommunikation von Patientendaten in elektronischer Form - Teil 3: Referenzarchetypen und Begriffslisten
Informatique de la santé - Communication des dossiers de santé informatisés - Partie 3: Archétypes de référence et listes de termes
La présente norme traite de la communication de tout ou partie du dossier informatisé de santé (DIS) d'un seul sujet de soins identifié entre systèmes de DIS, ou entre des systèmes de DIS et un réceptacle de données de DIS centralisé. Elle peut également être utilisée pour la communication de DIS entre un système ou réceptacle de DIS et des applications médicales ou composants intergiciels (tels que des composants d'aide à la décision) nécessitant d'avoir d'accès aux ou de fournir des données de DIS, ou en tant que représentation de données de DIS au sein d'un système de dossiers répartis (fédérés).
La présente norme, Partie 3 de la série de normes EN 13606 relatives à la communication des DIS, définit des listes de termes spécifiant chacune l’ensemble des valeurs pouvant être prises par les différents attributs du Modèle de référence défini dans la Partie 1 de cette série. Elle définit également, à titre informatif, des Archétypes de référence correspondant aux structures de données composites de niveau ENTRY dans les Modèles de référence de openEHR et HL7 Version 3, pour permettre la représentation de ces instances au sein d'une structure cohérente lorsqu'elles sont communiquées selon la présente norme.
Zdravstvena informatika - Komunikacija z elektronskimi zapisi v zdravstvenem varstvu - 3. del: Referenčni arhetipi in seznami izrazov
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 3: Reference archetypes and term listsGUDYVWYHQHPInformatique de la santé - Communication des dossiers de santé informatisés - Partie 3: Archétypes de référence et listes de termesMedizinische Informatik - Kommunikation von Patientendaten in elektronischer Form - Teil 3: Referenzarchetypen und Begriffslisten35.240.80Uporabniške rešitve IT v zdravstveni tehnikiIT applications in health care technologyICS:SIST EN 13606-3:2008enTa slovenski standard je istoveten z:EN 13606-3:200801-junij-2008SIST EN 13606-3:2008SLOVENSKI
STANDARDSIST ENV 13606-3:20031DGRPHãþD
EUROPEAN STANDARDNORME EUROPÉENNEEUROPÄISCHE NORMEN 13606-3March 2008ICS 35.240.80Supersedes ENV 13606-3:2000
English VersionHealth informatics - Electronic health record communication -Part 3: Reference archetypes and term listsInformatique de la santé - Communication des dossiers desanté informatisés - Partie 3: Archétypes de référence etlistes de termesMedizinische Informatik - Kommunikation vonPatientendaten in elektronischer Form - Teil 3:Referenzarchetypen und BegriffslistenThis European Standard was approved by CEN on 28 February 2008.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© 2008 CENAll rights of exploitation in any form and by any means reservedworldwide for CEN national Members.Ref. No. EN 13606-3:2008: E
Reference archetypes.20 A.1 Introduction to the openEHR and HL7 mapping archetypes.20 A.2 openEHR ENTRY archetypes.21 A.2.1 Introduction.21 A.2.2 openEHR ENTRY.23 A.2.3 openEHR Evaluation.24 A.2.4 openEHR Observation.25 A.2.5 openEHR Instruction.26 A.2.6 openEHR Action.27 A.3 HL7 Version 3 entry archetypes.28 A.3.1 Introduction.28 A.3.2 HL7 Observation Act.28 A.3.3 HL7 Procedure Act.30 A.3.4 HL7 Substance Administration Act.31 A.3.5 HL7 Supply Act.32 A.3.6 HL7 Act.33 A.3.7 HL7 Encounter Act.34 A.4 Code set for RECORD_COMPONENT.meaning attribute.35 Annex B (informative)
Clinical example of the mapping between HL7 v3 and ISO 13606.37 B.1 Introduction.37 B.2 HL7 v3 representation of the Barthel Index.37 B.3 Table of correspondence between HL7 v3 and ISO 13606 for the Barthel Index.38
o set of HL7 version 3 Acts that form part of the Clinical Statement Domain Message Information Model; o specialisations of ENTRY that are defined in the openEHR Reference Model. 0.2 Term Lists Each term list is referenced by its corresponding attribute as an invariant constraint in Part 1 of this standard series, by referring to its term list name. For each term list, every code value is accompanied by a phrase and description; however, in each case it is the code that is to be used as the Reference Model attribute value. Language translations of the phrase and description will therefore not affect the instances of RECORD_COMPONENT that are communicated using this standard.
Should any future revision prove necessary for these term lists, a technical revision of this standard will be required. Such a revised standard shall specify an updated Reference Model identifier that shall then be used as the value of the rm_id of an EHR_EXTRACT, to inform the recipient of the version of this standard that was used in its creation.
A cross-mapping of the term list for LINK.role to HL7 actRelationship codes is also provided for the convenience of those wishing to adopt or interface this standard with HL7 version 3. This is part of a longer-term vocabulary harmonisation project between the health informatics standards development organizations (SDO’s), and might therefore be extended in the future via other publications, such as the planned HL7-13606 Implementation Guide (see below). It is therefore informative in this standard. 0.3 Reference Archetypes Each Reference Archetype is represented in this standard as a mapping correspondence table to indicate the way in which the ITEM structure within a 13606 Part 1 ENTRY is to be used to represent the classes and attributes of relevant HL7 v3 and openEHR classes. These two external models have been chosen for inclusion as these are the most likely internationally-used source models from which fine-grained clinical data may need to be transformed into this standard for communication. These Reference Archetypes are included as an aid to those adopting this standard and wishing to transform Electronic Health Record (her) data from existing HL7 v3 or openEHR instances or messages. It is recognised that full two-way interoperability between these various representations requires more detail, including rich vocabulary and data type harmonisation, and a corresponding set of technical artefacts such as eXtensible Markup Language (XML) Schemata and Extensible Stylesheet Language Transformation (XSLT) scripts. Such interoperability is very much the goal of current SDO harmonisation efforts, and will be published as an HL7-13606 Implementation Guide, possibly as an open-access and regularly updated resource. However, the outstanding work required to achieve this level of interoperability might take up to another year from when this standard is expected to be published. It has therefore been decided to offer what does exist towards harmonisation in an informative form within this standard, as an aid to those already needing to make such data transformations. A worked example of the HL7 v3 to ISO 13606 mapping is given in Annex B.
This Standard, Part 3 of the 13606 EHR Communications Standard Series, defines term lists that each specify the set of values that particular attributes of the Reference Model defined in Part 1 of this Series may take. It also defines informative Reference Archetypes that correspond to ENTRY-level compound data structures within the Reference Models of openEHR and HL7 Version 3, to enable those instances to be represented within a consistent structure when communicated using this standard. 2 Terms and definitions For the purposes of this document, the following terms and definitions apply. 3.1 archetype instance individual metadata class instance of an Archetype Model, specifying the clinical concept and the value
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.