Configuration Guide

Purpose

Oracle Health Insurance enables customers to configure reference data that control daily operations like Claims Adjudication or Premium Calculation. This guide explains how to provide the system with these data.

To persist these data, it may require to extend the data model or to code custom logic. See the Developer Guide for more details on those topics.

Oracle Health Insurance supports migrating (the changes in) the configuration reference data from one environment to another, through its Configuration Migration tool. It supports detailed control over the objects, including dynamic logic modules, that need to be migrated. See the Developer Guide for more details on those topics.

Target Audience

The Configuration Guide supports business consultants and business process owners to set up the Oracle Health Insurance configuration according to the customer’s process requirements and reference data.

Guiding Principle

Guiding principle for the Configuration Guide is to provide the Oracle Health Insurance application with the process steps and reference data needed to execute daily or other (regular) operations.

In most cases this requires strong interaction with the development team who enable persisting custom specific extensions to the data model and who code the custom specific logic that extend the standard Oracle Health Insurance processes. In general one could say that the configuration team provides the specifications for the customer’s operational processes. The development team then makes the necessary extensions to the data model, and the processing logic. Then the configuration team records the reference data and includes the processing functionality in the right locations.

Always plan changes carefully, thoroughly test the impact on functionality and performance in a non-production environment and use a configuration management tool like Oracle Health Insurance’s Configuration Migration tool to promote the changes into production.