Archetype Query Language Grammar

Version Supported Features Unsupported Features Date
v0.6
  • Support matches operator
  • Spport matches on: string RegEx pattern criteria, uri criteira, string list, int list or double list. 
    • Uri criteria can be used to represent terminology criteria captured in a webservice call format. 
  • Allow parentheses in both FROM and WHERE clause
  • Support NOT and EXISTS operators in WHERE clause
  • matches a range
  • matches a data type
  • nested query
 1 Dec 2009
v0.5 Supports any length of digit for at codes (such as at0.9, at0.0.55) and allows number in archetype concept, such as HbA1c
2 Jul 2008

Diagram of v0.6 generated by Mikael Nyström at Linköping University; process was to use Notepad to convert the grammar to the right file format and the syntax diagram generator at the web page http://www-cgi.uni-regensburg.de/~brf09510/syntax.html to generate the diagrams.

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Comments (4)

 

  1. 16-Dec-2009

    Thomas Beale says:

    The diagram is very useful; what tool is used to do this? We could probably use ...

    The diagram is very useful; what tool is used to do this? We could probably use it on all grammars, including ADL.

  2. 10-Mar-2010

    Martin Eneling says:

    Note: There is no support for the TIMEWINDOW clause in the v0.6 grammar. Are the...

    Note: There is no support for the TIMEWINDOW clause in the v0.6 grammar. Are there plans to include it in later releases?

  3. 12-Mar-2010

    Mikael Nyström says:

    Hi Tom, I used Notepad to convert the grammar to the right file format and the ...

    Hi Tom,

    I used Notepad to convert the grammar to the right file format and the syntax diagram generator at the web page http://www-cgi.uni-regensburg.de/~brf09510/syntax.html to generate the diagrams.

     Greetings,
     Mikael

  4. 23-Mar-2010

    Heath Frankel says:

    Hi Martin, After further analysis we think this functionality should be implemen...

    Hi Martin,
    After further analysis we think this functionality should be implemented in the service model rather than in the query language. This allows multiple queries to be executed with the same time window without requiring it to be specified in the query. It would also allow queries against different services to be executed with the same time window, e.g demographics and EHR.