Ontoserver technical documentation

  1. Getting started
  2. Key features
  3. Common tasks
  4. More resources

Ontoserver provides three core RESTful API classes:

  • a FHIR API for terminology use
  • a Syndication API to ingest and distribute content
  • an Administration API to administer the server.

Ontoserver has been designed to support both small scale use and large scale deployments and can grow with your changing requirements. As described in deployment models, there are two common use-cases:

  • Read/write server primarily aimed at supporting content authoring
  • Read-only server designed to service runtime use of released terminology content.
View Ontoserver Collection in Postman

Getting started

Quick start

FHIR launchpad

Syndication and content ingestion

Planning a deployment

Understanding content release requirements and process design

Key features

FHIR API

Content syndication

SNOMED CT post-coordination support

Common tasks

Deploy new Ontoserver version

Authorisation for Ontoserver

Using system account credentials

More resources

Infrastructure/operations

Security

Shared resources and persistent storage