Page History
Implementing SNOMED CT can be made much easier with the effective use of tooling. On this page we explore a range of SNOMED CT tools that can help to support a successful range of implementation tasks, grouped according to the implementer needs, ranging from making SNOMED available to a software application through terminology services to different tools that support content authoring in extensions.
Browse
The SNOMED CT Browsers allows the user to navigate the terminology, see the different components and the relationships between them.
Search and Data Entry
This collection of best practice recommendations and open source examples demonstrate the possibilities for developing search and data entry user interfaces in end user applications.
Implement Terminology Services
Implementing a central solution that provides access to all the SNOMED CT content and features, a SNOMED CT Terminology Server, is the most common implementation architecture. It simplifies the development of clinical applications that consume these terminology services through APIs.
Subset
Subsets are an important resource in many implementations, grouping concepts in SNOMED CT that apply to a specific use case, like clinical specialties data entry, translations prioritization, data analysis, or others. The tools described in this section allow the implementers to create and maintain SNOMED CT subsets.
Map
Mappings support the use of SNOMED CT along other vocabularies, like codes in legacy systemsfrom managing the creation and maintenance of reference sets, maps and translations, to providing terminology services to effectively access SNOMED CT content from a software application.
Please click on the links below to explore the range of SNOMED CT tools available.
| Browsers | Allow users to search SNOMED CT, navigate its hierarchy and view the properties of each component. |
| Reference Set Tools | Allow implementers to create and maintain subsets of SNOMED CT codes for a specific use case, e.g. data entry of diagnoses for a clinical specialty, prioritisation of translations, data analytics queries, etc. |
| Mapping Tools | Allow users to create and maintain mappings between SNOMED CT and other code systems, e.g. local codes, billing codes, statistical classifications, |
to support a wide range of implementation use cases, e.g. migration to SNOMED CT, data integration, reporting. | |
| Translation Tools | Support |
Translate
Translation tools supportthe creation of SNOMED CT descriptions in different languages, |
Author Content
with the associated quality assurance processes. | |
| Authoring Tools | Support the creation and modelling |
of new SNOMED CT concepts |
in accordance with the SNOMED CT Editorial Guidelines and the SNOMED CT Concept Model. |
Manage Releases
Producing standard SNOMED CT releases| Release Services | Support the creation, validation and bundling of SNOMED CT release packages in a standard format that can be imported into terminology servers and other applications |
. | |
| Terminology Services | Provide an effective way of implementing SNOMED CT by enabling SNOMED CT content to be searched and queried via an API (application programming interface). |
| Record Services | Support the functions of a clinical record system, including the display and storage of terminology content in the health records. |
| User Interfaces | Allow users to search, enter and display SNOMED CT data in healthcare records. |
| Natural Language Processing | Support the extraction of coded clinical entities from free text sources, to support data-entry and analytics. |
| Data Analytics Tools | Enable users to query over clinical data that contains SNOMED CT codes to take advantage of the rich semantic definitions included in SNOMED CT. |
Overview
Content Tools
Apps
Feedback