Re: SNOMEDCT - correct representation

2017-04-26 Thread Daniel Karlsson 
Hi All,

please use this link to refer to the SNOMED CT URI Standard: 
https://confluence.ihtsdotools.org/display/DOCURI

This page contains more info about SNOMED CT languages:
https://confluence.ihtsdotools.org/display/SLPG/SNOMED+CT+Languages+Project+Group

Thanks,
Daniel
On ons, 2017-04-26 at 14:00 +0100, Thomas Beale wrote:


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"] = 

["id5"] = 

["id6"] = 

["id14"] = 

>
["openehr"] = <
["at1055"] = 
["at1056"] = 
["at1057"] = 
>
>

- 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 
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"] = 
>
>
>



On Mon, Apr 24, 2017 at 7:33 PM, Bjørn Næss 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?

 
Høyre øye

  
SNOMEDCT
  
  18944008

  

Vennlig hilsen
Bjørn Næss
Produktansvarlig
DIPS ASA

Mobil +47 93 43 29 10


___

openEHR-implementers mailing list
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://www.cabolabs.com
pablo.pa...@cabolabs.com
Subscribe to our newsletter

___
openEHR-technical mailing list
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
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
Chartered IT Professional Fellow, BCS, British Computer 
Society
Health IT blog | Culture 
blog


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

Re: SNOMEDCT - correct representation

2017-04-26 Thread Thomas Beale 


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"] = 
["id5"] = 
["id6"] = 
["id14"] = 
>
["openehr"] = <
["at1055"] = 
["at1056"] = 
["at1057"] = 
>
>

- 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 > 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"] =

>
>
>



On Mon, Apr 24, 2017 at 7:33 PM, Bjørn Næss 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?


Høyre øye


SNOMEDCT

18944008



Vennlig hilsen
Bjørn Næss
Produktansvarlig
DIPS ASA

Mobil +47 93 43 29 10 


___

openEHR-implementers mailing list
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

http://www.cabolabs.com 
pablo.pa...@cabolabs.com 
Subscribe to our newsletter 

___
openEHR-technical mailing list
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
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org


--

*Thomas Beale*
Management Board, Specifications Program Lead, openEHR Foundation 

Chartered IT Professional Fellow, BCS, British Computer Society 

Health IT blog  | Culture blog 




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