Basically - don't!! The UK has been trying to do this for over 20 years without success. It is a terminologists dream but implementers nightmare.
Make a start with high-value use cases e.g Allergy agent "Allergic to + causative agent" - so that you do not have to generate a new Snomed code for every potential allergen. Perhaps consider laterality. Beyond that, you risk delaying SNOMED CT implementation, as has happened in the UK. Post-coordination is like nuclear fusion - a damned good idea but tricky to do without blowing everything up. Ian 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 Mon, 19 Nov 2018 at 13:20, Bakke, Silje Ljosland < silje.ljosland.ba...@nasjonalikt.no> wrote: > Hi everyone, > > > > We’ve recently started an informal and practically oriented regular > contact with the Norwegian SNOMED CT NRC. One of the things they were > interested in discussing was how to use postcoordinated SNOMED CT > (expression constraint language) expressions with openEHR, which I know > nothing about. Does anyone have any knowledge about or experience with this? > > > > Kind regards, > *Silje Ljosland Bakke* > > > > Information Architect, RN > > Coordinator, National Editorial Board for Archetypes > Nasjonal IKT HF, Norway > > Tel. +47 40203298 > > Web: http://arketyper.no / Twitter: @arketyper_no > <https://twitter.com/arketyper_no> > > > _______________________________________________ > openEHR-technical mailing list > 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
