SIST EN ISO 12967-3:2021

Health informatics - Service Architecture (HISA) - Part 3: Computational viewpoint (ISO 12967-3:2020)

This document specifies the fundamental characteristics of the computational model implemented by a specific architectural layer of the information system (i.e. the service architecture) to provide a comprehensive and integrated interface to the common enterprise information and to support the fundamental business processes of the healthcare organization, as defined in ISO 12967‑1. The computational model is specified without any explicit or implicit assumption about the physical technologies, tools or solutions to adopt 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 which will be selected for the physical implementation.
The computational model specified in this document provides the basis for ensuring consistency between different engineering and technology specifications (including programming languages and communication mechanisms) since they are intended to be consistent with the same computational object model. This consistency allows open inter-working and portability of components in the resulting implementation.
This document does not aim at representing a fixed, complete, specification of all possible interfaces that might be necessary for any requirement of any healthcare enterprise. It specifies only a set of characteristics — in terms of overall organization and individual computational objects, identified as fundamental and common to all healthcare organizations, and that are satisfied by the computational model implemented by the service architecture.
Preserving consistency with the provisions of this document, physical implementations of the computational model specified in this document can allow extensions in order to support additional and local requirements. Extensions can include both the definition of additional properties of the objects of the computational model specified in this document and the implementation of entirely new objects.
Also, the computational model specified in this document can be extendable over time according to the evolution of the applicable standardization initiatives, in accordance to the methodology defined in ISO 12967‑1:2020, Clause 7, which identifies a set of healthcare common information services, describing the requirements behind them and the methodology through which they will be used.
The information services specified in this document are only the minimal set identifiable according to the identified requirements of the healthcare enterprise, and constituting the service architecture (i.e. the integration platform) to serve as the basis for healthcare applications, e.g. EHR or patient administration.

Medizinische Informatik - Servicearchitektur - Teil 3: Verarbeitungssicht (ISO 12967-3:2020)

Informatique de santé - Architecture de service - Partie 3: Point de vue informatique (ISO 12967-3:2020)

Le présent document spécifie les caractéristiques fondamentales du modèle de traitement mis en place par une couche architecturale spécifique du système d'informations (c'est-à-dire l'architecture de service) pour assurer une interface cohérente et intégrée aux données d'entreprise communes et prendre en charge les processus métier fondamentaux de l'organisme de santé, tel que défini dans l'ISO 12967-1. Le modèle de traitement est spécifié sans émettre d'hypothèse explicite ou implicite sur les technologies physiques, les outils ou les solutions à adopter pour sa mise en œuvre physique dans le cadre des différents scénarios cible. La spécification n'en est pas moins formelle, exhaustive et sans ambiguïté, afin de permettre aux implémenteurs de prévoir une conception efficace du système dans l'environnement technologique spécifique sélectionné pour sa mise en œuvre physique.
Le modèle de traitement spécifié dans le présent document fournit la base permettant de garantir la cohérence des différentes spécifications d'ingénierie et de technologie (notamment des langages de programmation et des mécanismes de communication) étant donné qu'elles sont censées être conformes au même modèle d'objet de traitement. Cette cohérence permet de garantir l'interfonctionnement ouvert et la portabilité des composants dans la mise en place finale.
Le présent document n'a pas pour objet d'être une représentation fixe et exhaustive de toutes les interfaces possibles susceptibles d'être nécessaires aux exigences d'une entreprise de santé. Il spécifie simplement un ensemble de caractéristiques (en termes d'objets organisationnels globaux et de traitement individuels) identifiées comme étant essentielles et communes à tous les organismes de santé et que le modèle de traitement mis en place par l'architecture de service doit satisfaire.
Tout en préservant la cohérence avec les dispositions du présent document, les mises en place physiques du modèle de traitement spécifié dans le présent document peuvent permettre des extensions afin de répondre à des exigences supplémentaires et locales. Les extensions peuvent inclure aussi bien la définition de propriétés supplémentaires d'objets du modèle de traitement spécifié dans le présent document que la mise en œuvre d'objets totalement nouveaux.
De même, le modèle de traitement spécifié dans le présent document peut être étendu dans le temps en fonction de l'évolution des initiatives de normalisation applicables, conformément à la méthodologie définie dans l'ISO 12967-1:2020, Article 7, qui identifie un ensemble de services d'informations communs au domaine de la santé, en décrivant les exigences sous-jacentes et la méthodologie en fonction de laquelle ils seront utilisés.
Les services d'informations spécifiés dans le présent document ne correspondent qu'au plus petit ensemble de services d'informations identifiable en fonction des exigences identifiées de l'entreprise de santé et constituant l'architecture de service (c'est-à-dire la plateforme d'intégration) servant de base aux applications de santé, par exemple DIS ou administration des patients.

Zdravstvena informatika - Arhitektura storitve - 3. del: Računalniški vidik (ISO 12967-3:2020)

General Information

• Status: Published
• Public Enquiry End Date: 19-Dec-2019
• Publication Date: 06-Dec-2020
• ICS: 35.240.80 - IT applications in health care technology
• Technical Committee: ITC - Information technology
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Dec-2020
• Due Date: 05-Feb-2021
• Completion Date: 07-Dec-2020
• Ref Project: EN ISO 12967-3:2020 - Health informatics - Service Architecture (HISA) - Part 3: Computational viewpoint (ISO 12967-3:2020)

Relations

• Replaces: SIST EN ISO 12967-3:2011 - Health informatics - Service architecture - Part 3: Computational viewpoint (ISO 12967-3:2009)
• Effective Date: 01-Jan-2021

Standards Content (Sample)

SLOVENSKI STANDARD
01-januar-2021
Nadomešča:
SIST EN ISO 12967-3:2011
Zdravstvena informatika - Arhitektura storitve - 3. del: Računalniški vidik (ISO
12967-3:2020)
Health informatics - Service Architecture (HISA) - Part 3: Computational viewpoint (ISO
12967-3:2020)
Medizinische Informatik - Servicearchitektur - Teil 3: Verarbeitungssicht (ISO 12967-
3:2020)
Informatique de santé - Architecture de service - Partie 3: Point de vue informatique (ISO
12967-3:2020)
Ta slovenski standard je istoveten z: EN ISO 12967-3:2020
ICS:
35.240.80 Uporabniške rešitve IT v IT applications in health care
zdravstveni tehniki technology
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EN ISO 12967-3
EUROPEAN STANDARD
NORME EUROPÉENNE
November 2020
EUROPÄISCHE NORM
ICS 35.240.80 Supersedes EN ISO 12967-3:2011
English Version
Health informatics - Service Architecture (HISA) - Part 3:
Computational viewpoint (ISO 12967-3:2020)
Informatique de santé - Architecture de service - Partie Medizinische Informatik - Servicearchitektur - Teil 3:
3: Point de vue informatique (ISO 12967-3:2020) Verarbeitungssicht (ISO 12967-3:2020)
This European Standard was approved by CEN on 11 June 2020.

CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this
European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references
concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN
member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by
translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC Management
Centre has the same status as the official versions.

CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,
Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and
United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION

EUROPÄISCHES KOMITEE FÜR NORMUNG

CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2020 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN ISO 12967-3:2020 E
worldwide for CEN national Members.

Contents Page
European foreword . 3

European foreword
This document (EN ISO 12967-3:2020) has been prepared by Technical Committee ISO/TC 215 "Health
informatics" in collaboration with Technical Committee CEN/TC 251 “Health informatics” the
secretariat of which is held by NEN.
This European Standard shall be given the status of a national standard, either by publication of an
identical text or by endorsement, at the latest by May 2021, and conflicting national standards shall be
withdrawn at the latest by May 2021.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CEN shall not be held responsible for identifying any or all such patent rights.
This document supersedes EN ISO 12967-3:2011.
According to the CEN-CENELEC Internal Regulations, the national standards organizations of the
following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria,
Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland,
Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Republic of
North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the
United Kingdom.
Endorsement notice
The text of ISO 12967-3:2020 has been approved by CEN as EN ISO 12967-3:2020 without any
modification.
INTERNATIONAL ISO
STANDARD 12967-3
Second edition
2020-11
Health informatics — Service
architecture (HISA) —
Part 3:
Computational viewpoint
Informatique de santé — Architecture de service —
Partie 3: Point de vue informatique
Reference number
ISO 12967-3:2020(E)
©
ISO 2020
ISO 12967-3:2020(E)
© ISO 2020
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting
on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address
below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: [phone]
Email: [e-mail]
Website: www.iso.org
Published in Switzerland
ii © ISO 2020 – All rights reserved

ISO 12967-3:2020(E)
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 2
4 Abbreviated terms . 2
5 Methodological principles . 2
5.1 General . 2
5.2 Clusters of objects . 2
5.3 Computational language . 3
5.4 The computational objects and interfaces . 4
5.5 Interactions . 5
6 General characteristics of the model . 6
6.1 The two types of computational objects for handling the information . 6
6.2 The ‘basic’ information services . 6
6.2.1 General requirements . 6
6.2.2 ‘Add’ basic information services . 7
6.2.3 "Update" basic information services . 8
6.2.4 "Delete" basic information services .10
6.2.5 "Detail" basic information services .12
6.2.6 "List" basic information services .13
6.3 General-purpose interface .15
6.3.1 General.15
6.3.2 List of information services .16
6.3.3 Behavioural specifications .16
6.4 The eHealth business-related interfaces supporting the workflow computational
objects . .17
6.4.1 General.17
6.4.2 eHealth business-related services managing healthcare workflows .17
6.4.3 Interfaces supporting the “Subject of care workflow” .17
6.4.4 Interfaces supporting the “Healthcare information workflow” .19
6.4.5 Interfaces supporting the “Activity management workflow” .21
6.4.6 Behavioural specifications, common to the eHealth business-related services .23
6.5 Common requirements of the interfaces .24
6.5.1 Interface documentation and organization .24
6.5.2 Naming criteria .24
6.5.3 Data types .25
6.5.4 Structure and organization of the interfaces .25
Annex A (informative) Example of services.27
Annex B (informative) HISA and FHIR® .29
Bibliography .33
ISO 12967-3:2020(E)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out
through ISO technical committees. Each member body interested in a subject for which a technical
committee has been established has the right to be represented on that committee. International
organizations, governmental and non-governmental, in liaison with ISO, also take part in the work.
ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of
electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the
different types of ISO documents should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www .iso .org/ directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of
any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received (see www .iso .org/ patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to
the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT), see
www .iso .org/ iso/ foreword .html.
This document was prepared by Technical Committee ISO/TC 215, Health informatics, in collaboration
with the European Committee for Standardization (CEN) Technical Committee CEN/TC 251, Health
informatics, in accordance with the Agreement on technical cooperation between ISO and CEN
(Vienna Agreement).
This second edition cancels and replaces the first edition (ISO 12967-3:2009), which has been technically
revised. The main changes compared to the previous edition are as follows:
— use of terms, definitions and concepts from ISO 13940:2015 (Contsys);
— reference to further standards, such as HL7® and FHIR®;
— updates to the Bibliography.
A list of all parts in the ISO 12967 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www .iso .org/ members .html.
iv © ISO 2020 – All rights reserved

ISO 12967-3:2020(E)
Introduction
The ISO 12967 series specifies fundamental requirements for 'information infrastructure' and 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 organizations
through an architecture integrating the common data and business logic into a specific architectural
layer (i.e. the healthcare specific service architecture), distinct from individual applications and
accessible throughout the whole information system through information services, as shown in
Figure 1.
Figure 1 — Scope of the ISO 12967 series
The overall architecture is formalized according to ISO/IEC 10746 (all parts) and is therefore structured
through the following three viewpoints.
a) Enterprise viewpoint: specifies a set of fundamental common requirements at enterprise level
with respect to the organizational purposes, scopes and policies that should be supported by
the information and functionality of the service architecture. It also provides guidance on how
one individual enterprise (e.g. a regional healthcare authority, a large hospital or any other
organization where this model is applicable) can specify and document additional specific business
requirements, with a view to achieving a complete specification, adequate for the characteristics of
that enterprise.
Enterprise viewpoint is specified in ISO 12967-1.
b) Information viewpoint: specifies the fundamental semantics of the information model to be
implemented by the service architecture to integrate the enterprise’s common data and to support
the enterprise requirements formalized in ISO 12967-1. It also provides guidance on how one
individual enterprise can extend the ISO 12967 series information model with additional concepts
needed to support local requirements in terms of information to be put in common.
Information viewpoint is specified in ISO 12967-2.
c) Computational viewpoint: specifies the scope and characteristics of the information services that
should be provided by the service architecture for allowing access to the common data as well as for
the execution of the business logic supporting the enterprise processes identified in the information
viewpoint and in ISO 12967-1. It also provides guidance on how one individual enterprise can
specify additional information services needed to support local specific requirements in terms of
common business logic to be implemented.
Computational viewpoint is specified in this document.
ISO 12967-3:2020(E)
1)
ISO 12967-1:2020, Annex C includes an explanation of ISO 23903:— and its relevance in regard to the
ISO 12967 series, for integration with other International Standards such as ISO 13940.
1) Under preparation. Stage at the time of publication: ISO/DIS 23903:2020.
vi © ISO 2020 – All rights reserved

