------------------------------
Message: 2
Date: Tue, 03 Jun 2008 16:39:37 +0100
From: Thomas Beale <[email protected]>
Subject: openEHR Querying specifications
To: Openehr-Technical <openehr-technical at openehr.org>
Message-ID: <484565B9.6030805 at oceaninformatics.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
The current material is therefore intended as a resource for discussion
and definition of a query language for openEHR. A team can be defined
after sufficient time for the community to react to this material and
determine if it makes sense to use AQL as the basis or to seek other
solutions or candidates.
- thomas beale
Perhaps this has been answered but as the archetypes change version is it
expected that the AQL will need to keep up with that - I assume our historic
data would be specific to the archetype version - not 'upgraded' ?
i.e. after v1:
FROM EHR [ehr_id/value=$ehrUid] CONTAINS COMPOSITION
[openEHR-EHR-COMPOSITION.encounter.v1]
CONTAINS OBSERVATION obs [openEHR-EHR-OBSERVATION.blood_pressure.v1]
WHERE obs/data[at0001]/events[at0006]/data[at0003]/items[at0004]/value/value
>= 140
after v2:
FROM EHR [ehr_id/value=$ehrUid]
CONTAINS COMPOSITION [openEHR-EHR-COMPOSITION.encounter.v1]
CONTAINS COMPOSITION [openEHR-EHR-COMPOSITION.encounter.v2]
CONTAINS OBSERVATION obs [openEHR-EHR-OBSERVATION.blood_pressure.v1]
CONTAINS OBSERVATION obs2 [openEHR-EHR-OBSERVATION.blood_pressure.v2]
WHERE (
obs/data[at0001]/events[at0006]/data[at0003]/items[at0004]/value/value >=
140 OR
obs2/data[at0001]/events[at0006]/data[at0003]/items[at0004]/value/value
>= 140 )
not sure if that is exactly right.
thanks!
Greg
http://www.patientos.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080603/4281de30/attachment.html>
