 |
Page History
| Info |
|---|
LexEVS and its data model LexGrid comprise a full function terminology service meeting a wide range of requirements. The Common Terminology Service 2 is a comprehensive standard defined by a broad range of community interests.
|
| Panel | ||||
|---|---|---|---|---|
| ||||
|
CTS2 Rest Client Quick Start
Refer to LexEVS 6.x CTS2 API Quick Start for information and a set of examples for the CTS2 REST implementation over LexEVS.
CTS2 API Documentation
Interactive CTS2 API Documentation has been updated and is available for LexEVS CTS2 6.5.1. It is available here:
LexEVS 6.5.1 CTS2
Refer to
...
...
LexEVS 6.5 CTS2
...
CTS2 documentation for information on changes made in LexEVS 6.5
...
.
...
LexEVS 6.4 CTS2
Refer to LexEVS 6.4.1 CTS2 documentation for information on changes made in LexEVS 6.4 CTS2.
LexEVS 6.3 CTS2
Refer to LexEVS 6.3 CTS2 documentation for information and a set of examples for changes made in LexEVS 6.3 CTS2.
LexEVS 6.2 CTS2
Refer to LexEVS 6.2 CTS2 documentation for information and a set of examples for changes made in LexEVS 6.2 CTS2.
Migration Notes for CTS2
Migrating from 6.1 to 6.2 REST services.
| Add Page | ||||
|---|---|---|---|---|
|
LexEVS 6.1 CTS2
| Info |
|---|
| As a specification CTS2 is comprehensive. As such it is easiest to visualize it as a set of modules that treat the aspects of a coding scheme or code system as pieces that fit together to form a whole. While the specification is nearly all-inclusive, it is not intended to be implemented as a monolithic whole. Instead it provides options for implementing a convenient subset of not only service objects, but also service functionality. CTS2 in LexEVS provides core modules and functionality that will serve the largest portion of use cases where terminologies are determined, queried, and traversed. |
CTS2 may be implemented as a service or as a client. Clients can access terminology data with minimum implementation.
Current State of CTS2
The current state of CTS2 as implemented in LexEVS 6.1 is outlined in a CTS2 implementation resources site
| Multiexcerpt include | ||||||
|---|---|---|---|---|---|---|
|
The
...
The OMG CTS2 1.1 Specification is written as a REST based architecture. It can be implemented as a minimal set of modules. Refer to CTS2 design document.
OMG CTS2 Specification
The OMG CTS2 specification is defined and hosted by the OMG group
| Multiexcerpt include | ||||||
|---|---|---|---|---|---|---|
|
The HL7 CTS2 Service Functional Model
The HL7 CTS2 Service Functional Model as normalized to the OMG group specification is hosted by HL7
| Multiexcerpt include | ||||||
|---|---|---|---|---|---|---|
|
...
URI Resolver
Given the RESTful nature of CTS2 along with the possibility of distributed queries over multiple terminology nodes, the need for canonical naming conventions around URI, IRI or URL becomes paramount. To serve this purpose a prototype URI resolving service has been built for CTS2 over LexEVS. This service attempts to provide a canonical name in the form of a URI based on curated convention and dependent upon the comprehensive storage of know other URIs known for a given terminology. As such this service provides some securely robust resolution of a given resource despite it's possible use of an alternative URI.
...
URI Whitepaper (pdf download)
Installing CTS2 as a Service
Refer to the instructions for installing your own CTS2 over LexEVS service.
LexEVS 6.0 CTS2
| Warning |
|---|
| This implementation, while not CTS2 compliant, still has value as it includes a number of unique features including terminology authoring and version control in a Java API. |
Refer to the following:
LexEVS 6.0 CTS2 GuideLexEVS 6.0 CTS2 API
