When I was trying to validate an archetype with the reference model
(openEHR-EHR-OBSERVATION.apgar), I found something strange on all
'event' archetypes.
The EVENT class has a function (method) that calculates the offset.
However, in that archetype the offset was restricted as if it was an
In ADL/AOM, constraints can be made on computed properties as well as
stored ones. If you look at the spec, EVENT.offset is computed as
time.diff(parent.origin). Making a constraint on EVENT.time, which is
the absolute time (which is what you want in the data) is annoying
because you want to
to look for ui annotations and do
sensible things with them.
thoughts?
- thomas
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20120109/b95561fd/attachment.html
obviously be made to
work, and isn't hard to implement. However, now rendering software has to know
to look for ui annotations and do sensible things with them.
thoughts?
- thomas
__ Information from ESET NOD32 Antivirus, version of virus signature
database 6780 (20120109
/mailman/private/openehr-technical_lists.openehr.org/attachments/20120109/7e3bd9d7/attachment.html
-- next part --
A non-text attachment was scrubbed...
Name: fdcdijfa.png
Type: image/png
Size: 8902 bytes
Desc: not available
URL:
http://lists.openehr.org/mailman/private
5 matches
Mail list logo