I agree > The message is simple: don't allow items with complex meanings in leafnodes, > but use archetypes to represent complexity.
Gerard Freriks +31 620347088 [email protected] Kattensingel 20 2801 CA Gouda the Netherlands > On 3 Apr 2018, at 00:04, A Verhees <[email protected]> wrote: > > In addition to this, OpenEhr tends to the use of simple precoordinated > concepts, that is because the archetypes explain the details. > > It is, for example, rare in OpenEhr to use the concept for "bloodpressure > sitting". Normally one would create two leafnodes, one with the concept for > "bloodpressure", the other for "sitting". This level of expressing detail in > archetypes is historically grown in the years from before SNOMED, and it > seems like a blessing now, because it makes the discussion about concepts > with complex meaning a bit superfluous. > > Avoid complex meanings in leaf nodes and express complexity in archetype > structure, and the number of different concepts to be used will be reduced > and the chance of availability of needed concepts rises. > > The message is simple: don't allow items with complex meanings in leafnodes, > but use archetypes to represent complexity. >
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
