I found it out, partly, myself. The document RC1.1/publishing/architecture/computable/terminology/Terminology.xsd.html (in my local copy of the repository) was very helpful.
I, now, more or less understand the structure of classes which form the terminology. *Please correct me if I am wrong.* It all boils down to the concept/language which will be represented in the terminology-access. This looks like this id: String all_codes: Set<CODE_PHRASE> codes_for_group_id (group_id: String): Set<CODE_PHRASE> codes_for_group_name (name, lang: String): Set<CODE_PHRASE> rubric_for_code (code, lang: String): String So, the groups (grouper) are visible in Group_id, which can be retrieved by querying the OPENEHR_TERMINOLOGY_GROUP_IDENTIFIERS Class. The openehr terminologies are all in the file terminology.xml, organised in the structure which is described in the above html-file. This is very good. There is one minor problem, the group_id's in the class do not sync 100% with the group-id's in the xml-file. Here is a question *Which one will prevail, that from xml, or that from PDF? * I found out, that there are some codes which have a structure that does not fit in terminology_access, because they have more "fields" like territory and terminologyidentifier, mediatype. *How to handle these? *Finally, there is the property-unit-propertyuntit structure. It looks like, but I am not sure, that these are for, I can guess. But maybe my guess is wrong, the terminolgoyaccess class does not offer space for properties. *How to handle these, what are these for *Thanks for your attention Bert -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20070307/2b3c6868/attachment.html> -------------- next part -------------- _______________________________________________ openEHR-technical mailing list openEHR-technical at openehr.org http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
