Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

One of the features of interest for a future version of OpenCDS is the ability to "hot deploy" new knowledge bases (e.g. - codes, concepts, drools rules, and supporting data) as needed without having to restart OpenCDS for the changes to take place. ICE, an application based on OpenCDS, envisions the following automated knowledge deployment capabilities within OpenCDS to support the operation of ICE. However, we also believe that the proposed functionality is generic and would benefit any OpenCDS-based services. For purposes of this discussion document, we will talk about the scenarios with respect to ICE for complete understanding of the requirements, and then abstract the requirements afterwards.

...

ICE is immunization forecasting software; the customizable rules are written in software called the CDS Administration Tool (CAT).

 

CAT manages the following data artifacts, all of which are also directly represented in OpenCDS XML files and we would like the ability to deploy in OpenCDS:

  • OpenCDS concepts
  • Code system codes 
  • Code mappings to OpenCDS concepts (which specifies the Concept Determination Method by which the mapping should occur)
  • Concept Determination Methods
  • Knowledge Modules

In addition, CAT manages the following deployable artifacts to OpenCDS:

  • Supporting data
  • Drools rules (DRL and DSLR)
  • DSLs
  • Concept Determination Methods (not directly deployable to OpenCDS but contained in code->concept mapping files)

Supporting data is any kind of data that is cached in instances of Java classes for the knowledge module at runtime operation. For ICE, most of the cached data is stored in various Maps and accessed by the rules. Examples include series table values such as recommended ages and intervals. The cached data is static and remains in memory for as long as the knowledge module is in memory by OpenCDS.

CAT also supports Value Sets (under construction), but value sets are not currently supported by OpenCDS in a specific way.

Scenarios

We would like to support the following "hot" deployment scenarios from CAT to OpenCDS:

  1. Deploy all