The specialisation in the OpenEHR RM itself is an anomaly, that can be circumvented.
Gerard Freriks +31 620347088 gf...@luna.nl Kattensingel 20 2801 CA Gouda the Netherlands > On 31 Mar 2018, at 12:14, Bert Verhees <bert.verh...@rosa.nl> wrote: > > On 31-03-18 12:11, GF wrote: >> Both styles are possible with any RM. >> It is a choice. > Do you mean, inside OpenEhr by using the GenericEntry? > Or are there other entry-types possible also? > >> >> Most archetype modellers use the Class-Attribute / Archetype Node style. >> >> Gerard Freriks >> +31 620347088 >> gf...@luna.nl <mailto:gf...@luna.nl> >> >> Kattensingel 20 >> 2801 CA Gouda >> the Netherlands >> >>> On 31 Mar 2018, at 11:04, Bert Verhees <bert.verh...@rosa.nl >>> <mailto:bert.verh...@rosa.nl>> wrote: >>> >>> Maybe we should relate this thinking to CEN13606 because that Reference >>> Model allows more generic thinking. >>> (Thinking this because GF was the convenor of this CEN standard) >>> >>> But even then some more explanation would be welcome. >>> >>> Bert >> >> >> >> _______________________________________________ >> 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>
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
