...

The Bioportal REST xml is traversed via the DOM API and converted to CTS2 objects. XPath for Java was also tried, but direct DOM traversals proved much faster. Transform occurs in the edu.mayo.cts2.rest.service.bioportal.transform package. Bioportal calls are cached as needed. For example, any XML that is needed on a regular basis will be persistently cached (such as current versions of ontologyId's, etc). All other Bioportal calls are cached in a Least-Recently-Used basis. For example, a term search Bioportal REST call may be cached for future use, but will be evicted from the cache when the cache reaches a certain size. This is an attempt to limit calls to Bioportal for data that is not expected to change often. Changes to Bioportal are listened for via Bioportal's RSS feed, and caches are evicted accordingly when a change is noticed. There are no persisted artifacts other than a cache file, and these will be stored in the $USER_HOME/.cts2 directory.

HL7 CTS2 Implementation Guide

As part of the CTS 2 development effort in the OMG community, it is necessary to ensure that HL7 content can be accurately represented in CTS 2. 

To be successful, the following need to be addressed:

• Unambiguous transformation between HL7 representation and CTS 2 core.
• Consistent representation of any HL7 extensions deemed appropriate.
• Specification of specific HL7 terminology business rules and workflow that need to be provided by HL7 CTS 2 service providers.

This will ensure that HL7 content, even though exposed through different implementations of the CTS2 specification, will be consistent and interoperable.

IHTSDO CTS2 Implementation Guide

CTS2 Prototypes

Bioportal Widgets

...