ISO/TR 14639-2:2014

TECHNICAL ISO/TR
REPORT 14639-2
First edition
2014-10-01
Health informatics — Capacity-based
eHealth architecture roadmap —
Part 2:
Architectural components and
maturity model
Informatique de santé — Feuille de route de l’architecture de santé
électronique fondée sur la capacité —
Partie 2: Composants architecturaux et modèle de maturité
Reference number
©
ISO 2014
© ISO 2014
All rights reserved. Unless otherwise specified, 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
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 2014 – All rights reserved

Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Terms and definitions . 2
3 Abbreviations.12
4 Overview of business requirements .13
5 Development and application of eHealth enterprise architectures .13
5.1 eHealth enterprise architectures .13
5.2 Development of an eHealth architecture .13
5.3 Building up the architecture: A methodology .14
6 Health architecture components and requirements .20
6.1 Governance and national ownership .22
6.2 Health process domain components .44
6.3 Foundation Components — eHealth infostructure .85
6.4 Foundation components — ICT infrastructure .100
7 Profiling countries with the eHAM .111
8 Future Considerations .115
Annex A (informative) World Economic Forum — Global Health Data Charter .117
Annex B (informative) Generic component model .121
Annex C (informative) Health informatics — Service architecture (HISA) .122
Annex D (informative) Candidate standards supporting eHealth Architecture Model and
Maturity Models .125
Annex E (informative) WHO Indicator and Measurement Registry (IMR) .128
Annex F (informative) Statistical Data and Metadata Exchange for the Health
Domain (SDMX-HD) .129
Annex G (informative) List of figures and tables in this part of ISO 14639 .132
Bibliography .133
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 on the meaning of ISO specific terms and expressions related to conformity
assessment, as well as information about ISO’s adherence to the WTO principles in the Technical Barriers
to Trade (TBT) see the following URL: Foreword - Supplementary information
The committee responsible for this document is ISO/TC 215, Health informatics.
ISO/TR 14639 consists of the following parts, under the general title Health informatics — Capacity-
based eHealth architecture roadmap:
— Part 1: Overview of national eHealth initiatives
— Part 2: Architectural components and maturity model
iv © ISO 2014 – All rights reserved

