HealthTerm was developed with a very advanced translation module and the basis for the logical structure was SNOMED CT’s data model, which is a general and recognised terminology model. Hence, SNOMED CT’s model for subdividing the terminology into smaller parts (subsets) was from the onset an important part of the system. It was necessary to select smaller parts of the terminology (in Denmark approx. 10,000 concepts per month) for translation, then again subdivide these into batches of 1,000 concepts for the individual translators. For these reasons HealthTerm started with a browser, a subset module and a translation module. On top of these modules one will find administration and setup of user rights and privileges. The Board of Health project quickly became successful, and the parties therefore began contemplating other code systems, which were maintained by the Board of Health in order to integrate these in the system to be maintained and distributed via HealthTerm. This was the start of the Editing Module, which was optimised for general code systems as well as advanced terminologies like SNOMED CT.
Later a mapping module was developed for handling the mapping of the old SKS system to the new SNOMED CT (The Mapping module supports mappings between all kind of code systems e.g. LOINC, ATC, DICOM ect.). A link between the various code systems was necessary and again quality and process were important features of the application.
The results of many years of work and cooperation with customers all together resulted in a perfect terminology toolset. A set of modules, which facilitates the many tasks involved in the maintenance and publication of code systems. It is unique to have a product that handles all facets of these often advanced tasks. The modules support extensions in many dimensions of the various code systems, just like language management has been a central aspect – in such a way that application language and content language (code systems etc.) have been separated and can be managed separately.