FW: SV: ACTIVITY and timing
timing in every ACTIVITY. (I guess clinical modeling should be done with specialization some way to define an Action Archetype with timing information). Use the openEHR-EHR-CLUSTER.timing.v1 (or another defined structure) ? to be able to share timing information as Archetype defined structure between openEHR enabled systems . ? to be able to let the Clinical Modeling people define the complexity of timing in HealthCare I can also see some challenges with the optional attribute WF_DEFINITION on the INSTRUCTION class and the mandatory attribute timing on the ACTIVITY class. I think there will be some correlation between these attributes in a given use-case. ___ 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/20130815/9c0b6776/attachment.html
How to start
Hi!
On Wednesday, August 14, 2013, Thomas Beale wrote:
do you have content you want on that learning centre page? If so, let's
put it up there.
Well, the appendix at http://www.biomedcentral.com/1472-6947/13/57#sec9 is
our attempt to create a very compact openEHR intro, if you feel that it is
useful, then feel free to link to it from the learning centre page or some
other place.
The illustrations/figures created by us (and the text) are CC-BY licensed
and can thus be freely reused in other contexts or translated provided that
the source is attributed.
//Erik
On 08/08/2013 21:27, Erik Sundvall wrote:
Hi!
On Wed, Aug 7, 2013 at 3:21 AM, Lexis Nexis lexisnexis5490 at gmail.com
javascript:_e({}, 'cvml', 'lexisnexis5490 at gmail.com'); wrote:
Is there a tutorial book I can purchase or some examples? Step-by-step
tutorial is best.
Skim through the
documenthttp://www.openehr.org/releases/1.0.2/architecture/overview.pdf to get
an overview then go back to that and other documents for more detail
when needed. Also there are some videos
athttp://www.openehr.org/resources/learning_centre if you prefer
watching over reading.
If you don't mind using alpha-versions of work in progress, then feel
free to do some openEHR hands-on experiments
usinghttps://github.com/LiU-IMT/EEE described in the
paperhttp://www.biomedcentral.com/1472-6947/13/57 (Appendix B
athttp://www.biomedcentral.com/1472-6947/13/57#sec9 is a very compact
openEHR intro, perhaps too compact.)
I hope the instructions at https://github.com/LiU-IMT/EEE/wiki/install
helps you get it up and running. Try running and modifying AQL queries
on the provided example content for example.
--
V?nliga h?lsningar, / Best regards,
Erik Sundvall
Tel: +46-72-524 54 55
LiO: erik.sundvall at lio.se http://www.lio.se/Verksamheter/IT-centrum/
LiU: erik.sundvall at liu.se http://www.imt.liu.se/~erisu/
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130815/edcfaa72/attachment-0001.html
SV: ACTIVITY and timing
-technical_lists.openehr.org/attachments/20130815/30365ef6/attachment-0001.html -- next part -- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 19468 bytes Desc: not available URL: http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130815/30365ef6/attachment-0001.png
SV: ACTIVITY and timing
Hi Thomas, On 13/08/2013 16:23, pablo pazos wrote: Hi Thomas, thanks for the input, is great to understand the rationale behind ACTIVITY.timing. Right now I've more questions than proposals :) ...The RM says that ACTIVITY.timing should always be present, and i believe it should be, otherwise processing software doesn't know what to do... Should all INSTRUCTION/ACTIVITIES be processed by a processing software? My guess is no, but maybe I'm wrong. It would be great to hear arguments on that. The need for timing seems to be required for medication INSTRUCTIONs, or generalizing that: all INSTRUCTIONS that involve some kind of event repetition/frequency. But what about LAB/RAD requests? Those are one time events, and their execution depends on scheduling, i.e. timing on request could not be something formal and specific. In practice, the only time specification I know for LAB/RAD requests is the urgent flag, and the real time of execution depends on the resource availability on each health center. What do you think about timing specification of ACTIVITIES that have no repetitions? What values should we use for ACTIVITY.timing when recording a RAD request? There is no assumption in ACTIVITY.time that the activity is repeated. In the GTS syntax, you can just as easily express a one-off event at a certain time as you can a repeated event. If you use cron syntax, I think you just put a full date / time from memory (although that's pretty unusual usage of cron syntax). I understand that timing can express just one date or a set of dates, what I try to understand is more about semantics: what's the purpose / meaning of having just one date on ACTIVITY.timing? If the answer is to specify the exact date/time that the ACTIVITY should be executed, the RAD/LAB case can be taken as a counter example, because the execution time depends on scheduling, and that is done after the recording the ACTIVITY. I don't know if I made that clear, please let me know if my question is not clear or if my understanding of the timing attribute is incorrect. One crucial thing is to ensure that these data remain interoperable. To do that, we need to limit the syntaxes that could be used in ACTIVITY.timing to a reasonably small number, and standardise their use. I am not sure for example, if it will be a good idea to have 3 ways of expressing '3 times/day for 7 days' or other typical things. Is not a problem to have several ways of expressing timing, as long as those are specified publicly. Then we just need to define some terminilogy subset to express each notation identifier e.g. as MIME-TYPE for email content. Then when we parse the expression, knowing the term id, we can choose the right parser. Obviously we need to write those, that's the easy part, but is easy only if all the notation specs are available and the term subset is specified. - thomas ___ openEHR-clinical mailing list openEHR-clinical at lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org -- next part -- An HTML attachment was scrubbed... URL: http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130815/6f6234ac/attachment.html
