Snow Owl® is a highly scalable, open source terminology server with revision-control capabilities and collaborative authoring platform features. It allows you to store, search and author high volumes of terminology artifacts quickly and efficiently. If you’d like to see Snow Owl in action, the Snowray Terminology Service™ provides a managed terminology server and high-quality terminology content management from your web browser.
Features include:
{% hint style="info" %} This distribution only includes features licensed under the Apache 2.0 license. To get access to the full set of features, please contact B2i Healthcare. {% endhint %}
View the detailed release notes here.
Not the version you're looking for? View past releases.
NOTE: You need to have at least version 17 of the JDK installed for local builds and running the development environment. Official releases include the runtime.
Once you have downloaded the appropriate package:
bin/snowowl.sh
on unix, or bin/snowowl.bat
on windowscurl http://localhost:8080/snowowl/info
to access server health status informationcurl http://localhost:8080/snowowl/fhir/metadata
to access FHIR terminology capabilitieshttp://localhost:8080/snowowl
to access the REST API documentation pageSnow Owl uses Maven for its build system. In order to create a distribution, simply run the following command in the cloned directory.
./mvnw clean package
The distribution packages can be found in the releng/com.b2international.snowowl.server.update/target
folder, when the build is complete.
To run the test cases, use the following command:
./mvnw clean verify
These instructions will get Snow Owl up and running on your local machine for development and testing purposes.
Snow Owl is an Equinox-OSGi based server. To develop plug-ins for Snow Owl you need to use Eclipse as IDE:
Required Eclipse plug-ins in order (install the listed features via Help
→ Install New Software...
):
Note: you may have to untick the Show only the latest versions of the available software
checkbox to get older versions of a feature. Please use the exact version specified below, not the latest point release.
Make sure you have the following preferences enabled/disabled.
settings.xml
in your ~/.m2/settings.xml location is updated with the content from the settings.xml
from this repository's root folder.Alt
+ F5
and trigger an update to all Maven projects manually (to download dependencies from Maven)target-platform/target-platform.target
fileResolve
button if it refuses to do so) and then click on Set as Active Target platform
snow-owl-oss
launch configuration in the Run Configurations menuhttp://localhost:8080/snowowl
Please see CONTRIBUTING.md for details.
Our releases use semantic versioning. You can find a chronologically ordered list of notable changes in CHANGELOG.md.
This project is licensed under the Apache 2.0 License. See LICENSE for details and refer to NOTICE for additional licensing notes and uses of third-party components.
In March 2015, SNOMED International generously licensed the Snow Owl Terminology Server components supporting SNOMED CT. They subsequently made the licensed code available to their members and the global community under an open-source license.
In March 2017, NHS Digital licensed the Snow Owl Terminology Server to support the mandatory adoption of SNOMED CT throughout all care settings in the United Kingdom by April 2020. In addition to driving the UK’s clinical terminology efforts by providing a platform to author national clinical codes, Snow Owl will support the maintenance and improvement of the dm+d drug extension which alone is used in over 156 million electronic prescriptions per month. Improvements to the terminology server made under this agreement will be made available to the global community.
Many other organizations have directly and indirectly contributed to Snow Owl, including: Singapore Ministry of Health; American Dental Association; University of Nebraska Medical Center (USA); Federal Public Service of Public Health (Belgium); Danish Health Data Authority; Health and Welfare Information Systems Centre (Estonia); Department of Health (Ireland); New Zealand Ministry of Health; Norwegian Directorate of eHealth; Integrated Health Information Systems (Singapore); National Board of Health and Welfare (Sweden); eHealth Suisse (Switzerland); and the National Library of Medicine (USA).