...
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 DISTINCT | syntax | SI | ||||||||
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 | SI | ||||||||
Support for XOR | syntax | SI | ||||||||
server | System JIRA | |||||||||
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution | |||||||||
serverId | 7788407e-95fd-3d19-96c6-946a2bd486dc | |||||||||
key | https://openehr.atlassian.net/browse/SPECQUERY-26concept / 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 | |||||||||
Support for GROUP BY / HAVING | concept / syntax | SI | ||||||||
...