Hi ACTIVITY has a field for timing. It's datatype is parsable. Some archetypes use a CLUSTER archetype to define detailed timing information for the given ACTIVITY.
I am curious if anyone have experiences with implementing timing for Activity and which strategy you are using? Will detailed timing information in a CLUSTER make timing information on Activity obsolete? Or will detailed timing information on Activity remove the need for a timing CLUSTER? Bj?rn N?ss Product Owner DIPS ASA Mobil +47 93 43 29 10<tel:+47%2093%2043%2029%2010> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130810/16f20e7c/attachment-0001.html>
