Introduction

After the Engine has calculated a determination result, the Engine must choose whether to store the determination result, and if so, how to store it.

The choice of whether to store a determination result hinges on a number of factors, described later. Typically each new determination result will end up being stored.

The Engine stores the determination result by writing a row to the CREOLECaseDetermination database table (and also some other data written to child database tables). The data stored includes the full details of the determination result and optionally also a "snapshot" of all the CER rule objects used in the calculation of the determination result.

The Engine also stores rows of eligibility and entitlement data CaseDecision and its child tables, so that this data can be used later by Cúram Financials to generate financial components for the case. The Engine links the CaseDecision rows to the CREOLECaseDetermination row by storing rows on CREOLECaseDecision.

This chapter is structured as follows:

• The Database Tables

  A description of the tables that the Engine uses to store determination data;

• Decision Periods

  How the Engine splits a determination into periods of constant eligibility/entitlement; and

• Determination Comparison Strategies

  How the Engine decides whether a new determination is "different" from an existing determination.