t;
- thomas beale
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20101116/9c30359a/attachment.html>
Hi Zam! :-)
I was merely trying to keep most of the same semantic power in the
change suggestion as when the abstract ITEM_STRUCTURE (that subsumed
ITEM_SINGLE, ITEM_TREE etc) was used rather than ITEM_TREE in various
places in the RM model. But you might be completely correct that it
would be bet
--- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20101116/a8ee2936/attachment.asc>
technical mailing list
> openEHR-technical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
>
>
------ next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20101116/4a04623b/attachment.html>
lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20101116/49fb391c/attachment.html>
Hi All
The adoption of all health standards is very slow; and it is universally so.
Government eHealth programs have embraced HL7v3 or CDA or openEHR or 13606 -
at great cost. Still things go slowly. The fact is that until people want a
shared logical model of the actual EHR (rather than a message
Hi Eric
I would always use CLUSTER rather than ITEM for the data and other features
in other classes. The alternative is to have far more versions of archetypes
as if you allow element at this point you have to version when cluster is
necessary (which you could argue it always will be at some time
7 matches
Mail list logo
