Health informatics — Terminological resources — Part 2: Implementation Capability (TIC)
Introduction: 0.1 Objective The aim of the ISO 17117 series is to enable health care organizations, vendors (including cloud services and conventional software products), governments and other decision makers to — understand requirements for implementation of terminology in healthcare systems, and — describe organization capability needed when using terminological resources. This document defines the capability of implemented terminological resources based on the information lifecycle. Terminology implementation is assessed by review of each of the following 5 terminological implementation component parts: — Data design; — Data capture; — Data storage; — Data retrieval; — Data exchange (interoperability) and re-use. And reviewed according to the implementation processes and capabilities as defined across 5 areas: — Terminological resource functionality; — Tool functionality; — Workforce capability; — Governance; — Conformity to standards. 0.2 Stakeholders and audience The users of this document include — health care organizations – 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, and — assess product requirements influencing future directions for software development. — government and other decision makers to identify areas of terminology practice that require i
Scope: This document defines the components (benchmarks) of capability of terminological resources implementation in healthcare software products, including electronic health record systems. It is intended that these benchmarks form the basis of a maturity model. The document will support analysis of requirements to meet use cases in the implementation of terminological resources in healthcare. This document does not specify requirements for any specific terminological resource. It is intended to provide a basis from which requirements for terminological resources capabilities can be specified in the future. The tooling being used can impact the level of maturity reached but is not covered in detail in this document. Terminological resources include code systems of all types, terminologies, classifications, value sets, and value domains. The impact of tooling (computer–assisted coding, speech recognition, template development) on the capability of the terminological resources is not covered in detail in this document.