Bjørn Næss

As you write - the result of such an operation should most likely be an RESULT_SET object. And it would be really easy to map this kind of endpoint outside...

@ppazos here is the same example (almost) - but now I ask for the composition. Does this answer your comment? ```SQL select c from composition c[openEHR-EHR-COMPOSITION.trajectory.v1] where c/archetype_details/archetype_id/value = 'openEHR-EHR-COMPOSITION.trajectory.v1'...

No - the "name" tells which parameter is located in a specific location. In this example the whole composition i present in the actual "column" of the result set. The...

@pablo - you might be right about the / . I am not sure why we choosed current form with null. Will ask my developers about the details.

We have implemented POST as a GET call to make it work for long queries. This is the same as the search servers do. Like Apache Solr and also Elastic...

One important challenge we are facing is to be able to reuse the same query within diffrerent scopes. One implementation of this could be the parameter function. We didn't find...

Related to the GET/POST topic - I think the query resource is something different than a ordinary REST resource. It is by definition a read only resource. You are not...

@erik - you have a working server at http://arenaehr.dips.no:9000/api-doc to test some queries From the api doc you find the following template for payload in the request . There are...

@thomas - I guess the partition question was answered by the comment above. Let me know if I missed something.

No - not crazy at all. I think we have implemented almost this feature with VAQM. Clients may query for several queries in a batch. Use case is I.e. a...