(CC'd to the implementers list)
Sergio,
I also want to say thanks for sharing these archetypes.
I am not an archetype expert but there is something about these that
confuse me. (as Sergio and I have discussed a bit). Maybe someone can
UN-CONFUSE me?
In the simple email address one pasted below (definition only for
brevity). In the definition section the ADDRESS class is shown to have
an attribute of 'details' (correct according to the RM). However,
'details' is supposed to be of type ITEM_STRUCTURE (so therefore it
should be an ITEM_LIST???). As well, the ELEMENT should have as its
contents a descendant of DATA_VALUE. CODED_TEXT is not; nor is
CODED_TEXT a class within the AM or RM.
So are these archetypes syntactically correct (checked in the ADL
Workbench) but just not valid with the openEHR information model?
OR! am I missing something?
--Tim
archetype (adl_version=1.4)
br-demographic-ADDRESS.email.v1
...
definition
ADDRESS[at0000] matches { -- correio eletr?nico
details matches {
LIST[at0001] matches { -- Itens do e-mail
items cardinality matches {1..*; ordered}
matches {
ELEMENT[at0002] occurrences matches
{0..1} matches { -- Tipo de
correio eletr?nico
value matches {
CODED_TEXT matches {
code matches {
[local::
at0003,
-- pessoal
at0004]
-- comercial
}
}
}
}
ELEMENT[at0005] occurrences matches {1}
matches { -- correio
eletr?nico
value matches {
DV_TEXT matches {*}
}
}
}
}
}
}
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL:
<http://lists.openehr.org/mailman/private/openehr-clinical_lists.openehr.org/attachments/20080912/6bb1aa00/attachment.asc>
