Yup - that's the right URI format.

Cheers,

-koray

From: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.org] On 
Behalf Of Thomas Beale
Sent: Thursday, 27 April 2017 1:01 a.m.
To: openehr-technical@lists.openehr.org
Subject: Re: SNOMEDCT - correct representation




In the new world of URIs representing SNOMED codes, this "SNOMED-CT" value for 
the terminology_id is understood as an openEHR-local (and maybe more widely 
agreed) namespace alias for the SNOMED CT namespace whose URI is 
http://snomed.info/sct (see 
http://doc.ihtsdo.org/download/doc_UriStandard_Current-en-US_INT_20140527.pdf).

Practically speaking this means that if other variants exist, e.g. 'snomed_ct', 
'SNOMED_CT' and so on, they can all be defined as aliases for SNOMED CT, in 
different contexts such as archetype tools, AQL queries and so on.

BTW, the ARchetype editor should generate URIs of this form for terminologies 
(from the ADL2 converted form of the CKM BP archetype):

    term_bindings = <
        ["SNOMED-CT"] = <
            ["id1"] = 
<http://snomed.info/id/163020007><http://snomed.info/id/163020007>
            ["id5"] = 
<http://snomed.info/id/163030003><http://snomed.info/id/163030003>
            ["id6"] = 
<http://snomed.info/id/163031004><http://snomed.info/id/163031004>
            ["id14"] = 
<http://snomed.info/id/246153002><http://snomed.info/id/246153002>
        >
        ["openehr"] = <
            ["at1055"] = <http://openehr.org/id/125><http://openehr.org/id/125>
            ["at1056"] = <http://openehr.org/id/497><http://openehr.org/id/497>
            ["at1057"] = <http://openehr.org/id/146><http://openehr.org/id/146>
        >
    >
- thomas
On 25/04/2017 07:03, Ian McNicoll wrote:
SNOMED-CT is the official designator, based on the archetype editor terminology 
list.
On Tue, 25 Apr 2017 at 06:36, Pablo Pazos 
<pablo.pa...@cabolabs.com<mailto:pablo.pa...@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 <b...@dips.no<mailto:b...@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-implement...@lists.openehr.org<mailto:openehr-implement...@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.pa...@cabolabs.com<mailto:pablo.pa...@cabolabs.com>
Subscribe to our newsletter<http://eepurl.com/b_w_tj>

_______________________________________________
openEHR-technical mailing list
openEHR-technical@lists.openehr.org<mailto:openEHR-technical@lists.openehr.org>
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
--
Ian McNicoll




_______________________________________________

openEHR-technical mailing list

openEHR-technical@lists.openehr.org<mailto:openEHR-technical@lists.openehr.org>

http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

--
[http://www.openehr.org/files/about/logoweb.png]

Thomas Beale
Management Board, Specifications Program Lead, openEHR 
Foundation<http://www.openehr.org>
Chartered IT Professional Fellow, BCS, British Computer 
Society<http://www.bcs.org/category/6044>
Health IT blog<http://wolandscat.net/> | Culture 
blog<http://wolandsothercat.net/>


_______________________________________________
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Reply via email to