List meeting participants using their @mention names:
List goals for this meeting (e.g., Set design priorities for FY19):
Discussion on persistent compositions i.e. problem list. Ian McNicoll and Thomas Beale has done some work on this which they will present.
RM issues - work out the TODO list
Time | Item | Presenter | Notes |
---|---|---|---|
AQL | ALL |
| |
| Ian/Thomas |
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
Thomas Beale - presented the proposed “VIEW_ITEM” see https://specifications.openehr.org/releases/UML/latest/#Diagrams___19_0_83e026d_1574366530113_751508_5059
Example AQL on FOLDER with Problem List (DIPS):
SELECT c/uid/value as CID, e/data[at0001]/items/value/value as Problem FROM EHR p CONTAINS FOLDER f CONTAINS FOLDER child CONTAINS COMPOSITION c CONTAINS EVALUATION e[openEHR-EHR-EVALUATION.problem_diagnosis.v1] WHERE f/name/value = 'Tidligere sykdommer' ORDER BY c/context/start_time desc LIMIT 10 |
Topic: AQL
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” .
Add action items to close the loop on open questions or discussion topics:
Type /decision to record the decisions you make in this meeting: