Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.21.3.0.12

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

Enhancements

ID Summary Patch

NXT-24489

JSON Re-Indexing Package

This enhancement introduces the package OHI_REFERENCE_SHEET_LINES_INDEX_MAINTENANCE_PKG, that creates an oracle text index OHI_REF_SHEET_LINE_IDX1 on OHI_REFERENCE_SHEET_LINES table in Oracle 19c format with Sync frequency option. This package needs to be executed in the Post-upgrade stage.

3.22.1.0.0

POL-10396

Additional Tier Determination Settings

Before this enhancement, the system determines the policy tier based on the reference date, typically configured to be the 1st of the calendar month. The tier is determined by every policy enrollment with a policy enrollment product for the tiered product that is active on the 1st.

This enhancement introduces more granular settings that support the following use case where:

  1. Members that were added to the policy on or after a configured day of the month, do not count towards that month’s tier determination

  2. Members that were termed on the policy on or before a configured day of the month, do not count towards that months tier determination

Documentation Links:
Operations Guide - Calculate Premium
Operations Guide - Tiers Determination

3.21.2.0.10, 3.22.1.0.1, 3.22.2.0.0

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

Additional Upgrade Steps for Installation

The following phases are defined:

  1. pre-upgrade: Application is still running

  2. pre-undeploy: Application is stopped, but not undeployed.

  3. post-undeploy: Application is undeployed. Database is backed up

  4. post-upgrade: Released upgrade script has run.

  5. post-deploy: New application is deployed and is up and running.

Stage: post-upgrade

A new OHI_REFERENCE_SHEET_LINES_INDEX_MAINTENANCE_PKG has been provided as part of the patch. Post upgrade of the patch login as ohi_<app>_owner and execute the below command to recreate the index.

begin
  ohi_reference_sheet_lines_index_maintenance_pkg.create_index;
end;

Configuration Properties

This section intentionally left blank.

Web Services

Ref Action Description

POL-10396

Modified

Premium Calculation

When Partial Period Resolution is set to Split Periods, tier determination will be based on the Enrolled Days Threshold instead of the reference date

Data Conversion

This section intentionally left blank.

Dynamic Logic

This section intentionally left blank.

UI Changes

This section intentionally left blank.

Deprecated items (to be removed in future release)

This section intentionally left blank.

Breaking Changes

This section intentionally left blank.

Bug Fixes

BugDB SR Internal BP Summary

34299790

3-29517034251, 3-30389098551, 3-28820355311

POL-10813

BP

In a Change Event Rule on Policy/PolicyEnrollment, old entity sometimes contain wrong time-valid dynamic field values.

Description:

When a Change Event Rule (which monitors a dynamic field) is invoked, because of multiple changes to that time-valid dynamic field or record, then, the values of the dynamic fields on the old entity (oldPolicyEnrollment/oldPolicy) are equal to those on the new entity, which is not the expected behavior in every use case.

Resolution:

The dynamic fields of old and new entities are now correctly initialized in the change event dynamic logic.

34069242

3-29167626501

POL-10430

BP

Address Type is not properly matched during Policy In IP

Description:

When a (new) Address is sent in with Policy In process, it is matched on AddressType and StartDate. When the AddressType is absent it is filled with the default AddressType. Which means that the AddressType of the incoming Address is null whereas the AddressType of the existing Address is never null, resulting in invalid mismatch.

Resolution:

When incoming addressType is null, it is matched on the default address type.

34281284

3-29420975001

POL-10786

BP

Updating dynamic records with many flex codes is slow

Description:

If a dynamic record is defined with many flex codes, change event rules defined on an update of this dynamic record take very long time to complete.

Resolution:

Performance on processing these change event rules has been significantly improved.

34322046

3-29943391705

POL-10907

BP

Calculating Premium with Tiered Premium Schedule results in NoSuchElementException

Description:

During policy processing, the system checks all eligible Policy Enrollment Products per Premium Schedule per Calculation Period. If the Partial Period Resolution is set to SplitPeriods, the Policy Enrollment Products that start after the threshold (or end before) are not included for PremiumTier determination. When, for a specific Period, all Policy Enrollment Products start after the threshold, but within the same period, a NoSuchElementException is thrown. The same argument holds when all Policy Enrollment Products end before the threshold, but still within the same period

Resolution:

For a specific Calculation Period, if all the Policy Enrollment Products start after the threshold (or end before), the tiered premium schedule is not considered during premium calculation for that period.

34344096

3-29942984031

POL-10939

BP

Tier based Premium Calculation with Split Periods takes threshold date based on Calculation Period Segment instead of Calculation Period

Description:

For tier based premium calculation, the system determines the threshold date based on the configured threshold. This date indicates a specific moment in a calculation period when an enrollment should be 'active' to be included in tier determination. This threshold date should be determined based on the start date of the Calculation Period, not based on the start date of the Calculation Period Segment.

Resolution:

The threshold date is now calculated based on the Calculation Period start date.

34988283

3-31692075331

POL-11999

BP

Cancelled policy is not shown under Person → Enrollment Section

Description:

After a Policy is Cancelled, the policy code is not getting listed under the Person →Enrollment section.

Resolution:

The canceled policy is shown under the Person → Enrollment section.

Issues that were backported in previous Release / Patch

No backports.