Aw well, we should have a real use-case for you to ponder over very soon :)

Ian

Dr Ian McNicoll
mobile +44 (0)775 209 7859
office +44 (0)1536 414994
skype: ianmcnicoll
email: ian at freshehr.com
twitter: @ianmcnicoll

Director, freshEHR Clinical Informatics
Director, openEHR Foundation
Director, HANDIHealth CIC
Hon. Senior Research Associate, CHIME, UCL

On 5 March 2015 at 10:26, Bj?rn N?ss <bna at dips.no> wrote:

>  Thanks Ian
>
> I forgot to tell that the example was only technical. I just picked
> Medication as an example J
>
> Anyway I guess this kind of technical possibilities is useful for the
> pharmacy review. And - then we must work on the tools to support this kind
> of definitions.
>
>
>
> /
> Bj?rn N?ss
> DIPS ASA
>
> Mobil +47 93 43 29 10 <+47%2093%2043%2029%2010>
>
>
>
> *From:* openEHR-technical [mailto:
> openehr-technical-bounces at lists.openehr.org] *On Behalf Of *Ian McNicoll
> *Sent:* 5. mars 2015 10:27
> *To:* For openEHR technical discussions
> *Cc:* openehr-implementers at lists.openehr.org
> *Subject:* Re: ISM Transition : definition of allowed transitions
>
>
>
> Hi Bj?rn,
>
>
>
> I'm not sure I can answer your technical question but thought I should
> flag up that I am likely to be working on the pharmacy review use case for
> a UK project. My initial analysis is that this might require a separate
> archetype, or at least some extra detail. It might be worth comparing
> requirements.
>
>
>
> Ian
>
>
>   Dr Ian McNicoll
> mobile +44 (0)775 209 7859
> office +44 (0)1536 414994
> skype: ianmcnicoll
> email: ian at freshehr.com
> twitter: @ianmcnicoll
>
> Director, freshEHR Clinical Informatics
> Director, openEHR Foundation
> Director, HANDIHealth CIC
> Hon. Senior Research Associate, CHIME, UCL
>
>
>
> On 3 March 2015 at 13:46, Bj?rn N?ss <bna at dips.no> wrote:
>
>  NB! This is a new e-mail on the same subject since I didn?t see any mail
> on the mailing list. Just to check if it is working
>
>
>
> We are currently developing a module for Careplan based on openEHR
> Archetypes. We are using INSTRUCTION/ACTIVITY/ACTION archetypes to model
> the clinical process.
>
>
>
> One issue we are facing is the need to define which transitions that are
> allowed for a given Careflow Step.
>
>
>
>
>
> To explain I will use openEHR-EHR-ACTION.medication.v1 as example. This
> ACTION archetype have Review medication as an possible ISM_TRANSITION. This
> is an transition that ends in ACTIVE state.
>
> What we want to express is that this careflow step is only allowed for an
> active step (openehr::543). This means that is it not allowed to do this
> careflow step as a start transition (openehr::540).
>
>
>
> A proposed ADL definition for this is given below:
>
>
>
> *ISM_TRANSITION[at0005] matches {     -- Review medication*
>
> *                            current_state matches { *
>
> *                                           DV_CODED_TEXT matches {*
>
> *                                                         defining_code
> matches {[openehr::245]}*
>
> *                                           }*
>
> *                            }*
>
> *                            transition matches{*
>
> *                                           DV_CODED_TEXT matches {*
>
> *                                                         defining_code
> matches {[openehr::543] } ? only allow transition 543 (active) *
>
> *                                           }*
>
> *                            }*
>
> *                            careflow_step matches {*
>
> *                                           DV_CODED_TEXT matches {*
>
> *                                                         defining_code
> matches {[local::at0005]}                            -- Review medication*
>
> *                            }*
>
> *              }*
>
> *}*
>
>
>
> To expand this example we want to allow only two transitions, i.e. ?active
> step? (openehr::543) and ?resume? (openehr::546).
>
>
>
> A proposed ADL definition for this is  given below:
>
>
>
>
>
> *ISM_TRANSITION[at0005] matches {     -- Review medication*
>
> *                            current_state matches { *
>
> *                                           DV_CODED_TEXT matches {*
>
> *                                                         defining_code
> matches {[openehr::245]}*
>
> *                                           }*
>
> *                            }*
>
> *                            transition matches{*
>
> *                                           DV_CODED_TEXT matches {*
>
> *                                                         defining_code
> matches {[openehr::543],[openehr::546] }*
>
> *                                           }*
>
> *                            }*
>
> *                            careflow_step matches {*
>
> *                                           DV_CODED_TEXT matches {*
>
> *                                                         defining_code
> matches {[local::at0005]}                            -- Review medication*
>
> *                            }*
>
> *              }*
>
> *}*
>
>
>
>
>
> And then the questions:
>
>
>
> 1.       Is the first example allowed?
> (defining the allowed transition)
>
> 2.       Is the second example allowed?
> (defining two allowed transitions)
>
>
>
>
>
>
>
>
>
>
>
> Vennlig hilsen
> Bj?rn N?ss
> Produktansvarlig
> DIPS ASA
>
> Mobil +47 93 43 29 10 <+47%2093%2043%2029%2010>
>
>
>
>
> _______________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20150305/dd42b3ca/attachment.html>

Reply via email to