Problem trying to specify pathway transition constraints
Description
Attachments
- Failed to load
Activity
Peter Gummer June 18, 2013 at 6:38 AM
The fix will be available in the next beta release.
Peter Gummer March 29, 2013 at 3:42 AM
EDT-775
(pablo pazos) inactive January 2, 2013 at 6:14 PM
Hi Sam, the issue refers to the UI elements on the Archetype Editor that doesn't seems to work.
About the ADL, is just a constraint of a DV_CODED_TEXT attribute (ISM_TRANSITION.transition), like the constraints to ISM_TRANSITION.current_state or ISM_TRANSITION.careflow_step.
Maybe we can discuss about requirements on the lists. I mentioned some points (questions) about this on the discussion area of the ACTION.medication archetype on the CKM.
Sam Heard January 2, 2013 at 12:23 PM
HI All
We have never found that the transition constraints should be limited more than the state diagram. Not to say that this will never be so, but it has not been required to this point.
If people actually need to constrain transitions, then there is some work to do in the editor. I am not sure that the ADL has been described?
Peter Gummer January 1, 2013 at 9:31 PM
Yes, it looks like a bug to me. If I save an ACTION archetype with those Suspended" and "Aborted" boxes set, when I reopen the archetype they are not set.
The same problem also happens in the latest beta release, 2.2.876.
I tried this in some very old versions of Archetype Editor too. They have the same problem. So it looks like those check boxes have never worked.
It seems there's is a problem in the Archetype Editor when trying to specify pathway transitions on an ACTION archetype. If I select the "prescribe" state in the "medication pathway" (openEHR-EHR-ACTION-medication.v1) and check on "transition" allowing transitions to "Suspended" and "Abort", the ADL is unchanged.
Is this a bug? I'm using Archetype Editor v2.2.779 Beta
Look the screen captures here: https://plus.google.com/109540968085207927247/posts/73jJSa8THSZ