INTERNATIONAL STANDARD ISO 12967-3:2020(E)
Health informatics — Service architecture (HISA) —
Part 3:
Computational viewpoint
1 Scope
This document specifies the fundamental characteristics of the computational model implemented
by a specific architectural layer of the information system (i.e. the service architecture) to provide
a comprehensive and integrated interface to the common enterprise information and to support
the fundamental business processes of the healthcare organization, as defined in ISO 12967-1. The
computational model is specified without any explicit or implicit assumption about the physical
technologies, tools or solutions to adopt 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 which will be selected
for the physical implementation.
The computational model specified in this document provides the basis for ensuring consistency
between different engineering and technology specifications (including programming languages and
communication mechanisms) since they are intended to be consistent with the same computational
object model. This consistency allows open inter-working and portability of components in the resulting
implementation.
This document does not aim at representing a fixed, complete, specification of all possible interfaces
that might be necessary for any requirement of any healthcare enterprise. It specifies only a set of
characteristics — in terms of overall organization and individual computational objects, identified as
fundamental and common to all healthcare organizations, and that are satisfied by the computational
model implemented by the service architecture.
Preserving consistency with the provisions of this document, physical implementations of the
computational model specified in this document can allow extensions in order to support additional and
local requirements. Extensions can include both the definition of additional properties of the objects of
the computational model specified in this document and the implementation of entirely new objects.
Also, the computational model specified in this document can be extendable over time according to
the evolution of the applicable standardization initiatives, in accordance to the methodology defined
in ISO 12967-1:2020, Clause 7, which identifies a set of healthcare common information services,
describing the requirements behind them and the methodology through which they will be used.
The information services specified in this document are only the minimal set identifiable according
to the identified requirements of the healthcare enterprise, and constituting the service architecture
(i.e. the integration platform) to serve as the basis for healthcare applications, e.g. EHR or patient
administration.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
ISO 12967-1:2020, Health informatics — Service architecture — Part 1: Enterprise viewpoint
ISO 12967-2:2020, Health informatics — Service architecture — Part 2: Information viewpoint
ISO 12967-3:2020(E)
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at http:// www .electropedia .org/
3.1
interface
abstraction of the behaviour of an object which consists of a subset of the possible interaction
mechanisms of that object, together with the set of constraints when that interaction occurs
3.2
computational object
object as seen in a computational viewpoint representing the functional decomposition of a system
showing a state and behaviour as well as interactions through interfaces with other computational objects
3.3
subject of care
patient
subject of healthcare
healthcare actor with a person role; who seeks to receive, is receiving, or has received healthcare
[SOURCE: ISO 13940:2015, 5.2.1, modified — Note and examples omitted.]
4 Abbreviated terms
EHR Electronic Health Record
HISA Health Informatics — Service Architecture
ODP Open Distributed Processing
UML Unified Modeling Language
5 Methodological principles
5.1 General
This document encompasses the computational viewpoint, which is concerned in answering HISA
design aspects through the functional decomposition of the system into a set of computational objects
that interact at interfaces, also enabling distribution. HISA will thus be further specified in terms of
computational objects, which manage information and provide services, and their interfaces, starting
from the clusters of objects identified in ISO 12967-1 and further detailed in ISO 12967-2.
5.2 Clusters of objects
ISO 12967-1 has identified the scope, need for, and use of the ISO 12967 series by both developers
and end users. It has described the scope of the business objects from the organization's viewpoint,
by summarizing the related user activities and requirements through natural language. During this
process the main healthcare common clusters of objects have been identified in ISO 12967-1:
a) Subject of care objects
These objects handle the information necessary for supporting the users’ activities that are
identified in the “Subject of care workflow”.
2 © ISO 2020 – All rights reserved

