Health informatics — Terminological resources — Part 3: Terminology implementation maturity model (TIMM)

The document defines the progression of implementation of terminology capability in information systems. This document does not specify requirements for any specific terminological resource. It is intended to provide a basis for conformance criteria for terminological resources capabilities in specific use cases. This document does not cover in detail the software being used, though the capabilities of that software are included and impact the level of maturity reached. This document is applicable to terminological resources of all types, terminologies, classifications, value sets, code systems, and value domains.

Informatique de santé — Ressources terminologiques — Partie 3: Modèle de maturité pour la mise en œuvre de la terminologie

General Information

Status
Published
Publication Date
04-Dec-2024
Current Stage
6060 - International Standard published
Start Date
05-Dec-2024
Due Date
05-Dec-2024
Completion Date
05-Dec-2024
Ref Project

Buy Standard

Technical specification
ISO/TS 17117-3:2024 - Health informatics — Terminological resources — Part 3: Terminology implementation maturity model (TIMM) Released:12/5/2024
English language
16 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


Technical
Specification
ISO/TS 17117-3
First edition
Health informatics —
2024-12
Terminological resources —
Part 3:
Terminology implementation
maturity model (TIMM)
Informatique de santé — Ressources terminologiques —
Partie 3: Modèle de maturité pour la mise en œuvre de la
terminologie
Reference number
© ISO 2024
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Terminology implementation maturity . 3
4.1 General .3
4.2 Purpose and audience .3
4.3 Implementation maturity levels .4
5 Pillar 1: Design of the data (data specifications) . 4
5.1 Terminological capabilities .4
5.1.1 General .4
5.1.2 Terminology resource selection .5
5.1.3 Data governance .7
5.1.4 Data dictionary .8
5.2 Maturity of terminology implementation within software product .8
5.2.1 Relationship to the information model .8
5.2.2 Software functionality .9
6 Pillar 2: Data capture (user interface) in healthcare implementations .10
6.1 Capability to display code system content .10
6.2 Capability of terminology tooling .11
6.3 Standards conformance . 12
7 Pillar 3: Data storage .12
8 Data retrieval .13
9 Data exchange and re-use .13
9.1 Data exchange . 13
9.2 Data re-use .14
10 Measuring maturity . 14
Bibliography .16

iii
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).
ISO draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). ISO takes no position concerning the evidence, validity or applicability of any claimed patent
rights in respect thereof. As of the date of publication of this document, ISO had not received notice of (a)
patent(s) which may be required to implement this document. However, implementers are cautioned that
this may not represent the latest information, which may be obtained from the patent database available at
www.iso.org/patents. ISO shall not be held responsible for identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 215, Health informatics.
A list of all parts in the ISO 17117 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.

iv
Introduction
This document identifies a model for evaluation of the maturity of terminology implementation in healthcare
systems and identifies a maturity module for terminology implementation for use in electronic health
records (EHRs) and healthcare systems in general.
This document supports common activities of healthcare including:
— identification of the relationship between each terminology resource capability to the safety and
effectiveness of system use in healthcare;
— support healthcare software vendors and organizations to;
— compare software terminological resource capabilities and organizational requirements for those
resources;
— plan improvements, i.e. align requirements and capabilities, as needed;
— improve the safety and utility of healthcare information systems and the data in them, and the use of
terminological resources in applications such as clinical decision support systems;
— improve information sharing (semantic interoperability) between organizations and systems;
— support short and long-term analytics within the organization and more broadly to enable knowledge
acquisition.
The impact of tooling (including computer-assisted coding, speech recognition, template development) on
the capability of the terminological resources is not covered in detail in this document.
This document provides a model against which conformity can be measured and improvements made to
products and implementations with a positive impact both on efficiency and patient safety. This assists
implementation, reduces inappropriate spending, manages expectations more effectively and encourages
software vendors and decision makers at all levels to progress their products into higher functional capacity.
This document is also produced to encourage the development of the skills required to safely and efficiently
implement and use terminologies in healthcare systems.
The users of this document include:
— health care organisation, to assess product capabilities and plan future directions and purchases;
— vendors (including cloud services and conventional software products), to:
— support implementation of terminological resources in their products;
— enable semantic interoperability across different systems;
— assess product conformance requirements influencing future directions for software development;
— government and other decision makers;
— educators and educational organizations;
— terminological resource developers.

v
Technical Specification ISO/TS 17117-3:2024(en)
Health informatics — Terminological resources —
Part 3:
Terminology implementation maturity model (TIMM)
1 Scope
The document defines the progression of implementation of terminology capability in information systems.
This document does not specify requirements for any specific terminological resource. It is intended to
provide a basis for conformance criteria for terminological resources capabilities in specific use cases. This
document does not cover in detail the software being used, though the capabilities of that software are
included and impact the level of maturity reached. This document is applicable to terminological resources
of all types, terminologies, classifications, value sets, code systems, and value domains.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content constitutes
requirements of this document. For dated references, only the edition cited applies. For undated references,
the latest edition of the referenced document (including any amendments) applies.
ISO/IEC 11179-1, Information technology — Metadata registries (MDR) — Part 1: Framework
ISO/IEC 11179-3, Information technology — Metadata registries (MDR) — Part 3: Metamodel for registry
common facilities
ISO/IEC 11179-4, Information technology — Metadata registries (MDR) — Part 4: Formulation of data
definitions
ISO/TS 21526, Health informatics — Metadata repository requirements (MetaRep)
ISO/TS 21564, Health informatics — Terminology resource map quality measures (MapQual)
ISO 22287, Health informatics — Workforce roles and capabilities for terminology and terminology services in
healthcare (term workforce)
1)
HL7, Value Set Specification
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
1) Available at https:// www .hl7 .org/ fhir/ valueset .html.

3.1
concept
unit of knowledge created by a unique combination of characteristics
Note 1 to entry: Informally, the term ‘concept’ is often used when what is meant is ‘concept representation’. However,
this leads to confusion when precise meanings are required. Concepts arise out of human individual and
...

Questions, Comments and Discussion

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