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:
https://github.com/openEHR/specifications-ITS/search?utf8=%E2%9C%93&q=snomed&type=

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 Næss <[email protected]> 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>
>                     <defining_code>
>                       <terminology_id>
>                         <value>SNOMEDCT</value>
>                       </terminology_id>
>                       <code_string>18944008</code_string>
>                     </defining_code>
>                   </value>
>
>
>
> Vennlig hilsen
> Bjørn Næss
> Produktansvarlig
> DIPS ASA
>
> Mobil +47 93 43 29 10 <+47%2093%2043%2029%2010>
>
>
>
> _______________________________________________
> openEHR-implementers mailing list
> [email protected]
> http://lists.openehr.org/mailman/listinfo/openehr-
> implementers_lists.openehr.org
>



-- 
Ing. Pablo Pazos Gutiérrez
Cel:(00598) 99 043 145
Skype: cabolabs
<http://cabolabs.com/>
http://www.cabolabs.com
[email protected]
Subscribe to our newsletter <http://eepurl.com/b_w_tj>
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Reply via email to