EN ISO 12967-3:2011

SLOVENSKI STANDARD
01-julij-2011
1DGRPHãþD
SIST EN 12967-3:2008
=GUDYVWYHQDLQIRUPDWLND$UKLWHNWXUDVWRULWYHGHO5DþXQDOQLãNLYLGLN,62

Health informatics - Service architecture - Part 3: Computational viewpoint (ISO 12967-
3:2009)
Medizinische Informatik - Servicearchitektur - Teil 3: Verarbeitungssicht (ISO 12967-
3:2009)
Informatique de santé - Architecture de service - Partie 3: Point de vue informatique (ISO
12967-3:2009)
Ta slovenski standard je istoveten z: EN ISO 12967-3:2011
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.

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

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, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom.

EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION

EUROPÄISCHES KOMITEE FÜR NORMUNG

Management Centre: Avenue Marnix 17, B-1000 Brussels
© 2011 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN ISO 12967-3:2011: E
worldwide for CEN national Members.

Contents Page
Foreword .3

Foreword
The text of ISO 12967-3:2009 has been prepared by Technical Committee ISO/TC 215 “Health informatics” of
the International Organization for Standardization (ISO) and has been taken over as EN ISO 12967-3:2011 by
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 September 2011, and conflicting national standards shall be
withdrawn at the latest by September 2011.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. CEN [and/or CENELEC] shall not be held responsible for identifying any or all such patent rights.
This document supersedes EN 12967-3:2007.
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, Romania, Slovakia, Slovenia, Spain,
Sweden, Switzerland and the United Kingdom.
Endorsement notice
The text of ISO 12967-3:2009 has been approved by CEN as a EN ISO 12967-3:2011 without any
modification.
INTERNATIONAL ISO
STANDARD 12967-3
First edition
2009-08-15
Health informatics — Service
architecture —
Part 3:
Computational viewpoint
Informatique de santé — Architecture de service —
Partie 3: Point de vue informatique

