Release Notes for Oracle Health Insurance Product Definition Patch 4.23.1.0.3

This document contains the release notes for Oracle Health Insurance Product Definition Patch 4.23.1.0.3.

Version compatibility: Oracle Health Insurance Product Definition Release 4.23.1.x is only compatible with other Oracle Health Insurance applications release version 4.23.1.x unless explicitly stated otherwise.
In accordance with the OHI error correction policy (Document 1494031.1 on My Oracle Support), error correction support will be provided for this release and the previous two releases.

Enhancements

ID Summary Patch

PRD-3875

Selective financial limit Carry-over

This enhancement introduces the ability to decide whether an out-of-pocket-maximum (OOPM) limit consumption counts towards year-end carryover. For example: * An OOPM consumption from a coinsurance or a copay do not count towards a carryover. * An OOPM consumption from a deductible does count towards a carryover.

A new indicator, exclude from carry over is introduced on the product-benefit-specification limit to help make this decision. The indicator is available for the build product process to define the carryover settings.

Documentation Links:
Configuration Guide - Carryover Settings
Configuration Guide - Product Benefit Specification Limit
Operations Guide - Build Product

Upgrade Steps for Installation

To perform the upgrade, perform the following steps:

  1. Perform any pre-upgrade steps.

  2. Stop all the managed nodes running the existing version of the application.

  3. Perform any pre-undeploy steps.

  4. Undeploy the existing version of the application.

  5. Back up the database.

  6. Perform any post-undeploy steps.

  7. Unpack the release bundle into a directory that we refer to as OHI_ROOT from now on.

  8. Change Installation Configuration: In <OHI_ROOT>/util/install, make a copy of ohi_install.cfg.template and name it ohi_install.cfg.

  9. Edit ohi_install.cfg to contain your specific database connection data and other configuration settings. The settings are explained in the file itself.

  10. Make sure NO connections are present to the database using the OHI_xxx_USER account (where xxx is the abbreviation of the application)

  11. Run the Upgrade script:

    1. Open a command window and browse to <OHI_ROOT>/util/install.

    2. Run the upgrade by executing ./ohi-update.sh .

  12. Make the required changes to the ohi properties file

  13. Perform any post-upgrade steps

  14. Start WebLogic application server

  15. Deploy the Application

  16. Perform any post-deploy steps

Configuration Properties

This section intentionally left blank.

Web Services

Ref Action Description

PRD-3875

Modified

Build Product

Carry Over Settings are used when product benefit specification limits are generated

PRD-3875

Modified

Products Export

Exclude from carry over indicator is included in the product benefit specification limits

Data Conversion

This section intentionally left blank.

Dynamic Logic

This section intentionally left blank.

UI Changes

Ref Action Description

PRD-3875

Modified

View Generated Product

Exclude from carry over indicator is visible in the product benefit specification limits

PRD-3875

Modified

Products Page

New section to define carry over settings

Breaking Changes

This section intentionally left blank.

Bug Fixes

BugDB SR Internal Summary

36203984

3-34786906091

PRD-4066

Dynamic logic byte code is not loaded during server startup on non master nodes after invalidateall API is invoked

Description:

Dynamic logic byte code is expected to load at the startup of non-master nodes if the invalidateall API was invoked in master node but was not being observed.

Resolution:

Dynamic logic byte code is now loaded at the startup of non-master nodes if the invalidateall API was invoked in master node.

Issues that were backported in previous Release / Patch

No backports.