We face with the need to store AQL’s to be able to provide them when necessary to different initiatives projects or actors. We are not sure where to store them. Has anyone else encountered this need? We would be very grateful if anyone could share their experience. Thank you so much.

Hey David, From a tech-savvy perspective, you could leverage the ability store AQL queries via REST API: Definition API openEHR specs And execute them when needed: Query API openEHR specs Is that what you are looking for or did I understand your question wrong?

Yes, the REST API allows to have stored queries, so any CDR that implemented those endpoints will be able to store AQLs. Though the challenge, and I guess that’s from where this question comes, we don’t have a standard way of managing AQLs. That is: defining their purpose, authoring metadata, versi…

Yes, I think that’s the question of @david.alonso In Catalonia we will need to build a specific system for AQL publication and governance, much beyond of what stored queries can offer. I will include not only the purpose and authoring metadata but also the description of the query parameters, the d…

We actually got a similar request from our UX and requirement engineers at vitagroup. Hence, I think there is some general appetite to enhance the spec of stored queries.

We need something similar for authorising specific queries across CDR vendors. So we need basic things like naming and hashing a query and probably (semantic?) versioning.

I know that both @sebastian.garde and @rong.chen have been looking at what other metadata might be needed to store shared stored AQL queries for federation purposes.

At Cambio, we have the concept of reusable AQL queries that are used in forms and CDS apps. These query defintions are versioned and kept in light weight CKM with some basic metadata and authorship information. I think we have a ticket on sharable AQLs in the SEC board, need to progress if there is…

Has anyone thought of using ADL with a query-RM ( not existing in spec) to fulfill this need? If that would work and if it would also make sense, then the governance including versioning. reviewing could be the same as for EHR archetypes ( e.g. CKM). That would be cool :sunglasses:

I like your thinking. I definitely think a lot can be reused/inherited from archetypes, like identification, namespaceing, versioning, meta data like author, maybe multi language. But the definition section will be very different I assume? I’m also interested in defining a result set for a query (m…

Where do you keep the AQL's ?

Specifications AQL

siljelb (Silje Ljosland Bakke) 26 March 2024 12:39 2

DIPS has created a separate concept for storing queries that they call “VAQM”. More about them from @bna here: AQL through GraphQL - #12 by bna

Topic		Replies	Views
[EHRbase] Storing and querying data without an standalone archetype Platform ehrbase , aql	38	1169	17 April 2024
New major archetype version and AQL queries Platform aql , archetype	5	74	31 July 2026
query writing question 2 Implementers (archive)	16	101	13 October 2018
AQL: querying data from several archetypes AQL aql	9	857	9 September 2023
Using aql for data set in DV_CODED_TEXT Technical (archive)	4	34	5 July 2017
AQL formalism AQL	4	133	25 June 2024
EHRs with different system_id in the same server? RM	39	1237	7 November 2024
Generic modeling and issues for querying Technical (archive)	9	66	21 September 2018
AQL semantics: separating RM semantics from AQL semantics AQL	4	432	17 November 2020
Does anyone implemented a transformation between AQL and XML? Technical (archive)	13	69	19 January 2015

Where do you keep the AQL's ?

Related topics