Introduction
ISO/TC 215 has identified that there is an urgent need to provide International Standards for health
information architectures that includes requirements tailored also to low- and middle-income countries
with relatively immature resources available. A Public Health Task Force of international experts,
established by TC 215, has developed a report outlining the challenges these countries face and some of
the relevant standardization strategies.
This part of ISO/TR 14639 provides a guide to best practice business requirements and principles for
planning the use of information and communications technology (ICT) to support the development,
coordination, and delivery of healthcare services by countries and subordinate health authorities within
a country.
One of the activities motivating this work originates from a meeting in March 2010, in Bellagio, Italy to
[10]
explore how the “digital divide” between high-income and low-income countries could be addressed.
The following observations were noted.
a) There is a surge of interest in the development of eHealth infostructure to support effective Health
Information Systems (HIS) in low-income countries, including responding to disease outbreaks,
monitoring the health status of the population, and improving both public and individual health.
b) Health informatics International Standards help countries to make the proper decisions regarding
their eHealth architecture such that they can strengthen their health systems. HIS architectures
that are non-proprietary and based on International Standards are likely to be more robust and
future-proof.
c) The use of health informatics International Standards in low-income countries is hampered due
to lack of knowledge and awareness about appropriate standards, affordable access to standards
and implementation guides, and little participation in Standards Development Organization (SDO)
activities due to little or no funding to support such engagement.
d) Existing international health informatics International Standards insufficiently address the
needs of low-income countries (LICs) for developing their monitoring, public health, and patient
care systems. An example of this is mobile computing and the use of SMS for transmitting patient
information, reminders, and alerts. Thus, the participation of LICs in the International Standards
development process is essential.
e) Participation in ISO activities requires a national standards organization or government department
as an official member of ISO.
f) Development of International Standards has a cost. A significant amount of money and time needs
to be invested in preparation of documents, commenting on proposals, and participation in SDO
meetings and for adopting, adapting, and localization of standards. These costs represent a genuine
barrier to the participation of low-income countries.
g) Access to International Standards also comes with a cost that is often prohibitive for people and
organizations in low-income countries.
h) There is recognition that the business model of some SDOs is based on the sale of International
Standards to support the standards development process and operating expenses.
i) HIS strengthening can be promoted by using commonly shared International Standards to carry out
Monitoring and Evaluation (M & E) activities for government bodies, international organizations,
donors, and other interested parties.
j) There are duplications and overlaps in health informatics International Standards across multiple
SDOs. Low-income countries require a single set of usable International Standards based on the
work of ISO/TC 215, HL7, and CEN/TC 251 Joint Initiative Council (JIC) to harmonize International
Standards and facilitate the global, international adoption, and adaption of organizational and
regional standards based on the ISO standards process.
k) Promotion of International Standards worldwide is consistent with the ISO mission yet barriers
exist to the achievement of this objective.
While not all of these observations are addressed within the scope of this Technical Report, the report
is an attempt to respond to some of these observations, providing a robust framework for low-income
countries for their eHealth architecture planning and health system development. The other items are
intended to be addressed in due course.
This part of ISO/TR 14639 examines various activities and associated criteria for the effective use of
information and communication technology (ICT) in support of health service delivery, planning, and
coordination. It aims to provide relevant guidance on uses of information, based on model criteria by
which development of eHealth capability can be planned and progress toward its mature use can be
assessed.
In preparing this part of ISO/TR 14639, the original aim was to provide guidance for developing
and emerging countries and for the many international groups that conduct health programs in the
developing and emerging world. As the work proceeded, it became clear that the work is more widely
applicable to all health services and that there are potential lessons for all as they examine the way in
which information is produced, managed, and used in various aspects of their work. The identification
of relevant health informatics standards and the role of international standardization in support of
eHealth were also important drivers.
This part of ISO/TR 14639 builds on lessons from many countries, including those whose activities are
summarized in ISO/TR 14639-1 and was, in large part, inspired by experience with the Health Metrics
Network (WHO/HMN Framework) activities sponsored by the World Health Organization (WHO).
The particular focus of this part of ISO/TR 14639 is the potential for ICT to assist in the collection,
communication, storage, processing, and use of information to support the delivery, planning, and
coordination of health services; however, it also recognizes the importance of initial measures that
involve paper-based collection and the need for a migration path from manual to semi-automated to
fully automated information management systems.
The enterprise-wide business reference architecture described in this part of ISO/TR 14639 represents a
starting point for the enterprise viewpoint or business layer of a comprehensive enterprise architecture,
which would include other layers or viewpoints, such as the information/data, computational/function,
engineering, and technology perspectives. This model would serve, for example, to assist in identifying
initiatives and exploring the attributes of the components that would form a national eHealth strategy.
A comprehensive enterprise architecture is typically set up and maintained using a structured process
that involves the following:
a) an organized approach to ensuring that investments in ICT technology and information systems
meet overall priorities for effective operation and delivery of healthcare services and the information
needed for their planning, development, and continuous improvement;
b) identifying and describing the main attributes of the eHealth information services, components,
activities, and policies needed to support the operational requirements for health services within a
jurisdiction (or organization);
c) development of structured requirements for more detailed planning and investment in health
information systems and for the development and dissemination of health information policies.
Where relevant, this part of ISO/TR 14639 takes advantage of and makes reference to the principles,
policies, and specifications set out in relevant International Standards and existing architectural
frameworks commonly used in the health sector including: ISO 12967, Health Informatics Service
[1][2][3]
Architecture (HISA), the vision and principles of the World Economic Forum (WEF) Global Health
[4] [5]
Data Charter as seen in Annex A, and the Health Enterprise Architecture Framework (HEAF).
A layered approach to structuring of information architectures and models is proposed in this part
of ISO/TR 14639, based on similar approaches such as the General Component Model introduced in
vi © ISO 2014 – All rights reserved

