Hi Bj?rn, I don't use timing yet, but only because the healthcare domains I'm working on doesn't require complex timing management.Said that, I have investigated how to use timing for more complex scenarios, like hospitalization medication management. One option is to use cron expressions. That's great because is a de facto standard for developers, and linux support that at the OS level. So it's something that you can write/parse but also execute to trigger events. Another option would be to use ISO 8601 duration notation, standard and easy to create/parse. I'm sure there are more options out there, but I would recommend those two. In my opinion the current specs lack information about how to use timing, and that makes things more complex to us (developers). http://en.wikipedia.org/wiki/Cron http://en.wikipedia.org/wiki/ISO_8601
-- Kind regards, Eng. Pablo Pazos Guti?rrez http://cabolabs.com From: b...@dips.no To: openehr-technical at lists.openehr.org Date: Sat, 10 Aug 2013 10:24:14 +0200 Subject: ACTIVITY and timing 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 _______________________________________________ openEHR-technical mailing list openEHR-technical at lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130810/b10cdd2e/attachment.html>
