Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.23.1.0.3

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

Version compatibility: Oracle Health Insurance Enterprise Policy Administration 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

POL-12478

Exclude reference resources for generic GET operation

This enhancement introduces a new resource representation parameter excludereferenceresources. When set to true, it excludes the list and reference resources from the generic GET response.

Additionally, for the search requests originating from UI, excludereferenceresources is set to true, that is, to retrieve only the required details.

3.22.2.0.21, 4.23.1.0.2, 4.23.2.0.0

POL-13467

Improvements on the persons page

This enhancement introduces a new object navigation link on the persons page to maintain person covered services.

3.22.2.0.21, 4.23.2.0.0

POL-14106

Allow adding and removing parameter values on an enrollment product at the same time in dynamic logic

This enhancement enables customers to add and remove parameter values at the same time in (validation) dynamic logic .

POL-14595

Additional logs for flexcodesystem code at the level of dynamic field setup cache and for translation records in the database

Policy submission led to a Null Pointer Exception because flexcodesystem code was not found at the dynamic field setup cache or because of missing entries for translation records of the code in the database.

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

Ref Action Description

POL-13467

Modified

Persons

Removed covered services tab from the persons floorplan. Added Person covered services as an object navigation

Breaking Changes

Ref Action Description

POL-13467

Modified

Persons

It is not allowed to re-configure person covered services as a tab on the persons page, as they are now available as a separate object navigation page.

Bug Fixes

BugDB SR Internal Summary

36295784

POL-14591

Business event is not getting generated due to incorrect parameter(entity name)

Description:

JET is sending incorrect value(employmentOfMember#policyEnrollment) to entity when creating a business event rule. As it is not matching the entity name in PolicyEnrollmentEvent, Business event is not getting generated.

Resolution:

Business event is getting generated properly and proper payload is sent from JET when creating a business event rule

36295837

3-35477511858

POL-14592

System unable to offset refund when there is an unapplied amount greater than refund

Description:

System unable to offset refund when there is an unapplied amount greater than refund

Resolution:

Enhanced SQL query to check if there is a registration with status 'N' and earliest offset payment date will only be set when there is no registration with status 'N' otherwise it will be NULL, and mutation recalculation will be done only when earliest offset payment is not null

36219176

POL-14433

Adjustment Rules - The amount field is not accepting negative value, also few columns are missing

Description:

In the amount field of Adjustment and Surcharge Rules page, negative values are not accepted. Also 'Amount Function' and 'Amount Not Prorated' is not displayed.

Resolution:

In the amount field of Adjustment and Surcharge Rules page, negative values are accepted. Also 'Amount Function' and 'Amount Not Prorated' is displayed.

36204027

3-34786906091

POL-14387

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.

36227371

3-35379874711

POL-14470

SQL execution plan to delete selected financial transactions for large group is inefficient

Description:

SQL execution plan to delete selected financial transactions (at the end of generate financial messages activity) for large group is inefficient

Resolution:

The SQL is optimized

36151014

3-35320237389

POL-14238

Enrollment IP metadata is invalid

Description:

Metadata returned by GET /enrollments/metadata IP is invalid.

Resolution:

Updated Metadata - Removed data related to get enrollment, and also added schema of enrollment request for post request

36061037

3-34993002381

POL-14036

Person Covered Services are removed when they end on the Reference Input Date.

Description:

Person Covered Services that end on the Reference Input Date are removed when reprocessed but not regenerated. Therefore, these Person Covered Services end up missing during a second generation cycle.

Resolution:

Person Covered Services that end on the Reference Input Date are not removed during a second generation cycle.

36250669

POL-14514

Length of OHI_ID_ARRAY database type is still 14 after upgrading to 4.23.1 release

Description:

Length of OHI_ID_ARRAY database type is still 14 after upgrading to 4.23.1 release

Resolution:

The length of OHI_ID_ARRAY database type is updated to 19

36275603

3-35379874711

POL-14570

Slowness in calculate premium when group client parameter is specified.

Description:

Inserting policy-level child activities was inefficient when the group client parameter is used, resulting in a longer execution time to calculate premiums.

Resolution:

The query inserting policy-level child activities is improved to address the slowness of calculate premium activities

36213517

3-35379874711

POL-14422

Slowness in calculate premium when group client parameter is specified.

Description:

Inserting policy-level child activities was inefficient when the group client parameter is used, resulting in a longer execution time to calculate premiums.

Resolution:

The query inserting policy-level child activities is improved to address the slowness of calculate premium activities

35854454

POL-13762

Dynamic logic timeout property is ignored when compiling dynamic logic at startup time

Description:

The dynamic logic timeout property (ohi.dynamiclogic.timeout or ohi.dynamiclogic.timeout.{0}) is ignored when the dynamic logic is compiled at system startup time.

Resolution:

Load the system property from the database if the loading of system properties is not completed. If loading of system property is completed then load from cache.

Issues that were backported in previous Release / Patch

No backports.