Skip to content
Scalable SNOMED CT Terminology Server using Elasticsearch
Branch: master
Clone or download
kaicode Fix release 2.2.3.
Updated change log.
Latest commit 9ec2680 Apr 23, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
docs Clarify documentation for extension loading Mar 31, 2019
kubernetes Clarify documentation for extension loading Mar 31, 2019
parser-generation Generated ECL parser and source grammar files. Jul 28, 2017
src Fix #39 wiring of descendants endpoint. Apr 23, 2019
.gitignore Git ignore shell scripts and local snomed-drools-rules Mar 4, 2019
.travis.yml Add Travis CI config. Dec 3, 2018 Fix release 2.2.3. Apr 23, 2019
Dockerfile Fix Dockerfiles for missing directory inside docker + Kubernetes Dep… Mar 4, 2019 Clarify documentation for extension loading Mar 31, 2019
docker-compose.yml A whole load of documentation and docker updates Mar 4, 2019
pom.xml Fix release 2.2.3. Apr 23, 2019

❄️ Snowstorm Terminology Server Build Status Language grade: Java codecov

Snowstorm is a SNOMED CT terminology server built on top of Elasticsearch, with a focus on performance and enterprise scalability.

Project Status

Read-Only - tested and already used in the SNOMED International Browser for ECL queries. Snowstorm can be used in local implementations to query SNOMED CT with the following features:

  • Hosting multiple extensions alongside the International Edition of SNOMED CT
  • Multi-lingual search and content retrieval
  • Fully ECL v1.3 compliant
  • Full history (depending on initial RF2 import decision)
  • Read-only FHIR API

Authoring - although write and update features are available this aspect is currently not production ready, having not been fully tested, so should be considered proof of concept.

Please add any issues or any questions in the GitHub issues page.


Documentation is sparse for now, but will be improved as the project moves out of a proof of concept phase.


  1. Fork it!
  2. Create your feature branch: git checkout -b my-new-feature
  3. Commit your changes: git commit -am 'Add some feature'
  4. Push to the branch: git push origin my-new-feature
  5. Submit a pull request


Apache 2.0

See the included LICENSE file for details.

You can’t perform that action at this time.