on the big picture, not
the minutiae of data integrity, which is mostly overlooked but
ubiquitiously present.
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20071017/d5d147e3
Grahame Grieve wrote:
At the moment we have not seen any need for multiple inheritance in
archetypes.
I see this as very similar to multiple inheritance in objects.
There is no *need*, but there is useful things that can be done.
The question is whether the price is justified.
The
Hi Koray,
A practical example of 'C' that is currently in the archetype repository is
the Histological Diagnosis archetype -
openEHR-EHR-EVALUATION.problem-diagnosis-histological.v1.ad
Problem -- specialised to Diagnosis -- specialised to Histological
Diagnosis - all of which are in the
Andrew Patterson wrote:
I should note that in the next generation of archetypes and tooling,
archetype 'source' files for specialised archetypes will be
'differential' in nature - i.e. valid ADL, but containing only added and
changed items from the parent, just as for subclasses in an
4 matches
Mail list logo