SNOMEDCT - correct representation

Diego Boscá yampeku at
Tue Apr 25 05:52:42 EDT 2017

But you probably need to define national extensions in constraint binding
in templates. Templates are archetypes in the end

2017-04-25 11:47 GMT+02:00 Bert Verhees <bert.verhees at>:

> On 25-04-17 09:50, Diego Boscá wrote:
>> I think having this in a hardcoded terminology list is probably far from
>> ideal (e.g. how do you put "snomed ct+norway national extension"? do we
>> need an exhaustive listing of all possible extensions/versions?)
> When you use SNOMED in termbindings, you don't need to mention extensions,
> the code will do. But we need post coordinated expressions for the things
> which are not coded but still required to express in a SNOMED. At this
> moment, the ADL standard is not ready for that. I already made a JIRA entry
> When you need SNOMED in a terminology constraint, and you want to
> constrain to a subset, then it should be sufficient to use the code to that
> subset. The terminology service should be able to find out if it is a code
> to an entry, an hierarchy or a subset, and response appropriate.
> I am not sure about national extensions
> Bert
> _______________________________________________
> openEHR-technical mailing list
> openEHR-technical at


[image: VeraTech for Health SL] <>

[image: Twitter]  <> [image: LinkedIn]
<> [image: Maps]

Diego Boscá Tomás / Senior developer
diebosto at
yampeku at

VeraTech for Health SL
+34 961071863 <+34%20961%2007%2018%2063> / +34 627015023

Su dirección de correo electrónico junto a sus datos personales forman
parte de un fichero titularidad de VeraTech for Health SL (CIF B98309511)
cuya finalidad es la de mantener el contacto con usted. Conforme a La Ley
Orgánica 15/1999, usted puede ejercitar sus derechos de acceso,
rectificación, cancelación y, en su caso oposición, enviando una solicitud
por escrito a veratech at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the openEHR-technical mailing list