ISO 12967-3:2020(E)
b) Activity management objects
These objects handle the information necessary for supporting the users’ activities that are
identified in the “Activity Management workflow”.
c) Healthcare information objects
These objects handle the information necessary for supporting the users’ activities that are
identified in the “Healthcare Information workflow”.
d) Users and authorization objects
These objects handle the information necessary for supporting the users’ activities related to the
management of users and authorizations.
e) Resources objects
These objects handle the information necessary for supporting the users’ activities related to the
management of resources.
f) Classification objects
These objects handle the information necessary for supporting the users’ activities related to the
management of classifications, coding criteria and dictionaries.
g) Messaging objects
These objects handle the information necessary for supporting the structuring of data and the
communications with other systems through messaging mechanisms.
ISO 12967-2 has formalized the conceptual model of the information being manipulated by the
information services, derived from the textual descriptions contained in ISO 12967-1. For each of
the clusters of objects, an information model composed of information objects has been identified in
ISO 12967-2.
This document defines the computational model, composed of computational objects, capable of meeting
the requirements described in ISO 12967-1. It is necessary in this document to identify its relationship
to the information model, and the interfaces or access mechanisms it provides to access and manipulate
the information handled by the system, which are also referred to as ‘methods’ but more appropriately
they are in the following referred to as ‘information services’.
The individual information services provided by the computational objects are described illustrating
how they allow actual access to the information handled by the system (identifying the interfaces, the
constraints, as well as which information of the underlying overall information model is accessed), and
eventual parallel actions to be taken.
5.3 Computational language
This document is directly concerned with the distribution of processing but not with the interaction
mechanisms that enable distribution to occur. The computational specification decomposes the system
into objects performing individual functions and interacting at well-defined interfaces.
The heart of the computational language is the computational object model, which constrains the
computational specification by defining:
— the form of interface that an object can have;
— the way the interfaces can be bound and the forms of interaction which can take place at them;
— actions an object can perform, in particular the creation of new objects and interfaces.
ISO 12967-3:2020(E)
5.4 The computational objects and interfaces
The computational objects provide the interfaces through which it is possible to access and manipulate
the information managed by the information objects described in the information viewpoint. Each
cluster itself can be seen as a computational object, providing several interfaces that comprise all
interfaces of the information objects belonging to such cluster. The computational objects are defined
at the level of the HISA object.
For each cluster of objects, there will be a set of computational objects providing interfaces allowing
the management of the common information and business logic relevant to the organization. Two types
of computational object are foreseen per cluster:
— ‘basic’ computational objects deriving directly from the corresponding information object (i.e. one
computational object per information object);
— higher-level eHealth-business related computational objects providing interfaces achieving higher-
level business logic.
Thus, the majority of the computational objects will be derived directly from the corresponding
information objects. The further higher-level computational objects also envisaged provide interfaces
achieving higher-level eHealth business logic on possibly multiple information objects within the same
operation. Such eHealth business logic is described in ISO 12967-1 and has to do with the main workflow
processes (i.e. patient management, activity management, etc.).
The basic computational objects, corresponding one-to-one to the information objects, will be equipped
with standardized lower-level basic interfaces having the scope of creating, reading, updating and
deleting — in short maintaining, listing, and getting one instance of — the main classes described in
the information viewpoint.
These basic information services allow the access to and the manipulation of each element of the
underlying model. Their availability secure the openness of the system.
Figure 2 shows an example.
Figure 2 — Example of "basic services"
NOTE 1 The basic services are detailed in 6.2.
The higher-level computational objects implement eHealth business-related transactions on the objects
of the information model, simplifying and ensuring consistency of developments and allowing the
building up of common fundamental procedures of the organization.
Figure 3 shows an example of the possible information handled by an "eHealth business-related
information service"
EXAMPLES
— Patient/person area: registering a person, patient administration, merging patient identifiers, period of
care, etc.;
— Activity management and life cycle: requests, planning, booking, etc.;
— Clinical and EHR: terminologies, classifications, problem-orientation, etc.;
4 © ISO 2020 – All rights reserved

