openEHR Ontoserver Terminology Server

We now have an instance of CSIRO’s Ontoserver available for the openEHR community. Thanks @SevKohler for reminding me I needed to make a more general post about its availability and how to access it.

[!danger] Licensing Terms
The terminology server is licensed to openEHR International by CSIRO for use in development and testing only for the openEHR archetype development community.
It must not be used in production - for any direct care, client delivery work or production workloads it is both unlicensed and underpowered.
For live/production use, seek out an appropriate license agreement from CSIRO directly. Additionally you may need to consider appropriate licensing of the underlying terminology in use, for example SNOMED.

Access

There is currently no access control on the terminology server, however this may be reviewed depending on usage and necessity.

URL: https://terminology.openehr.org

Using Ontoserver

A quick test query you can run in a browser is https://terminology.openehr.org/fhir/CodeSystem/$lookup?system=http://snomed.info/sct&code=248340003&_format=json which should return the JSON data for “Growth velocity centile”.

The full documentation for Ontoserver’s FHIR API is here

Postman

There is a Postman Collection for the Ontoserver here:

SCT versions, updates, localisations, etc

I’m happy to work with members of the openEHR community to set up Ontoserver with whatever version/localisation of SNOMED-CT is required - when I first set it up last year, there was nobody actually using it, so I haven’t yet optimised it for the term bindings work that openEHR’s community will want to use it for. Let me know here what you want and I’ll do my best to make it happen.

4 Likes

Fantastic news. Thanks to all concerned for getting it over the line.

@sebastian.iancu - can we see about getting openEHR terminology up there as well

2 Likes

Fantastic! This has been cooking for a good while, so fantastic to see this finally come to life!