Re: openEHR-technical Digest, Vol 80, Issue 12

y >> > >> > Tel. +47 40203298 >> > >> > Web: http://arketyper.no <http://arketyper.no/>/ Twitter: >> > @arketyper_no <https://twitter.com/arketyper_no> >> > >> > ___

Re: openEHR-technical Digest, Vol 80, Issue 12

nehr-technical_lists.openehr.org > > > > > > ___ > > openEHR-technical mailing list > > openEHR-technical@lists.openehr.org > > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > -- > T

Re: Postcoordinated terminology expressions in openEHR

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

Re: Postcoordinated terminology expressions in openEHR

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

Re: Postcoordinated terminology expressions in openEHR

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

Re: Postcoordinated terminology expressions in openEHR

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

openEHR BMM files have moved to new specifications-ITS-BMM repository

*Attention all users of the openEHR BMM files*: these used to be in the Github repo reference-models , but have now moved to specifications-ITS-BMM Github repo . They have also had numerous small

Re: Postcoordinated terminology expressions in openEHR

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

Postcoordinated terminology expressions in openEHR

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