Saltar navegación principal
Normas DIN – AENOR
DIN EN 12967-2:2008-02

DIN EN 12967-2:2008-02

Health informatics - Service architecture - Part 2: Information viewpoint; English version EN 12967-2:2007

Informatique de la santé - Architecture de service - Partie 2: Point de vue informationnel; Version anglaise EN 12967-2:2007

Medizinische Informatik - Servicearchitektur - Teil 2: Informationssicht; Englische Fassung EN 12967-2:2007

Fecha Anulación:
2011-06 /Withdrawn
Equivalencias internacionales:

EN 12967-2 (2007-10)

Relación con otras normas DIN:
This European standard provides guidance for the description, planning and development of new systems as well as for the integration of existing information systems, both within one enterprise and across different healthcare organisations through an architecture integrating the common data and business logic into a specific architectural layer (i. e. the middleware), distinct from individual applications and accessible throughout the whole information system through services. The architectural principles are formalised according to the ISO/IEC 10746 criteria and are therefore structured through the following three viewpoints: a) The Enterprise Viewpoint that specifies a set of fundamental common requirements at enterprise level with respect to the organisational purposes, scopes and policies that must be supported by the information and functionalities of the middleware. It also provides guidance on how one individual enterprise (e. g. a regional healthcare authority, a large hospital or any other where this model is applicable) may specify and document additional specific business requirements, with a view of achieving a complete specification, adequate for the characteristics of that enterprise. b) The Information Viewpoint that specifies the fundamental semantics of the information model to be implemented by the middleware to integrate the common enterprise data and to support the enterprise requirements formalised in the Enterprise Viewpoint. It also provides guidance on how one individual enterprise may extend the standard model with additional concepts, needed to support local requirements in terms of information to be put in common. c) The Computational Viewpoint that specifies the scope and characteristics of the services that must be provided by the middleware for allowing the access to the common data as well as the execution of the business logic supporting the enterprise processes identified in the Information and Enterprise viewpoints. It also provides guidance on how one individual enterprise may specify additional services, needed to support local specific requirements in terms of business logic to be put in common. The standard is also independent from, and does not imply either explicitly or implicitly, any specific technological solution or product for its deployment. Accordingly, the formalisation of the architecture according to two lower levels of the ODP reference model, the Engineering and Technology viewpoints is outside the scope of this standard. The language and notations used here for specifying the architecture are based on UML (Unified Modelling Language) complemented by case studies and other paradigms widely utilised by other standards in health informatics. The level of the specification is complete and non-ambiguous enough to allow its implementation into the specific physical and technological scenarios adopted by the various healthcare organisations and vendors. For this exercise it is recommended to follow the methodology formalised by the Engineering and Technology viewpoints of the ISO ODP Reference model. The standard is organised in three parts: - Part 1 specifies the overall characteristics of the architecture, formalises the specification methodology and the conformance criteria, details the Enterprise Viewpoint of the architecture - Part 2 (this part) specifies the Information Viewpoint of the architecture - Part 3 specifies the Computational viewpoint of the architecture Each document is self-consistent and is independently utilisable for the intended purposes also by different types of users (Part 1 being more oriented to the managerial level, Parts 2 and 3 being more dedicated to the design activities). Nevertheless, it should be understood that they represent three aspects of the same architecture. Mutual references therefore exist between the different parts and evolutions of the individual documents shall be carried out according to the defined methodology to preserve the overall integrity and consistency of the specification.
Architecture (IT), Compatibility, Computer sciences, Computer software, Data exchange, Data processing, Data representation, Definitions, English language, Information exchange, Information interchange, Information models, Information systems, Interfaces, Interfaces (data processing), Layers, Medical informatics, Medical sciences, Middleware, Open distributed processing, Public health, Reference model, Specification (approval), Structure, System architecture
Idioma Formato

Formato digital

Nota: Precios sin IVA ni gastos de envío

Añadir a la cesta