BS DD ENV 12612-1998 Medical informatics - Messages for the exchange of healthcare administrative information《医疗信息学 医疗保健管理信息交换的文电》.pdf

《BS DD ENV 12612-1998 Medical informatics - Messages for the exchange of healthcare administrative information《医疗信息学 医疗保健管理信息交换的文电》.pdf》由会员分享，可在线阅读，更多相关《BS DD ENV 12612-1998 Medical informatics - Messages for the exchange of healthcare administrative information《医疗信息学 医疗保健管理信息交换的文电》.pdf（162页珍藏版）》请在麦多课文档分享上搜索。

1、DRAFT FOR DEVELOPMENT DD ENV 12612:1998 Medical informatics Messages for the exchange of healthcare administrative information ICS 11.020; 35.240.70DDENV12612:1998 This Draft for Development, having been prepared under thedirection of the DISC Board, was published under the authorityof the Standards

2、 Committee and comes intoeffecton 15 November 1998 BSI 06-1999 ISBN 0 580 30533 3 National foreword This Draft for Development is the English language version of ENV12612:1997. This publication is not to be regarded as a British Standard. It is being issued in the Draft for Development series of pub

3、lications and is of a provisional nature due to the limited duration of the European prestandard. It should be applied on this provisional basis, so that information and experience of its practical application may be obtained. Comments arising from the use of this Draft for Development are requested

4、 so that UK experience can be reported to the European organization responsible for its conversion into a European Standard. A review of this publication will be initiated2years after its publication by the European organization so that a decision can be taken on its status at the end of its three-y

5、ear life. The commencement of the review period will be notified by an announcement in Update Standards. According to the replies received by the end of the review period, the responsible BSI Committee will decide whether to support the conversion into a European Standard, to extend the life of the

6、prestandard or to withdraw it. Comments should be sent in writing to the Secretary of BSI Technical CommitteeIST/35, Medical informatics, at389 Chiswick High Road, LondonW44AL, giving the document reference and clause number and proposing, where possible, an appropriate revision of the text. A list

7、of organizations represented on this committee can be obtained on request to its secretary. Cross-references The British Standards which implement international or European publications referred to in this document may be found in the BSI Standards Catalogue under the section entitled “International

8、 Standards Correspondence Index”, or by using the “Find” facility of the BSI Standards Electronic Catalogue. Summary of pages This document comprises a front cover, an inside front cover, pages i and ii, the ENV title page, pages 2 to 157 and a back cover. This standard has been updated (see copyrig

9、ht date) and may have had amendments incorporated. This will be indicated in the amendment table on the inside front cover. Amendments issued since publication Amd. No. Date CommentsDDENV12612:1998 BSI 06-1999 i Contents Page National foreword Inside front cover Foreword 2 Text of ENV 12612 5ii blan

10、kEUROPEAN PRESTANDARD PRNORME EUROPENNE EUROPISCHE VORNORM ENV 12612 April 1997 ICS 11.020; 35.240.70 Descriptors: Data processing, information interchange, medicine, messages English version Medical informatics Messages for the exchange of healthcare administrative information Informatique de sant

11、Messages pour lechange dinformations dordre administratif dans le domaine de la sant Medizinische Informatik Nachrichten fr den Austausch administrativer Information im Gesundheitswesen This European Prestandard (ENV) was approved by CEN on1997-03-11 as a prospective standard for provisional applica

12、tion. The period of validity of this ENV is limited initially to three years. After two years the members of CEN will be requested to submit their comments, particularly on the question whether the ENV can be converted into an European Standard (EN). CEN members are required to announce the existanc

13、e of this ENV in the same way as for an EN and to make the ENV available promptly at national level in an appropriate form. It is permissible to keep conflicting national standards in force (in parallel to the ENV) until the final decision about the possible conversion of the ENV into an EN is reach

14、ed. CEN members are the national standards bodies of Austria, Belgium, Denmark, Finland, France, Germany, Greece, Iceland, Ireland, Italy, Luxembourg, Netherlands, Norway, Portugal, Spain, Sweden, Switzerland and UnitedKingdom. CEN European Committee for Standardization Comit Europen de Normalisatio

15、n Europisches Komitee fr Normung Central Secretariat: rue de Stassart 36, B-1050 Brussels 1997 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Members. Ref. No. ENV 12612:1997 EENV12612:1997 BSI 06-1999 2 Foreword This European Prestandard has been pre

16、pared by Technical Committee CEN/TC251 “Medical Informatics”, the secretariat of which is held by IBN. The preparation of this European Prestandard was undertaken by Project Team 3-023 of CEN/TC251 and covered by the European Commission under voucher M021/BC/CEN/93/17.10.1. According to the CEN/CENE

