I model using ITEM_TREE as default in every archetype, except where we might
need a table structure.
So I always aim to allow for maximal flexibility as the archetype evolves...
and in almost every situation it does.
Heather
-Original Message-
From: openehr-clinical-bounces at
Yes - and if you want to go one further, ITEM_LIST is nothing more than
a special case of ITEM_TREE as well.
Modelling this explicitly hasn't been extremely useful I believe,
especially if weighed against your evolution argument.
Sebastian
Am 04.10.2011 01:42, schrieb Heather Leslie:
I model
(Espa?a)
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20111004/4d18e261/attachment.html
://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20111004/7588c5be/attachment.html
4 matches
Mail list logo