What should AQL return in this case?

Hi Seref, It would return a cross join of the X.attr and Y.attr, but only from EHRs with both an X and Y. We have uses workflow ids because this is more efficient to evaluate than URIs (including links) due to string length and being bidirectional, but this only works for certain usecases. Heath.

What should AQL return in this case?

Hi All The work_flow_id of an entry provides a way to link any ENTRY with an INSTRUCTION. There are more complex workflow parameters possible within the ENTRY class that can be used if more complex issues arise. Relating ENTRYs in a general way outside a particular application or repository is

What should AQL return in this case?

Thanks, I think this is the best thing to do. On Mon, Aug 20, 2012 at 1:17 PM, Thomas Beale < thomas.beale at oceaninformatics.com> wrote: > On 20/08/2012 05:47, Seref Arikan wrote: > >> Hi Tom, >> Your comments are quite helpful, but they do not belong to the context >> I'm asking about. I'm ask

What should AQL return in this case?

Ascii would take time iPad + Notability + a proper stylus I love it. On Mon, Aug 20, 2012 at 12:52 PM, Hugh Leslie < hugh.leslie at oceaninformatics.com> wrote: > You could have done the diagram in ascii... > -- next part -- An HTML attachment was scrubbed... URL:

What should AQL return in this case?

Hi Tom, Your comments are quite helpful, but they do not belong to the context I'm asking about. I'm asking the default behaviour for returning results when no constraints are there. It may not be a meaningful use case for using AQL, but it is a technically valid one. My question is: how should the

What should AQL return in this case?

Greetings, Here is the setting in which AQL is being used: We are interested in outcomes of a particular clinical instruction in cases where a particular observation has been recorded. We want to get an attribute of both the observation and the and the instruction from patient EHR. The patient's E

What should AQL return in this case?

On 20/08/2012 05:47, Seref Arikan wrote: > Hi Tom, > Your comments are quite helpful, but they do not belong to the context > I'm asking about. I'm asking the default behaviour for returning > results when no constraints are there. > It may not be a meaningful use case for using AQL, but it is a

What should AQL return in this case?

This is a good question. I wold summarise it as: how do I ensure an AQL query picks up proximate rather than distant objects for a given object? It depends on the data. If the only thing in the data that indicates that INSTR Y1 is related to OBS X1 is temporal proximity, then you would have to