# Why does the Terminology id table has no version instead this Stringbuild logic

**Category:** [RM](https://discourse.openehr.org/c/rm/42)
**Created:** 2026-01-28 15:17 UTC
**Views:** 33
**Replies:** 2
**URL:** https://discourse.openehr.org/t/why-does-the-terminology-id-table-has-no-version-instead-this-stringbuild-logic/11707

---

## Post #1 by @SevKohler

Shouldnt the RM have a dedicated version field also for query stability?

SNOMED-CT (VERSION) is what is currently in the spec. 
That makes AQLs frankly quite annoying.
Also SNOMED has modules and versions would be good to not have 
http://snomed.info/sct/900000000000207008/version/20230731 in the string


This has also major consequences if using a term server since then you want to use the url stuff usually which you cant since you cant put versionse like snomed.info/ct (12030120).

---

## Post #2 by @joostholslag

Could you share some context please? I’m interested to understand your question.

---

## Post #3 by @yampeku

the version of the terminology is embedded in the identifier, which makes it really clunky to use in any kind of terminology service

---


**Canonical:** https://discourse.openehr.org/t/why-does-the-terminology-id-table-has-no-version-instead-this-stringbuild-logic/11707
**Original content:** https://discourse.openehr.org/t/why-does-the-terminology-id-table-has-no-version-instead-this-stringbuild-logic/11707