EN 12967-1:2007

Foreword
Introduction
1 Scope
2 Normative references
3 Terms and definitions
  3.1 System concepts
  3.2 Concepts relating to organisation
  3.3 Community concepts
  3.4 Behaviour concepts
  3.5 Policy concepts
  3.6 Accountability concepts
4 Symbols and abbreviations
5 Methodology for the specification of the architecture
  5.1 The viewpoints for the specification of the architecture
  5.2 The HISA specification procedure
      5.2.1 The strategic paradigm
      5.2.2 Specification of the Enterprise viewpoint
      5.2.3 Specification of the Information viewpoint
      5.2.4 Specification of the Computational viewpoint
  5.3 Iterative specification
  5.4 Viewpoints specification languages and notations
6 HISA overview
  6.1 General requirement
  6.2 Enterprise viewpoint
  6.3 Information viewpoint
  6.4 Computational viewpoint
7 The methodology for extensions
8 Conformance criteria
  8.1 Conformance of specification documents to the HISA
      methodology
  8.2 Conformance of middleware products to the HISA
      architectural requirements
9 The HISA Enterprise viewpoint
  9.1 Introduction (informative)
      9.1.1 General
      9.1.2 The regional, inter-enterprise perspective
      9.1.3 The medical/clinical perspective
      9.1.4 The operational/clinical and organisational
            process model perspective
      9.1.5 The Healthcare Information Services and their
            complexity
  9.2 The fundamental workflows and groups of users'
      activities to be supported by the middleware
  9.3 General information requirements for all users'
      activities
      9.3.1 Introduction
      9.3.2 Common attributes
      9.3.3 Extensibility
      9.3.4 Versioning
      9.3.5 Auditing
      9.3.6 Handling of lifecycle
  9.4 Subject of Care workflow
      9.4.1 Textual description of requirements
      9.4.2 Use case examples (informative)
  9.5 Clinical information workflow
      9.5.1 Textual specification of requirements
      9.5.2 Use case examples (informative)
  9.6 Activity management workflow
      9.6.1 Textual description of requirements
      9.6.2 Use case examples (informative)
  9.7 Resources management activities/Textual description
      of requirements
  9.8 Users and Authorisations management activities/
      Texutual description of requirements
  9.9 Classifications, coding and dictionaries management
      activities/Textual description of requirements
Annex A (informative) - Highlights on ODP
Annex B (informative) - Rationale on the federative structure
                        of the Health Informatics Systems
                        architecture
Bibliography

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, as shown in Figure 2 Figure 2The architectural principles are formalised according to the ISO/IEC 10746 (all parts) criteria and are therefore structured through the following three viewpoints:a)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)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)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 Ent