Furthermore application developers can be confident that the terminology will behave in a consistent and predictable way, and thus make it easier to design advanced clinical applications. The CORE model is intended to be language independent and hence information entered in one language can be displayed in another. As a minimum these lexicons must contain words for the elementary concepts. This makes the task of translating a terminology much smaller than that of translating all the possible terms. Phrases for complex compositions can be generated from these individual components by the Multilingual Module.
Many schemes are detailed and aim for extensive clinical coverage.
However they typically lack the structure and formal basis that is necessary to meet the needs of advanced systems. The project is divided into two streams. The first of these is producing the Terminology Server, related technologies and the CORE model, while the second is responsible for demonstrators and experiments to test the products of stream one. The TeS combines the functionality of the three modules to provided sophisticated but uniform terminology services to client applications. Client applications can make high level requests of the TeS such as 'what are the kinds of this' or more excitingly 'what can I say about this'.