ISO 12967-3:2020(E)
— Resource management: standard usages, etc.
Figure 3 — Example of the information handled by an "eHealth business-related information
service"
NOTE 2 The eHealth business-related information services are detailed in 6.4.
The HISA service architecture also provides a set of interfaces relating to functionalities of general utility
for the management of the overall system, with respect to the execution of particular functionalities.
These services do not pertain to any specific cluster of objects, and are related to general-purpose
issues like session management (e.g. when consumer programs and services are communicating back
and forth, logging in and out of the system, etc.), transaction management, setting system variables, etc.
These information services will be provided by at least a further computational object equipped with
appropriate services, namely the general-purpose interface.
5.5 Interactions
Three types of interaction are envisaged in ODP: signals, operations and flows. Signals are single
actions conveying data from one object to another, while operations can be seen as “client-server”
interactions between objects in which the server object elaborates the data provided by the client or
better ‘consumer’, sending back a result. Flows can be considered as a sequence of interactions (i.e.
information exchanges) between objects pertaining to a specific domain.
The interaction type is part of the interface signature. In HISA the focus is on the interaction type
operation. For this reason, it will not be explicitly referred to in this specification. Such interaction
type implies the need to identify for each computational object the role it plays in the client-server
interaction. However, HISA prescribes the general external characteristics through which each
identified computational object provides interfaces, while the interaction amongst the computational
objects is not part of this document. Thus, the role is always “server”.
NOTE Of the three types of interaction, operations are the ones that present the service-oriented call/return,
or client-server pattern required in the service architecture. The other interaction types can, when necessary, be
described as particular type of operations.
ISO 12967-3:2020(E)
6 General characteristics of the model
6.1 The two types of computational objects for handling the information
The computational objects provide the interfaces through which it is possible to access and manipulate
the information managed by the information objects described in the information viewpoint. An
example of the two types of computational objects is displayed in Figure 4 and shall be referred to in the
following as ‘basic’ and eHealth business-related’ computational objects according to the terminology
adopted in 5.4. The information services that these will expose shall also be referred to in the following
as ‘basic’ and business-related’.
Figure 4 — types of computational object
6.2 The ‘basic’ information services
6.2.1 General requirements
For each class belonging to the seven clusters of objects defined in ISO 12967-1 and specified in the
information viewpoint, the service architecture shall be equipped with a computational object each of
which is in turn equipped with a set of information services allowing to access and to manipulate every
concept (i.e. objects and properties) of the class. The generic structure is displayed in Figure 5.
Figure 5 — Generic structure of the computational objects
6 © ISO 2020 – All rights reserved

