Hi Tiago, This should only be an issue if you have to perform an update. My best understanding is that known of the well-known implementations try to perform a 'diff' in event of an update they simply create a full new version of the composition based on the new data.
Whilst this is a bit inefficient, the realities for performing diffs safely across the full range of potential scenarios is quite daunting and raises many potential clinical safety issues. My suggestion would just to recreate the composition each time. ian Dr Ian McNicoll mobile +44 (0)775 209 7859 office +44 (0)1536 414994 skype: ianmcnicoll email: [email protected] twitter: @ianmcnicoll Co-Chair, openEHR Foundation [email protected] Director, freshEHR Clinical Informatics Ltd. Director, HANDIHealth CIC Hon. Senior Research Associate, CHIME, UCL On 12 September 2016 at 05:16, Tiago Santos da Silva <[email protected]> wrote: > I understood. > > The solution is using multiples DV_CODED_TEXT and uniqueness is > implemented by software. > > In this case I think that the data persistence is made of many leaf paths > (one value by leaf). I don't see the problem in saving the entire > composition in a contribution, but if I send only changed data I have to > find a way of delete a leaf when "checkbox" is deselected. I know how to > update key/path data but I didn't find deletion in the openEHR > specification (Probably I failed when I was searching for this). > > I think that is just a implementation problem and I wont't find that in > specification. Am I correct? > > Thanks, you helped me a lot! > > 2016-09-10 20:48 GMT-03:00 Tiago Santos da Silva <[email protected]>: > >> I understand that you can use a cluster with multiple Boolean. But I >> would like that the values came from a terminology. >> >> Maybe a better example would be the following: >> >> 1) Select the laboratory tests that should I request: >> [ ] Blood Glucose >> [ ] Blood Culture >> [ ] Albumin >> < 100 other tests ...> >> [ ] Amylase >> >> Can't I use the values of a terminology such as list of options using >> openEHR? Do I must write all the laboratory tests in the archetype like >> booleans? >> >> I have trouble understanding how openEHR handles lists of values. I think >> I have to use the field "occurrences 0.*" but I'm not sure if that is the >> correct way. >> >> Maybe I'm not thinking right about how to use OpenEHR. >> >> Thanks for helping. >> >> - Tiago >> >> 2016-09-10 16:37 GMT-03:00 Tiago Santos da Silva <[email protected]>: >> >>> Hi, >>> >>> Can anyone tell how I can model the example below? >>> >>> "What parts of the body hurt? [ ] right leg [ ] left leg [ ] head [ ] >>> right arm .." >>> >>> I know to model a single option (radio-buttom) but I don't know to model >>> a multiple options (checkbox) >>> >>> The idea is that the options are of the terminology, so I can't model >>> right in the archetype. >>> >>> I'm using the key-path strategy for data persistence. In the case of >>> the radiobutton leaf is a DV_CODED_TEXT but I don't know when use checkbox. >>> >>> Note: English is not my native language I hope it is clear the doubt. >>> >>> Thank you! >>> >> > > _______________________________________________ > openEHR-technical mailing list > [email protected] > http://lists.openehr.org/mailman/listinfo/openehr- > technical_lists.openehr.org >
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
