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
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
rg] På
vegne av Thomas Beale
Sendt: søndag 3. april 2016 15.31
Til: openehr-technical@lists.openehr.org
Emne: Re: Usage of Compositoin.Category
these examples from Ian illustrate exactly why we never figured this out before
- because of the possible mixture of original content, referenced c
r-technical-boun...@lists.openehr.org] On
Behalf Of Bjørn Næss
Sent: 10. mars 2016 20:33
To: For openEHR technical discussions <openehr-technical@lists.openehr.org>
Subject: SV: Usage of Compositoin.Category
Hi Ian
Great response.
The most important thing for me is to precisely defin
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.
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
9 24 06
Mobil +47 90 78 89 33
-Original Message-
From: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.org] On
Behalf Of Ian McNicoll
Sent: 14. mars 2016 18:50
To: For openEHR technical discussions <openehr-technical@lists.openehr.org>
Subject: Re: Usage of Composi
> To: For openEHR technical discussions <openehr-technical@lists.openehr.org>
> Subject: Re: Usage of Compositoin.Category
>
> Hi Ivar,
>
> I'm not sure the situation is quite as clear-cut, in that I donlt think there
> is necessarilly a simple distinction between pri
2016 08:41
To: For openEHR technical discussions <openehr-technical@lists.openehr.org>
Subject: Re: Usage of Compositoin.Category
Hi Ivar,
I'm not sure the situation is quite as clear-cut, in that I donlt think there
is necessarilly a simple distinction between primary data which should no
06
> Mobil +47 90 78 89 33
> -Original Message-
> From: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.org]
> On Behalf Of Bjørn Næss
> Sent: 10. mars 2016 20:33
> To: For openEHR technical discussions <openehr-technical@lists.openehr.org>
> Subject: SV:
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
iscussions <openehr-technical@lists.openehr.org>
Subject: SV: Usage of Compositoin.Category
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
ical-boun...@lists.openehr.org] På
vegne av Ian McNicoll
Sendt: mandag 7. mars 2016 18.16
Til: For openEHR technical discussions <openehr-technical@lists.openehr.org>
Emne: Re: Usage of Compositoin.Category
Hi Björn,
I finally got around to thinking a bit about this.
It is an interesting pr
;
Fra: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.org] På
vegne av Thomas Beale
Sendt: fredag 4. mars 2016 09.50
Til: openehr-technical@lists.openehr.org
Emne: Re: Usage of Compositoin.Category
Re: process, yes, it needs to be managed separately. Ian is the termi
* Team Selecta <teamsele...@dips.no>
*Subject:* SV: Usage of Compositoin.Category
I just added a «composition category» on my fork of the terminology
project.
https://github.com/bjornna/terminology/commit/600dec3058cd85f9db3e5859d6bf
openehr-technical@lists.openehr.org<mailto:openehr-technical@lists.openehr.org>
Emne: Usage of Compositoin.Category
We are discussing the use of Composition.Category which is a DV_CODED_TEXT.
There is a terminology:
Is
?
Vennlig hilsen
Bjørn Næss
Produktansvarlig
DIPS ASA
Mobil +47 93 43 29 10<tel:+47%2093%2043%2029%2010>
Fra: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.org] På
vegne av Bjørn Næss
Sendt: onsdag 17. februar 2016 22.00
Til: openehr-technical@lists.openehr.org
Emne:
We are discussing the use of Composition.Category which is a DV_CODED_TEXT.
There is a terminology:
Is it required to use only these categories or could an application set any
DV_CODED_TEXT?
I think it would be
18 matches
Mail list logo
