Hi dear Ian
According to openEHR-technical Digest, Vol 49, Issue 12 you saied two bellow
statement are correct (in scope of ADL 1.4):
1- The archetype-node-id in a locatable constructed around an archetype
in an archetypeslot is the archetype-node-id it gets from its own archetype
(which is called in the slot).
2- The archetype-node-id in a locatable constructed around the
archetype calling the archetypeslot is to be ignored.
I have a validation problem:
If the archetype-node-id in a locatable constructed around an archetype in
an archetypeslot is the archetype-node-id it gets from its own archetype,
means at(child archetype node id) instead of at0001(slot node id) so how
can I apply occurrence of slot? for example
Entry[at] matches {-- Encounter
content matches {
allow_archetype INSTRUCTION [at0001] occurrences matches {0..1}
matches {
include
domain_concept matches {/instruction.v1/}
}
allow_archetype OBSERVATION [at0002] occurrences matches {1..1}
matches {
include
domain_concept matches {/observation.v1/}
}
}
}
the object may be something like this:
.
.
In the above example how I can apply occurrence for INSTRUCTION objects
optional or just one occurrence and OBSERVATION only one occurrence must be
appear.
Or maybe we must bypass constraint defined on slots?
What is the main constraint applied? Slot constraint or child archetype
constraint?
Thanks in advance
-Original Message-
From: openehr-technical-boun...@openehr.org
[mailto:openehr-technical-bounces at openehr.org] On Behalf Of
openehr-technical-request at openehr.org
Sent: Monday, August 23, 2010 5:05 PM
To: openehr-technical at openehr.org
Subject: openEHR-technical Digest, Vol 49, Issue 12
Send openEHR-technical mailing list submissions to
openehr-technical at openehr.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
or, via email, send a message with subject or body 'help' to
openehr-technical-request at openehr.org
You can reach the person managing the list at
openehr-technical-owner at openehr.org
When replying, please edit your Subject line so it is more specific than
"Re: Contents of openEHR-technical digest..."
Today's Topics:
1. Re: ArchetypeNodeId of an archetypeslot (Ian McNicoll)
2. Re: ArchetypeNodeId of an archetypeslot (Bert Verhees)
--
Message: 1
Date: Mon, 23 Aug 2010 13:19:09 +0100
From: Ian McNicoll
Subject: Re: ArchetypeNodeId of an archetypeslot
To: For openEHR technical discussions
Message-ID:
Content-Type: text/plain; charset="utf-8"
Hi Bert,
I appreciate you will be currently using ADL1.4, but in essence, by
aggregating archetypes as you suggest, you are creating a template. ADL 1.4
does not define this aggregation/template behaviour, which is why I pointed
you to the ADL1.5 specs, which cover both the templates and specialised
archetypes. We, therefore do not have an official ADL1.4 answer to your
question but your final statement is correct :
The archetype-node-id in a locatable constructed around an archetype in an
archetypeslot is the archetype-node-id it gets from its own archetype (which
is called in the slot).
The archetype-node-id in a locatable constructed around the archetype
calling the archetypeslot is to be ignored.
Also remember that there is no absolute requirement for a single slot to
have an atnode name but Heather and I now pretty well always assign one
routinely as it helps document the usage of the slot for downstream users.
Ian
Dr Ian McNicoll
office / fax +44(0)141 560 4657
mobile +44 (0)775 209 7859
skype ianmcnicoll
ian.mcnicoll at oceaninformatics.com
ian at mcmi.co.uk
Clinical Analyst Ocean Informatics
Honorary Senior Research Associate, CHIME, University College London openEHR
Archetype Editorial Group Member BCS Primary Health Care SG Group
www.phcsg.org / BCS Health Scotland
On 23 August 2010 11:51, Bert Verhees wrote:
> Thanks Ian,
>
> I will not surprise you that I don't work with ADL 1.5.
> So I have to understand your answer to this issue in ADL 1.4 context.
>
> Archetypeslots are typically very convenient in templates, but also in
> archetypes.
>
> In archetypes, the convenience is it makes it possible for easily
> archetype (code)-reuse.
> But in an archetype the approach is different because the locatable
> constructed around the archetype (in the slot) is a property from the
> locatable constructed around the archetype which calls the
archetype(slot).
> (sorry the express this so complicated, I don't know a more simpler
> way to say this)
>
> This is not the case in a template, because the