17、LEC Internal Regulations, the national standards organisations of the following countries are bound to announce this European Prestandard: Austria, Belgium, Denmark, Finland, France, Germany, Greece, Iceland, Ireland, Italy, Luxembourg, Netherlands, Norway, Portugal, Spain, Sweden, Switzerland and t

18、he UnitedKingdom. Contents Page Foreword 2 Introduction 5 1 Scope 6 2 Normative references 6 3 Definitions 7 4 Requirements 10 5 Communication roles and supported services 10 5.1 General 10 5.2 Communication roles 10 5.3 Communication roles, services and General Message Descriptions 10 6 Domain Info

19、rmation Model 14 6.1 Introduction 14 6.2 DoMain Information Model diagrams 16 6.3 Textual description of the objects, their relationships and attributes 19 6.4 Textual description of common attribute groups 40 7 General Message Descriptions 42 7.1 Introduction 42 7.2 Request foR Unique Identifier of

20、 Patient on Registration System 43 7.3 Request for Administrative Information of an Identified Patient 46 7.4 Request for Patient list for given Selection Criteria 49 7.5 Message to Add Patient Registration Record 51 Page 7.6 Message to Modify Patient Registration Record 55 7.7 Message to Add Patien

21、t Related Payment Record 61 7.8 Message to Modify Patient Related Payment Record 64 7.9 Message to Add Patient Related Event Record 68 7.10 Message to Modify Patient Related Event Record 74 7.11 Message to Link/Unlink Patient Registration Records 81 7.12 Message to Link/Unlink Action Events 84 7.13

22、Patient Unique Identification Report 88 7.14 Patient Administrative Information Report 90 7.15 Patient Administrative List Report 96 7.16 Message for Acknowledgement of Receipt 100 7.17 Attribute layer 103 Annex A (normative) How to read the models 119 Annex B (informative) Scenarios and theirimplem

23、entation 124 Index 156 Figure 1 Request for and Report of Patient Unique Identifier on a Registration System 11 Figure 2 Request for and Report of Administrative Information of an Identified Patient 11 Figure 3 Request for and Report of Patient Administrative List for Given Selection Criteria 12 Fig

24、ure 4 Message to Add or Modify Patient Administrative Information and Associated Responses 12 Figure 5 Administrative information request and report model 16 Figure 6 Subject model for healthcare party 17 Figure 7 Subject model for patient 18 Figure 8 Subject model for action event 19 Figure 9 Reque

25、st for Unique Identifier of Patient on Registration System: Top level model 44 Figure 10 Request for Unique Identifier of Patient on Registration System: Subject model for healthcare party 45ENV12612:1997 BSI 06-1999 3 Page Figure 11 Request for Unique Identifier of Patient on Registration System: H

26、ierarchical GMD 46 Figure 12 Request for Administrative Information for an Identified Patient: Top level model 47 Figure 13 Request for Administrative Information for an Identified Patient: Hierarchical GMD 48 Figure 14 Request for Patient List for given Selection Criteria: Top level model 49 Figure

27、 15 Request for Patient List for given Selection Criteria: Hierarchical GMD 50 Figure 16 Message to Add Patient Registration Record: Top level model 51 Figure 17 Message to Add Patient Registration Record: Subject model for healthcare party 52 Figure 18 Message to Add Patient Registration Record: Su

28、bject model for patient 53 Figure 19 Message to Add Patient RegistrationRecord: Hierarchical GMD 55 Figure 20 Message to Modify Patient Registration Record: Top level model 56 Figure 21 Message to Modify Patient Registration Record: Subject model for healthcare party 57 Figure 22 Message to Modify P

29、atient Registration Record: Subject model for patient 57 Figure 23 Message to Modify Patient Registration Record: Hierarchical GMD 61 Figure 24 Message to Add Patient Related Payment Record: Top level model 62 Figure 25 Message to Add Patient Related Payment Record: Hierarchical GMD 64 Figure 26 Mes

30、sage to Modify Patient Related Payment Record: Top level model 65 Figure 27 Message to Modify Patient Related Payment Record: Hierarchical GMD 68 Figure 28 Message to Add Patient Related Event Record: Top level model 69 Figure 29 Message to Add Patient Related Event Record: Subject model for Action

31、Event 70 Figure 30 Message to Add Patient Related Event Record: Hierarchical GMD 74 Figure 31 Message to Modify Patient Related Event Record: Top level model 75 Page Figure 32 Message to Modify Patient Related Event Record: Subject model for action event 76 Figure 33 Message to Modify Patient Relate

