Terminology Service Providers
Terminology Service Requirements
Terminology service providers should refer to the following sections of this guide for statements of requirements that their services should meet when accessing SNOMED CT:
Outlines user requirements for high-performance services that provide appropriate access to SNOMED CT.
Healthcare Application Providers
Outlines requirements from the perspective of healthcare applications that consume terminology services.
Provides examples of practical use cases involving access to SNOMED CT that an application may need to complete. For each of these use cases, it identifies one or more of the required terminology services that can be used to complete the required activity.
Describes specific terminology services or functions that are required to enable effective use of SNOMED CT.
Support for Different Terminologies and Interfaces
Clinical systems can be effectively implemented using a service oriented architecture, in which the terminology services are designed as an independent software component, accessible via an API (Application Programming Interface) gateway. This enables the other system components to access the key services without being affected by changes to the way these services are implemented.
When designing terminology services for SNOMED CT, it is important to utilize the sophisticated design features of the terminology, as this will support its effective use. When designing terminology services to support a range of different terminologies, it is important to consider the commonality between these terminologies. The table below summarizes some of the advantages and disadvantages of designing terminology services that only work with SNOMED CT, compared with designing services that can also enable access to terminologies or code systems. It also identifies advantages and disadvantages of supporting one or more interfaces through which applications can access SNOMED CT and/or other terminologies.
Terminology Service Design Options
The following tables outline key design choices for terminology services, focusing on the types of terminologies supported and the interfaces provided. Each option includes potential advantages and disadvantages from the perspective of service design, helping organizations assess trade-offs between specialization, interoperability, and maintainability. These options can inform procurement decisions, integration strategies, and long-term terminology management planning.
Terminologies Supported
SNOMED CT only
A terminology service provider may develop and deliver services that are specific to SNOMED CT. ✅ Advantage: Services can be tailored to the structure and features of SNOMED CT. ❌ Disadvantage: May be less attractive to organizations seeking broader terminology support.
SNOMED CT and other code systems
A provider may support access to SNOMED CT along with other terminologies, code systems, or classifications. ✅ Advantage: Single solution for customers needing access to multiple terminologies. ❌ Disadvantage: Risk of underutilizing SNOMED CT-specific features.
Terminology Service Interfaces Supported
Proprietary interface
A provider may define a custom interface to access SNOMED CT and/or other terminologies. ✅ Advantage: Interface can be optimized for specific service features. ❌ Disadvantages: • Application providers may resist supporting multiple proprietary interfaces. • Vendor lock-in risk makes switching providers difficult.
SNOMED CT-specific interface
Example: SNOMED International's Snowstorm API. ✅ Advantage: Allows services optimized for SNOMED CT features. ❌ Disadvantage: Requires app providers to use separate interfaces for other code systems.
General-purpose interface
Example: FHIR Terminology Service API. ✅ Advantages: • Uniform interface for accessing multiple code systems. • Easier to switch between service implementations. ❌ Disadvantage: May not support full optimization for SNOMED CT features.
Multiple interfaces
Example: Snowstorm supports both its native REST API and FHIR API. ✅ Advantage: Combines benefits of SNOMED-specific and general-purpose interfaces. ❌ Disadvantage: Increased maintenance burden; differences in behavior, performance, or output may exist between interfaces.
Last updated