In general questions like this can be answered by looking at any of:
- thomas beale
On 16/07/2010 10:47, Leonardo Moretti wrote:
Hi Alessandro,
items cardinality matches {0..*; unordered} is referred to "items" elements,
not to "protocol" element
This means we can have something like this:
<observation>
<data>
...
</data>
<protocol archetype_node_id="at0011" xsi:type="ITEM_TREE">
<name>
<value>*List(en)</value>
</name>
</protocol>
<observation>
Is the section
<protocol archetype_node_id="at0011" xsi:type="ITEM_TREE">
<name>
<value>*List(en)</value>
</name>
</protocol>
mandatory, even if it doesn't have any items?
Looking at the archetype defintion, so it seems!
leo
Alessandro Torrisi-3 wrote:
Leo,
as far as i can see the protocol section is not mandatory :
protocol matches {
ITEM_TREE[at0011] matches { -- lijst structuur
items cardinality matches {0..*; unordered} matches {
as you can see 0..* (means zero times until unbounded times), so not
mandatory
Alessandro
On 15 July 2010 17:57, Moretti Leonardo <lmoretti@noemalife.com> wrote:
Hi all,
I have a doubt in interpretating the archetype definition when there are
"state" or "protocol" structure. For example, looking at "Blood
Pressure" in http://openehr.org/knowledge/, I'm wondering if "protocol"
structure is mandatory, as it seems looking at the archetype. If I don't
know any details about the protocol, do I have to insert an empty tag
<protocol> however?
Best regards
leo
_______________________________________________
openEHR-technical mailing list
openEHR-technical@openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
--
Alessandro Torrisi
_______________________________________________
openEHR-technical mailing list
openEHR-technical@openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
|