Currently the use of specific SNOMED CT codes in archetypes is for further definition / specification of the clinical concepts.
To use SNOMED CT at runtime, external constraints are used in the form of URIs, that might point to a SNOMED domain or specific subset. If the subset is local, the archetype might not be the place of setting the constraints since archetypes should be general purpose & globally valid. A template might be the right place of setting those constraints (specific, locally valid). Regards, Pablo. On Wed, Apr 12, 2017 at 5:56 AM, Bert Verhees <bert.verh...@rosa.nl> wrote: > Hi, > I needed to clean up archetypes from SNOMED bindings because of > license-reasons, I "grepped" the local directory from CKM. > To my surprise I found there SNOMED bindings in over 50 archetypes. > This can, I think, be a problem for countries which have no SNOMED license. > Or is the opinion that SNOMED is allowed in archetypes even in > non-member-countries. > > Bert > > > _______________________________________________ > openEHR-clinical mailing list > openEHR-clinical@lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-clinical_ > 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-clinical mailing list openEHR-clinical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