ISO 12967-3:2020(E)
The following information services shall be available in the basic computational objects. Each
information service has a scope and a description. Many of the information service specification tables
also include an example.
6.2.2 ‘Add’ basic information services
6.2.2.1 General
The “add” information services shall allow the client of the computational object to create instances of
HISA objects.
6.2.2.2 List of information services
6.2.2.2.1 Information service add
Information add
service
Scope Shall be used to create a new instance of a HISA object.
Description The instances that shall be added are the individual HISA classes specified in ISO 12967-
2:2020, Clause 7. The instance, its class-specific attribute set, and the common system and
version properties shall be created through this information service.
Example The addition of a new person in the system shall be accomplished by calling the add
information service of the person computational object [Person.add]. The caller will
pass as input several fields belonging to the class-specific attribute set (id, name,
birthTime, deceasedTime, gender, address, etc.). The information service shall also
allow the user to pass information to override any default value for its common system
and version-related attributes.
6.2.2.2.2 Information service Xadd
Information Xadd
service
Scope Shall be used to create a new instance of extended data and associate it to a HISA object.
Description The specification of the extended data object that will be created is found in ISO 12967-2:2020,
6.3.7. The instances to which the extended data shall be attached are the individual HISA
classes specified in ISO 12967-2:2020, Clause 7. The extended data properties and the common
system and version properties it comprises shall be created through this information service.
Example The calling of this information service [Person.Xadd] shall allow doing things such as adding,
among others: the digital photograph of the person to the instance of the person object, the
scanned image of the signed consent to receive treatment, etc. The semantics of the extended
datum shall be classified in its property type, the media type in the property mediaType, the
language in the language property, etc.
6.2.2.2.3 Information service Cadd
Information Cadd
service
Scope Shall be used to create a new instance of classification criteria data and associate it to a
HISA object.
Description The specification of the classification criteria data that will be created is found in ISO 12967-
2:2020, 6.3.10. The instances to which the classification data shall be attached are the individ-
ual HISA classes specified in ISO 12967-2:2020, Clause 7. The classification data properties and
its common system and version properties shall be created through this information service.
Example Persons might be classified in healthcare organizations according to their education. The
calling of this information service [Person.Cadd] allows classifying the person according to the
criteria in use e.g. in the national, regional, or local classification in use.
ISO 12967-3:2020(E)
6.2.2.2.4 Information service BRadd
Information BRadd
service
Scope Shall be used to create a new instance of a business rule concerning the HISA object to which it
is associated.
Description The specification of the business rule data that will be created is found in ISO 12967-2:2020,
6.3.9. The instances to which the business rule data shall be attached are the individual HISA
classes specified in ISO 12967-2:2020, Clause 7. The business rule properties and its common
system and version properties shall be created through this information service.
Example Experimental drugs are often used in specific treatments and require the identification of spe-
cific business rules for their correct usage, for example that a specific drug can be prescribed
only by certain physicians for a certain class of illnesses. In this case, the information service
[Resource.BRadd] shall be used once the business rule is defined.
6.2.2.3 Behavioural specifications
It is up to the client of the object (i.e. the caller) to pass valid data as input for the class-specific properties
and for those system and version attributes for which the default values should be overridden.
The system shall generate appropriate values for the common system and version attributes of the HISA
class when the instance is created, for those parameters that are not passed by the caller. In particular
the following.
— Instance identifier shall be unique within the open distributed processing environment of the
system within the enterprise. A unique identifier of the HISA class may be specified by the caller of
the operation. In this case the service shall verify the uniqueness of the identifier.
— System shall take care of managing state changes by adding dynamically and automatically the
values that record the changes occurred in the specific properties of the class or when extended
data, classification data and business rules are attached to it, thus keeping track of the life cycle of
the instance during time. The state changes class is specified in ISO 12967-2:2020, 6.3.8.
— Information service shall return to the client at least the set of common attributes related to the
HISA object created. Such information shall include a value indicating successful execution of the
operation or an error indicating the reason for failure.
— Information service shall implement all integrity checks with respect to the information passed by
the client of operation, aborting it if the operation would lead to an inconsistent informational state.
6.2.3 "Update" basic information services
6.2.3.1 General
The “update” information services shall allow the client of the operation to update instances of HISA
objects.
6.2.3.2 List of information services
6.2.3.2.1 Information service update
Information update
service
Scope Shall be used to update an existing instance of a HISA object.
Description The instances that shall be updated are the individual HISA classes specified in ISO 12967-
2:2020, Clause 7. The instance, its class-specific attribute set, and the common system and
version properties shall be updated through this information service.
8 © ISO 2020 – All rights reserved

