We should document for AQL 1 what’s the expected results given data and a specific AQL
Topic: Persistent data and use-cases like Problem List
How do we do allergy list or problem lists in openEHR. These kind of lists should be pointers to the real underlying data. Querying for *-list should give back the data defined in the persistent composition containing the list.
@Bjørn Næss - DIPS is using FOLDER to carry the problem list
c/uid/value as CID,
e/data[at0001]/items/value/value as Problem
CONTAINS FOLDER f
CONTAINS FOLDER child
CONTAINS COMPOSITION c
CONTAINS EVALUATION e[openEHR-EHR-EVALUATION.problem_diagnosis.v1]
f/name/value = 'Tidligere sykdommer'
ORDER BY c/context/start_time desc
AQL vs. RM - is the AQL semantic bound to the RM i.e. EHR contains COMPOSITION and the realation to DEMOGRAPHICS.
Is “SYSTEM” the root for AQL ? Seems like a good idea to navigate the HIS (Health Informatics System) clients wants to query data from. Suggestion to add a “virtual system node” .
Need to follow up the AQL topic. Next SEC call
Make persistent data as a topic on the SEC Meeting in Stockholm