Hi all,
I'm currently upgrading the Java Archetype Editor (can be found at
http://www.imt.liu.se/mi/ehr) to support the newest COMPOSITION archetypes
that are available on the openEHR website. For this upgrade I have come upon
a question about some attributes.
The attributes I'm wondering about are the ones that have occurrences 1..1,
meaning they are mandatory. Here I'm interested in the attributes
COMPOSITION.composer and COMPOSITION.category. The composer attribute is of
the type PARTY_PROXY and the category is a DV_CODED_TEXT. Now to my
questions.
Should COMPOSITION archetypes always contain these attributes, e.g. with at
least a line "the_attribute matches {*}" in the ADL or can these mandatory
attributes be discarded completely in the archetypes? Actually this question
goes for ENTRY subclass archetypes as well, because the
ENTRY.subjectattribute is also mandatory.
If mandatory attributes always should be present in archetypes, it would
mean that attributes such as COMPOSITION.territory also would be modeled but
I believe some of the mandatory attributes aren't supposed to be put in
archetypes as of yet. At least I haven't found this attribute in any
archetypes at the openEHR website.
The reason for this question is actually because I saw that the category
attribute is only modeled with one category code at a time in Ocean's
archetype editor. I think that the attribute could be modeled with several
category codes to chose from when creating the EHR content. I'm not sure if
it's good in a user perspective, but I don't see a reason why it shouldn't
be possible. Any comments?
Regards,
Mattias Forss
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060804/b3c8ecd2/attachment.html>
