ISO/TR TECHNICAL REPORT 12310 First edition 2015-05-15 Health informatics Principles and guidelines for the measurement of conformance in the implementation of terminological systems Informatique de santé - Principes et lignes directrices pour le mesurage de la conformité dans la mise en oeuvre des systemes terminologiques Reference number ISO/TR 12310:2015(E) ISO International Organization for Standardization ee=Zhejang Institute of Standardization 5956617 @IS02015 HS unde mitted without license from IHS IS0/TR 12310:2015(E) COPYRIGHTPROTECTEDDOCUMENT IS0 2015, Published in Switzerland 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 Ch. de Blandonnet 8 . CP 401 CH-1214 Vernier, Geneva, Switzerland Tel. +41 22 749 01 11 Fax +41 22 749 09 47 [email protected] www.iso.org Not for Resale, 2015/8/7 03:25:31 networking permited without license from IHS IS0/TR 12310:2015(E) Contents Page Foreword ..V Introduction. ..vi 1 Scope.... 2 Objective. 3 Terms and definitions ..1 4 Purposes for conformance ..3 4.1 Interoperability .4 4.2 Data analysis. ..4 4.3 Consistency of user experience ..4 4.4 Application functionality 4.5 Acceptance filter. .4 5 Conformance process ..4 5.1 Documenting expectations. ..4 5.1.1 Optionality ..5 6 Terminology artefact conformance considerations .6 6.1 Code system considerations. ..6 6.1.1 What is the code system being referenced? .6 6.1.2 What version(s) of the code system are supported? ..6 6.1.3 How are codes represented?. 7 6.1.4 What are the version migration expectations, if any? .7 6.1.5 What is the authoritative source that will be used for processing updates to a given terminology? ..7 6.1.6 What status must usable code system elements have? 6.1.7 Which codes and concepts are usable for what purpose? ..8 6.1.8 What representations are allowed for what purposes? 6.1.9 What code system relationships must be understood and navigated? 6.1.10 Arethesemanticsclearlydefines? ..9 6.1.11 What are the expectations for post-coordination?. .9 6.1.12 What partitions are included?.. .9 6.1.13 What code system supplements are supported? ..10 6.2 Reference sets: sets of codes that are allowed .10 6.2.1 What code systems are drawn from? ..10 6.2.2 How is the reference set defined? .10 6.2.3 Which representations are allowed from a code system?. 6.2.4 What constraints are there on post-coordinated concepts? .11 6.2.5 What is post-coordinated vs. Pre-coordinated?. 11 6.2.6 What happens if the concept exists more than once in the reference set? .11 6.3 Reference set bindings ..11 6.3.1 Is the binding to the reference set static or dynamic? ..12 6.3.2 What reference set representation capabilities are supported? .12 6.3.3 Is the reference set extensible?. 12 6.3.4 What expectation is there to support all codes within the bound reference set? 12 6.4 What is the reference set bound to?. .13 6.5 When and where does the binding apply? ..13 7 Terminology usage conformance considerations ..13 7.1 Data capture, ..14 7.1.1 Are the code system contents expected to be exposed directly?. ..14 7.1.2 What aspects may be or must be exposed to users? ..14 7.1.3 Are the available codes to be displayed in a particular order? ..14 7.1.4 Arethereconstraintsonhowthecodesaretobenavigated? ..14 7.1.5 Are deprecated, retired, or pending codes expected to be presented differently? .14 ntemaionalganzation5All rightsreserved iii icensee=Zhejiang Institute of Standardization 5956617 ed without license from IHS Not for Resale, 2015/8/7 03:25:3 No reproduction or networking pe