Terminology Service Use Cases

This section describes practical use cases which require the use of specific terminology services.

Overview of Use Cases

The following use cases are covered in this section:

Notes on the attributes used in the tables of this page:

*Status: Applications designed to address this use case must support the practical requirements marked as Required. Support for the practical requirements marked as Optional is recommended as these provide enhanced functionality that may be required by some users.

*Required Services: In most cases, a reference to a subsection of Terminology Service Types, implies a requirement for all services marked as Required in that subsection. However, where a reference is followed by a bulleted list, that list specifies the specific terminology services required. Some of the specific services listed as required for an Optional practical requirement may be marked as Recommended in the referenced subsection.

*Dependencies: This columns contains references to services on which a Required Terminology Service depends. This column does not restate dependencies on services listed as required service or additional dependencies for essential requirements listed in earlier rows.

A full list of the dependencies of each terminology service is provided in the relevant subsection of Terminology Service Types.

Last updated