Archetype Query Language (AQL)
An Archetype Query Language (AQL) is a declarative query language that was developed specifically for expressing queries used for searching and retrieving data in archetype-based repositories.
- AKA: OpenEHR-AQL.
- Example(s):
- Counter-Example(s):
- See: Clinical Data, Electronic Health Record (EHR), OpenEHR Reference Model, OpenEHR Clinical Archetype Model, Clinical Data Standard, Clinical Terminology Standard, OpenEHR Clinical Knowledge Manager (CKM).
References
2022a
- (OpenEHR, 2022) ⇒ https://specifications.openehr.org/releases/QUERY/latest/AQL.html#_what_is_aql Retrieved:2022-03-05.
- QUOTE: Archetype Query Language (AQL) is a declarative query language developed specifically for expressing queries used for searching and retrieving the data found in archetype-based repositories. The examples used in this specification mostly relate to the openEHR Reference Model (RM) and the openEHR clinical archetypes, but the syntax is independent of information model, application, programming language, system environment, and storage model.
The minimum requirement for data to be queried using AQL (including with archetype structures and terminology) is that it be based on archetypes, which concretely means that it contains fine-grained semantic markings in the form of archetype and terminology codes. This may be native openEHR RM data, or legacy system data to which the relevant semantic markers (i.e. archetype and terminology codes) have been added. Consequently, AQL expresses queries in terms of a combination of archetype semantic elements and RM data structure elements on which the archetypes are based, rather than solely the latter, which is the case for EAV-based query languages such as SQL. This is the key in developing and sharing semantic queries across system and enterprise boundaries.
- QUOTE: Archetype Query Language (AQL) is a declarative query language developed specifically for expressing queries used for searching and retrieving the data found in archetype-based repositories. The examples used in this specification mostly relate to the openEHR Reference Model (RM) and the openEHR clinical archetypes, but the syntax is independent of information model, application, programming language, system environment, and storage model.
2022b
- (Wikipedia, 2022) ⇒ https://en.wikipedia.org/wiki/OpenEHR#Archetype_formalism Retrieved:2022-03-05.
- QUOTE: openEHR archetypes are expressed in "Archetype Definition Language", an openEHR public specification. Two versions are available: ADL 1.4,[1] and ADL 2,[2]a new release with better support for specialisation, redefinition and annotations, among other improvements.[3] The 1.4 release of ADL and its "object model" counterpart Archetype Object Model (AOM) are the basis for the CEN and ISO "Archetype Definition Language" standard (ISO standard 13606-2).
Templates have historically been developed in a simple, de facto industry-developed XML format, known as ".oet", after the file extension.[4] ADL 2 defines a way to express templates seamlessly with archetypes, using extensions of the ADL language.[5]
- QUOTE: openEHR archetypes are expressed in "Archetype Definition Language", an openEHR public specification. Two versions are available: ADL 1.4,[1] and ADL 2,[2]a new release with better support for specialisation, redefinition and annotations, among other improvements.[3] The 1.4 release of ADL and its "object model" counterpart Archetype Object Model (AOM) are the basis for the CEN and ISO "Archetype Definition Language" standard (ISO standard 13606-2).
- ↑ Beale, T; Heard, S, eds. (12 Dec 2008), Archetype Definition Language 1.4, openEHR Foundation.
- ↑ openEHR Specification Program (3 Nov 2015), Archetype Definition Language 2, openEHR Foundation
- ↑ "ADL/AOM 2 specifications". openEHR Foundation. Retrieved 3 Nov 2015.
- ↑ "Template ".oet" XSD". openEHR Foundation. Retrieved 9 April 2013.
- ↑ openEHR Specification Program. "Archetype Definition Language (ADL2) specification". openEHR Foundation. openEHR Foundation. Retrieved 3 November 2015.