Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.24.1.0.2

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

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

OIG-3474

Improve error messages on timeout

When a timeout occurs, the error message will clearly state which timeout setting resulted in the timeout.

We have had cases of long-running dynamic logic producing a timeout. It was not clear whether this was due to:

  • A general dynamic logic timeout setting

  • A setting specific to this dynamic logic

  • A timeout for the exchange (step)

  • An HTTP timeout

  • Or another reason

In this enhancement, we have addressed the following timeout errors:

  • ohi.ws.client.connectiontimeout

  • ohi.ws.client.readtimeout

  • ohi.dynamiclogic.timeout

  • ohi.dynamiclogic.timeout.{0}

  • Exchange timeout

  • Exchange step timeout

An example error message that will be shown in the error log in case of a dynamic logic execution timeout scenario is:

"Timeout error occurred at PayloadTransformer for step RNI_TRAFO_STEP of integration/subflow ID 400345758 due to execution timed out after 300 seconds. Start time: Thu Jul 18 21:14:56 IST 2024. You can configure this timeout limit by setting the property [ohi.dynamiclogic.timeout=100]."

POL-15307

Financial: Ability to send Accounting Details seperately

OHI application sends out accounting details along with the financial message. Also, the granularity of grouping of account details is bounded by invoice grouping. That is details within an invoice can only be grouped. This posses challenges for customers who would like accounting to be done at different level , compared to invoice. Example Invoice is per member, but accounting across member for a product

With this enhancement it will be possible to 1) send out account details as part of separate batch and 2) have grouping logic which is not bounded by financial message grouping or invoice grouping.

4.24.1.0.1

POL-15369

Create / Update registration records to handle payments

This enhancement allows users to register policy binder payments in OHI as "Generic" Payments. It allows users to manage binder payment and also generate accounting details for them.

4.24.1.0.1

Additional Upgrade Steps

Pre-Upgrade Phase

If registrations of type G(eneric) are present, update the type to another: like P(ayment) or B(ill) using either API or the following SQL statement with user OHI_POLICIES_OWNER: update fin_registrations set type = 'P' where type = 'G'

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

Added

ohi.financialmessage.includeaccounting

Should accounting details be included when financial message is generated? (default value true)

Web Services

Ref Action Description

POL-15307

Added

financialtransactions/{id}/accountingdetails/undo IP

New IP to make accounting details for a specific transaction void

POL-15307

Added

accountingdetails API

Read-only API to query on accounting details (new entity).

POL-15307

Modified

financialtransactionprocessdata API

Added attribute accountingDetailsGeneratedDateTime

POL-15369

Added

registrations/{id}/accountingdetails/create

New IP to create accounting details for a specific registration

POL-15369

Added

registrations/{id}/accountingdetails/undo

New IP to undo accounting details for a specific registration

POL-15369

Added

Create Accounting Details from Registrations IP

New long running operation to create accounting details for the selected registrations

POL-15369

Modified

registrations API

New type added: "G"(eneric) and automatic generation of code. And added attributes Currency and Grouping.

GET, PUT, POST, PATCH, DELETE is enabled on the registration entity

AU specific registration type/code types are protected by BR’s.

Data Conversion

This section intentionally left blank.

Dynamic Logic

Ref Action Description

POL-15369

Added

UpdateRegistration

New pre-defined method to update a registration of type "G"(eneric)

POL-15369

Added

AddRegistration

New pre-defined method to add a registration of type "G"(eneric)

POL-15369

Added

Create accounting detail with dual for registration

New signature for creating accountingDetail and accountingDetailDual for a specific registration

POL-15369

Added

Registration Code Generation

New signature for automatic generation of registration.code

POL-15369

Added

Create Accounting Detail (Registrations)

New signature for creation of accounting detail for registration

UI Changes

Ref Action Description

POL-15307

Added

FI0027 Accounting Details

Added Accounting Details page as object navigation link in policies page

POL-15307

Modified

FI0014 Registrations

Create, Update, Delete support is added in Registrations page

POL-15307

Modified

FI0027 Accounting Details

Custom UI properties i.e. 'segmentsJET' and 'accountingAttributesJET' are introduced for the accounting details on policy page

Breaking Changes

This section intentionally left blank.

Bug Fixes

BugDB SR Internal Summary

37303033

POL-16287

Outbound exchange: values are not getting updated after building a data set

Description:

When trying to build a data set, exactVersionMatch and disableDeleteByOmission are not getting updated. Also If we try to update the inclusionDate by passing empty value it is not getting updated.

Resolution:

The attributes exactVersionMatch and disableDeleteByOmission are now being correctly applied during dataset creation. Also updates to inclusionDate are handled properly, allowing modifications even when an empty value is provided.

37196579

POL-16117

Restrictions on amount, type etc. from the generic registations resource API not properly removed

Description:

For POL-15396: it was decided to lift restrictions on amount, type etc. from the generic registations resource API, as a new business rule was introduced for AU-implementations: FIN-REGI-002. But the restrictions on the properties are not removed properly.

Resolution:

Removed all retstrictions on generic registrations API.

37147501

POL-16011

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.

37157973

3-38290202691

POL-16045

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.

37136049

3-36700304951

POL-15998

New nodes in the cluster remain unresponsive when added during ongoing application activities

Description:

Node startup fails due to a NullPointerException caused by premature invocation of ServiceLocator while loading ReferenceSheets objects

Resolution:

The NullPointerException was fixed by replacing ServiceLocator with required objects during node startup

37193145

3-38423134371

POL-16102

Access restriction grant applied on PO0001 Policies JET but allows to cancel policy

Description:

When a access restricted role is created for PO0001 Policies JET, RM0012 Persons JET and PO0130 Member JET with only 'retrieve' checked, it’s still possible to cancel a policy or edit a person

Resolution:

It is not possible to cancel or edit a person with readonly access

37153250

POL-16028

Title is not coming in summary and detailed view of list view Tabs

Description:

Title property is not enhanced for the dynamic record when added as tab result. As well as in the title property of the corresponding detail page

Resolution:

Title property is now displayed for dynamic record when added as tab result

37342904

3-37391765051

POL-15698

CMT: inclusionDate, exactVersionMatch, disableDeleteByOmission are not applied when building CMT sets

Description:

When building any CMT sets, the values in the dialog are not being applied

Resolution:

The parameters inclusionDate, exactVersionMatch, disableDeleteByOmission are sent in payload if values are entered while building CMT sets

37200392

3-38363602931

POL-16132

Policies parameter values sequence incorrect when not using the toggle

Description:

Policies parameter values sequence incorrect when not using the toggle to expand view format

Resolution:

Policies parameter values are being sorted on display sequence and code in expanded and old view

37215130

3-38065813361

POL-16159

Calculation result lines are not displayed under each calculation period

Description:

Calculation result lines are not displayed under each calculation period. Calculation result (including all the calculation result lines under it) per calculation period is visible under the row displaying the member name (used for looking up products to be used for premium calculation)

Resolution:

Calculation result lines are getting displayed under each calculation period

Issues that were backported in previous Release / Patch

No backports.