Pablo Pazos pablo.pazos at
Mon Apr 17 17:57:07 EDT 2017

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


On Wed, Apr 12, 2017 at 5:56 AM, Bert Verhees <bert.verhees at> 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 at

Ing. Pablo Pazos Gutiérrez
Cel:(00598) 99 043 145
Skype: cabolabs
pablo.pazos at
Subscribe to our newsletter <>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the openEHR-clinical mailing list