Hi
Yes that is my opinion as well.

And there is one more "missing link" in my understanding:

Given that there is an ACTIVITY in INITIAL state and the user want to cancel 
the ACTIVITY; then it should be possible to do a transition from INITIAL 
directly to CANCELLED state.

This transition is not defined in the state machine - as far as I can see.

First I thought that the right way to do this was to remove the ACTIVITY. But 
after some thinking I was not satisfied with this solution. I think it would be 
correct if the ACTIVITY was terminated in CANCELLED state.

One reason to do this is if the patient dies.

With regards,
Bj?rn N?ss
Product owner
DIPS ASA
Telephone +47 75 59 24 55
Mobile +47 93 43 29 10


Fra: openEHR-technical [mailto:openehr-technical-bounces at lists.openehr.org] 
P? vegne av pablo pazos
Sendt: 10. september 2013 23:30
Til: openeh technical
Emne: RE: State transitions - ACTIVITY/ACTION

Hi Bj?rn, I think your points are correct, and there are some missing 
transitions on the ISM.


--
Kind regards,
Eng. Pablo Pazos Guti?rrez
http://cabolabs.com<http://cabolabs.com/es/home>
________________________________
From: bna at dips.no<mailto:b...@dips.no>
To: openehr-technical at lists.openehr.org<mailto:openehr-technical at 
lists.openehr.org>
Date: Tue, 10 Sep 2013 10:38:47 +0200
Subject: State transitions - ACTIVITY/ACTION
Hi all.

We are discussing some details with the INSTRUCTION STATE MACINE. I will go 
directly to my two questions:

1
The state machine define transition from all not-terminated states to a 
terminated state. Except from POSTPONED state. There is no defined transition 
from POSTPONED to CANCELLED. The question is how we should model the scenario 
where the ACTIVITY is in POSTPONED and the user want to CANCEL the ACTIVITY in 
one step?

Is there a missing transition in the specification or did we misunderstood 
something?

2
There is a time_out transition from all not-terminated step to EXPIRED. Except 
from Scheduled. There is no time_out transition defined from SCHEDULED to 
EXPIRED

Given the scenario is SCHEDULED and the time for start of the ACTIVTY is 
passed. Should there be a transition named time_out from SCHEDULED to EXPIRED. 
When this transition occurs then system should be notified in some way.

Is there a missing transition named time_out from SCHEDULED or do we 
misunderstood something?

With regards,
Bj?rn N?ss
Product owner
Telephone +47 75 59 24 55
Mobile +47 93 43 29 10
www.dips.com<http://www.dips.com/>

[cid:image001.png at 01CEAF16.E6344690]

This message is for the designated recipient only and may contain confidential 
or private information. If you have received it in error, please notify the 
sender immediately and delete the original.


_______________________________________________ openEHR-technical mailing list 
openEHR-technical at lists.openehr.org<mailto: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/20130911/57d3af8c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 4149 bytes
Desc: image001.png
URL: 
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130911/57d3af8c/attachment-0001.png>

Reply via email to