Well, at the risk of stepping on Ian's toes (he has spent a lot more
time on these particular archetypes and also AQL in general than me), I
would say that what we need to do is to create a data-type specific
version of this archetype for each DATA_VALUE descendant, e.g.
It depends on what you mean with "specialise". I do not wish to create a
new archetype but I rather would like to query existing instances of the
openEHR-EHR-CLUSTER.laboratory_test_analyte.v1 archetype. From those
instances I would like to query only this with specific attributes.
Please note that you can always define your FROM clause with a high level
node such as an OBSERVATION o[archetype_id] and access the particular path
you're interested in using a path starting from o as in o/data[..]/...
Regarding your assumptions re FROM clause, technically there is
The instance data will actually have been subclassed to have a specific
datatype and therefore the relevant attributes.
Therefore if you know that a particular analyte is a quantity, you can use
aql to access the data just as if it had originally been modelled
specifically as a
Just to be clear, are you trying to specialise the
openEHR-EHR-CLUSTER.laboratory_test_analyte.v1 archetype for specific
analytes, e.g. serum sodium, TSH etc?
On 29/04/2019 23:46, Georg Fette wrote:
How do I constrain the Analyte result of a
How do I constrain the Analyte result of a laboratory_test_analyte.v1 ?
The Analyte result are defined as an ELEMENT that is only constrained by
a node predicate (i.e. ELEMENT[at0001]). Therefore the results cannot be
bound with a specialized type and an alias within the FROM part, as in
Mail list logo