Reference number
ISO 12967-3:2009(E)
©
ISO 2009
ISO 12967-3:2009(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.

©  ISO 2009
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2009 – All rights reserved

ISO 12967-3:2009(E)
Contents Page
Foreword .iv
Introduction.v
1 Scope.1
2 Normative references.2
3 Terms and definitions .2
4 Abbreviations.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 Interaction.5
6 General characteristics of the model .5
6.1 The two types of computational objects for handling the information .5
6.2 The basic methods .6
6.2.1 General requirement.6
6.2.2 “Add” basic methods.7
6.2.3 “Update” basic methods.8
6.2.4 “Delete” basic methods.10
6.2.5 “Detail” basic methods.11
6.2.6 “List” basic methods .13
6.3 General purpose interface.15
6.3.1 General.15
6.3.2 List of methods.15
6.3.3 Behavioural specifications.16
6.4 The complex interfaces of the workflow related computational objects.16
6.4.1 General.16
6.4.2 Complex services managing healthcare workflows .16
6.4.3 Interfaces supporting the “Subject of care workflow” .16
6.4.4 Interfaces supporting the “Clinical information workflow” .18
6.4.5 Interfaces supporting the “Activity management workflow”.19
6.4.6 Behavioural specifications, common to the complex services.22
6.5 Common requirements of the interfaces .23
6.5.1 Interface documentation and organization.23
6.5.2 Naming criteria.23
6.5.3 Data types.24
6.5.4 Structure and organization of the interfaces.24
Annex A (informative) Examples of services .25
Bibliography.27

ISO 12967-3:2009(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.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards
adopted by the technical committees are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the member bodies casting a vote.
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.
ISO 12967-3 was prepared by Technical Committee ISO/TC 215, Health informatics, based on the European
Standard EN 12967-3:2007 with minor editorial amendments.
ISO 12967 consists of the following parts, under the general title Health informatics — Service architecture:
⎯ Part 1: Enterprise viewpoint
⎯ Part 2: Information viewpoint
⎯ Part 3: Computational viewpoint
iv © ISO 2009 – All rights reserved

ISO 12967-3:2009(E)
Introduction
ISO 12967 is a multi-part standard that 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 middleware), distinct from individual applications and accessible
throughout the whole information system through services, as shown in Figure 1.
Applications
Scope of the
standard
Middleware of objects
integrating common data and common business logic

Figure 1 — Scope of this International Standard
[10] [11][12][13]
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 must be supported by the information
and functionality of the middleware. 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 middleware to integrate the common enterprise data and to support the enterprise requirements
formalized in ISO 12967-1. It also provides guidance on how one individual enterprise can extend the
standard 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 services that must be provided by
the middleware for allowing access to the common data as well as 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 services needed to support
local specific requirements in terms of common business logic to be implemented.
Computational viewpoint is specified in this part of ISO 12967.

INTERNATIONAL STANDARD ISO 12967-3:2009(E)

Health informatics — Service architecture —
Part 3:
Computational viewpoint
1 Scope
HISA specifies fundamental requirements for 'information infrastructure' and healthcare specific middleware
services.
This part of ISO 12967 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 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 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 which 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 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
middleware.
Preserving consistency with the provisions of this part of ISO 12967, physical implementations shall allow
extensions to the standard computational model in order to support additional and local requirements.
Extensions shall include both the definition of additional properties in the objects of the standard model and
the implementation of entirely new objects.
Also this standard specification shall be extendable over time according to the evolution of the applicable
standardization initiatives. The specification of extensions shall be carried out according to the methodology
defined in Clause 7 of ISO 12967-1:2009, which identifies a set of healthcare common information services,
describing their need and the methodology through which they will be used. These are only the minimal
identifiable set of services according to the needs of the healthcare enterprise, and constituting the
"middleware" platform (i.e. integration platform) to serve as the basis for healthcare applications, e.g. EHR or
patient administration.
ISO 12967-3:2009(E)
2 Normative references
The following referenced documents are indispensable for the application 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:2009, Health informatics — Service architecture — Part 1: Enterprise viewpoint
ISO 12967-2:2009, Health informatics — Service architecture — Part 2: Information viewpoint
3 Terms and definitions
For the purposes of this document the following terms and definitions apply.
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
4 Abbreviations
EHR Electronic Health Record
HISA Health Informatics Service Architecture
ODP Open Distributed Processing
UML Unified Modelling Language
5 Methodological principles
5.1 General
This part of ISO 12967 encompasses the computational viewpoint, which is concerned in answering HISA
middleware design aspects through the functional decomposition of the system into a set of computational
objects that interact at interfaces, also enabling distribution. The Health Informatics Service Architecture 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 HISA standard by both developers and end
users. It has described the scope of the business objects from the organization's viewpoint, by summarising
the related user activities and requirements through natural language. During this process the main healthcare
common clusters of objects have been identified:
1) Subject of care objects
These objects handle the information necessary for supporting the users’ activities identified in the
“Subject of Care workflow” of ISO 12967-1.
2 © ISO 2009 – All rights reserved

