《DD-ENV-12967-1-1998.pdf》由会员分享，可在线阅读，更多相关《DD-ENV-12967-1-1998.pdf（84页珍藏版）》请在三一文库上搜索。
1、DRAFT FOR DEVELOPMENT DD ENV 12967-1:1998 Medical informatics Healthcare Information System Architecture (HISA) Part 1: Healthcare Middleware Layer ICS 11.020; 35.240.70 Licensed Copy: London South Bank University, London South Bank University, Sun Dec 10 13:19:53 GMT+00:00 2006, Uncontrolled Copy,
2、(c) BSI DD ENV 12967-1:1998 This Draft for Development, having been prepared under the direction of the DISC Board, was published under the authority of the Standards Committee and comes into effect on 15 November 1998 BSI 07-1999 ISBN 0 580 30537 6 National foreword This Draft for Development is th
3、e English language version of ENV 12967-1:1998. 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 due to the limited duration of the European prestandard. It should be applied on this pr
4、ovisional 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 so that UK experience can be reported to the European organization responsible for its conversison into a European Standard. A r
5、eview of this publication will be initiated 2 years after its publication by the European organization so that a decision can be taken on its status at the end of its three-year life. The commencement of the review period will be notified by an announcement in Update Standards. According to the repl
6、ies 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 prestandard or to withdraw it. Comments should be sent in writing to the Secretary of BSI Technical Committee IST/35, Medical
7、informatics, at 389 Chiswick High Road, London W4 4AL, giving the document reference and clause number and proposing, where possible, an appropriate revision of the text. A list of organizations represented on this committee can be obtained on request to its secretary. Cross-references The British S
8、tandards which implement international or European publications referred to in this document may be found in the BSI Standards Catalogue under the section entitled “International Standards Correspondence Index”, or by using the “Find” facility of the BSI Standards Electronic Catalogue. Summary of pa
9、ges This document comprises a front cover, an inside front cover, pages i and ii, the ENV title page, pages 2 to 79 and a back cover. This standard has been updated (see copyright date) and may have had amendments incorporated. This will be indicated in the amendment table on the inside front cover.
10、 Amendments issued since publication Amd. No.DateComments Licensed Copy: London South Bank University, London South Bank University, Sun Dec 10 13:19:53 GMT+00:00 2006, Uncontrolled Copy, (c) BSI DD ENV 12967-1:1998 BSI 07-1999i Contents Page National forewordInside front cover Foreword2 Text of ENV
11、 12967-15 Licensed Copy: London South Bank University, London South Bank University, Sun Dec 10 13:19:53 GMT+00:00 2006, Uncontrolled Copy, (c) BSI ii blank Licensed Copy: London South Bank University, London South Bank University, Sun Dec 10 13:19:53 GMT+00:00 2006, Uncontrolled Copy, (c) BSI EUROP
12、EAN PRESTANDARD PRNORME EUROPENNE EUROPISCHE VORNORM ENV 12967-1 February 1998 ICS 11.020; 35.240.70 Descriptors: Data processing, information interchange, data transmission, medicine, social welfare, compatibility, specifications English version Medical Informatics Healthcare Information System Arc
13、hitecture (HISA) Part 1: Healthcare Middleware Layer This European Prestandard (ENV) was approved by CEN on 5 January 1998 as a prospective standard for provisional application. The period of validity of this ENV is limited initially to three years. After two years the members of CEN will be request
14、ed to submit their comments, particularly on the question whether the ENV can be converted into a European Standard. CEN members are required to announce the existence 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 perm
15、issible 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 reached. CEN members are the national standards bodies of Austria, Belgium, Czech Republic, Denmark, Finland, France, Germany, Greece, Icel
16、and, Ireland, Italy, Luxembourg, Netherlands, Norway, Portugal, Spain, Sweden, Switzerland and United Kingdom. CEN European Committee for Standardization Comit Europen de Normalisation Europisches Komitee fr Normung Central Secretariat: rue de Stassart 36, B-1050 Brussels 1998 CEN All rights of expl
17、oitation in any form and by any means reserved worldwide for CEN national Members. Ref. No. ENV 12967-1:1998 E Licensed Copy: London South Bank University, London South Bank University, Sun Dec 10 13:19:53 GMT+00:00 2006, Uncontrolled Copy, (c) BSI ENV 12967-1:1998 BSI 07-1999 2 Foreword This Europe
18、an Prestandard has been prepared by Technical Committee CEN/TC 251 “Medical informatics”, the secretariat of which is held by SIS. According to the CEN/CENELEC Internal Regulations, the national standards organizations of the following countries are bound to implement this European Standard: Austria
19、, Belgium, Czech Republic, Denmark, Finland, France, Germany, Greece, Iceland, Ireland, Italy, Luxembourg, Netherlands, Norway, Portugal, Spain, Sweden, Switzerland and the United Kingdom. Annex A, Annex B, Annex C, Annex D, Annex E and Annex F are informative. Non-technical readers are advised to s
20、tart analysis of the document with Annex C which provides an introduction to the objectives of the architecture and the technical background underlying its specification. Contents Page Foreword2 Introduction5 1Scope6 2Normative references6 3Definitions7 4Symbols and abbreviations7 5Structure of a he
21、althcare information system architecture9 6Rationale for the identification of the Healthcare Common Services10 7Subject of care Healthcare Common Services (HC-HCS)12 8Health Characteristic Healthcare Common Services (HC-HCS)15 9Activity Healthcare Common Services (A-HCS)17 10Resource Healthcare Com
22、mon Services (R-HCS)24 11Authorisation Healthcare Common Services (AU-HCS)27 12Concept Healthcare Common Services (C-HCS)30 13Additional requirements common to all Healthcare Common Services32 14Common functional characteristics of the Healthcare Common Services (HCS)32 15Additional capabilities for
23、 the Healthcare Common Services33 Annex A (informative) Conformance to the Healthcare Information System Architecture34 Annex B (informative) Classification criteria for the applications36 Annex C (informative) Tutorial38 Annex D (informative) Relationship with prENV 12265 Electronic Healthcare Reco
24、rd Architecture74 Annex E (informative) Conformance to prENV 12443 Healthcare Information Framework77 Annex F (informative) Bibliography79 Figure 1 The layers of the architecture of healthcare information systems9 Figure 2 The conceptual schema of the essential information managed by the Subject of
25、Care Healthcare Common Services12 Licensed Copy: London South Bank University, London South Bank University, Sun Dec 10 13:19:53 GMT+00:00 2006, Uncontrolled Copy, (c) BSI ENV 12967-1:1998 BSI 07-19993 Page Figure 3 Conceptual schema of the essential information managed by the Health Characteristic
26、Healthcare Common Services16 Figure 4 Conceptual schema of the essential information managed by the Activity Healthcare Common Services19 Figure 5 Conceptual schema of the essential information managed by the Resource Healthcare Common Services25 Figure 6 Conceptual schema of the essential informati
27、on managed by the Authorisation Healthcare Common Services27 Figure 7 Conceptual schema of the essential information managed by the Concept Healthcare Common Services30 Figure C.1 The different levels of the territorial organisation of the healthcare structure39 Figure C.2 The evolution of healthcar
28、e information systems40 Figure C.3 The architecture as an instrument for ensuring the modularity of the information system42 Figure C.4 The evolution strategies for a system on the basis of the architecture42 Figure C.5 The two steps of the specification of the architecture45 Figure C.6 The scope of
29、 the standard specification with respect to the complete specification framework46 Figure C.7 The need for formalising the external behaviour of each component to enable the integration and interoperability of the different modules47 Figure C.8 The openness and modularity of the architecture48 Figur
30、e C.9 B in the whole scenario of healthcare actors49 Figure C.10 The correspondence between the levels of the organisation and the layers of the Conceptual Architectural Framework in which functional areas or units represent examples52 Figure C.11 The overall structure of the architecture of Healthc
31、are Information Systems B applications represent examples52 Figure C.12 The high-level model of the activities in any generic healthcare organisation53 Page Figure C.13 The role of the Concept Common Services with respect to the other Common Services59 Figure C.1461 Figure C.1562 Figure C.1662 Figur
32、e C.1763 Figure C.18 HISA fundamental architectural standards65 Figure C.1970 Licensed Copy: London South Bank University, London South Bank University, Sun Dec 10 13:19:53 GMT+00:00 2006, Uncontrolled Copy, (c) BSI 4 blank Licensed Copy: London South Bank University, London South Bank University, S
33、un Dec 10 13:19:53 GMT+00:00 2006, Uncontrolled Copy, (c) BSI ENV 12967-1:1998 BSI 07-19995 Introduction Healthcare organisational structure in all European countries consists of networks of centres distributed over the territory, characterised by a high degree of heterogeneity and diversity, from o
34、rganisational, logistic, clinical and even cultural perspectives. The structure of individual centres is evolving from a vertical, aggregated organisation towards the integration of a set of specialised functional areas, with specific needs and characteristics. Such a situation determines two main n
35、eeds which conflict with each other in a certain way. On the one hand it is necessary to support effectively the specific requirements of each unit or user in the most appropriate and cost-effective way whilst on the other hand it is vital to ensure the consistency and integration of the overall org
36、anisation, both at local and territorial level. The large number of applications, mutually isolated and incompatible, that are already available on the market and installed and operational in healthcare organisations, effectively supporting specific needs of users cannot be underestimated. Under the
37、 present circumstances, the main need is to make possible the integration and interoperability of already existing applications thereby securing investments already made and allowing continuity of the service whilst facilitating a gradual migration of existing proprietary, monolithic systems towards
38、 the new concepts of openness and modularity. The cost-effectiveness of the solutions, especially when projected on the scale of the whole organisation, represents another crucial aspect to be evaluated carefully. Such objectives are not only related to the need for improving clinical treatments to
39、the subject of care but are also demanded by the urgent necessity of all European countries to control and optimise the current level of expenditure for health, whilst ensuring the necessary qualitative level of services to all subjects of care. The purpose of the standard architecture is to identif
40、y a set of common services used within healthcare information systems, supporting specific requirements of the target organisation, as well as being capable of co-operating and interworking according to the requirements of the organisation as a whole. The architecture is intended as a basis both for
41、 the comparison, evolution and integration of existing systems as well as for the planning and high-level design of new open and modular systems, capable of providing consistent and integrated support to the clinical, organisational and managerial requirements of healthcare organisations. The standa
42、rd architecture aims at presenting a practical tool, usable by different types of users, involved with different responsibilities during the whole life-cycle of the information system: Suppliers who plan and design high-level consistent information systems, meeting the actual requirements of healthc
43、are organisations and capable of interworking in a generic information systems: Consumers at managerial level to plan the implementation and evolution of the Healthcare Information System at strategic level according to organisational goals and requirements; to validate the compliance of different s
44、olutions with respect to the needs of the organisation; to facilitate the selection of different but integratable products; Consumers at operational level to provide an active contribution to the technicians in the specification of the requirements for the system; to assess the basic compliance of i
45、ndividual solutions with their specific requirements. General aims to provide a comprehensive and consistent, even if preliminary, framework for the integration of the two main foci of development, research and standardisation activities: patient treatment and management of the organisation; to defi
46、ne the scope of a set of subsequent fundamental standards, each capable of detailing the various components of the architecture to a level permitting the physical connection of different products in an open environment. It should be stressed that this European Prestandard does not aim to recognise a
47、 unique model for clinical, organisational, managerial or administrative activities, but rather defines a set of healthcare-specific information and services common to all healthcare information systems, usable by any application, to manage mutual interworking. Licensed Copy: London South Bank Unive
48、rsity, London South Bank University, Sun Dec 10 13:19:53 GMT+00:00 2006, Uncontrolled Copy, (c) BSI ENV 12967-1:1998 6 BSI 07-1999 This European Prestandard is a foundation standard and may require further standards as indicated in Annex C. In particular, further future standards detailing the aspec
49、ts related to the description, formalisation and composition of the services should extend the specifications of this standard. These future standards should increase the level of accuracy and compliability suitable for the formalisation of the mechanisms according to which different software products may interact in a generic physical environment. 1 Scope This European Prestandard establishes general principles for the architecture of healthcare information systems as well as the scope of a set of Healthcar