Implementing Terminologies

  • Tim Benson
  • Grahame Grieve
Part of the Health Information Technology Standards book series (HITS)


Implementation of terminologies involves making choices about when to use codes and when to structure information in separate fields. Terminology binding is the process of specifying in archetypes and templates what codes belong in which fields. The model of use is how information appears to the end user. This often differs from the model of meaning, which is always true, but sometimes harder to use. It is important to distinguish between coded text, which refers to a code, and codeable text where a code reference is optional. Value sets represent the permissible codes, while a coding scheme may represent all codes in a scheme. A number of different scenarios are explored for when codes may be known or not known. The task of the receiver is critical, to ensure information is not lost.


Reference terminology Terminology binding Information model Model of use Model of meaning Structured data entry Views into EHR Common user interface Structural models Reference model ISO 13606 Archetype Template Coded data types Coded text Codeable text Null flavor Code system Version Original text Display name Translation Value set Complex coded expressions Common scenarios Coded data types in v2 V3 and FHIR Receivers Expression storage 


  1. 1.
    Vendor Introduction to SNOMED CT. IHTSDO. May 2015.Google Scholar
  2. 2.
    SNOMED CT IHTSDO Glossary. IHTSDO. January 2015.Google Scholar
  3. 3.
    Markwell D, Sato L, Cheetham E. Representing clinical information using SNOMED Clinical terms with different structural information models. In: Cornet R, Spackman K, editors. Representing and sharing knowledge using SNOMED. Proceedings of the 3rd international conference on Knowledge Representation in Medicine (KR-MED 2008). 2008: 72–9.Google Scholar
  4. 4.
    Rector AL, Qamar R, Marley T. Binding ontologies and coding systems to electronic health records and messages. Appl Ontol. 2009;4(1):51–69.Google Scholar
  5. 5.
    NHS CUI Design Guide Workstream – Design Guide Entry – Terminology – Matching. 2007.Google Scholar
  6. 6.
    NHS CUI Design Guide Workstream – Design Guide Entry – Terminology – Elaboration. 2007.Google Scholar
  7. 7.
    NHS CUI Design Guide Workstream – Design Guide Entry – Terminology – Display Standards for Coded Information. 2007.Google Scholar
  8. 8.
    HL7 Version 3 Implementation Guide: TermInfo – Using SNOMED CT in CDA R2 Models, Release 1 Draft Standard for Trial Use. December 2015.Google Scholar

Copyright information

© Springer-Verlag London 2016

Open Access This chapter is licensed under the terms of the Creative Commons Attribution-NonCommercial 2.5 International License (, which permits any noncommercial use, sharing, adaptation, distribution and reproduction in any medium or format, as long as you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license and indicate if changes were made.

The images or other third party material in this chapter are included in the chapter's Creative Commons license, unless indicated otherwise in a credit line to the material. If material is not included in the chapter's Creative Commons license and your intended use is not permitted by statutory regulation or exceeds the permitted use, you will need to obtain permission directly from the copyright holder.

Authors and Affiliations

  • Tim Benson
    • 1
  • Grahame Grieve
    • 2
  1. 1.R-Outcomes LtdNewburyUK
  2. 2.Health Intersections Pty LtdMelbourneAustralia

Personalised recommendations