Features

Overview

Details features of this terminology server.

License

This software is offered with a standard Apache 2 licence.  Like other free software licenses, the license allows the user of the software the freedom to use the software for any purpose, to distribute it, to modify it, and to distribute modified versions of the software, under the terms of the license, without concern for royalties.[1]

Features

• Data model built around RF2, so it natively handles SNOMED and other terminologies that can be transformed to an RF2 representation (including ClaML).  The data model also includes “first class” representation of standard RF2 reference set patterns (such as Attribute Value and Complex Map).
• Support for multiple terminologies.  This means the server is capable of handling non-SNOMED based terminologies, such as ICD10, ICD10CM, ICD9CM, and ICPC.  It also means the server is capable of handling and supporting SNOMED extension use cases (such as the US Edition)
  • Includes support for delta, full and snapshot RF2 data
  • Includes support for ClaML data
• Supports transitive closure computation and maintenance.  This means ancestor and descendant computations are simple lookups and do not require any graph walking.
• Supports classification via SnoRocket, including incremental classification (if needed).
• Supports a customizable identifier management mechanism allowing various approaches to ID maintenance to be used, including application managed identifiers, content hash-based UUID assignment, and SNOMEDCT identifier assignment based on sequences.  This includes the ability to assign UUID identifiers during development to core components followed by SNOMED identifier assignment at release time.
• Supports a customizable authentication/authorization mechanism, including default implementations for native SNOMED security architecture, and “no” security.
• Supports a customizable “graph resolver” mechanism to define the depth into the graph that various read and write calls should support.  The default implementation of this mechanism supports reading/writing a concept that includes descriptions, language refset members, and relationships.
• Supports a customizable validation framework that allows testing of data states prior to serialization.  The default implementation includes a few basic checks to demonstrate use.
• Supports paging, filtering, and sorting at the API level.  For example, a “find concepts” call can be combined sorting and filtering and can also page results one page at a time with flexible page sizes supported.
• Supports multiple, simultaneous editing of the same concepts for dual independent review, conflict identification, and conflict resolution.
• Supports a customizeable “workflow listener” mechanism to interface with an external or third party workflow management system.  Workflow can be tracked at the concept or description level but is not itself maintained by the system. Instead, any “change” to the system can facilitate a callback to a custom handler that respond in any way desired.
• Supports REST API for batch changes.
• Includes a default release process for performing identifier assignment and delta RF2 generation.
• Includes complete administrative, technical, and user documentation, and a full swagger API with example values that yield legitimate results.
• Flexible back-end data store.  Default support for MySQL but uses hibernate facilitate connections to a variety of other database environments, including MongoDB and Oracle.

Emerging Features