Page Comparison

...

We discussed whether all functions should be allowed on the virtual demographics. We agreed that, for simplicity, we will only allow LIMIT, OFFSET, and ORDER BY. Functions like COUNT, MEAN, MAX, MIN, and AVERAGE will not be supported. We also agreed that the virtual demographics parameters should be based on FHIRsearch parameters. We agreed that we want to maintain only this version instead of 2, since a typical AQL syntax (/defining_code/….) could confuse users that these are RM elements.

Sebastian made a comment that we need to emphasize that the virtual demographics extension to AQL is agnostic of the format in which demographic data is maintained by vendors. It is oriented towards FHIRsearch parameters but does not require the underlying data to be in FHIR.

...

• Define the e@subject return.

• Should we create a REST API endpoint to connect to demographic data for the AQL engine?

SELECT e as ehr
FROM EHR e
WHERE e@subject.birthdate < '1958-01-01' and
e@subject.gender matches{'http://loinc.org|LA2-8'} and -- matches is interchangable with =
e@subject.birthdate > current_timestamp('-P12Y')