# openEHR Ontoserver Terminology Server
**URL:** https://discourse.openehr.org/t/openehr-ontoserver-terminology-server/11583
**Category:** Terminology
**Tags:** fhir, snomed-ct, ontoserver
**Created:** [7 November 2025 10:56 UTC](https://discourse.openehr.org/t/openehr-ontoserver-terminology-server/11583 "2025-11-07T10:56:56Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@marcusbaw](https://discourse.openehr.org/u/marcusbaw)
#### Post date: [7 November 2025 10:56 UTC](https://discourse.openehr.org/t/openehr-ontoserver-terminology-server/11583/1 "2025-11-07T10:56:56Z")
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](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](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
> **[FHIR API - Ontoserver](https://ontoserver.csiro.au/site/technical-documentation/ontoserver-technical-documentation/fhir-api/)**
>
> FHIR terminology resource types Bundle API Extensions Use cases for the FHIR API FHIR terminology resource types There are three \[…\]
### Postman
There is a Postman Collection for the Ontoserver here:
> **[Postman](https://www.postman.com/jimsteel/workspace/ontoserver/collection/784165-fb95a213-ff25-4253-8b02-9368f2e59cc9)**
### 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.
---
### Author:  [@ian.mcnicoll](https://discourse.openehr.org/u/ian.mcnicoll)
#### Post date: [7 November 2025 11:06 UTC](https://discourse.openehr.org/t/openehr-ontoserver-terminology-server/11583/2 "2025-11-07T11:06:31Z")
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
---
### Author:  [@birger.haarbrandt](https://discourse.openehr.org/u/birger.haarbrandt)
#### Post date: [8 November 2025 12:51 UTC](https://discourse.openehr.org/t/openehr-ontoserver-terminology-server/11583/3 "2025-11-08T12:51:50Z")
Fantastic! This has been cooking for a good while, so fantastic to see this finally come to life!
---
### Author:  [@marcusbaw](https://discourse.openehr.org/u/marcusbaw)
#### Post date: [7 July 2026 12:30 UTC](https://discourse.openehr.org/t/openehr-ontoserver-terminology-server/11583/4 "2026-07-07T12:30:29Z")
Is the Ontoserver being used by any active projects?