When designing or implementing a glossary-ref
, the first step is to assess the range of services necessary to meet user requirements. The two main categories of services required by applications are glossary-ref
that only interact with the terminology and glossary-ref
which apply the terminology to instance data. These services are described in separate sections of this guide
The Terminology Services Guide describes services that access glossary-ref
reference data. These services are summarized in .
Figure 2. SNOMED CT Enabled Terminology
SNOMED CT Enabled Terminology services
The Record services guide describes services that apply glossary-ref
to represent information in a clinical record. These services are summarized in .
Figure 3. SNOMED CT Enabled Record
SNOMED CT Enabled Record Services
may be completely self-contained, delivering all the required services as part of a single development. Alternatively, service delivery may be modularized so that separately developed reusable modules are used to meet specific sets of requirements.
A distinction can be made between functions that only require interaction with terminology resources ( glossary-ref
) and functions that involve using the terminology as part of an application such as an glossary-ref
glossary-ref can be generalized, so that they are independent of the way the terminology is used in a particular clinical record application. glossary-ref
include support for the following types of function.
- Importing and updating a local terminology repository with a glossary-ref ;
- Determining the properties or an identified glossary-ref ;
- Text or pattern searches for glossary-ref that include a matching term;
- Displaying a part of the glossary-ref hierarchy;
- Determining whether a glossary-ref or glossary-ref is equivalent to or a glossary-ref of another glossary-ref or glossary-ref ;
- Locating the glossary-ref from a particular glossary-ref to a code in another scheme or classification.
- Authoring and maintenance functions:
- Enabling the creation and maintenance of core glossary-ref to facilitate production of the glossary-ref and glossary-ref to glossary-ref ;
- Enabling the creation and maintenance of derivative such as glossary-ref to customize and enhance the effective use of glossary-ref .
glossary-ref are intimately related to ways in which information is entered, stored and retrieved by a particular application. Therefore, while these services interact with glossary-ref
they are usually specific to a particular application or to a family of applications with a common underlying record design. glossary-ref
include support for the following types of function:
- glossary-ref functions that:
- Enable entry of information using glossary-ref where these are relevant;
- Display of previously entered information, with appropriate rendering of glossary-ref ;
- Enable design of protocols that guide data entry to encourage efficient and consistent use of glossary-ref ;
- Enable specification of queries that include appropriate use of glossary-ref to meet requirements for selective retrieval.
- Application server functions that:
- Store glossary-ref as part of the individual record entries (or in other types of instance data);
- Communicate data including glossary-ref in ways dictated by standards and local specifications;
- Apply queries to efficiently, accurately and precisely retrieve information taking account of the data structure of the application and the logical glossary-ref between glossary-ref .
These two sets of services can be developed and provided separately. This approach allows glossary-ref
to access required glossary-ref
through an glossary-ref
). The guide does not specify an glossary-ref
but, by making a clear distinction between glossary-ref
, it identifies the functions that such an interface should support.
Self-contained and modular approaches offer different profiles of advantages, some of which are summarized below.
A modular approach offers the following advantages:
- Rapid development of glossary-ref related functionality, focused on meeting the requirements of users of a specific software application.
- Opportunities to choose between different glossary-ref to deliver a cost-effective solution.
- Simplifies future migration to enhanced or more cost-effective solutions by separately identifying reusable and replaceable modules.
- Allows several applications used by a single organization to use a single glossary-ref . This has several advantages:
- Reduction of maintenance and support cost associated with installing each release of glossary-ref ;
- Guaranteed alignment of glossary-ref between applications that share the server;
- Consistency of the glossary-ref and technical characteristics of different applications with respect to their access to glossary-ref .
- A fully integrated approach offers the following advantages:
- Independence of third party development;
- Customized access to glossary-ref tailored to the needs of particular application users.
The approach chosen depends on a careful consideration taking into account the cost and functionality of available glossary-ref
. Commercial and technical concerns about dependence on third-party glossary-ref
may be a valid reason for in-house development of all the required services. However, even where all the development is undertaken within a single organization, separation of terminology and glossary-ref
into separate glossary-ref
may offer a more robust approach, allowing future extensibility and migration at lower cost.