EN 12967-3:2007

Foreword
Introduction
1 Scope
2 Normative references
3 Terms and definitions
4 Symbols and abbreviations
5 Methodological Principles (informative)
  5.1 General
  5.2 Clusters of Objects
  5.3 Computational language
  5.4 The computational objects and Interfaces
  5.5 Interaction
6 General characteristics of the Model
  6.1 The two types of computational objects
  6.2 The basic methods
      6.2.1 General requirement
      6.2.2 "Add" basic methods
      6.2.3 "Update" basic methods
      6.2.4 "Delete" basic methods
      6.2.5 "Detail" basic methods
      6.2.6 "List" basic methods
  6.3 General purpose interface
      6.3.1 General
      6.3.2 List of methods
      6.3.3 Behavioural specifications
  6.4 The complex interfaces of the workflow related
      computational objects
      6.4.1 General
      6.4.2 Complex services managing healthcare workflows
      6.4.3 Interfaces supporting the "Subject of Care
            Workflow"
      6.4.4 Interfaces supporting the "Clinical Information
            workflow"
      6.4.5 Interfaces supporting the "Activity Management
            workflow"
      6.4.6 Behavioural specifications, common to the complex
            services
  6.5 Common requirements of the interfaces
      6.5.1 Interface documentation and organization
      6.5.2 Naming criteria
      6.5.3 Data types
      6.5.4 Structure and organization of the interfaces
Annex A (informative) - Examples of services
Bibliography

HISA specifies fundamental requirements for 'information infrastructure' and healthcare specific middleware services. This part of the standard specifies the fundamental characteristics of the computational model to be implemented by a specific architectural layer of the information system (i.e. the middleware) to provide a comprehensive and integrated interface to the common enterprise information and to support the fundamental business processes of the healthcare organisation, as defined in the document “Health Informatics – Service Architecture - Part 1: Enterprise Viewpoint”. The computational model is specified without any –explicit or implicit- assumption about the physical technologies, tools or solutions to be adopted for its physical implementation in the various target scenarios. The specification is nevertheless formal, complete and non-ambiguous enough to allow implementers to derive an efficient design of the system in the specific technological environment that will be selected for the physical implementation.The computational model provides the basis for ensuring consistency between different engineering and technology specifications (including programming languages and communication mechanisms) since they must be consistent with the same computational object model. This consistency allows open inter-working and portability of components in the resulting implementation.This specification does not aim at representing a fixed, complete, specification of all possible interfaces that may be necessary for any requirement of any healthcare enterprise. It specifies only a set of characteristics –in terms of overall organisation and individual computational objects, identified as fundamental and common to all healthcare organisations, and that are satisfied by the computational model implemented by the middleware.Preserving consistency with the provisions of this standard, physical implementations shall allow extensions to the standard computational m