Enterprise Architecture – The DTS server has been completely rewritten to use Enterprise JavaBeans 3 (EJB) and Service Oriented Architecture (SOA). EJB replaces much of the “back-end”/transaction aspects of DTS (concurrency, pooling, security) with industry-standard, open source components, e.g., JBoss. Use of EJB simplifies many operational aspects of DTS and will provide enhanced security and transaction options. With this new architecture, the comprehensive DTS API is also now available as web services in addition to Java and .NET forms simplifying the integration of DTS with web-based applications. The API is, however, fully backwards-compatible, so existing DTS applications can run essentially unmodified.
Versioning – Version 4 extends the DTS Object Model to support complete history (versioning) of Namespaces and Subsets. Search and browse functions can specify the desired version/date and comparison and full historical views are supported. All the data you need for terminologies such as SNOMED CT, LOINC and ICD-9 and ICD-10 are all in one place and easily accessible.
New Metadata – New metadata (implemented as user-definable "Property Types") can now be added to Namespaces, Versions, Authorities and Subsets. This metadata is available for both Subscription and Local DTS Objects. This new metadata provides for more expressive objects and can include definitions, provenance, URIs, etc.
The DTS Browser – With Version 4 we are introducing a new DTS Browser, based on the JavaServer Faces 2 architecture and RichFaces 4 framework. We are very excited about the opportunities to provide enhanced web browsing, and editing, via this platform.
The DTS Editor – The DTS Editor provides extensive support of Version 4 features. The Search, Browse and Detail panels, for example, all support one-click selection and viewing of version ”snapshots” of DTS objects. The Version 4 DTS Editor also extends its popular Plug-in Framework to a new Module Framework. All Editor functionality is now provided through independent Modules. This means that the Editor can be completely customized for specific user requirements. The Editor is no longer an extensible application, but a customizable platform for the delivery of terminology management functionality. The “classic” DTS Editor is still available as one example of an Editor implementation. Finally, the Editor has been enhanced for internationalization; prompts and messages have been relocated to a Locale-dependent Resources file. This enables the GUI of the Editor to be translated into many non-English languages.