Search



Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

SNOMED CT 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).

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 A rapid and effective way of deploying SNOMED CT in a national or local implementation is to use SNOMED CT terminology servers. SNOMED CT terminology servers simplify the development of clinical applications that consume these use SNOMED CT, by providing optimized terminology services through an APIs .(Application Programming Interfaces). Terminology services may include:

  • Searching for SNOMED CT content using term matching, the hierarchy, or defining relationships,
  • Retrieving information about a given concept, including descriptions for a given dialect, supertypes, subtypes and defining relationships,
  • Executing Expression Constraint Queries (ECL) on a particular SNOMED CT edition, and
  • Accessing maps to/from SNOMED CT and other reference set information.

Terminology servers can either import data from a SNOMED CT release package, or periodically synchronise its content with another terminology server. The loaded SNOMED CT content can then be made The terminology servers can import data from the SNOMED CT release packages and make the information available to browsers or electronic medical health records with using a convenient APIs API that implement implements terminology best practices in terminology management, including search and sorting algorithms, support for ECL, language filters, hierarchy navigation, etc. Using terminology servers saves the time of implementing these features from scratch starting from the plain text files, and they can provide standardized APIs that simplify the integration into en Using a terminology server in your implementation can save time, by removing the need to implement these services from scratch. The use of standardized APISs can also simplify their integration into end user applications.

Snowstorm

...

SNOMED International develops and maintains Snowstorm, a SNOMED CT terminology server built on top of Elasticsearch, with a focus on performance and enterprise scalability. Snowstorm provides the terminology server API for the a range of SNOMED CT tools used by SNOMED International Browser , including the SNOMED CT Browser and the SNOMED CT Authoring Platform.

International Edition and around fourteen national Extensions. As an open-source tool, Snowstorm can be installed locally to provide a terminology services API to clinical applications.

Main The main features of Snowstorm include:

  • Open source, based on a modern open-source stack, Elasticsearch, Spring Boot, Docker
  • Advanced SNOMED specific API
  • Read-only HL7 FHIR API
  • Multi-lingual search and content retrieval
  • Fully ECL v1.3 compliant
  • Full history (depends on full RF2 import)
  • Supports a Read-only mode and an Authoring mode

Snowstorm's open source repository code is available at: https://github.com/IHTSDO/snowstorm

...

Other SNOMED CT terminology servers are available, as listed below. Please note that these terminology servers may use different licensing models and APIs (e.g. a standard HL7 FHIR APIs API, or a proprietary API).

Hermes Terminology Server, UKhttps://github.com/wardle/hermes
Ontoserver, CSIRO, Australiahttps://ontoserver.csiro.au/
PHAST FHIR Terminology Server, Francehttps://www.phast.fr/tioct/
SNOMED CT Terminology Server, West Coast Informatics, UShttps://www.westcoastinformatics.com/resources.html
Snow Owl Terminology Server, B2i Healthcarehttp://b2i.sg/terminology-server/

Please note that this This list of terminology servers is provided in alphabetical order. To request the addition or removal of a terminology servers to/from this list, please submit a request via the 'Feedback' button at the bottom of this page.

...


Feedback