Health informatics - Service architecture - Part 3: Computational viewpoint (ISO 12967-3:2009)

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.

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)

L'ISO 12967-3:2009 spécifie les caractéristiques fondamentales du modèle de traitement qu'une couche architecturale spécifique (c'est-à-dire la couche interstitielle) du système d'informations doit mettre en place 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 place 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 place physique.

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

HISA določa temeljne zahteve za »informacijsko infrastrukturo« in za zdravstvo značilne storitve vmesne programske opreme.
Ta del ISO 12967 določa temeljne značilnosti računalniškega modela, namenjenega implementaciji z določeno arhitekturno plastjo informacijskega sistema (tj. vmesna programska oprema) za zagotavljanje celovitega in integriranega vmesnika do skupnih informacij podjetja in za podporo temeljnih poslovnih procesov zdravstvene organizacije, kot je določeno v ISO 12967-1. Računalniški model je določen brez kakršne koli eksplicitne ali implicitne predpostavke o fizičnih tehnologijah, orodjih ali rešitvah, privzetih za njegovo fizično implementacijo v različne ciljne scenarije. Kljub temu je specifikacija uradna, celovita in dovolj nedvoumna, da omogoča tistim, ki jo implementirajo, izpeljavo učinkovitega načrta sistema v določenem tehnološkem okolju, ki bo izbran za fizično implementacijo.
Računalniški model zagotavlja podlago za zagotavljanje skladnosti med različnimi inženirskimi in tehnološkimi specifikacijami (vključno s programskimi jeziki in komunikacijskimi mehanizmi), saj morajo biti skladne z enakim računalniškim predmetnim modelom. Ta skladnost omogoča odprto medsebojno delovanje in prenosljivost komponent v posledični implementaciji.
Specifikacija ne stremi k predstavitvi fiksne in celotne specifikacije vseh mogočih podatkov, ki so lahko potrebni za katero koli zahtevo katere koli zdravstvene organizacije. Določa samo sklop značilnosti glede na celotno organizacijo in posamične računalniške predmete, določene kot temeljne in skupne vsem zdravstvenim organizacijam, in da temu ustreza računalniški model, implementiran z vmesno programsko opremo.
Ohranjanje skladnosti z določbami tega dela ISO 12967 dopušča fizičnim implementacijam razširitve standardnega računalniškega modela, tako da podpira dodatne in lokalne zahteve.

General Information

Status
Withdrawn
Publication Date
12-Jun-2011
Withdrawal Date
01-Dec-2020
Technical Committee
Current Stage
9900 - Withdrawal (Adopted Project)
Start Date
01-Dec-2020
Due Date
24-Dec-2020
Completion Date
02-Dec-2020

RELATIONS

Buy Standard

Standard
SIST EN ISO 12967-3:2011 - BARVE str. 11
English language
35 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (sample)

SLOVENSKI STANDARD
SIST EN ISO 12967-3:2011
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
SIST EN ISO 12967-3:2011 en

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------
SIST EN ISO 12967-3:2011
---------------------- Page: 2 ----------------------
SIST EN ISO 12967-3:2011
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.
---------------------- Page: 3 ----------------------
SIST EN ISO 12967-3:2011
EN ISO 12967-3:2011 (E)
Contents Page

Foreword ..............................................................................................................................................................3

---------------------- Page: 4 ----------------------
SIST EN ISO 12967-3:2011
EN ISO 12967-3:2011 (E)
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.
---------------------- Page: 5 ----------------------
SIST EN ISO 12967-3:2011
---------------------- Page: 6 ----------------------
SIST EN ISO 12967-3:2011
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
---------------------- Page: 7 ----------------------
SIST EN ISO 12967-3:2011
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.

COPYRIGHT PROTECTED DOCUMENT
© 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
---------------------- Page: 8 ----------------------
SIST EN ISO 12967-3:2011
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 2009 – All rights reserved iii
---------------------- Page: 9 ----------------------
SIST EN ISO 12967-3:2011
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
---------------------- Page: 10 ----------------------
SIST EN ISO 12967-3:2011
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.
© ISO 2009 – All rights reserved v
---------------------- Page: 11 ----------------------
SIST EN ISO 12967-3:2011
---------------------- Page: 12 ----------------------
SIST EN ISO 12967-3:2011
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 2009 – All rights reserved 1
---------------------- Page: 13 ----------------------
SIST EN ISO 12967-3:2011
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
---------------------- Page: 14 ----------------------
SIST EN ISO 12967-3:2011
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 2009 – All rights reserved 3
---------------------- Page: 15 ----------------------
SIST EN ISO 12967-3:2011
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
---------------------- Page: 16 ----------------------
SIST EN ISO 12967-3:2011
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

...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.