Terminology Tooling Options

Implementing terminology requires supporting tools

Tools required are highly dependant on the type of implementation

Covered in this presentation◦Types of implementation activities◦Types of tools required◦Description of some available tools

Terminology Tooling Options

2

Setting the scene…

3

This presentation mentions tools and vendors as examples◦but doesn’t imply how good, bad or

otherwise these tools are◦and can’t cover all known tools

Where to find more◦Australian Clinical Terminologies User’s

Group◦Available Terminology Products and Service

s forum page

Disclaimer…

4

Systems have existing code sets

Native replacement can be expensive and time consuming

Mapping can be used for interoperability

…however remember that maintenance of maps can also be costly

Local coding sets

Tooling needed - Mapping

5

Store SNOMED CT / AMT codes in records Display SNOMED CT / AMT preferred terms Searching functionality with context based filtering Custom widgets for screen use Create and maintain value sets Load new terminology versions Retrieve/analyse SNOMED CT / AMT encoded data

Native implementation

Tooling needed - User interface guidance and widgets - Process/manipulate release files (RF2) - Querying/searching - Reference set authoring - Mapping

6

Customise language preferences Add descriptions Add concepts Natural language processing Store/process/render SNOMED CT expressions

Native implementation

Tooling needed - Localisation/authoring - Natural language processing service - Compare and interpret SNOMED CT expressions

7

Terminology distribution Terminology configuration management Conversion to proprietary formats Customise language preferences Query support Add descriptions Add concepts Central real-time access to terminology services

Enterprise terminology management

Tooling needed - Terminology servers/services - Localisation/authoring - Browsing - Compliance/testing

8

9

Browsing Process/manipulate release files (RF2) Mapping Reference set authoring User interface guidance and widgets Terminology servers/services Localisation/authoring Compare and interpret SNOMED CT expressions Natural language processing Compliance/testing

Tooling landscape

10

Not all possible tools are listed in this presentation – there are others

Listing of tools in this presentation doesn’t state how good, bad or otherwise the tools are

Tools are listed in no particular order Tools won’t necessarily cover all features on

the slide on which they are listed, but will have some relevant capabilities

You don’t need all of these tools – depends on what you are doing

11

Before we go through the tools

Browsing

Example capabilities Existing tools

Hierarchy/taxonomy view Concept definition and

relationships Preferred and alternate terms Searching – syntactic and

semantic SNOMED CT expression

handling Export features Diagramming Browse/view reference sets

Web based◦ Federation Health Browser◦ Healthbase AMT Explorer◦ SnoFlake

Download and install◦ Snapper/Minnow◦ IHTSDO Workbench Viewer◦ SNOyowie◦ SNOB◦ CliniClue◦ Snow Owl

…many, many more

12

Release file processing (RF2)

Example capabilities Existing tools

Import/transform SNOMED CT RF2 files

Interpret Australian Dialect Reference Set

Import and use reference sets

Subsumption and transitive closure

Process/export to proprietary formats

NCTIS Reference Set Guide Application

SNOMED CT Technical Implementation Guide

Snofyre

13

Mapping

Capabilities required Existing tools

Two distinct types of mapping◦ local code set to SNOMED CT /

AMT◦ SNOMED CT / AMT to other

code systems (e.g. ICD) “Auto” mapping Workflow management Version management Map maintenance SNOMED CT expression

handling

Snapper IHTSDO Workbench CareCom HealthTer

m HLI LExScape Apelon TermWorks

14

Reference set authoring

Example capabilities Existing tools

Browse/view reference sets Create new reference sets

based on◦ Individual concept selection◦ Queries/searches/expressions◦ Existing reference sets

(unions, intersections etc) Maintain reference sets

◦ Update based on changes to underlying terminology

Manage reference set versions and history

IHTSDO Workbench

Snapper HLI LExScape CareCom HealthTer

m Ocean Subset Buil

der Apelon TDE Snow Owl

15

User interface guidance/widgets

Example capabilities Existing tools

Guidance on user interface design/layout

Widgets for integration in applications

Microsoft Common User Interface

CliniThink CLIP

16

Terminology servers/services

Example capabilities Existing tools

Realtime◦ Basic lookup◦ Value set retrieval◦ Searching – syntactic/semantic◦ Expression processing

Management◦ Version management◦ Conversion/export◦ Publication/distribution◦ Localisation/authoring◦ Reference set authoring◦ Mapping

Apelon DTS HLI Language Engin

e CareCom HealthTer

m Mondeca Conceptual Snofyre Ocean Terminology

Server CTS2

17

Language preferencesand authoring

Example capabilities Existing tools

Customise language preferences (Australian Dialect Reference Set)

Create descriptions Create new concepts Classify

IHTSDO Workbench Apelon TDE HLI LExScape CareCom HealthTer

m Mondeca Snow Owl Snorocket

18

Compare and interpret SNOMED CT expressions

Example capabilities Existing tools

Render expressions Compare

expressions Store and retrieve

expressions Convert between

forms

Snofyre Snorocket Snapper/Minnow CliniThink CLIP

19

Natural language processing

Example capabilities Existing tools

Process text to SNOMED CT and/or AMT◦ Individual concepts◦ Expressions

Render SNOMED CT expressions to natural language

CliniThink CLIP CSIRO AEHRC University of Sydne

y

20

Compliance/testing

Example capabilities Existing tools

Validate release file◦ Format◦ Structure◦ Integrity

Report on terminology errors

Developer level tools under development at IHTSDO

21

22

Depends upon what you are doing Native implementation

◦Mapping and browsing◦Localisation/authoring◦Reference set authoring

Advanced native implementations◦Expression handling◦Natural language processing◦Custom widgets◦RF2 processing / terminology server

What tools do I need?

23

Enterprise terminology management◦Mapping and reference set authoring and

management◦Localisation/authoring◦Distribution and configuration management◦Load, conversion and export to proprietary

formats◦Real-time terminology service◦Compliance/testing

What tools do I need?

24

Local coding system, mapping at boundary◦Browsing◦Mapping

25

What tools do I need?