[6] [7] [8] [9]
Annex B, the WHO Health Metrics Network Framework, TOGAF, and the Zachman framework.
In particular, HISA and the HEAF have been developed specifically to assist in the process of defining
eHealth architectures for use in health services. See Annex C for more information on HISA. A short list
of selected health informatics International Standards upon which the architectural components are
based is found in Annex D. See 6.1.4 regarding governance and national ownership of eHealth standards
adoption and implementation.
[93]
In May 2012, WHO and ITU published a National eHealth Strategy Toolkit that embodies most of the
concepts relevant to an Enterprise Architecture, tailored to the creation of a National eHealth Strategy.
This resulted in a process that is exhaustive yet streamlined and easier to understand and apply. The
Toolkit presents a thorough step-by-step set of methods, checklists, and examples to be used by country
or region-level managers when developing an eHealth Strategic Vision, an eHealth Action Plan, and a
Monitoring and Evaluation Plan. The WHO-ITU National eHealth Strategy Toolkit and ISO/TR 14639-1
and this part of ISO/TR 14639 form a complementary set of tools for the design and deployment of an
eHealth architecture.
The architectural components and their characteristics as described in this part of ISO/TR 14639
are designed to be reviewed and, where appropriate, adopted by countries and subordinate health
authorities at a level relevant to their specific needs. In particular:
a) The components and characteristics may be used as model requirements in developing enterprise
architectures or as a means of assessing and improving eHealth maturity.
b) Each component is configurable to meet local needs by describing characteristics indicative of a
range of capability from the most basic through to the highly advanced.
c) The characteristics of various capacity levels for each component form the basis of the underlying
maturity model.
d) Typical starting points for the development of capability are provided for each of the components at
the lowest maturity level, together with the basic principles the architecture should adhere to.
e) There is an emphasis on developing appropriately layered, well-structured eHealth architectures
with well-defined and preferably standardized interfaces between the various components and
layers.
f) There is a particular focus on potential eHealth requirements relevant to low- and middle-income
(LMIC) countries.
TECHNICAL REPORT ISO/TR 14639-2:2014(E)
Health informatics — Capacity-based eHealth architecture
roadmap —
Part 2:
Architectural components and maturity model
1 Scope
This part of ISO/TR 14639 provides a guide to best practice business requirements and principles for
countries and their subordinate health authorities planning and implementing the use of information
and communications technology (ICT) to support the delivery and development of healthcare. A business
reference architecture is described in terms of components and capabilities that health authorities may
use as a framework for building their own eHealth architectures and also for measuring the maturity of
their health systems’ use of ICT to support the delivery and development of healthcare.
It is worth noting that while this part of ISO/TR 14639 was developed with a particular view to support
low- and middle-income countries, it can also be a useful guide for any country. Even if maturity is high
in some aspects, highly developed countries may still need advice on architectural components for some
aspects of a total eHealth system.
The development of eHealth architectures based on the guidelines set out in this part of ISO/TR 14639
will facilitate and optimize investments in Health Information Systems to achieve the following goals:
a) information being used cost-effectively for improvement of health services;
b) health information being harmonized, consistent, accessible, and able to be used effectively;
c) patients, health professionals, and policy-makers having the right data available to make decisions
about health services, treatment, and delivery of care;
d) appropriate information being available to support evidence-based practice and health services
planning, health services quality, and safety and to improve public health;
e) improving accessibility to healthcare services;
f) supporting harmonization of Health Information Systems and health information standards.
It is envisaged that this part of ISO/TR 14639 will be a valuable source of information for
g) personnel responsible for health services policy, planning, and provision,
h) those developing health information resources and eHealth policy at national and subordinate
levels in a country,
i) non-governmental organizations (NGOs) and others seeking to support or implement systems for
information gathering, statistics, and care delivery in developing and emerging economies,
j) developers and implementers of Health Information Systems and services,
k) academic and research institutions and students in health informatics, and
l) other stakeholders in the health sector.
This part of ISO/TR 14639 also proposes a maturity model and methodology that organizations may
consider in developing and evolving their eHealth capacities in specified areas of operational capability
from low to medium to high levels. The proposed business reference architecture identifies components
and capabilities needed to support various health service activities along with the governance,
infostructure, and ICT infrastructure that is necessary for the effective and efficient use of information
in the delivery and development of health services.
2 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
2.1.1
architecture system
structure of components, their functions, and their inter-relationships and the principles and
guidelines governing their design and evolution over time
[SOURCE: Adapted from Open Group Architecture Framework (TOGAF), 2009.]
2.1.2
architecture system
description of the structure and behaviour of a system, a system’s components, its functions and
inter-relationships
[SOURCE: Adapted from Blobel B., Application of the Component Paradigm for Analysis and Design of
Advanced Health System Architectures, 2000.]
Note 1 to entry: See definition of system architecture (2.74).
2.2
business reference architecture
reference architecture that is evolved based on a set of identified, high-level business requirements
(functional, non-functional, and relevant supporting processes) for an enterprise, which the overall
enterprise strategy and its infrastructure (business and IT) must support
[SOURCE: Adapted from IBM Tivoli Reference Architectures and the SKMT definitions of business
architecture from Canada Health Infoway.]
Note 1 to entry: This architecture also needs to take into consideration the “wants and needs” of the clients
served that may not map exactly to business drivers but nonetheless offer functional value to clients. It is the
business “blueprint” for how a technical project will roll out and what it is trying to accomplish.
Note 2 to entry: See definition of reference architecture (2.65).
2.3
care plan
personalized statement of planned healthcare activities relating to one or more specified health issues
[SOURCE: EN 13940-1:2007]
2.4
chronic disease
health condition of 3 months duration or longer
[SOURCE: U.S. Centers for Disease Control and Prevention (CDC) National Center for Health Statistics]
2.5
classification
terminology which aggregates data at a prescribed level of abstraction for a particular domain
[SOURCE: ISO/TS 17117:2002]
2.6
client
person receiving social or medical services
2 © ISO 2014 – All rights reserved

