On 01/03/2017 09:43, Bert Verhees wrote:
Op 1-3-2017 om 10:34 schreef Thomas Beale:
Hi Bert,
all these problems went away with ADL2 some years ago. See my post on
the technical list.
Hi Thomas, what problem went away?
I cannot find an answer to my question in this reply. I try again
The question was, do I need to specialize an archetype to make it
specific (lab-test, for example) so it will get a a specific ADL-path
to a data-item which can be used in a query?
(I used the other text to describe advantages/disadvantages of the
choice)
Can you please respond to this question?
If you specialise an ADL2 archetype with a path like
/events[id4]/items[id12], you will get paths like
/events[id4]/items[id12.1] if you specialise the id12 node. A query
engine can easily search for 'id12.*' (regex) or 'id12%' (SQL) to match
data based on either the parent or the child.
Note also that a 'template' in ADL2 is just an ADL2 artefact, with the
same rules for paths, specialisation and so on.
Here's a simple example:
parent archetype:
child archetype:
So, normally, you want to specialise and you will get appropriate search
results, whether you use the parent or child archetype archetype paths
as the search key.
Does that answer the question?
- thomas
_______________________________________________
openEHR-clinical mailing list
openEHR-clinical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
