RE: Composition commit and change types

2016-04-04 Thread pablo pazos
Eng. Pablo Pazos Gutiérrez http://cabolabs.com > From: i...@freshehr.com > Date: Mon, 4 Apr 2016 21:12:00 +0100 > Subject: Re: Composition commit and change types > To: openehr-technical@lists.openehr.org > > Hi Pablo, > > I think there are lots of interesting approaches

RE: Composition commit and change types

2016-04-04 Thread pablo pazos
Pazos Gutiérrez http://cabolabs.com Subject: Re: Composition commit and change types To: openehr-technical@lists.openehr.org From: thomas.be...@openehr.org Date: Mon, 4 Apr 2016 19:50:50 +0100 On 04/04/2016 19:14, pazospa...@hotmail.com wrote:

Re: Composition commit and change types

2016-04-04 Thread Thomas Beale
On 04/04/2016 19:14, pazospa...@hotmail.com wrote: Hi Thomas, What about having the 'delta' mode just at the API level? Storage might not store delta objects, just full objects, but the API allows to send only what was added, modified or deleted instead of the full compo? then you

Re: Composition commit and change types

2016-04-04 Thread pazospablo
: Thomas BealeDate: Mon, Apr 4, 2016 10:31To: openehr-technical@lists.openehr.org;Subject:Re: Composition commit and change types On 04/04/2016 07:23, pablo pazos wrote: I thought you had more specific cases :) Having specific lists per

Re: Composition commit and change types

2016-04-04 Thread Thomas Beale
On 04/04/2016 07:23, pablo pazos wrote: I thought you had more specific cases :) Having specific lists per clinician was commented by Karsten on a previous message and I commented on that. I'm not sure at which extent that is a backend issue, an API issue or an UI issue. I would say if

RE: Composition commit and change types

2016-04-04 Thread pablo pazos
es any sense? Thanks! -- Kind regards, Eng. Pablo Pazos Gutiérrez http://cabolabs.com From: heath.fran...@oceaninformatics.com To: pazospa...@hotmail.com; openehr-technical@lists.openehr.org Subject: RE: Composition commit and change types Date: Mon, 4 Apr 2016 05:35:13 + Hi Pablo, I did inc

RE: Composition commit and change types

2016-04-03 Thread Heath Frankel
__ From: heath.fran...@oceaninformatics.com To: pazospa...@hotmail.com; openehr-technical@lists.openehr.org CC: openehr-technical@lists.openehr.org Subject: Re: Composition commit and change types Date: Sun, 3 Apr 2016 23:36:25 + Hi Ian and Pablo, Although I don't like comme

RE: Composition commit and change types

2016-04-03 Thread pablo pazos
rrez http://cabolabs.com From: heath.fran...@oceaninformatics.com To: pazospa...@hotmail.com; openehr-technical@lists.openehr.org CC: openehr-technical@lists.openehr.org Subject: Re: Composition commit and change types Date: Sun, 3 Apr 2016 23:36:25 + Hi Ian and Pablo, Although I don't like c

Re: Composition commit and change types

2016-04-03 Thread Heath Frankel
ith change_type creation, and version > them using amendment or modification. > > Does this makes sense? If yes, maybe this can help other implementations :) > > -- > Kind regards, > Eng. Pablo Pazos Gutiérrez > http://cabolabs.com > >> From: i...@freshehr.com >> D

Re: Composition commit and change types

2016-04-03 Thread Ian McNicoll
s sense? If yes, maybe this can help other implementations :) > > -- > Kind regards, > Eng. Pablo Pazos Gutiérrez > http://cabolabs.com > >> From: i...@freshehr.com >> Date: Sun, 3 Apr 2016 11:06:53 +0100 >> Subject: Re: Composition commit and change types >>

RE: Composition commit and change types

2016-04-03 Thread pablo pazos
amendment or modification. Does this makes sense? If yes, maybe this can help other implementations :) -- Kind regards, Eng. Pablo Pazos Gutiérrez http://cabolabs.com > From: i...@freshehr.com > Date: Sun, 3 Apr 2016 11:06:53 +0100 > Subject: Re: Composition commit and change types >

Re: Composition commit and change types

2016-04-03 Thread Ian McNicoll
rom: Ian McNicoll > > Date: Sat, Apr 2, 2016 15:50 > > To: For openEHR technical discussions; > > Subject:Re: Composition commit and change types > > Hi Pablo,When I am advising implementers on this, I use the following > categories ...## Composition Commit StylesDepending on

Re: Composition commit and change types

2016-04-03 Thread Ian McNicoll
m my LG Mobile > > -- Original message-- > > From: Bert Verhees > > Date: Sat, Apr 2, 2016 15:01 > > To: openehr-technical@lists.openehr.org; > > Subject:Re: Composition commit and change types > > I guess you need to version it, if you want it to be ac

Re: Composition commit and change types

2016-04-03 Thread Ian McNicoll
gt; -- Original message-- > > From: Karsten Hilbert > > Date: Sat, Apr 2, 2016 04:25 > > To: openehr-technical@lists.openehr.org; > > Subject:Re: Composition commit and change types > > On Sat, Apr 02, 2016 at 05:59:33AM +, pazospa...@hotmail.com wrote:> >

Re: Composition commit and change types

2016-04-03 Thread pazospablo
: openehr-technical@lists.openehr.org;Subject:Re: Composition commit and change typesI guess you need to version it, if you want it to be according the specs. That means, when you use it for a medication-list, you will get many versions of the same compositions for a patient

Re: Composition commit and change types

2016-04-03 Thread pazospablo
I think that has more to do with the user interface than how compositions are committed, since I can filter meds by who prescribe them with ease. Sent from my LG Mobile -- Original message--From: Karsten HilbertDate: Sat, Apr 2, 2016 04:25To:

Re: Composition commit and change types

2016-04-02 Thread Ian McNicoll
Hi Pablo, When I am advising implementers on this, I use the following categories ... ## Composition Commit Styles Depending on the clinical requirement, 3 styles of commit strategy are suggested. 1. **’Event’** e.g Nursing observations, clinical encounters, reports. Each time the