: Tuesday, 17 September 2013 8:15 p.m.
To: openehr-clinical at lists.openehr.org
Subject: Re: Recording absence of (clinical) information
On 15/07/2013 10:17, Koray Atalag wrote:
Hi Gerard, thanks for your response.
I agree that a simple Boolean data type is not suitable - that's why we used a
On 15/07/2013 09:39, Koray Atalag wrote:
> Hi Tom, has anyone come across an example where "Unavailability of certain
> information" requires more than a single TEXT item to represent? I'm not
> talking about positive statements about exclusion of certain information -
> just "Unknown" cases.
>
On 15/07/2013 10:17, Koray Atalag wrote:
>
> Hi Gerard, thanks for your response.
>
> I agree that a simple Boolean data type is not suitable -- that's why
> we used a TEXT item (called Presence) with Present, Absent, Unknown
> values. The reasons why information is not known can further be
> sp
Cc: For openEHR technical discussions
Subject: Re: Recording absence of (clinical) information
Hi Koray,
I recognise the issue but it is not simple to reconcile three differing
requirements
1. To ensure that negative/absence statements are not inadvertantly picked
up by default quer
> Hi everyone,
Hi koray,
how do you want to do this? We decided against absence / exclusion in th RM a
long time ago,
because it is not a simple negation in general, but a complex (i.e. archetyped)
statement.
-thomas
>
> This is to do with my long standing issue about recording absence of in
y, 15 July 2013 7:41 p.m.
> To: For openEHR technical discussions; For openEHR technical discussions; For
> openEHR clinical discussions
> Subject: Re: Recording absence of (clinical) information
>
> > Hi everyone,
> Hi koray,
> how do you want to do this? We decided against a
Dear Koray,
According to SIAMM:
Any thing can be negated (or better it is declared that something is absent.
Since each ENTRY archetype is a named process that is: ordered, executed,
assessed or summarised after termination, we can describe:
- that there is no order, no execution, no assessment
Hi Koray,
I recognise the issue but it is not simple to reconcile three differing
requirements
1. To ensure that negative/absence statements are not inadvertantly picked
up by default querying. e.g if we simply put a present/absent on
'diagnosis' we either have to explicitly set 'present' on eve
oposal.
Cheers,
-koray
From: openEHR-clinical [mailto:openehr-clinical-boun...@lists.openehr.org] On
Behalf Of Gerard Freriks
Sent: Monday, 15 July 2013 8:00 p.m.
To: For openEHR clinical discussions
Cc: For openEHR technical discussions
Subject: Re: Recording absence of (clinical) information
riginal Message-
From: openEHR-clinical [mailto:openehr-clinical-boun...@lists.openehr.org] On
Behalf Of Thomas Beale
Sent: Monday, 15 July 2013 7:41 p.m.
To: For openEHR technical discussions; For openEHR technical discussions; For
openEHR clinical discussions
Subject: Re: Recording absence
Hi everyone,
This is to do with my long standing issue about recording absence of info. In
endoscopy models the "Presence" of endoscopic findings was represented as a
CLUSTER where a special ELEMENT (that is internally referenced many times for
each finding thereafter) captured "Presence" of
11 matches
Mail list logo