ISO 12967-3:2020(E)
Information update
service
Example The updating of a person in the system shall be accomplished by calling the update informa-
tion service of the person computational object [Person.update]. The information service shall
also allow the user to pass information to override any default value for its common system
and version-related attributes.
6.2.3.2.2 Information service Xupdate
Information Xupdate
service
Scope Shall be used to update an existing instance of the extended data associated to a HISA object.
Description The extended data instances that shall be updated are the ones already attached to the indi-
vidual HISA classes specified in ISO 12967-2:2020, Clause 7. The extended data object and its
common system and version properties shall be updated through this information service.
Example The updating of the properties of the extended data of a person in the system shall be accom-
plished by calling the update information service of the person computational object [Person.
Xupdate]. The information service shall also allow the user to pass information to override any
default value for the extended data’s common system and version-related attributes.
6.2.3.2.3 Information service Cupdate
Information Cupdate
service
Scope Shall be used to update an existing instance of classification data associated to a HISA object.
Description The classification data instances that shall be updated are the ones already attached to the
individual HISA classes specified in ISO 12967-2:2020, Clause 7. The classification object and
its common system and version properties shall be updated through this information service.
Example The updating of the classification criteria of a person in the system shall be accomplished by
calling the update information service of the person computational object [Person.Cupdate].
The information service shall also allow the user to pass information to override any default
value for its common system and version-related attributes.
6.2.3.2.4 Information service BRupdate
Information BRupdate
service
Scope Shall be used to update an existing instance of a business rule associated to the HISA object.
Description The specification of the business rule that will be created is found in ISO 12967-2:2020, 6.3.9.
The instances to which the business rule data shall be attached are the individual HISA classes
specified in ISO 12967-2:2020, Clause 7. The business rule properties and its common system
and version properties shall be updated through this information service.
Example Experimental drugs are often used in treatments and need specific business rules to be
identified for their correct usage, e.g., that a specific drug can be prescribed only by certain
physicians for a certain class of illnesses. When these business rules need to be updated, the
information service [Resource.BRupdate] shall be used.
6.2.3.3 Behavioural specifications
It is up to the client of the object to pass valid data as input for the class specific properties and for those
system and version attributes for which the default values should be overridden.
The system shall generate and/or update the appropriate values for the common system and version
attributes of the HISA class when it is updated.
...