The correct way to do this IMO, and my earliest idea for AQL in about
2006 was using archetype fragments, which are a kind of Frame-logic
approach, formally. Today, people think in terms of GraphQL, but you
need constraints.
E.g.
WHERE
dv matches {
magnitude matches {|>=140.0|}
units matches {"mm[Hg]"}
}
Or, more readably:
WHERE
dv ∈ {
magnitude ∈ {|>=140.0|}
units ∈ {"mm[Hg]"}
}
- thomas
On 08/10/2018 16:27, Pablo Pazos wrote:
But maybe that kind of query should be written as:
WHERE dv/magnitude >= 140 AND dv/units = "mmHg"
--
Thomas Beale
Principal, Ars Semantica <http://www.arssemantica.com>
Consultant, ABD Project, Intermountain Healthcare
<https://intermountainhealthcare.org/>
Management Board, Specifications Program Lead, openEHR Foundation
<http://www.openehr.org>
Chartered IT Professional Fellow, BCS, British Computer Society
<http://www.bcs.org/category/6044>
Health IT blog <http://wolandscat.net/> | Culture blog
<http://wolandsothercat.net/> | The Objective Stance
<https://theobjectivestance.net/>
_______________________________________________
openEHR-implementers mailing list
openEHR-implementers@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-implementers_lists.openehr.org
