How to install Snow Owl terminology server on Windows?

Download the Windows ZIP package from the artifacts repository, extract it, and run bin/snowowl.bat to start the server, following the README's installation instructions. You can then access APIs via localhost:8080.

Snow Owl vs Ontoserver: which is better for FHIR terminology services?

Snow Owl excels with revision-controlled authoring and Elasticsearch scalability for large datasets, while Ontoserver is more focused on pure FHIR compliance; choose Snow Owl for collaborative terminology management needs.

Can Snow Owl handle SNOMED CT extensions?

Yes, Snow Owl supports SNOMED CT extensions and custom reference sets with its revision-control features, allowing authoring and versioning of specialized clinical codes.

How to configure Elasticsearch with Snow Owl?

Snow Owl requires an external Elasticsearch 7 or 8 cluster; you need to set it up separately and configure Snow Owl to connect via its settings, as it relies on Elasticsearch for storage and search.

What are the licensing costs for Snow Owl enterprise features?

Full access to terminologies like LOINC and ICD-10 requires contacting B2i Healthcare for enterprise licensing, as the open-source version has limited features under Apache 2.0.

How to contribute to Snow Owl open-source project?

Set up the Eclipse development environment as per the README, follow the CONTRIBUTING.md guidelines, and submit pull requests via GitHub after testing with the provided Maven commands.

Open-Awesome

Snow Owl

Apache-2.0Javav10.1.0

A production-ready, scalable, open-source terminology server supporting SNOMED CT, LOINC, RxNorm, ICD-10/11, and custom code systems with FHIR compliance.

Visit Website GitHub

290 stars39 forks0 contributors

What is Snow Owl?

Snow Owl is an open-source terminology server designed to store, search, and author high volumes of standardized medical terminology artifacts like SNOMED CT, LOINC, and ICD-10/11. It provides a scalable, revision-controlled platform with FHIR Terminology Service compliance, solving the problem of managing complex clinical code systems for healthcare interoperability.

Target Audience

Healthcare IT organizations, clinical terminology authors, EHR/EMR system developers, and health data interoperability teams who need to manage and integrate standardized medical terminologies.

Value Proposition

Developers choose Snow Owl for its production-ready scalability, comprehensive FHIR compliance, robust revision-control for collaborative authoring, and extensible plugin architecture—all available as open-source with enterprise-grade features.

Overview

:owl: Snow Owl Terminology Server - a production-ready, fast, scalable, FHIR Terminology Service compliant server that supports SNOMED CT International and Extensions, LOINC, RxNorm, UMLS, ICD-10/11, custom code systems and many others

Use Cases

Best For

Building FHIR-compliant terminology services for healthcare applications
Authoring and versioning SNOMED CT extensions or custom clinical code systems
Managing multiple medical terminologies (LOINC, RxNorm, ICD) in a unified server
Implementing scalable search and retrieval of clinical terminology artifacts
Developing collaborative terminology authoring platforms with branch isolation
Integrating standardized medical codes into EHR/EMR systems via APIs

Not Ideal For

Projects that don't involve medical terminology or healthcare data interoperability, as it's specialized for clinical code systems.
Teams wanting a simple, out-of-the-box terminology server without managing Elasticsearch clusters or complex Java ecosystems.
Organizations needing immediate, full access to all supported terminologies like LOINC and ICD-10 without additional licensing or enterprise contracts.

Pros & Cons

Pros

Revision-Controlled Authoring

Maintains multiple versions and isolated work branches for collaborative terminology management, enabling team workflows and version history as highlighted in the features.

FHIR Terminology Compliance

Provides APIs compliant with FHIR R4, R4B, and R5 formats in a single deployment, facilitating seamless healthcare interoperability and standards adherence.

Scalable Elasticsearch Backend

Built on Elasticsearch 7/8 for distributed full-text search and analytics, ensuring high performance with large terminology datasets, as noted in the README.

Broad Terminology Support

Handles SNOMED CT, LOINC, RxNorm, and more with extensibility for custom code systems, supporting diverse healthcare terminology needs.

Cons

Complex Development Setup

Requires Eclipse IDE with specific plugins and configurations for development, as detailed in the README, which can be a significant barrier for teams not using this toolchain.

Limited Open-Source Features

The Apache 2.0 licensed version excludes some terminology systems like LOINC and ICD-10, requiring enterprise licensing for full functionality, as mentioned in the download notes.

Elasticsearch Version Constraints

Currently supports only up to Elasticsearch 8 with no support for Elasticsearch 9 yet, which may complicate infrastructure upgrades and long-term maintenance.

Frequently Asked Questions

Related Projects

Synthea Patient Generator

Synthetic Patient Population Simulator

Stars3,163

Forks877

Last commit3 days ago

EDS_NLP

Modular, fast NLP framework, compatible with Pytorch and spaCy, offering tailored support for French clinical notes.

Stars165

Forks42

Last commit26 days ago

IHRIS

Health Information System for management of human resources for health

Natural Language Processing System for extraction of information from Electronic Medical Record clinical free-text