that simple.
>
>
>
> Maybe I’m dreamin’?
>
>
>
> Cheers
>
>
>
> Heather
>
>
>
> *From:* openEHR-clinical *On
> Behalf Of *Thomas Beale
> *Sent:* Saturday, 28 July 2018 6:12 AM
> *To:* openehr-clinical@lists.openehr.org
> *Subject:* Re:
90 78 89 33
Fra: openEHR-clinical [mailto:openehr-clinical-boun...@lists.openehr.org] På
vegne av Pablo Pazos
Sendt: 2. juli 2018 22:45
Til: For openEHR clinical discussions
mailto:openehr-clinical@lists.openehr.org>>
Emne: Re: How to define transitions in the ISM
Hi Heather,
-clinical-boun...@lists.openehr.org] *På vegne av*
Pablo Pazos
*Sendt:* 2. juli 2018 22:45
*Til:* For openEHR clinical discussions
<mailto:openehr-clinical@lists.openehr.org>>
*Emne:* Re: How to define transitions in the ISM
Hi Heather, thanks for the insight.
It seems this is a well k
Thomas, when I said "mapped to ASSIGNED" was an error, it is "mapped to
PLANNED", the flow that I explained is correct, not the last comment. My
domain "NEW" and "ASSIGNED" are mapped to ISM "PLANED". THe core issue is
the need to define the transition between domain ASSIGNED to domain
STARTED,
On 01/07/2018 08:21, Heather Leslie wrote:
Hi Pablo,
Every archetype ideally needs to be designed for the maximal dataset
and universal use case. The ACTION archetypes are no different.
But you have picked up on a major gap in our tooling at present – the
modellers need the ability to be
On 27/06/2018 08:35, Bakke, Silje Ljosland wrote:
Hi Pablo!
I’ll try to answer your question about how clinical modellers solve
this problem. Have a look at the ACTION.medication archetype
(http://openehr.org/ckm/#showArchetype_1013.1.123). This archetype has
11 separate steps for the
stemutvikler
>
> DIPS AS
> Telefon +47 75 59 24 06
>
> Mobil +47 90 78 89 33
>
>
>
>
> *Fra:* openEHR-clinical [mailto:openehr-clinical-boun...@lists.openehr.org]
> *På vegne av* Pablo Pazos
> *Sendt:* 27. juli 2018 11:45
>
> *Til:* For openEHR clinical discuss
å vegne av* Pablo Pazos
> *Sendt:* 27. juli 2018 10:32
> *Til:* For openEHR clinical discussions <
> openehr-clinical@lists.openehr.org>
> *Emne:* Re: How to define transitions in the ISM
>
>
>
> @Peter thanks for the feedback!
>
>
>
> As Diego mentioned, I think c
...@lists.openehr.org]
> *På vegne av* Pablo Pazos
> *Sendt:* 27. juli 2018 10:32
> *Til:* For openEHR clinical discussions <
> openehr-clinical@lists.openehr.org>
> *Emne:* Re: How to define transitions in the ISM
>
>
>
> @Peter thanks for the feedback!
>
>
>
&g
t;> desperately needed for serious use of the ISM.
>>
>>
>>
>> Vennlig hilsen
>>
>> *Ivar Yrke*
>>
>> Senior systemutvikler
>>
>> DIPS AS
>> Telefon +47 75 59 24 06
>>
>> Mobil +47 90 78 89 33
>>
>>
&
nehr-clinical-boun...@lists.openehr.org]
> *På vegne av* Peter Gummer
> *Sendt:* 26. juli 2018 15:18
>
> *Til:* For openEHR clinical discussions openehr.org>
> *Emne:* Re: How to define transitions in the ISM
>
>
>
> Hi Ivar and Pablo,
>
>
>
> Reading this,
Hi Ivar,
On 27 Jul 2018, at 18:02, Ivar Yrke wrote:
>
> I actually did look into the code. After some struggling into the VB code
> (which isn’t my strong side) I eventually found that the problem also went
> into the underlying java-classes (which is not my strong side either). I
>
the user through the states. In fact, it could be
> argued that this be recorded as an ad hoc action.
>
> With regards,
> Ivar Yrke
> Senior systemutvikler
> DIPS AS
> Telephone +47 75 59 24 06
> Mobile +47 90 78 89 33
>
>
> Fra: openEHR-clinical
ut not as a suggestion from our system! This
>> situation must be handled separately from guiding the user through the
>> states. In fact, it could be argued that this be recorded as an ad hoc
>> action.
>>
>>
>>
>> With regards,
>> *Ivar Yrke*
>>
&g
ct, it
> could be argued that this be recorded as an ad hoc action.
>
>
>
> With regards,
> *Ivar Yrke*
>
> Senior systemutvikler
>
> DIPS AS
> Telephone +47 75 59 24 06
>
> Mobile +47 90 78 89 33
>
>
>
>
> *Fra:* openEHR-clinical [mailto:openehr-c
rs implementing systems.
>
>
>
> No silver bullet here, yet. But open to collaborate with anyone who has
> suggestions…
>
>
>
> Regards
>
>
>
> Heather
>
>
>
> *From:* openEHR-clinical *On
> Behalf Of *Pablo Pazos
> *Sent:* Sunday, 1 July 2018
to define transitions in the ISM
Hi Silje,
I got the issue with complex workflows.
With the current solution you'll need to provide more metadata to the
developers so they can implement the correct workflows, like possible or
impossible transitions from one state to another, because constraints
Hi Silje,
I got the issue with complex workflows.
With the current solution you'll need to provide more metadata to the
developers so they can implement the correct workflows, like possible or
impossible transitions from one state to another, because constraints are
not in the archetype.
On the
Hi Pablo!
I’ll try to answer your question about how clinical modellers solve this
problem. Have a look at the ACTION.medication archetype
(http://openehr.org/ckm/#showArchetype_1013.1.123). This archetype has 11
separate steps for the ACTIVE state. In each medication management context, one
19 matches
Mail list logo
