SNOMED Documentation Search


 Other Documents
Skip to end of metadata
Go to start of metadata

Current Version - Under Revision

A

$gterm

should be able to deliver all the essential

$gterm

identified in the

$gterm

. It should also provide the recommended

$gterm

and should achieve a performance that meets the more general requirements for the functionality of

$gterm

.

$gterm

may provide two types of service:

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

      $gterm

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

      $gterm

      $gterm

      .

Example:
A reference server may return a list of

$gterm

matching a particular search string . The client application may use this data to populate a list from which a user makes a selection.

  • $gterm

    (

    $gterm

    ) Services (see ):
    • Services that include the one or more

      $gterm

      $gterm

      that can be used in and programmatically accessed by the client application.

Example:
A

$gterm

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

    $gterm

    service is a

    $gterm

    with an

    $gterm

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

      $gterm

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

      $gterm

      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