Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.23.2.0.9

This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.23.2.0.9.

Version compatibility: Oracle Health Insurance Enterprise Policy Administration Release 4.23.2.x is only compatible with other Oracle Health Insurance applications release version 4.23.2.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

POL-15792

Optimize loading of SVNTV fields into the memory during extracts

Currently, the system loads all the Single Value Non-Time Valid(SVNTV) dynamic fields associated with resources into the memory which causes OOM. Only the required SVNTV dynamic fields should be loaded into memory while processing the extracts.

4.23.1.0.8, 4.24.1.0.1

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

This section intentionally left blank.

Data Conversion

This section intentionally left blank.

Dynamic Logic

This section intentionally left blank.

UI Changes

This section intentionally left blank.

Breaking Changes

This section intentionally left blank.

Bug Fixes

BugDB SR Internal Summary

36925407

3-37554577351

POL-15663

Evaluate Conditions not working in Edit Mode

Description:

Evaluate condition in floorplan not working for the first time in edit mode. Its working fine in create mode. initconditions are not used in floorplan, as evaluateconditions are not working as intended when used with initconditions

Resolution:

Evaluate conditions are working in edit mode as well as expected

37091028

POL-15943

Include stand alone catchUp periods when running APPLY_REGISTRATIONS activity

Description:

During the APPLY_REGISTRATIONS activity, periods are (re)generated and used to apply registrations. CatchUp periods are defined as periods that start before the reference input date. When the system generates periods, the catchUp periods are only generated in combination with the first regular cycle, which is the period starting on the reference date. If the first regular cycle is not generated, neither are the catchUp periods, causing gaps when the first regular cycle is never generated (for example when the reference date is after the end date of the collection setting).

Resolution:

The Apply Registrations activity does not make a distinction between catchUp periods and regular periods so registrations can be applied to catchUp periods only.

37157979

POL-16046

Reconciliation is not applied when enrollment period ends in the mid of calculation period

Description:

When the enrollment period ends in the middle of a calculation period, meaning the calculation period segment’s end date does not match the span end date, reconciliation is not applied. Instead, the amount is calculated as the product of the daily rate and the total days enrolled within the segment. This leads to discrepancies between the expected and actual outcomes.

Resolution:

Reconciliation is now applied to the calculation period segment where the enrollment ends, treating it as the last period segment. This has resolved the discrepancy between the expected and actual outcomes.

37093053

POL-15947

Parameter Amount Value is saved With Default Value instead of zero

Description:

Parameter Amount Value is saved With Default Value when value zero is sent.

Resolution:

Parameter Amount Value is saved with value zero instead of default value

Issues that were backported in previous Release / Patch

No backports.