There is a spec that tells you how to identify different editions and versions of SNOMED CT - see http://snomed.org/uri
In short, http://snomed.info/sct 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 http://snomed.info/sct/12345678 Michael Sent from my iPhone On 25 Apr 2017, at 5:52 pm, Diego Bosc? <yamp...@gmail.com<mailto:yamp...@gmail.com>> 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 <i...@freshehr.com<mailto:i...@freshehr.com>>: 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 Naess <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 Naess 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 -- [VeraTech for Health SL]<https://htmlsig.com/t/000001C268PZ> [Twitter] <https://htmlsig.com/t/000001C47QQH> [LinkedIn] <https://htmlsig.com/t/000001C4DPJG> [Maps] <https://htmlsig.com/t/000001BZTWS7> [https://s3.amazonaws.com/htmlsig-assets/spacer.gif] Diego Bosc? Tom?s / Senior developer diebo...@veratech.es<mailto:diebo...@veratech.es> yamp...@gmail.com<mailto:yamp...@gmail.com> VeraTech for Health SL +34 961071863<tel:+34%20961%2007%2018%2063> / +34 627015023<tel:+34%20627%2001%2050%2023> www.veratech.es<http://www.veratech.es/> 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 verat...@veratech.es<mailto:verat...@veratech.es>. _______________________________________________ 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
_______________________________________________ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org