Ontoserver - Next Generation Terminology
Recording the right code -- diagnosis, procedure, medication -- can be simple.
With fast, incremental search, and context-specific result ordering,
Ontoserver puts SNOMED CT, AMT, LOINC, and FHIR-based CodeSystems at your fingertips.
Available under licence from the CSIRO's Australian eHealth Research Centre.
(free for use in Australia by registered license-holders with the Australian Digital Health Agency)
Core Features
- Approved for use with the FHIR validator and the FHIR IG publisher
- Ontoserver® v6.21.0 passed all HL7 terminology service tests (modes flat;ontoserver, tests v1.6.0, runner v6.4.0)
- Fast & Precise Search
- sub-100ms response times for most code searches in SNOMED CT
- SNOMED CT RF2
- SNOMED CT Expression Constraint Language
- Multiple SNOMED CT Versions including local extensions
- OWL2 EL (with Concrete Domains) Description Logic via Snorocket or ELK
FHIR Terminology Ecosystem
Ontoserver® v6.21.0 passed all HL7 terminology service tests (modes flat:ontoserver, tests v1.6.0, runner v6.4.0)
The FHIR Terminology Ecosystem is documented here: https://github.com/FHIR/ig-registry/blob/master/tx-registry-doco.md
FHIR🔥 APIs (R4)
-
SCRUD operations on ValueSet, ConceptMap, CodeSystem, StructureDefinition, Bundle and NamingSystem.
-
Resource-specific operations: ValueSet $expand, ValueSet $validate-code, CodeSystem $find-matches, CodeSystem $lookup, CodeSystem $subsumes, CodeSystem $validate-code, NamingSystem $preferred-id, ConceptMap $translate, and $closure
Syndication 
Ontoserver instances can syndicate terminology content from an up-stream or to a down-stream instance via its Syndication API.
This makes it almost trivial to deploy and access the latest version of SNOMED CT-AU and other standard terminologies.
OpenAPI Specifications
Third Party content
Ontoserver owes a great debt to the HAPI “plain server” framework and Apache Lucene.