Overview of:

NCBO Implemenation

Introduction

...

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.

CTS 2 Implemenation Guides

Why do we need implementation guides?

To address what the CTS 2 Specification does not do:

• Specify how CTS2 content will be represented in a backing store
• Specify how various terminology models and formats are imported and exported
• Specify how specific terminology workflow and business rules are realized in a CTS2 service

HL7 CTS2 Implementation Guide

...