constraining of laboratory_test_analyte Analyte result

Thomas Beale thomas.beale at
Tue Apr 30 15:35:36 EDT 2019

Hi Georg,

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?

- thomas

On 29/04/2019 23:46, Georg Fette wrote:
> Hello,
> 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 the FROM part only archetypeID-predicates are allowed and 
> no node predicates. As the result is defined with the abstract ELEMENT 
> type, which has an abstract DATA_VALUE as its content, no paths can be 
> defined that constrain specific aspects of subclasses of DATA_VALUE 
> that are actually stored in the ELEMENT[at0001] field of the 
> test_analyte.
> How can this problem be resolved ?
> Greetings
> Georg
Thomas Beale
Principal, Ars Semantica <>
Consultant, ABD Project, Intermountain Healthcare 
Management Board, Specifications Program Lead, openEHR Foundation 
Chartered IT Professional Fellow, BCS, British Computer Society 
Health IT blog <> | Culture blog 
<> | The Objective Stance 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the openEHR-technical mailing list