was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-clinical_lists.openehr.org/attachments/20111004/db19cc74/attachment.html>
...
URL:
<http://lists.openehr.org/mailman/private/openehr-clinical_lists.openehr.org/attachments/20111004/7588c5be/attachment.html>
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 opene
- thomas
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-clinical_lists.openehr.org/attachments/20111004/89b31518/attachment.html>
ierrez
> >>> Blog: http://informatica-medica.blogspot.com/
> >>> Twitter: http://twitter.com/ppazos
>
> ___
> openEHR-technical mailing list
> openEHR-technical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
>
--
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
Instituto ITACA
http://www.ibime.upv.es
Universidad Polit?cnica de Valencia (UPV)
Camino de Vera, s/n, Edificio G-8, Acceso B, 3? planta
Valencia ? 46022 (Espa?a)
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-clinical_lists.openehr.org/attachments/20111004/4d18e261/attachment.html>
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
6 matches
Mail list logo