Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.24.1.0.8

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

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-16443

Ability to prevent a policy from being picked up from premium calculation.

This enhancement provides the ability to prevent a policy from being picked up for premium calculation. Ability to add or remove premium hold on a policy from the user interface.

Documentation Links:
Developer Guide - Run Calculation and Produce Invoice for a Group Account
Developer Guide - Policy In Integration Point
Developer Guide - Run Calculation and Select in Set for a Group Account
Operations Guide - Calculate Premium
Operations Guide - Attached Policy Data Data Model

POL-16484

Accounting details per financial transaction set

This enhancement allows accounting details, as generated in the financial message, to be persisted. It also enables the inclusion or exclusion of the subject (policy/claim) and reversal indicator as bulking criteria when creating accounting details.

Note: For financial transactions created prior to this feature, the reversal indicator cannot be excluded as part of the bulking criteria.

Documentation Links:
Developer Guide - Run Calculation and Produce Sample Invoice for a Policy
Developer Guide - Run Calculation and Produce Invoice for a Group Account
Developer Guide - Predefined Methods
Developer Guide - Functions
Developer Guide - Cancel Policy and Produce Invoice
Operations Guide - Generate Accounting Detail Message
Operations Guide - Generate Financial Message

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

Ref Action Description

POL-16484

Removed

ohi.financialmessage.includeaccounting

This system property (to indicate if account details should be part of fin message or not) has been removed.

Web Services

Ref Action Description

POL-16484

Modified

financialtransactions API

Object has been made auditable

POL-16484

Modified

financialtransactiondetails API

Object has been made auditable

POL-16484

Modified

financialtransactionprocessdata API

Attribute accountingDetailGeneratedDateTime has been removed

POL-16484

Modified

basefinancialobjects API

Object has been made auditable

POL-16484

Modified

accountingdetails API

Reference to financial transaction has been replaced by financialMessageId. Attribute stampId is added. Reversal indicator has bee made optional

POL-16484

Modified

Cancel Policy and Produce Invoice IP

New parameters added in the request: Create Accounting Detail to Persist Dynamic Logic Function

Include Subject for Grouping Accounting?

Include Reversal Indicator In Accounting Grouping?

POL-16484

Modified

Run Calculation and Produce Invoice for a Policy

New parameters added in the request: Create Accounting Detail to Persist Dynamic Logic Function

Include Subject for Grouping Accounting?

Include Reversal Indicator In Accounting Grouping?

POL-16484

Removed

Long running operation for creating accounting details for financial transaction

Has been replaced by functionality in Generate financial message.

POL-16484

Removed

financialtransactions/{id}/accountingdetails/undo IP

Will be replaced by functionality in unsend financial message

Data Conversion

This section intentionally left blank.

Dynamic Logic

This section intentionally left blank.

UI Changes

This section intentionally left blank.

Breaking Changes

Ref Action Description

POL-16443

Modified

Policy In Integration Point

Added new attribute premium Hold in the request payload for attached policy data.

POL-16443

Modified

Policy Update Request Integration Point

Added new attribute premium Hold in the request payload for attached policy data.

POL-16443

Modified

Attached Data Integration Point

Added new attribute premiumHold in the request payload

POL-16443

Modified

Policy IN Patch Integration Point

Added new attribute Premium Hold in the request payload for attached policy data.

Bug Fixes

BugDB SR Internal Summary

37685393

POL-16762

Issue with premium calculation for 3-Year contracted policies involving leap years

Description:

  1. A validation error (POL-FL-CAPR-001) occurred during the execution of a Quote IP for a policy with a contract period exceeding one year, which included a leap year and started mid-year.

  2. The premium calculation was incorrect for policies with a contract period of over one year, including a leap year, and a policy calculation period length of 1.

  3. The premium calculation was incorrect for policies with a contract period of over one year, including a leap year, and a policy calculation period length greater than 1.

Resolution:

  1. The premium calculation is now accurate for policies with a contract period longer than one year, starting in the middle of the year and including a leap year.

  2. A new Business Rule (BR) - POL-CLST-004 has been introduced to prevent the use of a policy calculation period length greater than one when the policy calculation period unit of measurement (UoM) is 'Year.'

36992173

3-37787970011

POL-15741

NullPointerException is thrown when running sample calculation for policies having surcharge of type amount

Description:

NullPointerException is thrown on screen on running sample calculation for policies having surcharge of type amount and policy enrollment product ending before the PCP (yearly PCP)

Resolution:

The exception was handled and the surcharge was derived based on the policy enrollment product duration.

37749682

3-39289517481

POL-16822

Getting row lock contention when running sampleinvoice IP

Description:

sampleinvoice IP taking more than 60s to return the response. The Api call internally invokes a plsql procedure that puts record under lock for the current transaction. When sampleinvoice is triggered for same policy ID, response time of more than 60s is observed.

Resolution:

A NOWAIT clause was incorporated into the PL/SQL procedure to immediately terminate any concurrent process waiting for the lock to be released. This fix optimizes the response time of the sampleinvoice IP call

37496451

POL-16478

Null pointer Exception while fetching data from Non-Entity cache

Description:

When application in critical memory state, memory protector kicks in which leads creates possibility of L2 cache corruption. When trying to fetch DynamicFieldUsage from a corrupted cache, getting null values.

Resolution:

To prevent the L2 cache from returning stale or corrupted data, L2 cache for DynamicFieldUsage is cleared before querying it during cache rebuild.

37576319

3-33766349291

POL-16613

Registrations are not re-applied

Description:

Policy calculation periods are deleted based on look back date in order to (re-)apply registrations. This is to trigger recalculation. First the initial look back date is determined to select applicable registrations. Then existing registrations are unzipped (applied registration status is set to N(ew)). But then policy calculation periods are deleted based on the initial look back date, not the look back date that is based on the 'unzipped ' registrations. This is causing the registrations not to be re-applied.

This bug is present apply registrations activity only, not the integration points.

Scenario to reproduce: 1) Create Policy with a Policy Collection Setting starting on 01/01 and Span Reference Date 15/01; 2) Create a single enrollment and a premium of $10 a day; 3) Create (and apply) Registration accounting for the first period ($142) and a Pay Date of 01/01; 4) Calculate Premium with Calculation Input Date 14/01 5) Create (and apply) Registration accounting for the first period ($138) and a Pay Date of 15/01; 6) Create (and apply) Registration accounting for the first period ($142) and a Pay Date of 14/01;

Expected: Look Back Date should be set to 01/01 and all registrations need to be re-applied.

Instead: look back date is not updated.

Resolution:

After unzip of registrations, the look back date is recalculated first before policy calculation periods are deleted, so the registrations are re-applied.

37749552

POL-16818

Activities are not purged when auto-purge job is enabled for Policies.

Description:

Following errors are being experienced in policies environment during the usage of Auto purge.

Error starting at line : 25 in command - BEGIN ohi_auto_purge_pkg.purge_all; END; Error report - ORA-20000: Failed jobs detected, check the table user_scheduler_job_run_details for details ORA-06512: at "OHI_POLICIES_OWNER.OHI_PARALLEL_JOBS_PKG", line 114

Cause for the error -

ORA-02292: integrity constraint (OHI_POLICIES_OWNER.FIN$ACTIVITY_BUCKET_FK1) violated - child record found ORA-06512: at "OHI_POLICIES_OWNER.OHI_ACT_PURGE_PKG", line 42 ORA-06512: at line 1

Resolution:

Ordering the PL/SQL script to delete child records before parent records resolved the issue.

37779138

POL-16874

"Usages" header cannot be translated to other languages in Usages page

Description:

It is not possible to translate the "Usages" header in usages page in any other languages because boilerplate is not available for that header

Resolution:

Translations are added to "Usages" header in Usages page

37743381

3-39391191701

POL-16803

Default value of startdate of time valid flex code fields mentioned in the floorplan is not applied in UI

Description:

The start date in time-valid flex code fields and list resource is not defaulting to the system date as expected when a trigger condition is applied to set the value.

Resolution:

Now, the start date field defaults to the system date when a trigger condition is applied to set the value for time-valid flex code fields.

37630681

POL-16690

Unsaved Changes Submit pop-up message appears unnecessarily when the user switches to another tab in Group Clients page

Description:

Warning message on the Group Clients page to Submit the group client before moving away from the page is not working as expected. It appears even when user tries to add child data and save

Resolution:

The warning message on group client page is fixed now and gives clear message to user to submit the group client while navigating away from the page and doesn’t appear on Save action

Issues that were backported in previous Release / Patch

No backports.