2.7
clinical data warehouse
CDW
grouping of data pertaining to a health system or sub-system, possibly of diverse sources, accessible
by a single data management system that enables secondary data analysis for questions relevant to
understanding the functioning of that health system or sub-system, and hence supporting proper
maintenance and improvement of that system or sub-system
[SOURCE: Adapted from ISO/TR 22221:2006.]
Note 1 to entry: A CDW tends not to be used in real-time; however, depending on the rapidity of transfer of data to
the data warehouse and data integrity, near real-time applications are not excluded.
2.8
clinical decision support
type of system that assists healthcare providers in making medical decisions
[SOURCE: Health Level Seven International (HL7)]
Note 1 to entry: These types of systems typically require input of patient-specific clinical variables and, as a
result, provide patient-specific recommendations.
2.9
clinical information
information about a person, relevant to his or her health or healthcare
[SOURCE: ISO 13606-1:2008]
2.10
clinical process
set of interrelated or interacting healthcare activities performed by one or more healthcare professionals
[SOURCE: ISO 18308:2011]
2.11
clinical vocabulary
system of standardizing the terms used in describing client-centred health and health service-related
concepts
[SOURCE: ISO/TS 22789:2010]
2.12
community-based services
blend of health and social services provided to an individual or family at his/her place of residence or
at other non-institutional locations within the community for the purposes of promoting, maintaining,
or restoring health, minimizing the effects of illness and disability, and supporting and facilitating self-
help and self-care
[SOURCE: Adapted from WHO 2004 A Glossary of Terms for Community Healthcare and Services for
Older Persons.]
Note 1 to entry: Services and programs can include visiting nurses, delivered meals, home care, palliative care,
community mental health, health education, screening, immunizations, family planning, sexual health, etc.
2.13
country income
classification of all World Bank member countries and all other economies with populations of more
than 30,000 (213 total)
[SOURCE: World Bank Country Classification]
Note 1 to entry: Economies are divided according to 2009 GNI per capita, calculated using the World Bank Atlas
method. The groups are: low income, $995 or less; lower middle income, $996 to $3,945; upper middle income,
$3,946 to $12,195; and high income, $12,196 or more.
2.14
data warehouse
grouping of data, possibly of diverse courses, pertaining to a system or sub-system, accessible by a single
data management system that enables secondary data analysis for questions relevant to understanding
the functioning of that system or sub-system, and hence supporting its proper maintenance and
improvement
[SOURCE: Adapted from ISO/TR 22221:2006.]
Note 1 to entry: A data warehouse tends not to be used in real-time; however, depending on the rapidity of transfer
of data to the data warehouse and data integrity, near real-time applications are not excluded.
2.15
eHealth
use of information and communication technologies (ICT) for health
[SOURCE: World Health Organization (WHO) eHealth]
Note 1 to entry: In its broadest sense, eHealth is about improving the flow of information, through electronic
[93]
means, to support the delivery of health services and the management of health systems.
Note 2 to entry: Health and health-related fields include healthcare services, health surveillance, health literature,
[26]
and health education, knowledge, and research.
2.16
eHealth architecture
architecture of a system of eHealth components and services
[SOURCE: ISO 18308:2011]
2.17.1
electronic health record
EHR
information relevant to the wellness, health, and healthcare of an individual, in computer-
processable form and represented according to a standardized information model
[SOURCE: ISO 18308:2011]
2.17.2
electronic health record
EHR
longitudinal electronic record of an individual that contains or virtually interlines to data in
multiple EMRs and EPRs, which is to be shared and/or interoperable across healthcare settings and is
patient-centric
[SOURCE: Adapted from ISO 18308:2011.]
Note 1 to entry: EHRs often capture data from multiple point-of-service systems and enable authorized access by
the various providers of care to pertinent patient data across multiple service delivery locations or organizations
in order to ensure continuity of care for the patient.
4 © ISO 2014 – All rights reserved

