Re: relationship between change type and lifecycle state
Thomas Beale-3 wrote: > > > ... > > well, the audit change types are not states in a cycle - they merely > indicate what kind of change was done in going from the previous > version the information to the current version. But there is certainly > a (albeit simple) state machine implied in the lifecycle state, which > is currently: > > (initial) -> incomplete -> complete > (initial) -> complete > incomplete -> deleted > complete -> deleted > > ... > > A matrix of allowed combinations between lifecycle state and change type would be very useful. Also a deeper description of state machine for lifecycle state in the specs would be great. Indeed I have again some doubts about possible transitions: Is it possible to have a the following transition: ... -> deleted -> complete ... -> deleted -> incomplete in the case that we have deleted the compostion wrongly, and now we want to "resume" it! and can we have (initial) -> incomplete -> complete -> incomplete Thanks leo -- View this message in context: http://old.nabble.com/relationship-between-change-type-and-lifecycle-state-tp18477554p28509028.html Sent from the openehr-implementers mailing list archive at Nabble.com. _______________________________________________ openEHR-implementers mailing list openEHR-implementers@openehr.org http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-implementers