...
Release 1.1.0 is based on RM Release 1.1.0 and BASE Release 1.2.0
This will add new functionality to AQL specification, but will maintain backwards compatibility.
This Release should consider also AQL Evolution Notes
an older analysis: https://docs.google.com/document/d/1g8zOh06LhSNi1yFZWKuBzUX0bJN88r7mKpAFqDNi2JI/edit , AQL Proposed Functions (discussion)
Requirements
The following is an overview of all candidate issues (some not yet recorded in JIRA) for Release 1.1.0.
...
Requirement | Priority / Importance | Category | Provisional acceptance | Notes | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
syntax / concept | SI | |||||||||||||||||
| concept | SI |
| |||||||||||||||
concept | SI | |||||||||||||||||
syntax | SI | |||||||||||||||||
doc | SI | SI: this is an umbrella | ||||||||||||||||
| concept | SI: need more discussions, examples; need good standard behaviour | ||||||||||||||||
| concept | SI | TB: should be based on Luis Marco-Ruiz / Diego Bosca et al work on the wiki pages: | |||||||||||||||
concept | SI | SI: need support for system & party types | ||||||||||||||||
syntax | SI, TB | |||||||||||||||||
syntax | SI, TB | |||||||||||||||||
doc | SI | TB: should become AT_TIME, as suggested by Seref, and be documented to mean clinical (i.e. ‘world’) time, not commit time. Requires formal changes. | ||||||||||||||||
doc | SI | TB: this should be defined in terms of a generic set of rules that tell a query process what things to ignore; this CR is just one specific rule. | ||||||||||||||||
syntax | SI, TB | |||||||||||||||||
Support for UNION | syntax | SI | ||||||||||||||||
Support for FOLDERs | syntax | SI | TB: supported generically by use of RM model (i.e. BMM, JSON-schema or similar). | |||||||||||||||
Support for TAGs | syntax | SI | SI: TAGs should use functions | |||||||||||||||
functions / UDF | concept | SISupport for XOR | ||||||||||||||||
| syntax | SI | ||||||||||||||||
concept / syntax | SI | TB: this also requires access to an RM description that shows what ‘links’ are logically containment etc | ||||||||||||||||
terminology and value sets | should be covered by SPECQUERY-12 ? | |||||||||||||||||
Support for SET (declarations) | syntax | |||||||||||||||||
| ||||||||||||||||||
server | System JIRA | |||||||||||||||||
serverId | 7788407e-95fd-3d19-96c6-946a2bd486dc | key | SPECQUERY-27https://openehr.atlassian.net/browse/SPECQUERY-27concept / syntax | SI | ||||||||||||||
concept / syntax | SI | |||||||||||||||||
| concept / syntax | SI
|
Open Questions
Question | Answer | Date Answered |
---|---|---|
...