2.18
electronic health record architecture
EHRA
formal description of a system of components and services for recording, retrieving, and handling
information in electronic health records
[SOURCE: ISO 18308:2011]
2.19
electronic medical record
EMR
electronic record of an individual in a physician’s office or clinic, which is typically in one setting and is
provider-centric
[SOURCE: European 2011 eHealth Strategies Final Report, January 2011]
2.20
enterprise architecture
EA
rigorous description of the structure of an enterprise, which comprises enterprise components
(business entities), the externally visible properties of those components, and the relationships (e.g. the
behaviour) between them
[SOURCE: Blobel B. Architectural; Methods Inf Med 2010 — modified]
Note 1 to entry: An enterprise architecture describes the terminology, the composition of enterprise components,
and their relationships with the external environment and the guiding principles for the requirements (analysis),
design, and evolution of an enterprise. This description is comprehensive, including enterprise goals, business
processes, roles, organizational structures, organizational behaviours, business information, software
applications, and computer systems.
2.21
health
state of complete physical, mental, and social well-being and not merely the absence of disease or
infirmity
[SOURCE: World Health Organization (WHO)]
2.22
health condition
aspect of a person or group’s health that requires some form of intervention
Note 1 to entry: These interventions could be anticipatory or prospective, such as enhancing wellness, wellness
promotion, or illness prevention (e.g. immunization).
[SOURCE: ISO/TR 12773-2:2009]
2.23
health information
information about a person relevant to his or her health
[SOURCE: ISO 18308:2011, 3.28]
2.24
health information system
HIS
system that combines vital and health statistical data from multiple sources to derive information and
make decisions about health needs, health resources, health costs, uses of health services, and outcomes
of healthcare
[SOURCE: Adapted from Canada Health Infoway, pan- Canadian Standards Electronic Drug Messaging
(CeRx) Standards 1 −2010/03/29.]
2.25
health infostructure
foundational and up-to-date information and communications technologies (ICTs) developed, adopted,
and implemented in the healthcare system to allow people (the general public, patients, and caregivers,
as well as healthcare providers, health managers, health policymakers, and health researchers) to
communicate with each other and assist them to make informed decisions about their own health, the
health of others, and the health system
[SOURCE: Adapted from Canada’s Health Infostructure, Health Canada.]
2.26
health issue
issue related to the health of a subject of care, as identified or stated by a specific healthcare party
[SOURCE: EN 13940-1:2007]
2.27
health record extract
attestable unit of communication of all or part of a health record
[SOURCE: ISO/TR 12773-2:2009]
2.28
health summary record
HSR
health record extract comprising a standardized collection of clinical and contextual information
(retrospective, concurrent, prospective) that provides a snapshot in time of a subject of care’s health
information and healthcare
[SOURCE: ISO/TR 12773-2:2009]
2.29
health system
combination of components, activities, processes, and policies intended to promote, restore, and
maintain health
[SOURCE: Adapted from WHO Health System Strengthening Glossary.]
2.30
health worker
person engaged in actions that are primarily intended to enhance health
[SOURCE: Adapted from World Health Report, January 01, 2006.]
Note 1 to entry: This term also includes healthcare worker.
2.31
healthcare
activities, services, or supplies related to the health of an individual
[SOURCE: EN 13940-1:2007]
2.32
healthcare activity
activity performed for a subject of care with the intention of directly or indirectly improving or
maintaining the health of that subject of care
[SOURCE: EN 13940-1:2007]
6 © ISO 2014 – All rights reserved

