On 11/09/2016 15:48, pablo pazos wrote:
Hi Bert,
I was thinking about integrating SCT with path-based queries (I'm not
in AQL yet), but maintaining the complexity of the SCT relationships
and expressions on the terminology service (TS) side, so on queries
there are just simple codes (specific concept ids, subsets or
expressions identified just by one code). Then when evaluating a
query, with the TS we can get all the terms and concept ids that match
all the is_a relationships or subsets of expressions. I talked with
several TS providers and hopefully we can build an integration next
year to create and evaluate queries with SCT.
What I'm saying is that I prefer to delegate the complexity of SCT to
the TS and create simpler queries in AQL or path-based queries, but
your idea is interesting. One problem though is that query creators
need to be experts in SCT.
this is also a real issue - and one that has no clear answer that I know
of...
- thomas
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