ISO 12967-3:2009(E)
2) Activity management objects
These objects handle the information necessary for supporting the users’ activities identified in the
“Activity Management workflow” of ISO 12967-1.
3) Clinical information objects
These objects handle the information necessary for supporting the users’ activities identified in the
“Clinical Information workflow” of ISO 12967-1.
4) Users and authorization objects
These objects handle the information necessary for supporting the users’ activities related to the
management of users and authorizations, as identified in ISO 12967-1.
5) Resources objects
These objects handle the information necessary for supporting the users’ activities related to the
management of resources, as identified in ISO 12967-1.
6) Classification objects
These objects handle the information necessary for supporting the users’ activities related to the
management of classifications, coding criteria and dictionaries, as identified in ISO 12967-1.
7) Messaging objects
These objects handle the information necessary for supporting the structuring of data and the
communications with other systems through messaging mechanisms, as identified in ISO 12967-1.
ISO 12967-2 has formalized the conceptual model of the information being manipulated by the services,
arising 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 part of ISO 12967 defines the computational model, composed of computational objects, capable of
meeting the requirements described in ISO 12967-1. It is necessary here to identify its relationship to the
information model, and the interfaces or access mechanisms it provides to access the information handled by
the system, which below are also referred to as methods or services.
The individual methods 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 part of ISO 12967 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:
⎯ 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:2009(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 interfaces that comprise all interfaces of the 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);
⎯ complex, higher-level computational objects providing interfaces achieving higher-level complex 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 complex business logic on possibly multiple information objects within the same operation. Such more
complex business logic is described in ISO 12967-1 and has to do with the main workflow processes
(i.e. patient management, activity management, etc.).
NOTE The term patient is used in this specification as a synonym of subject of care as has been done in the other
parts of ISO 12967.
The basic computational objects, corresponding one to one to the information objects, will be equipped with
standard lower-level basic interfaces having the scope of adding, updating and deleting – in short maintaining,
listing, and getting one instance of the main classes described in the information viewpoint. These basic
methods allow the access to and the manipulation of each element of the underlying model and secure the
openness of the system.
Figure 2 shows an example.
Get List of.
Get Full Data of one.
Update one.
Figure 2 — Example of "basic services"
NOTE 1 The actual basic services that shall be available for HISA objects are detailed in 6.2.
The higher-level computational objects implement more complex business transactions on the objects of the
information model, simplifying and ensuring consistency of developments and building common fundamental
procedures of the organization.
EXAMPLES:
Patient/person area, including registering a person, patient administration, merging patient identifiers, period of care, etc.;
Activity management and life cycle, including requests, planning, booking, etc.;
Clinical and EHR, including terminologies, classifications, problem-orientation, etc.;
Resource management, including standard usages, etc.
4 © ISO 2009 – All rights reserved

ISO 12967-3:2009(E)
relative to
relative to
Person
Person
SubjectOfCare Agent
SubjectOfCare Agent
? ccaareredd by by
HealthcareProvider
HealthcareProvider
ClinicalInformation
ClinicalInformation
Figure 3 — Example of "complex services"
NOTE 2 The actual complex services that shall be available for HISA objects are detailed in 6.4.
The HISA middleware 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 middleware component, and are related to general-purpose issues like session
management (logging in and out of the system, setting system variables, etc.), transaction management, etc.
These services will be provided by at least a further computational object equipped with appropriate methods,
namely the general purpose interface.
5.5 Interaction
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, 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 part of ISO 12967. Thus,
the role is always “server”.
NOTE Of the three types of interaction or operation are the ones that present a 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.
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
“complex” computational objects according to the terminology adopted in 5.4. The methods that these will
expose shall also be referred to in the following as “basic” and “complex”.
ISO 12967-3:2009(E)
<>
HISAObject
<> <>
HISAComplex HISABasic
Figure 4 — types of computational object

6.2 The basic methods
6.2.1 General requirement
For each class belonging to the seven clusters of objects defined in ISO 12967-1 and specified in the
information viewpoint the middleware shall be equipped with a computational object in turn equipped with a
set of methods allowing to access and to manipulate every concept (i.e. objects and properties) of the class,
the generic structure of which is displayed in Figure 5.

next version >
0.1
0.1
Generic HISA 0.*
State changes
class
0.*
0.*
0.*
0.* 0.1 Structured
Extended attributes
Classification criteria
Business rules
classified attribute >
attributes set
0.*
1 1
Class-specific
Common
attributes set
attributes set
1 1
Version System
attributes set attributes set
HISA Concept class
Figure 5 — Generic structure of the computational objects

The following methods shall be available in the basic computational objects. Each method has a scope and a
description. Many of the method specification tables also include an example.
6 © ISO 2009 – All rights reserved