2.33
healthcare professional
person authorized to be involved in the direct provision of certain healthcare provider activities in a
jurisdiction according to a mechanism recognized in that jurisdiction
[SOURCE: Adapted from EN 13940–1:2007]
2.34
healthcare provider
healthcare professional or an organization involved in the direct provision of healthcare
[SOURCE: EN 13940-1:2007]
2.35
high-income country
HIC
country with a gross national income per capita of USD 12 746 or more
[SOURCE: World Bank Country Classification]
Note 1 to entry: A HIC is part of the classification system of all World Bank member countries (187) and all other
economies with populations of more than 30,000 (213 total). Economies are divided according to 2009 GNI per
capita, calculated using the World Bank Atlas method. The groups are: low income, $995 or less; lower middle
income, $996 to $3,945; upper middle income, $3,946 to $12,195; and high income, $12,196 or more.
2.46
HL7 clinical document architecture
CDA
documentation that defines structure and semantics of medical documents for the purpose of exchange
[SOURCE: ISO/TR 18307:2001]
Note 1 to entry: CDA documents are encoded in extensible mark-up language (XML). They derive their meaning
from the HL7 Reference Information Model (RIM) and use the HL7 Version 3 Data Types, which are part of the
HL7 RIM.
2.47
HL7 v2.x (version 2.x)
series of electronic messages to support administrative, logistical, financial, as well as clinical processes,
[18][190]
and primarily uses a textual, non-XML encoding syntax based on delimiters
[SOURCE: Health Level Seven International]
2.48
hospital information system
system that is used by end-users at the point-of-care or service, in this instance, a hospital
[SOURCE: Adapted from Canadian definition of point-of-care or point-of-service system in the SKMT
Glossary Tool.]
2.49
integrated data repository
IDR
component of a health infostructure that maintains and manages the integrated common information
generated in real-time by consolidating data from a variety of clinical sources to present a unified view
(together with the related and required classifications, terminologies, ontologies, etc.), regarding the
core business of the healthcare enterprise
Note 1 to entry: An IDR is also a key component of enterprise architecture modelling. Enterprise architecture is
foundational for developing a health infostructure.
Note 2 to entry: The IDR can also be used for secondary purposes such as surveys, clinical research, statistics,
reporting, and analysis.
Note 3 to entry: See definitions of health infostructure and enterprise architecture from References [36] and [30].
2.50
integrated disease surveillance (Africa Region)
IDSR
strategy by WHO African Region that includes communicable and non-communicable health conditions
and events
[SOURCE: Integrated Disease Surveillance — WHO Regional Office for Africa]
2.51
interoperability
ability of two or more systems or components to exchange information and to use the information that
has been exchanged
Note 1 to entry: See semantic interoperability (2.70) and syntactic interoperability (2.73).
[SOURCE: ISO/TS 27790:2009, 3.39, modified to add note to entry]
2.52
low-income country
LIC
low-income country as defined by the World Bank where income is USD 1,005 gross national income
(GNI) per capita or less, calculated using the World Bank Atlas method
[SOURCE: Adapted from World Bank Country Classifications.]
Note 1 to entry: An LIC is part of the classification system of all World Bank member countries and all other
economies with populations of more than 30,000 (213 total). Economies are divided according to 2009 GNI per
capita, calculated using the World Bank Atlas method. The groups are: low income, $995 or less; lower middle
income, $996 to $3,945; upper middle income, $3,946 to $12,195; and high income, $12,196 or more.
2.53
maturity model
set of structured levels that describe how well the behaviours, practices, and processes of an organization
can reliably and sustainably produce required outcomes
2.54
middle-income country
MIC
middle-income country as defined by the World Bank country where income is between USD 1,005 and
12,275 gross national income (GNI) per capita or less, calculated using the World Bank Atlas method
[SOURCE: Adapted from World Bank Country Classifications]
Note 1 to entry: An MIC is part of the classification system of all World Bank member countries (187) and all other
economies with populations of more than 30,000 (213 total). Economies are divided according to 2009 GNI per
capita, calculated using the World Bank Atlas method. The groups are: low income, $995 or less; lower middle
income, $996 to $3,945; upper middle income, $3,946 to $12,195; and high income, $12,196 or more.
Note 2 to entry: The MIC group is also split into Lower-Middle and Upper-Middle, below and above US $3,975
respectively.
2.55
monitoring and evaluation
M & E
routine tracking of the key elements of program/project performance, usually inputs and outputs, through
record-keeping, regular reporting and surveillance systems, as well as health facility observation and
client surveys, and the episodic assessment of the change in targeted results that can be attributed to
the program or project/project intervention
[SOURCE: Global Fund for AIDS, Tuberculosis, and Malaria (GFATM) Monitoring and Evaluation]
8 © ISO 2014 – All rights reserved

