On 10/12/2011 17:04, Eunice Ab wrote:
Hi Thomas and Seref
Many thanks for your response ... this was what I thought too
.... but then does that not mean that all that is needed to be
able to capture both under actions is an attribute of 'type' for
'intended' and 'actual' OR 'request' and 'response' rather than
separating them to remove the confusion of thinking both are not
actions.
no, because the information structure of an Instruction is in future
time, so specifying it requires structures / data items that
correspond to that. The model we use in openEHR is by no means the
best, but it illustrates: in future time you specify what might
possibly happen, including with conditional branches, as workflow
engines do. Actions are in past time, and are therefore simpler to
represent. On the other hand, Actions being performed usually
represent transitions in a state machine. See the openEHR models of
these two Entry types
here.
- thomas
_______________________________________________
openEHR-clinical mailing list
openEHR-clinical@...
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical
