Modelling pattern - imaging examination - what do you think?

[thomas.beale]

@bna

Not sure about this. AFAIK the query engine doesn’t need access to any archetype library. This is needed in design-time for templates and other artefacts for input, and also for the query developer for tooling and guidance. The query engine can work without any such archetype knowledge. It must somehow know about the RM, but that’s another story.

@thomas.beale

That should be the default, because by definition, data that is an instance of a specialised archetype A’ is an instance of its parent A. So not picking up the A’ data is an error.

I would be happy to know if other implementers do this. This will certainly break most of our applications. Navigation though a hierarchy of archetyped data either with AQL or traversing paths within a composition tend to use the archetype root id as is. Adding some regexp around this adds new level of complexity.

I forgot to mention something important - in ADL 1.4-based systems (currently most vendors today), the query engine can work out if there is data from specialised archetypes just by searching on the top archetype id with any extended form of the concept part of the id, i.e. if the parent is

openEHR-EHR-CLUSTER.exam.v1

in ADL 1.4, children are named like

openEHR-EHR-CLUSTER.exam-palpation.v1

and

openEHR-EHR-CLUSTER.exam-palpation-cervix.v1

So the query engine just has to know to search for openEHR-EHR-CLUSTER.exam%.v1 or similar (maybe there is something smarter you can do - need to check with SQL experts) - no need to have access to archetype repository.