2.56
notifiable disease
[40]
any disease that is required by law to be reported to government authorities
Note 1 to entry: The 2005 WHO International Health Regulations (IHR) provides a list of events that involves
cases of specific reportable diseases and reporting mechanisms.
2.57
organization
unique framework of authority within which a person or persons act or are designated to act towards
some purpose
[SOURCE: Adapted from ISO/IEC 6523-1:1998, 3.1.]
2.58
patient
individual who is a subject of care
[SOURCE: Adapted from ISO/TR 20514:2005, 2.30]
2.59
personal health information
information that concerns a person’s health, health history, health treatment, or genetic characteristics
in a form that enables the person to be identified
[SOURCE: Adapted from ISO/TR 18307:2001.]
2.60
personal health record
PHR
representation of information regarding or relevant to the health, including wellness, development, and
welfare of a subject of care, which may be stand-alone or integrating health information from multiple
sources, and for which the individual, or their authorized representative, manages and controls the PHR
content and grants permissions for access by and/or sharing with other parties
[SOURCE: ISO/IEC 2382-8:1998]
2.61
policy
rule or set of rules that speak to one or more legal, political, organizational, functional, business,
technical, or related matters that may be expressed as obligations, permissions, or prohibitions
[SOURCE: Adapted from ISO/TS 22600-1:2006, 2.13.]
2.62
primary care
first level of care (access to first contact), characterized mainly by longitudinality, comprehensiveness,
and coordination of care for the client within the overall health system
[SOURCE: Adapted from Starfield, B., Primary care: concept, evaluation and policy. New York, Oxford
University Press, 1992]
Note 1 to entry: May have additional features such as family counselling and community and cultural competence
2.63
privacy
freedom from intrusion into the private life or affairs of an individual when that intrusion results from
undue or illegal gathering and use of data about that individual
[SOURCE: ISO/IEC 2382-8:1998, 08.01.23]
2.64.1
Public health surveillance
systematic collection, analysis, interpretation, and follow-up of communicable or infectious
[24]
diseases
[SOURCE: SKMT Glossary Tool]
2.64.2
Public health surveillance
systematic collection, analysis and interpretation of health-related data needed for the planning,
[96]
implementation, and evaluation of public health practice
[SOURCE: WHO Health Topics — Public Health Surveillance]
Note 1 to entry: These activities are usually reactive in nature and can be used to track and monitor emerging
outbreaks of illness that may influence public health wellness.
2.65
reference architecture
in the field of software architecture or enterprise architecture, provides a proven template solution
for an architecture for a particular domain, as well as a common vocabulary with which to discuss
[13]
implementations, often with the aim of stressing commonality
2.66
register
formal or official recording of items, names, or actions
[SOURCE: ISO/IEC 10036:1996, 3.3]
Note 1 to entry: This data should be maintained electronically so that it is accessible by other systems.
2.67
registry
[97]
directory-like system that focuses solely on managing data pertaining to one conceptual entity
[SOURCE: Canada Health Infoway Registry Messaging Standards]
Note 1 to entry: In an interoperable Electronic Health Record (iEHR), the registries store, maintain, and provide
access to peripheral information not categorized as clinical in nature, but required to operationalize the EHR.
Note 2 to entry: The primary purpose of a Registry is to respond to searches using one or more pre-defined
parameters in order to find and retrieve a unique occurrence of an entity.
Note 3 to entry: Examples of registries include Client Registry, Provider Registry, Location Registry, and Consent
Registry.
2.68
roadmap
detailed plan to guide progress towards a goal
2.69
secure messaging
electronic communication between two parties that ensures only those parties can access the
[99]
communication.
[SOURCE: Centers for Medicare and Medicaid Services, USA]
Note 1 to entry: The electronic message could be email or the electronic messaging function of a PHR, an online
patient portal, or any other electronic means.
10 © ISO 2014 – All rights reserved

2.70
semantic interoperability
ability for data shared by systems to be understood at the level of fully defined domain concepts
[SOURCE: ISO 18308:2011, 3.45]
2.71
standard
document, established by consensus and approved by a recognised body that provides, for common and
repeated use, rules, guidelines, or characteristics for activities or their results, aimed at achievement of
the optimum degree of order in a given context
[SOURCE: ISO/IEC Guide 2:2004]
2.72
subject of care
person seeking to receive, receiving, or having received healthcare
[SOURCE: EN 13940-1:2007]
2.73
syntactic interoperability
capability of two or more systems to communicate and exchang
...