Hi Pablo, Can you give a specific use-case? In general I would expect a completed activity to need to need a new instruction. As Thomas says, if you have a scenario where there multiple rounds of activity take place, I would regard that as the instruction still being active, and the completed state would only apply when all of the rounds had been completed.
BTW - I have updated all the ACTION archetypes on CKM to have nodeIds on ISM_TRANSITION. Ian On 9 August 2012 17:44, pablo pazos <pazospablo at hotmail.com> wrote: > Hi Thomas, > > I agree with that, but I think we are talking about different scenarios. I > understand we can have various ACTIONs for "active" states (and reschedule > or suspend/resume transitions). > > My question is: if an ACTIVITY is "completed" (or "aborted" or "expired", > i.e. a terminated state) > > is it possible or valid to start another execution cycle for that ACTIVITY > instance? or, > should I create another ACTIVITY instance with the same info in order to > execute it? i.e. create another ACTION with state "scheduled" or "active" > for the same ACTIVITY that is "completed". > > > Thanks a lot! > > -- > Kind regards, > Ing. Pablo Pazos Guti?rrez > LinkedIn: http://uy.linkedin.com/in/pablopazosgutierrez > Blog: http://informatica-medica.blogspot.com/ > Twitter: http://twitter.com/ppazos > > ________________________________ > Date: Thu, 9 Aug 2012 16:47:07 +0100 > > From: thomas.beale at oceaninformatics.com > To: openehr-technical at lists.openehr.org > Subject: Re: Commiting ACTIONs for the same INSTRUCTION ACTIVITY > > On 08/08/2012 22:03, pablo pazos wrote: > > Hi, > > Just a small related question: can I continue executing ACTIONs for an > ACTIVITY that has already be "completed"? or do I need to create another > ACTIVITY with the same information in order to have another execution > workflow? > > e.g. is this valid? > > - create INSTRUCTION/ACTIVITY > - create ACTION (state = scheduled) > - create ACTION (state = active) > - create ACTION (state = completed) > - create ACTION (state = scheduled) // for the same INSTRUCTION/ACTIVITY > instance as the previous flow: scheduled > active > completed > > > > > Pablo, > > it's completely up to what you have archetyped. If you have an ACTION who > state is 'active', you can map numerous care pathway steps to that, e.g. you > might map 'dispense', 'administer', 're-issue' all to the 'active' state. So > that means 3 different kinds of Action that can keep occurring in time, and > each time, the state machine is still in 'active' state. > > Even if you only map one care pathway step, say 'administer' to the active > state, you can of course have numerous occurrences of administration over > time. > > So both ways, a single ACTIVITY can lead to numberous ACTIONs. > > - thomas > > > _______________________________________________ openEHR-technical mailing > list openEHR-technical at lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org -- Dr Ian McNicoll office +44 (0)1536 414 994 fax +44 (0)1536 516317 mobile +44 (0)775 209 7859 skype ianmcnicoll ian.mcnicoll at oceaninformatics.com Clinical Modelling Consultant, Ocean Informatics, UK Director openEHR Foundation www.openehr.org/knowledge Honorary Senior Research Associate, CHIME, UCL SCIMP Working Group, NHS Scotland BCS Primary Health Care www.phcsg.org
