EN 13606-3-2008 en Health informatics - Electronic health record communication - Part 3 Reference archetypes and term lists《健康信息学 电子健康记录通信 第3部分 参考原型和术语表》.pdf

《EN 13606-3-2008 en Health informatics - Electronic health record communication - Part 3 Reference archetypes and term lists《健康信息学 电子健康记录通信 第3部分 参考原型和术语表》.pdf》由会员分享，可在线阅读，更多相关《EN 13606-3-2008 en Health informatics - Electronic health record communication - Part 3 Reference archetypes and term lists《健康信息学 电子健康记录通信 第3部分 参考原型和术语表》.pdf（50页珍藏版）》请在麦多课文档分享上搜索。

1、BRITISH STANDARDBS EN 13606-3:2008Health informatics Electronic health record communication Part 3: Reference archetypes and term listsICS 35.240.80g49g50g3g38g50g51g60g44g49g42g3g58g44g55g43g50g56g55g3g37g54g44g3g51g40g53g48g44g54g54g44g50g49g3g40g59g38g40g51g55g3g36g54g3g51g40g53g48g44g55g55g40g39

2、g3g37g60g3g38g50g51g60g53g44g42g43g55g3g47g36g58BS EN 13606-3:2008This British Standard was published under the authority of the Standards Policy and Strategy Committee on 31 July 2008 BSI 2008ISBN 978 0 580 57889 2National forewordThis British Standard is the UK implementation of EN 13606-3:2008. I

3、t supersedes DD ENV 13606-3:2000 which is withdrawn. The UK participation in its preparation was entrusted to Technical Committee IST/35, Health informatics.A list of organizations represented on this committee can be obtained on request to its secretary.This publication does not purport to include

4、all the necessary provisions of a contract. Users are responsible for its correct application.Compliance with a British Standard cannot confer immunity from legal obligations.Amendments/corrigenda issued since publicationDate CommentsEUROPEAN STANDARDNORME EUROPENNEEUROPISCHE NORMEN 13606-3March 200

5、8ICS 35.240.80 Supersedes 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 informatiss - Partie 3: Archtypes de rfrence etlistes de termesMedizinische In

6、formatik - 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 Euro

7、peanStandard 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,

8、 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, Cypru

9、s, 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 E

10、UROPEN DE NORMALISATIONEUROPISCHES KOMITEE FR NORMUNGManagement Centre: rue de Stassart, 36 B-1050 Brussels 2008 CEN All rights of exploitation in any form and by any means reservedworldwide for CEN national Members.Ref. No. EN 13606-3:2008: EEN 13606-3:2008 (E) 2 Contents Page Foreword3 Introductio

11、n .4 0.1 Summary.4 0.2 Term Lists.4 0.3 Reference Archetypes.4 1 Scope 5 2 Terms and definitions .5 3 Abbreviations.6 4 Conformance6 5 Term lists 7 5.1 Introduction7 5.2 Termlist SUBJECT_CATEGORY, Class ENTRY, attribute subject_of_information_category.7 5.3 Termlist ITEM_CATEGORY, Class ITEM, attrib

12、ute item_category .8 5.4 Termlist VERSION_STATUS, Class AUDIT_INFO, attribute version_status9 5.5 Termlist MODE, Class FUNCTIONAL_ROLE, attribute mode10 5.6 Termlist ACT_STATUS, Class ENTRY, attribute act_status11 5.7 Termlist LINK_NATURE, Class LINK, attribute nature.12 5.8 Termlist LINK_ROLE, Opti

13、onal term list for LINK attribute role (Informative) 13 5.8.1 Introduction13 5.8.2 Optional term list for LINK attribute role (Informative)13 5.8.3 Mapping of extended term list to ENV13606-2 categories of Link (Informative).16 5.8.4 Mapping of extended term list to HL7 act.Relationship codes (Infor

14、mative) 17 5.9 Termlist STRUCTURE_TYPE, Class CLUSTER, attribute structure_type19 Annex A (informative) Reference archetypes.20 A.1 Introduction to the openEHR and HL7 mapping archetypes 20 A.2 openEHR ENTRY archetypes .21 A.2.1 Introduction21 A.2.2 openEHR ENTRY23 A.2.3 openEHR Evaluation .24 A.2.4

15、 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 Introduction28 A.3.2 HL7 Observation Act .28 A.3.3 HL7 Procedure Act.30 A.3.4 HL7 Substance Administration Act31 A.3.5 HL7 Supply Act 32 A.3.6 HL7 Act .33 A.3.7 HL7 Encounter Act

16、.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 Introduction37 B.2 HL7 v3 representation of the Barthel Index 37 B.3 Table of correspondence between HL7 v3 and ISO 13606 for the Barthel Index38 BS E

17、N 13606-3:2008EN 13606-3:2008 (E) 3 Foreword This document (EN 13606-3:2008) has been prepared by Technical Committee CEN/TC 251 “Health informatics”, the secretariat of which is held by NEN. This European Standard shall be given the status of a national standard, either by publication of an identic

18、al text or by endorsement, at the latest by September 2008, and conflicting national standards shall be withdrawn at the latest by September 2008. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. CEN and/or CENELEC shall not be hel

19、d responsible for identifying any or all such patent rights. This document supersedes ENV 13606-3:2000. 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

20、, 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 the United Kingdom. BS EN 13606-3:2008EN 13606-3:2008 (E) 4

21、 Introduction 0.1 Summary Part 3 of the 13606 standards series contains two kinds of specifications: 1 normative set of (coded) term lists that each defines a controlled vocabulary for a Reference Model attribute that is defined in Part 1 of this standard series; 2 informative set of Reference Arche

22、types: expressed as mappings that each specifies how the Part 1 Reference Model should be used to represent information originating from: 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

23、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 t

24、he 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 r

25、evision 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 te

26、rm 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 (SDOs), a

27、nd 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 in

28、dicate 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 fin

29、e-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 recogni

30、sed 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

31、 (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 m

32、ight 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 HL

33、7 v3 to ISO 13606 mapping is given in Annex B. BS EN 13606-3:2008EN 13606-3:2008 (E) 5 1 Scope 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 rep

34、ository. 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

35、. 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

36、 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

37、.1 archetype instance individual metadata class instance of an Archetype Model, specifying the clinical concept and the value constraints that apply to one class of Record Component instances in an electronic health record extract 3.2 clinical information information about a person, relevant to his

38、or her health or health care 3.3 committed information that has been persisted within an electronic health record system and which constitutes part of the electronic health record for a subject of care 3.4 committer agent (party, device or software) whose direct actions have resulted in data being c

39、ommitted to an electronic health record 3.5 composer agent (party, device or software) responsible for creating, synthesising or organising information that is committed to an electronic health record 3.6 electronic health record extract part or all of the electronic health record for a subject of c

40、are, communicated in compliance with EN 13606 3.7 electronic health record system system for recording, retrieving and manipulating information in electronic health records 3.8 entries health record data in general (clinical observations, statements, reasoning, intentions, plans or actions) without

41、particular specification of their formal representation, hierarchical organisation or of the particular Record Component class(es) that might be used to represent them 3.9 patient synonym for a subject of care BS EN 13606-3:2008EN 13606-3:2008 (E) 6 3.10 Record Component part of the electronic healt

42、h record extract of a single subject of care, represented as a node within a hierarchical data structure conforming to EN 13606 3.11 state (of a process) condition or situation during the lifecycle of an object during which it satisfies some condition, performs some activity or waits for some event

43、ISO/TS 18308:2004 3.12 subject of care person scheduled to receive, receiving, or having received health care 3 Abbreviations CEN Comit Europen de Normalisation (European Committee for Standardization) CEN/ TC 251 CEN Technical Committee 251 EHR Electronic Health Record EU European Union HISA Health

44、 Information Systems Architecture HL7 Health Level Seven ISO International Organization for Standardization UML Unified Modelling Language XML Extensible Mark-up Language 4 Conformance When electronic health record information is to be communicated using the 13606 Standard Series and where an attrib

45、ute of the Reference Model defined in Part 1 of this series requires a value to be taken from a bounded set of codes from a named term list, the code shall be one of those defined in Clause 5 of this standard for the correspondingly-named term list. BS EN 13606-3:2008EN 13606-3:2008 (E) 7 5 Term lis

46、ts 5.1 Introduction The Reference Model defined in Part 1 of this standard series defines several attributes whose values are to be selected from a fixed list of values. This section defines those value lists (term lists) for each of those attributes. Attributes not included in this section (or defi

47、ned in Part 4 of this series) may take any value that conforms to the data type and invariant specifications defined in Part 1 of this series. 5.2 Termlist SUBJECT_CATEGORY, Class ENTRY, attribute subject_of_information_category This attribute provides a coarse-grained definition of the person who i

48、s the subject of an ENTRY. The default value is DS00 (the patient or subject of care). A more fine-grained definition of the information subject (such as the precise relative with a family history) can be specified through the ENTRY.subject_of_information.relationship attribute. Code Meaning Descrip

49、tion DS00 subject of care subject of care DS01 relative of subject of care any human relative, without limitation to biological or adoptive relatives DS02 foetus or neonate or infant baby or babies being described by an ENTRY in the EHR of the mother DS03 mother mother of a foetus or neonate, if being described in the EHR of a baby (e.g. during pregnancy) DS04 donor donor of an organ or body specimen being described by an ENTRY in the EHR of the recipient DS05 unrelated person any other person not related to the subject of care, such as an employer, friend, carer N