32、d Event Record: Hierarchical GMD 81 Figure 34 Message to Link/Unlink Patient Registration Records: Top level model 82 Figure 35 Message to Link/Unlink Patient Registration Records: Hierarchical GMD 83 Figure 36 Message to Link/Unlink Action Events: Top level model 85 Figure 37 Message to Link/Unlink

33、 Action Events: Hierarchical GMD 87 Figure 38 Patient Unique IdentificationReport:Top level model 88 Figure 39 Patient Unique Identification Report: Hierarchical GMD 90 Figure 40 Patient Administrative Information Report: Top level model 91 Figure 41 Patient Administrative Information Report: Hierar

34、chical GMD 96 Figure 42 Patient Administrative List Report: Top level model 97 Figure 43 Message to Add Patient Registration Record: Subject model for patient 98 Figure 44 Patient Administrative List Report: Hierarchical GMD 100 Figure 45 Message for Acknowledgement ofReceipt: Top level model 101 Fi

35、gure 46 Message for Acknowledgement of Receipt: Subject model for healthcare party 102 Figure 47 Legend 120 Figure 48 Examples of model components 121 Figure 49 Representation of cardinalities in the DIM compared with SSADM 122 Figure 50 The notation used in hierarchical GMDs 123 Table 1 Description

36、 of data-types 154 blankENV12612:1997 BSI 06-1999 5 Introduction The increased use of data processing and telecommunications capabilities has made possible the interchange of information in machine readable and machine processable formats. As automated interchange of information in healthcare increa

37、ses, it is essential to provide appropriate information interchange standards. Computer systems are in use for the storage and processing of information in many healthcare organisations, including the offices of individual healthcare professionals such as doctors and nurses. Electronic transfer of a

38、dministrative data for identification and registration reduces the need for repeated manual data entry and the risk of transcription errors. Standards are required to facilitate the identification and registration since these processes are fundamental to the sharing of clinical and administrative in

39、formation between healthcare professionals. Implementation of this standard will therefore: facilitate the electronic transfer of requests for administrative data needed for the process of identification and registration in healthcare, sent from requesting healthcare parties to the healthcare partie

40、s that are able to provide the requesters with the information needed; facilitate the electronic transfer of administrative data to requesters and other healthcare parties; reduce the need for human intervention in information interchange between applications used by healthcare parties; minimise the

41、 time and effort required for the introduction of information interchange agreements; reduce the development effort required by suppliers to allow communication between a wide range of applications in this field; reduce (in consequence of the foregoing) the cost of information interchange between he

42、althcare parties. When implementing information exchange based upon this European Prestandard data protection and secrecy principles ought to be guaranteed at least at a level conforming with current legislation in force in the different CEN member countries. Security issues are outside the scope of

43、 this Prestandard. The method by which this European Prestandard has been developed is based on the recommendations of the CEN Technical Report “Investigation of Syntaxes for Existing Interchange Formats to be used in Healthcare” (CR1350:1993). This document is intended for use by message developers

44、. Its provisions are directly relevant to suppliers of computer systems for use in healthcare organisations such as hospitals, general practices, insurance companies, clinical departments and specialist clinics. Its provisions are also relevant to those planning, specifying, procuring or implementin

45、g information systems for use in healthcare organisations such as hospitals, general practices, clinical departments and specialist clinics. The main normative provisions in this European Prestandard are expressed in clauses4 and5 and apply to the General Message Descriptions (GMDs), clause7. The sy

46、mbols used in this European Prestandard have the meaning as defined in normativeAnnex A for the purposes of this European Prestandard only. InformativeAnnex B provides additional explanation about the General Message Descriptions and gives a number of example scenarios of message use. A supplementar

47、y document to this pr-ENV, called “Generic EDIFACT message implementation guide”, provides in its first chapters the method and conformance information on how the EDIFACT messages meet the requirements of the General Message Descriptions of the pr-ENV. This supporting document contains message imple

48、mentation guidelines for the Implementable Message Specifications (IMSs). They should be considered an essential component of the IMS providing a generic EDIFACT implementation specification for use in Europe. Specifically these chapters cover: A general description of how the mapping from GMDs to E

49、DIFACT is carried out. A structure table indicating how the defined IMSs meet the relationships defined in the GMDs. Data tables indicating how the defined IMSs support the objects and attributes of the GMDs The supporting document is not a constituent part of this pr-ENV.ENV12612:1997 6 BSI 06-1999 1 Scope 1.1 This European Prestandard specifies general administrative messages for electronic Information exchange between healthcare informa