Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Need to obtain XSD for result set.

Correct statements about AQL 'being for EHR' to be broader (i.e. will work for demographics)

Example population queries for demographics

HF: what does conformance def look like for AQL? Be careful of extensions

BN:

  • in the DIPS, they use FOLDER CONTAINS COMPOSITION; FOLDER CONTAINS FOLDER etc.
  • need to define Care Plan semantics

HF: in fact we do EHR CONTAINS COMPOSITION (probably take out 'EHR CONTAINs'? to get consistency); but: EHR => compositions etc is logical containment

could we have an 'IN' operator to cover all logical 'containment'?

Ian:

  • want to make e.g. Problems linked from problem list via LINK? or DV_EHR_URI Composition should be selected same as if inline inside COMPOSITION.
  • Care Plan linking

Link depth issue.

TB: need marked up Ref Model to indicate what links to follow.

  • SParql
  • GraphQL

Pablo: if we want to state conditions (e.g. Contains / Where) on LINK targets - it's a nested sub-query

Birger:

  • ?alignment to SQL 
    • HF: we don't do 'JOINs' (yet) - LINK following might be a JOIN concept
  • need aggregate functions like SUM(); GROUP-BY() e.g. list of patient counts keyed by ICD code
  • set functions: Union; Intersect; 
    • e.g. SELECT x FROM y WHERE z UNION SELECT x FROM y etc - (need same nr or columns in each result)
  • No labels