< classified through
ISO 12967-3:2009(E)
6.2.2 “Add” basic methods
6.2.2.1 General
The “add” methods shall allow the client of the computational object to create instances of HISA objects.
6.2.2.2 List of methods
6.2.2.2.1 Method add
Method add
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 Clause 7
of ISO 12967-2:2009. The instance, its class-specific attribute set, and the common system and
version properties shall be created through this method.
Example The addition of a new person in the system shall be accomplished by calling the add method 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 method
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 Method Xadd
Method Xadd
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 6.3.7 of
ISO 12967-2:2009. The instances to which the extended data shall be attached are the individual HISA
classes specified in Clause 7 of ISO 12967-2:2009. The extended data properties and the common
system and version properties it comprises shall be created through this method.
Example The calling of this method [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 Method Cadd
Method Cadd
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 6.3.10 of
ISO 12967-2:2009s standard. The instances to which the classification data shall be attached are the
individual HISA classes specified in Clause 7 ISO 12967-2:2009. The classification data properties and
its common system and version properties shall be created through this method.
Example Persons might be classified in healthcare organizations according to their education. The calling of this
method [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:2009(E)
6.2.2.2.4 Method BRadd
Method BRadd
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 6.3.9 of ISO 12967-2:2009.
The instances to which the business rule data shall be attached are the individual HISA classes
specified in Clause 7 of ISO 12967-2:2009. The business rule properties and its common system and
version properties shall be created through this method.
Example As happens in Denmark, experimental drugs are used in some treatments and need specific business
rules to be identified 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 method [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 6.3.8 of ISO 12967-2:2009.
⎯ Method 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.
⎯ Method 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 methods
6.2.3.1 General
The “update” methods shall allow the client of the operation to update instances of HISA objects.
6.2.3.2 List of methods
6.2.3.2.1 Method update
Method update
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 Clause 7 of
ISO 12967-2:2009. The instance, its class-specific attribute set, and the common system and version
properties shall be updated through this method.
Example The updating of a person in the system shall be accomplished by calling the update method of the
person computational object [Person.update]. The method shall also allow the user to pass information
to override any default value for its common system and version-related attributes.
8 © ISO 2009 – All rights reserved

ISO 12967-3:2009(E)
6.2.3.2.2 Method Xupdate
Method Xupdate
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 individual
HISA classes specified in Clause 7 of ISO 12967-2:2009. The extended data object and its common
system and version properties shall be updated through this method.
Example The updating of the properties of the extended data of a person in the system shall be accomplished
by calling the update method of the person computational object [Person.Xupdate]. The method 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 Method Cupdate
Method Cupdate
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 Clause 7 of ISO 12967-2:2009. The classification object and its common
system and version properties shall be updated through this method.
Example The updating of the classification criteria of a person in the system shall be accomplished by calling the
update method of the person computational object [Person.Cupdate]. The method 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 Method BRupdate
Method BRupdate
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 6.3.8 of ISO 12967-2:2009. The
instances to which the business rule data shall be attached are the individual HISA classes specified in
Clause 7 of ISO 12967-2:2009. The business rule properties and its common system and version
properties shall be updated through this method.
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 method [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. In particular the following.
⎯ Operation shall require as input the common attributes necessary for the update information.
⎯ Instance identifier shall never be updated.
⎯ Update shall not occur if the timestamp of the instance to be updated differs from the timestamp received
as input, since this indicates that the value in the HISA system has changed since the client originally
read the instance from the system. The change occurred while the caller was performing the operation
and the update would cause inconsistency in the common information heritage.
NOTE Such an approach in managing concurrent access to data is generally called “optimistic-locking”.
ISO 12967-3:2009(E)
⎯ System shall take care of managing state changes when the update operation is invoked 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 attached to it are updated, thus
keeping track of the life cycle of the instance during time. The state changes class is specified in 6.3.8 of
ISO 12967-2:2009.
⎯ Operations shall return to the client at least the set of common attributes related to the HISA object
updated with the update operation. Such information shall include a value indicating successful execution
of the operation or an error indicating the reason for failure.
⎯ operations 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.4 “Delete” basic methods
6.2.4.1 General
The “delete” methods shall allow the client of the operation to logically delete instances of HISA objects.
6.2.4.2 List of methods
6.2.4.2.1 Method delete
Method delete
Scope Shall be used to delete an existing instance of a HISA object.
Description The instances that shall be deleted are the individual HISA classes specified in Clause 7 of
ISO 12967-2:2009f. The object, its class-specific attribute set, and its common system and version
properties shall be deleted through this method.
6.2.4.2.2 Method Xdelete
Method Xdelete
Scope Shall be used to logically delete an existing instance of the extended data associated to a HISA object.
Description The extended data instances that are deleted shall be the ones already attached to the individual HISA
classes specified in Clause 7 of ISO 12967-2:2009. The extended data object and
...