Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.24.1.0.6

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

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

User Defined Validations for Registrations

This enhancement introduces the ability to define additional validations for the registrations entity when using generic APIs to create or update registrations. A new dynamic logic of signature User Defined Validation (Registration) is introduced to support this functionality.

POL-16447

Repeatable Generation of Accounting Details

This enhancement introduces embedded logic that ensures that the same accounting details for a given grouping value and registration combination are not generated twice.

POL-16645

Additional Dynamic Fields on Policy Enrollment and Policy Enrollment Product

This enhancement increases the number of single-value non-time-valid dynamic fields that can be stored on the Policy Enrollment and Policy Enrollment Product entities.

POL-16724

AU: Additional Restrictions for Registrations Entity

This enhancement introduces Australian localization-specific restrictions from the registration entity, that is:

  • It is not allowed to update the following fields for registrations:

    • type

    • correlationId

    • amount

    • payDate

    • appliedPayDate

  • It is not allowed to delete the existing registrations.

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

POL-16447

Added

accountinggroupingdetails API

New read-only API

POL-16447

Modified

registrations/{id}/accountingdetails/undo IP

Added removal of accounting detail groupings

POL-16447

Modified

registrations API

Added accountingDetailGroupingList (display only)

POL-16447

Modified

registrations/{id}/accountingdetails/create IP

Added check if accounting detail grouping already exists: FIN-IP-REGI-007

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

37601039

POL-16642

Accounting detail message is getting generated for already handled records when incremental is not mentioned

Description:

Accounting detail message is getting generated for already handled records when incremental is not mentioned. Default value "true" for incremental is not getting considered for accounting detail message generation. Default value is not set.

Resolution:

Default value "true" is set for the attribute incremental if no value is provided. This resolved the issue

37558211

POL-16585

Null pointer exception at startup while constructing dynamic field mapping

Description:

At startup, a NullPointerException (NPE) was encountered while constructing dynamic field mappings due to the presence of a null object. Additionally, another NPE occurred during the invalidation of process cache.

Resolution:

Added null checks before performing operations on potentially null objects.

37201752

3-38101497351

POL-16136

Policy events for a policy are not all "cleared" when executing the policies invoice IP

Description:

Policy events of type 'R' and eventType 'I' were not getting cleared, on invoking invoice IP. The issue occurred because the deletion of policy events was dependent on a condition requiring the associated policy ID to be null.

Resolution:

The issue was resolved by modifying the condition to permit the policy ID to be either null or non-null. Additionally, the condition for the associated insurable entity ID was updated to target specific insurable entities linked to the corresponding policy.

37548208

POL-16559

PL/SQL function uses inefficient access path

Description:

The statistics were not associated with the function preventing optimizer from making better decisions when executing queries.

Resolution:

The statistics are associated for ohi_return_collection which allowed function to access efficient path and allows queries to run faster

37603667

3-39727327231

POL-16647

Incorrect matching of start dates for policy enrollment products with reverse order

Description:

In Policy IN IP, submitting multiple Policy Enrollment Product spans for the same enrollment product results in an error if the latest span appears first. However, arranging the spans from oldest to latest allows the policy to be submitted successfully.

Resolution:

Added a check to distinguish matching of policy enrollment products for automatically ending in patch operations from that in non-patch updates.

Issues that were backported in previous Release / Patch

No backports.