That is correct Bert, There is no need to remove the SNOMED CT bindings from the archetypes.
Ian Dr Ian McNicoll mobile +44 (0)775 209 7859 office +44 (0)1536 414994 skype: ianmcnicoll email: i...@freshehr.com twitter: @ianmcnicoll Co-Chair, openEHR Foundation ian.mcnic...@openehr.org Director, freshEHR Clinical Informatics Ltd. Director, HANDIHealth CIC Hon. Senior Research Associate, CHIME, UCL On 25 April 2017 at 11:40, Bert Verhees <bert.verh...@rosa.nl> wrote: > On 25-04-17 09:32, Ian McNicoll wrote: > >> Hi Bert, >> >> SNOMED CT Licensing re openEHR is under active discussion with SNOMED. >> >> The principle will be that archetypes or templates containing SNOMED CT >> codes can be freely used within systems, unless the system actually uses >> SNOMED CT codes in the patient data i.e as part of a defining_code or >> mapping, in which case a SNOMED license will be required. >> > > Ok, I misunderstood that, I thought you were in discussion about using > SNOMED in CKM term-bindings, and that users without affiliate license > should manually remove them. > But as I understand it now, you are in discussion about permission for > using SNOMED in term-bindings, also when you have no affiliate license. > > That would make life simpler for many (not for me, but our German friends) > > > Bert > > _______________________________________________ > openEHR-clinical mailing list > openEHR-clinical@lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-clinical_ > lists.openehr.org >
_______________________________________________ openEHR-clinical mailing list openEHR-clinical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
