Rahil Qamar wrote: > Hi Bert > > I had a read through your posting. I have one query though. Which > terminology are you planning to use? The openEHR terminology is very > small and limited in scope and content which makes it fine to be > available in the current Terminology.xml file. However if you are > planning to use one of the larger, more widely published and used > terminologies such as SNOMED CT, LOINC, ICD, NANDA, and the rest, you > might run into problems with trying to convert the terminologies to > the XML format used for the openEHR terminology. How are you planning > to handle relationships and concept definitions using the present XSD? > > I might have caught the wrong end of the stick but on initial look > this is what came to my mind. > Yes - the openEHR terminology is just a (small) support terminology for the reference model, not a clinical terminology. Although it is probably good to be able to access openEHR support terms in the same way as Snomed or Loinc terms, we need to be aware: * I only specified a minimal Terminology access service interface, simply for teh purposes of making the openEHR specs correct; * there will be significantly more complexity in the interface to bigger terminologies; for example we have implemented a terminology server that handles Snomed, ICD etc - it is a lot more inivolved than the simple interface specified in the openEHR RM.
- thomas _______________________________________________ openEHR-technical mailing list openEHR-technical at openehr.org http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
