SNOMEDCT - correct representation

Bjørn Næss bna at dips.no
Tue Apr 25 14:38:24 EDT 2017


Thanks Ian
You are right. The correct ID is  “SNOMED-CT” . Then the example will be as follows:
 <value xsi:type="DV_CODED_TEXT">
                    <value>Høyre øye </value> <! - - Right eye - - >
                    <defining_code>
                      <terminology_id>
                        <value>SNOMED-CT</value>
                      </terminology_id>
                      <code_string>18944008</code_string>
                    </defining_code>
                  </value>
I don’t think any subsets should be used on this context. What we need is a way to say that the code_string “18944008” is defined by the terminology defined by terminology_id/value = “SNOMED-CT”.  This must be done the same way by all openEHR systems to enable a true open platform based on openEHR archetypes.

Thanks for the feedback from all of you!



Vennlig hilsen
Bjørn Næss
Product owner
DIPS ASA

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

From: openEHR-technical [mailto:openehr-technical-bounces at lists.openehr.org] On Behalf Of Ian McNicoll
Sent: tirsdag 25. april 2017 08.03
To: For openEHR technical discussions <openehr-technical at lists.openehr.org>; For openEHR implementation discussions <openehr-implementers at lists.openehr.org>
Subject: Re: SNOMEDCT - correct representation

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 cabolabs.com<mailto:pablo.pazos at cabolabs.com>> 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: 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 <bna at dips.no<mailto:bna at dips.no>> 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<tel:+47%2093%2043%2029%2010>


_______________________________________________
openEHR-implementers mailing list
openEHR-implementers at lists.openehr.org<mailto:openEHR-implementers at lists.openehr.org>
http://lists.openehr.org/mailman/listinfo/openehr-implementers_lists.openehr.org



--
Ing. Pablo Pazos Gutiérrez
Cel:(00598) 99 043 145
Skype: cabolabs

[https://docs.google.com/uc?export=download&id=0B27lX-sxkymfdEdPLVI5UTZuZlU&revid=0B27lX-sxkymfcUwzT0N2RUs3bGU2UUovakc4VXBxWFZ6OXNnPQ]<http://cabolabs.com/>
http://www.cabolabs.com<http://www.cabolabs.com/>
pablo.pazos at cabolabs.com<mailto:pablo.pazos at cabolabs.com>
Subscribe to our newsletter<http://eepurl.com/b_w_tj>

_______________________________________________
openEHR-technical mailing list
openEHR-technical at lists.openehr.org<mailto:openEHR-technical at lists.openehr.org>
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
--
Ian McNicoll
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20170425/acb7e56d/attachment-0002.html>


More information about the openEHR-technical mailing list