Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

https://openehr.atlassian.net/browse/SPECQUERY-29

Requirement

Priority / Importance

Category

Provisional acceptance

Notes

https://openehr.atlassian.net/browse/SPECQUERY-1

syntax / concept

SI

https://openehr.atlassian.net/browse/SPECQUERY-3

 

concept

SI

 

https://openehr.atlassian.net/browse/SPECQUERY-5

concept

SI

https://openehr.atlassian.net/browse/SPECQUERY-7

syntax

SI

https://openehr.atlassian.net/browse/SPECQUERY-8

doc

SI

SI: this is an umbrella
TB: I think this must be close to done in 1.0.1?

https://openehr.atlassian.net/browse/SPECQUERY-9

Status
colourRed
titleHIGH

concept

SI: need more discussions, examples; need good standard behaviour

https://openehr.atlassian.net/browse/SPECQUERY-12

Status
colourRed
titleHIGH

concept

SI

TB: should be based on Luis Marco-Ruiz / Diego Bosca et al work on the wiki pages:

https://openehr.atlassian.net/browse/SPECQUERY-13

concept

SI

SI: need support for system & party types
TB: this is just a question of giving AQL visibility of any RM, e.g. via a BMM or JSON-schema.

07-Dec: moved to v1.2.0

https://openehr.atlassian.net/browse/SPECQUERY-16

syntax

SI, TB

https://openehr.atlassian.net/browse/SPECQUERY-17

syntax

SI, TB

https://openehr.atlassian.net/browse/SPECQUERY-21

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.

https://openehr.atlassian.net/browse/SPECQUERY-24

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.

https://openehr.atlassian.net/browse/SPECQUERY-25

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

SI

Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId7788407e-95fd-3d19-96c6-946a2bd486dc

key

syntax

SI

https://openehr.atlassian.net/browse/SPECQUERY-26

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

https://openehr.atlassian.net/browse/SPECQUERY-27

concept / syntax

SI

https://openehr.atlassian.net/browse/SPECQUERY-28

concept / syntax

SI

07-Dec splitted original ticket in two tickets, GROUP BY and HAVING moved to v1.2.0

Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId7788407e-95fd-3d19-96c6-946a2bd486dc
keySPECQUERY-32

concept / syntax

https://openehr.atlassian.net/browse/SPECQUERY-28

concept / syntax

SI

https://openehr.atlassian.net/browse/SPECQUERY-30

Open Questions

Question

Answer

Date Answered

...