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>: > 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> > 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> 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 >>> 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://cabolabs.com/> >> http://www.cabolabs.com >> pablo.pa...@cabolabs.com >> Subscribe to our newsletter <http://eepurl.com/b_w_tj> >> _______________________________________________ >> 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 > -- [image: VeraTech for Health SL] <https://htmlsig.com/t/000001C268PZ> [image: Twitter] <https://htmlsig.com/t/000001C47QQH> [image: LinkedIn] <https://htmlsig.com/t/000001C4DPJG> [image: Maps] <https://htmlsig.com/t/000001BZTWS7> Diego Boscá Tomás / Senior developer diebo...@veratech.es yamp...@gmail.com VeraTech for Health SL +34 961071863 <+34%20961%2007%2018%2063> / +34 627015023 <+34%20627%2001%2050%2023> 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.
_______________________________________________ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
