Hi Ivar,
I'm not sure the situation is quite as clear-cut, in that I donlt
think there is necessarilly a simple distinction between primary data
which should normally be query-accessible and in-line vs. secondary
data which is normally query-inaccessible and referenced.
A few scenarios
1. Vital
Currently I think we filter on 'report' COMPOSITIONs via something like:
FROM COMPOSITION c[openEHR-EHR-COMPOSITION.report.v1]
CONTAINS OBSERVATION o[openEHR-EHR-OBSERVATION.body_weight.v1]
So that would not need any change to the COMPOSITION.category to be
achieved. Not saying there
Hi
An interesting discussion that touches the very concept of structured
information, in my opinion. I wonder if the suggested solution looks at the
problem from the best angle. So here is my angle:
As a person with some SQL experience I would expect an AQL to return ONLY
primary content
3 matches
Mail list logo
