Re: Postcoordinated terminology expressions in openEHR

2018-11-19 Thread Michael.Lawley
I'm with Ian on this. The only use of post coordination is hard and requires complex tooling support that is way beyond any value you get. I would say even laterality & other qualifiers should go in the information model and not in the terminology if you have the choice. If you are instead ta

Re: Postcoordinated terminology expressions in openEHR

2018-11-19 Thread David Moner
Hi, just for clarification, you have mixed are two different things: - SNOMED CT postcoordinated expressions are structured combinations of one or more concepts to express a clinical idea. You use them to create new concepts not available in the SNOMED release. They are built using the SNOMED CT C

Re: Postcoordinated terminology expressions in openEHR

2018-11-19 Thread Ian McNicoll
Yes agree laterality is another potentially high value case. They should probably talk to the CIMI folks. Stan Huff has a good an idea as anyone of both the potential and pitfalls of complex terminology handling. I suspect that really held CIMI back at a critical moment but at least they have a go

Re: Postcoordinated terminology expressions in openEHR

2018-11-19 Thread Thomas Beale
I mostly agree with Ian, but with the small caveat that for very specific and well-known cases such as body laterality, you just /might consider/ post-coordination on body site e.g. * 56459004 |foot structure| : 272741003 |laterality| = 7771000 |left|) However, even here, laterality often see

Re: Postcoordinated terminology expressions in openEHR

2018-11-19 Thread Ian McNicoll
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 ev