Skip to Navigation | Skip to Content

openEHR-Implementers mailing list archives

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: ArchetypeOntology


Hi Tim,

term_codes and constraint_codes are really just codes not ArchetypeTerms as indicated by the AOM specification. But you do need other attributes to keep the mapping between different language, codes and ArchetypeTerms in order to implement the methods.

In the Java implementation, a nested Map (Hash in Java) is used to keep all the mappings. The key of the outer map is language and the key for inner map is the code.

Cheers,
Rong

On Mon, Sep 29, 2008 at 8:26 PM, Tim Cook <timothywayne.cook@gmail.com> wrote:
Hi All,

While attempting to implement the ArchetypeOntology I have ran into some
confusion.

The attributes term_codes and constraint_codes are documented as being a
List of strings.

However, it seems to me that they should be a List of ArchetypeTerms. So
that the code is associated with the Hash (or Tuple) of the
text/description etc.

how is everyone else implementing this?

--Tim



--
Timothy Cook, MSc
Health Informatics Research & Development Services
LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook
Skype ID == timothy.cook
**************************************************************
*You may get my Public GPG key from  popular keyservers or   *
*from this link http://timothywayne.cook.googlepages.com/home*
**************************************************************

_______________________________________________
openEHR-implementers mailing list
openEHR-implementers@openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-implementers

_______________________________________________
openEHR-implementers mailing list
openEHR-implementers@openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-implementers