Hi Bert,

Yes, I believe it should be changed. I actually made a heading change for
the subject setting in the GUI of the archetype editor when I saw that the
subject attribute of the ENTRY classes should be a PARTY_RELATED (which
represents the relation to the subject of data) and not a PARTY_SELF (which
represents the subject of data).

For some reason I never realized that the terminology.xml was wrong.

Regards,

Mattias


2007/3/16, Bert Verhees <bert.verhees at rosa.nl>:
>
> This line is in it:
> <Concept Language="en" ConceptID="32" Rubric="Subject of data" />
>
> when you go to grouper:
> <Grouper id="1" ConceptID="32" />
>
> and then to groupedconcept:
> <GroupedConcept GrouperID="1" ChildID="0" />
> <GroupedConcept GrouperID="1" ChildID="3" />
> <GroupedConcept GrouperID="1" ChildID="6" />
> <GroupedConcept GrouperID="1" ChildID="7" />
>
> etc....
>
> which points to:
> <Concept Language="en" ConceptID="0" Rubric="self" />
> <Concept Language="en" ConceptID="3" Rubric="foetus" />
> <Concept Language="en" ConceptID="6" Rubric="donor" />
> <Concept Language="en" ConceptID="7" Rubric="maternal grandmother" />
> etc...
> --------------------------------
> I wonder if the above (first) line should be
> <Concept Language="en" ConceptID="32" Rubric="Related party
> relationship" />
>
> because this is also in the PDF-documents: terminology.pdf page 22
> and in support_im.pdf, page: 59
>
> Thanks,
> bert
>
>
>
>
> _______________________________________________
> openEHR-technical mailing list
> openEHR-technical at openehr.org
> http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20070316/85cd43b2/attachment.html>
-------------- next part --------------
_______________________________________________
openEHR-technical mailing list
openEHR-technical at openehr.org
http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical

Reply via email to