Skip to end of metadata
Go to start of metadata

Current Version - Under Revision

A terminology server should be able to deliver all the essential Terminology services identified in the Terminology Services Guide (RF2) . It should also provide the recommended Terminology services and should achieve a performance that meets the more general requirements for the functionality of SNOMED CT enabled applications .
Terminology server may provide two types of service:

  • Reference Services (see ):
    • Services that do not include a

      user interface

      ;
    • The client application may use reference services to undertake many different functions;
    • For some of these functions the client application will populate an appropriate

      user interface

      component

      .

Example:
A reference server may return a list of Descriptions matching a particular search string . The client application may use this data to populate a list from which a user makes a selection.

Example:
A UI server may provide a control that includes a text box and a list. When the user types in the text box, the server populates the list and allows the user to select an item. The selected item is accessible from the client program.

  • One possible type of

    UI

    service is a

    SNOMED CT browser

    with an

    API

    for returning selected data to a client application:
    • This may be useful as mechanism for providing some

      SNOMED CT

      capabilities to an application. However, it is less suitable for frequent entry of

      SNOMED CT

      encoded information.


Figure 62. Terminology server providing reference services to a client application

Figure 63. Terminology server providing user-interface and reference services to a client application


Feedback