Many countries are in the process of switching from paper-based patient records to electronic based
patient records. This migration is expected to be one of the greatest public sector IT challenges of the near future.

As a basic part of any electronic-based patient record system, a common terminology must be agreed upon. HealthTerm® is one of the world’s leading applications for the effective management of healthcare terminology.

Enterprise environment
The maintenance and construction of terminology lists is generally a highly resource-intensive process, involving many people. HealthTerm® is an enterprise back office system, based on a serviceoriented architecture in which all terminology is centrally concentrated and managed. The application has been specially developed for the distribution and management of terminology processes, as an online solution based on Oracle's 10G database and the SUN JAVA Enterprise Environment (J2EE).

Based on the SNOMED CT® structure
The fundamental structure of the HealthTerm® system is based on SNOMED's structures, with a development of the history mechanism, so as to provide a history of all objects. The model has been extended with dynamic attributes and associated history. This provides an opportunity to use HealthTerm® for many different classifications and terminologies at the same time. In this way, HealthTerm® concentrates all classification and terminology work in one place!

The HealthTerm® terminology browser
The terminology browser supports a multi-language view of all terms, and can easily be used in local-language or multi-language environments. Translation of terms to the local language can easily be done by using the HealthTerm® Translator (see the separate product sheet).

It is possible to view the data through a classic tree structure and a simultaneous star view in order to view multiple axes of the terminology system.

Subset module
HealthTerm® supports subsets of the terminology and makes it possible to extract and save these subsets for later viewing or distribution.

Workflow of subsets
In general, if many people are to work together efficiently, it is important to have a controlled work process. HealthTerm® gives you the opportunity to create an advanced workflow, in which
different working groups are assigned different roles and rights to a subset, for example in connection with a review process.

User management
HealthTerm® has been developed for company processes, which is why it is possible to assign particular roles to all users in groups. These rights may be inherited between groups, and may be
based on either menus or objects, or combinations of these – such as different classifications, extensions or specific subsets.

Basic functionality – subset handling
Subsets are created in a user-friendly subset generator which enables the creation of different types of subsets (including both concept-based, description-based and navigational subsets). Subsets are created using a tree structure whichmakes it possible to add selected concepts, as well as any sub-level of the concepts, such as children and descendents. It is also possible to create your own tree structure as a navigational subset with easy drag-and-drop functionality. Subsets can be stored and structured in a user-defined hierarchy within the realm and context.

Advanced functionality – subset handling
Subsets can also be constructed and maintained in the form of rule definitions (query-based). It is subsequently possible to automatically view any alterations in the subset, and if necessary update these to new versions when making alterations in
the terminology. Subsets contain a full history just like all other objects, and version control can be applied to them.

References in subsets
HealthTerm® supports the possibility of uploading reference documents in, for example, Word, Excel or PDF formats, whereupon these become versions and are indexed. It is subsequently possible to search the documents and create direct links to the desired index in the file. It is similarly possible to upload and link the entire document to a subset, or create web references or comments for the specific subset. All of these functions play a part in documenting and supporting the clinical subsets.