1、DRAFT FOR DEVELOPMENTDD CEN/TS 14822-4:2005Health informatics General purpose information components Part 4: Message headersICS 35.240.80g49g50g3g38g50g51g60g44g49g42g3g58g44g55g43g50g56g55g3g37g54g44g3g51g40g53g48g44g54g54g44g50g49g3g40g59g38g40g51g55g3g36g54g3g51g40g53g48g44g55g55g40g39g3g37g60g3g
2、38g50g51g60g53g44g42g43g55g3g47g36g58DD CEN/TS 14822-4:2005This Draft for Development was published under the authority of the Standards Policy and Strategy Committee on 31 March 2008 BSI 2008ISBN 978 0 580 54849 9National forewordThis Draft for Development is the UK implementation of CEN/TS 14822-4
3、:2005. This publication is not to be regarded as a British Standard.It is being issued in the Draft for Development series of publications and is of a provisional nature. It should be applied on this provisional basis, so that information and experience of its practical application can be obtained.C
4、omments arising from the use of this Draft for Development are requested so that UK experience can be reported to the European organization responsible for its conversion to a European standard. A review of this publication will be initiated not later than three years after its publication by the Eu
5、ropean organization so that a decision can be taken on its status. Notification of the start of the review period will be made in an announcement in the appropriate issue of Update Standards.According to the replies received by the end of the review period, the responsible BSI Committee will decide
6、whether to support the conversion into a European Standard, to extend the life of the Technical Specification or to withdraw it. Comments should be sent to the Secretary of the responsible BSI Technical Committee at British Standards House, 389 Chiswick High Road, London W4 4AL.The UK participation
7、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 all the necessary provisions of a contract. Users are responsible for its
8、correct application.Amendments/corrigenda issued since publicationDate CommentsTECHNICAL SPECIFICATIONSPCIFICATION TECHNIQUETECHNISCHE SPEZIFIKATIONCEN/TS 14822-4June 2005ICS 35.240.80English versionHealth informatics - General purpose information components -Part 4: Message headersInformatique de s
9、ant - Composants dinformation usagegnral - Partie 4: En-ttes de messageMedizinische Informatik - Allgemeine Mehrzweck-Komponenten fr Nachrichten - Teil 4: Allgemeine klinischeKomponentenThis Technical Specification (CEN/TS) was approved by CEN on 26 March 2005 for provisional application.The period
10、of validity of this CEN/TS is limited initially to three years. After two years the members of CEN will be requested to submit theircomments, particularly on the question whether the CEN/TS can be converted into a European Standard.CEN members are required to announce the existence of this CEN/TS in
11、 the same way as for an EN and to make the CEN/TS availablepromptly at national level in an appropriate form. It is permissible to keep conflicting national standards in force (in parallel to the CEN/TS)until the final decision about the possible conversion of the CEN/TS into an EN is reached.CEN me
12、mbers are the national standards bodies of Austria, Belgium, Cyprus, Czech Republic, Denmark, Estonia, Finland, France,Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Slovakia,Slovenia, Spain, Sweden, Switzerland and Uni
13、ted Kingdom.EUROPEAN COMMITTEE FOR STANDARDIZATIONCOMIT EUROPEN DE NORMALISATIONEUROPISCHES KOMITEE FR NORMUNGManagement Centre: rue de Stassart, 36 B-1050 Brussels 2005 CEN All rights of exploitation in any form and by any means reservedworldwide for CEN national Members.Ref. No. CEN/TS 14822-4:200
14、5: E2 Contents Page Foreword .3 1 Scope5 2 Normative References.5 3 Terms and Definitions.5 4 Symbols and Abbreviations .6 5 Rules Governing the Use of General Purpose Information Components .6 6 General Purpose Information Components6 Annex A (informative) How to read the models 16 Bibliography18 C
15、EN/TS 14822-4:20053 Foreword This document (CEN/TS 14822-4:2005) has been prepared by Technical Committee CEN/TC 251 “Health Informatics”, the secretariat of which is held by SIS. This is part four of the multi part standard EN 14822: Health informatics - General purpose information components with
16、the following parts: Part 1: Overview Part 2: Non-Clinical Part 3: Clinical Part 4: Message headers According to the CEN/CENELEC Internal Regulations, the national standards organizations of the following countries are bound to announce this CEN Technical Specification: Austria, Belgium, Cyprus, Cze
17、ch Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom. CEN/TS 14822-4:20054 Introduction Many previous messaging
18、 and information structure standards for health have overlapping parts with a number of objects being defined in separate documents, sometimes with small variations making implementation of conformant applications more difficult. It therefore makes sense to define a set of general purpose components
19、 that can be used for definition of message structures for different purposes. This approach was suggested and approved as a strategy for CEN/TC 251 in the Short Strategic Study on message standards alignment in 1999 examining a set of five European Standards for messages. This Technical Specificati
20、on is aiming to provide such a set of components and has been developed jointly with a new European Standard for Service Request and Report messages that is using the components defined herein. Another important background to the development of this Technical Specification has been the wish for a ha
21、rmonisation of information models for health developed in Europe and the USA expressed in the collaboration agreement entered March 2000 between CEN/TC 251 and HL7 (Health Level Seven, Ann Arbor. Michigan). The goal was set for a maximum degree of alignment while maintaining their independence and n
22、eed to serve the business requirements of the respective markets but also to make the results available to ISO for possible international standardization. HL7 have adapted a general strategy similar to CEN/TC 251 using information modelling expressed in UML (Unified Modelling Language) for their new
23、 standards and a lot of interaction and information sharing has occurred between CEN experts and HL7 in an open spirit of collaboration. This Technical Specification includes a large number of objects which are technically identical to descriptions in draft documents of HL7, although partly describe
24、d differently due to the fact that CEN is following the ISO rules for drafting and presentation of standards which HL7 is not. CEN wishes to express its gratitude towards HL7 experts for generously sharing their models with the European expert team. This part 4 document is definition of a set of mes
25、sage header General Purpose Information Components. CEN/TS 14822-4:20055 1 Scope It is now widely or even universally accepted that computer systems that are used within healthcare to record information about the care given to patients need to share that information with other computer systems and t
26、heir users. In order that computer systems may share information effectively there is a requirement that the communicating parties, and particularly their computer systems have a common understanding of how the information which they are sharing is represented. This sharing of representation needs t
27、o take place at a number of levels, most notably at the data representation or syntactic level which is the subject of CEN/TS 14796, but also at the macro or semantic level where groupings of data are used to provide a context or set of contexts for the data. This part 4 of the standard is limited t
28、o descriptions of components concerned with messaging, and in particular the message and batch headers. 2 Normative References Not applicable. 3 Terms and Definitions For the purposes of this Technical Specification, the following terms and definitions apply. 3.1 batch collection of messages 3.2 com
29、municating party person, organisation or device which acts in the role of a sender or receiver of a communication 3.3 communication techniques for the effective transmission of information, ideas, etc. Longmans 1995 3.4 healthcare agent healthcare person, healthcare organisation, healthcare device o
30、r that performs a role in a healthcare activity 3.5 message communication in writing, speech or by signals 3.6 organisation unique framework of authority within which a person or persons act, or are designated to act towards some purpose NOTE Groupings or subdivisions of an organisation may also be
31、considered as organisations where there is need to identify them for information interchange. ISO/IEC 6523-1 CEN/TS 14822-4:20056 4 Symbols and Abbreviations CS Coded Simple value CV Coded Value GPIC General Purpose Information Component II Instance Identifier INT Integer ST Character String TS Poin
32、t in Time UML Unified Modelling Language 5 Rules Governing the Use of General Purpose Information Components 5.1 When using a GPIC, a system which conforms to this Technical Specification shall implement all of the features (classes, associations, attributes) that are described within the GPIC core.
33、 In particular, A conformant system that utilises a GPIC shall be able to receive and process information present in all classes and attributes, even where the attributes are specified as being optional. A conformant system that utilises a GPIC to send information shall not be obliged to populate op
34、tional attributes. 5.2 One of the GPICs described (MessageTransmission) in this part may be associated with another GPIC (RelatedMessage) which in effect extends the functionality of the GPIC. This extension is informative in nature and shall not subject to conformance testing. 6 General Purpose Inf
35、ormation Components CEN/TS 14822-4:20057 6.1 Communicating Party 6.1.1 General Description GPIC Name CommunicatingParty GPIC_ID = 4.001 Description Information about the devices and the organisations that are using these devices in the sending and/or receiving of communications. Notes 1. Each commun
36、ication shall have one device/organisation which is acting in the role of sender and at least one device/organisation which is acting as the recipient of the communication. 2. This GPIC is generally concerned with the transport of the message. Details of the persons that are acting as sender or reci
37、pient should be included in the content of the message. Examples Sending doctor, receiving laboratory UML Representation CommunicationFunction type_cd: CS (sender, receiver) External InterfaceGPIC Core 1 1* classCode: CS Identifier(s) for the organisation that is acting as a communication sender or
38、receiver name O ST Name of the organisation telecom O Telecom One or more telecommunication numbers/addresses or the communicating organisation 6.2 Message Transmission 6.2.1 General Description GPIC Name MessageTransmission GPIC_ID = 4.002 Description The “envelope” into which a message is placed.
39、Use This GPIC resides at the head of the message and therefore does not have a conventional GPIC interface requirement. However, the class ControlEvent is shown as the point at which the message content is to be attached. It is mandated that the ControlEvent class will interface to a class of genera
40、l CEN/TS 14822-4:200510 type ACT, i.e. the message content will always start with an ACT class or one of its specialisations. Notes The ControlAct class is not described here except to the extent that it is necessary that the instance of MessageTransmission will normally be associated with a message
41、 payload and where there is a payload, this shall always start with an Act class (ControlAct). Although the content of the ControlAct is not described here, the content should describe the act of message sending/receiving, i.e. provide information about the sender, receivers (as persons/organisation
42、s), the purpose of the message, date and time of its creation, etc. MessageTransmission is not associated directly with a payload (ControlAct) only where a message is merely being referred to as in the RelatedMessage GPIC. UML Representation MessageTransmission creationTime: TS id: II interactionId:
43、 II versionCode: CS GPIC Core CommunicatingParty 1 2* 1 01 ControlAct Message RelatedMessage 0* 1 CEN/TS 14822-4:200511 6.2.2 MessageTranmission GPIC Core Description MessageTransmission Description Information about the message as a whole NOTE: This class concatenates the attributes of the HL7 RIM
44、class Transmission and its specialisation class Message Related Classes Type of Relationship Cardinality CommunicationFunction (in CommunicatingParty GPIC) Association 2 to many ControlAct Association 0 or 1 Attributes O Type Description creationTime M TS The date/time that the sending system create
45、d the transmission. If the time zone is specified, it will be used throughout the transmission as the default time zone. id M II Unique identifier of the transmission. interactionId O II Unique identification of the message type. versionCode O CS Version of the messaging standard. This attribute is
46、matched by the receiving system to its own version to be sure the message will be interpreted correctly. The set of allowable values (i.e. version identifiers) must be defined by the standards development body responsible for the definition and maintenance of the messaging standards. processingCode
47、O CS Defines whether the message is part of a production, training, or debugging system VALUES: D = Debugging P = Production T = Training acceptAckCode O CS Identifies the conditions under which accept acknowledgements are required to be returned in response to this message. VALUES: AL Always ER Err
48、or/reject only NE Never SU Successful only CEN/TS 14822-4:200512 responseCode O CS Specifies whether an application response is expected from the addressee of this interaction and what level of detail that response should include. This attribute restricts the default response options specified by th
49、e receiver responsibilities for the interaction. For example, if an interaction has receiver responsibilities to send either an accept interaction or a refuse interaction, and the responseCode is set to E - Exception, the receiver should only respond if they refuse. VALUES: C = Completion: Respond with exceptions and a notification of completion. F = Confirmation: Respond with exceptions, completion, and modification with detail (as above), and send positive confirmations even if no modifications are being made. D = Detail: Respond w
