SNOMEDCT - correct representation

Michael.Lawley at Michael.Lawley at
Tue Apr 25 04:08:41 EDT 2017

There is a spec that tells you how to identify different editions and versions of SNOMED CT - see

In short, is the identifier for any version of SNOMED CT.  for the Norway extension you need to know which module it is in (this is what will be used in the Module Dependency Reference Set for the Norway release) and then, if it was 12345668 for example, the identifier is


Sent from my iPhone

On 25 Apr 2017, at 5:52 pm, Diego Bosc? <yampeku at<mailto:yampeku at>> 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?)

2017-04-25 8:03 GMT+02:00 Ian McNicoll <ian at<mailto:ian at>>:
SNOMED-CT is the official designator, based on the archetype editor terminology list.
On Tue, 25 Apr 2017 at 06:36, Pablo Pazos <pablo.pazos at<mailto:pablo.pazos at>> wrote:
Congratulations about the new adoption!

The IHTSDO recommends to use exactly "SNOMED CT" as the *name*, in our specs we are using SNOMED-CT as the name (it should be corrected to the name preferred by the IHTSDO). On an event they explicitly asked to avoid the SNOMED-CT with the hyphen when referencing the standard.

As for the term id, I've seen [snomed-ct::35917007 on the specs, or SNOMED-CT on sample archetypes:

Tested on the Ocean's archetype editor and they use:

constraint_bindings = <
        ["SNOMED-CT"] = <
            items = <
                ["ac0001"] = <terminology:SNOMED-CT/release?subset=cabolabs>

On Mon, Apr 24, 2017 at 7:33 PM, Bj?rn Naess <bna at<mailto:bna at>> wrote:
Norway just became a SNOMED country.
One simple question - what is the correct terminologyId to use for SNOMED-CT.

Currently we use 'SNOMEDCT' like below. Is this correct?

 <value xsi:type="DV_CODED_TEXT">
                    <value>H?yre ?ye</value>

Vennlig hilsen
Bj?rn Naess

Mobil +47 93 43 29 10<tel:+47%2093%2043%2029%2010>

openEHR-implementers mailing list
openEHR-implementers at<mailto:openEHR-implementers at>

Ing. Pablo Pazos Guti?rrez
Cel:(00598) 99 043 145
Skype: cabolabs
        [] <><>
pablo.pazos at<mailto:pablo.pazos at>
Subscribe to our newsletter<>

openEHR-technical mailing list
openEHR-technical at<mailto:openEHR-technical at>
Ian McNicoll

openEHR-technical mailing list
openEHR-technical at<mailto:openEHR-technical at>


[VeraTech for Health SL]<>

[Twitter] <>  [LinkedIn]  <>  [Maps]  <>


Diego Bosc? Tom?s / Senior developer
diebosto at<mailto:diebosto at>
yampeku at<mailto:yampeku at>

VeraTech for Health SL
+34 961071863<tel:+34%20961%2007%2018%2063> / +34 627015023<tel:+34%20627%2001%2050%2023><>

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<mailto:veratech at>.

openEHR-technical mailing list
openEHR-technical at<mailto:openEHR-technical at>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the openEHR-technical mailing list