SV: SV: Usage of Compositoin.Category

2016-04-11 Thread Bjørn Næss
-technical-boun...@lists.openehr.org] På vegne av Thomas Beale Sendt: mandag 11. april 2016 12.42 Til: openehr-technical@lists.openehr.org Emne: Re: SV: Usage of Compositoin.Category ___ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Re: SV: Usage of Compositoin.Category

2016-04-11 Thread Thomas Beale
On 11/04/2016 11:07, Bjørn Næss wrote: But if we want to avoid double results in querying, we need some sort of 'is_derived' or 'is_copy' marker (and a link to original content) on the copy. At least that's where I got to the last time I thought about it. Yes – I think we need some kind o

SV: Usage of Compositoin.Category

2016-04-11 Thread Bjørn Næss
enehr-technical-boun...@lists.openehr.org] On Behalf Of Bjørn Næss Sent: 10. mars 2016 20:33 To: For openEHR technical discussions <mailto:openehr-technical@lists.openehr.org> Subject: SV: Usage of Compositoin.Category Hi Ian Great response. The most important thing for me is to preci

Re: SV: SV: Usage of Compositoin.Category

2016-04-03 Thread Thomas Beale
On 16/03/2016 05:19, Bjørn Næss wrote: The problem is not to filter in data. The most important feature to support is to filter out data. The proposed solution is to add a new category code to add a new group of Compositions which by default is sorted out. This could be done by archetypes. Bu

SV: SV: Usage of Compositoin.Category

2016-03-15 Thread Bjørn Næss
Best regards Bjørn Næss Product owner DIPS ASA Mobil +47 93 43 29 10 -Opprinnelig melding- Fra: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.org] På vegne av Thomas Beale Sendt: fredag 11. mars 2016 14.12 Til: openehr-technical@lists.openehr.org Em

Re: SV: Usage of Compositoin.Category

2016-03-11 Thread Thomas Beale
Currently I think we filter on 'report' COMPOSITIONs via something like: FROM COMPOSITION c[openEHR-EHR-COMPOSITION.report.v1] CONTAINS OBSERVATION o[openEHR-EHR-OBSERVATION.body_weight.v1] So that would not need any change to the COMPOSITION.category to be achieved. Not saying there a

SV: Usage of Compositoin.Category

2016-03-10 Thread Bjørn Næss
Hi Ian Great response. The most important thing for me is to precisely define the semantic meaning of the content in a composition. In this specific use-case the content of the composition is always a copy of the primary source. This means that the Discharge letter only bring one new thing in

SV: Usage of Compositoin.Category

2016-03-04 Thread Bjørn Næss
[mailto:openehr-technical-boun...@lists.openehr.org] On Behalf Of Bjørn Næss Sent: Friday, 4 March 2016 6:46 PM To: For openEHR technical discussions <mailto:openehr-technical@lists.openehr.org> Cc: Team Selecta <mailto:teamsele...@dips.no> Subject: SV: Usage of Compositoin.Category I just added

SV: Usage of Compositoin.Category

2016-03-04 Thread Bjørn Næss
I just added a «composition category» on my fork of the terminology project. https://github.com/bjornna/terminology/commit/600dec3058cd85f9db3e5859d6bffa7f01a45edf + Any comments? Ven