Pablo, I agree that there are special rules on how to use coding systems.
Only in specified domains at specified levels in ontology the pre- or postco-orinated codes can be used safely. Without rules there will be overlap of ways to code in the archetype versus coding in the coding system. This is the Boundary Problem. It can be avoided by rules: - refrain from using co-ordinated codes, except for anatomical structures - create archetypes that allow to express all the pre/post-co-oriated codes - all nodes in the archetype need to be coded using Reference Coding Systems (SNOMED, LOINC) In my view the Archetype is the preferred way to express pre-/post coordinated terms. Gerard Freriks +31 620347088 gf...@luna.nl Kattensingel 20 2801 CA Gouda the Netherlands > On 9 Aug 2018, at 23:10, Pablo Pazos <pablo.pa...@cabolabs.com> wrote: > > IMO it means post coordinated stuff can't be used at design time in > archetypes. It can be used at runtime. For instance we use snomed expressions > embedded in openEHR queries to filter coded texts. In the archetype or > template that defines that coded text, there is only a binding with snomed, > nothing else. > > On Thu, Aug 9, 2018, 09:21 Georg Fette <georg.fe...@uni-wuerzburg.de > <mailto:georg.fe...@uni-wuerzburg.de>> wrote: > Hello, > Using terminology bindings it is posssible to bind terminology IDs of > specific terminologies to archetypes as well as to their members. In the > openEHR documentation it is written that there is no concept of > post-coordination outside the terminology environment. What does that > exactly mean ? When I have a post-coordinated expression, how do I use > it within openEHR ? The linkage of an openEHR system to a potential > terminology server is something that I do not yet unterstand very well. > Greetings > Georg > > -- > --------------------------------------------------------------------- > Dipl.-Inf. Georg Fette Raum: B001 > Universität Würzburg Tel.: +49-(0)931-31-85516 > Am Hubland Fax.: +49-(0)931-31-86732 > 97074 Würzburg mail: georg.fe...@uni-wuerzburg.de > <mailto:georg.fe...@uni-wuerzburg.de> > --------------------------------------------------------------------- > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical@lists.openehr.org > <mailto:openEHR-technical@lists.openehr.org> > http://lists.openehr.org/mailman/listinfo/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
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
