Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.25.1.0.23

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

Version compatibility: Oracle Health Insurance Enterprise Policy Administration Release 4.25.1.x is only compatible with other Oracle Health Insurance applications release version 4.25.1.x unless explicitly stated otherwise.

Enhancements

ID	Summary	Patch
POL-19010	Extensible Waiver Reasons With this enhancement it is now possible to configure non time valid dynamic fields for Waiver Reasons

Summary

Patch

POL-19010

Extensible Waiver Reasons

With this enhancement it is now possible to configure non time valid dynamic fields for Waiver Reasons

Upgrade Steps for Installation

To perform the upgrade, perform the following steps:

Perform any pre-upgrade steps.
Stop all the managed nodes running the existing version of the application.
Perform any pre-undeploy steps.
Undeploy the existing version of the application.
Back up the database.
Perform any post-undeploy steps.
Unpack the release bundle into a directory that we refer to as OHI_ROOT from now on.
Change Installation Configuration: In <OHI_ROOT>/util/install, make a copy of ohi_install.cfg.template and name it ohi_install.cfg.
Edit ohi_install.cfg to contain your specific database connection data and other configuration settings. The settings are explained in the file itself.
Make sure NO connections are present to the database using the OHI_xxx_USER account (where xxx is the abbreviation of the application)
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 .
Make the required changes to the ohi properties file
Perform any post-upgrade steps
Start WebLogic application server
Deploy the Application
Perform any post-deploy steps

Configuration Properties

This section intentionally left blank.

Web Services

Ref Action Description

Ref	Action	Description
POL-19122	Modified	Data Transfer IP Introduced an optional attribute `maxFileSize` in the request.

POL-19122

Modified

Data Transfer IP

Introduced an optional attribute maxFileSize in the request.

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

Ref	Action	Description
POL-19122	Modified	Data Transfer IP If an integration relies on the previous 200 MB export file limit, it must explicitly provide `maxFileSize` in the data transfer IP request. The value is expressed in MB ( min 10 MB and max 1 GB). Larger values can affect export performance.

POL-19122

Modified

Data Transfer IP

If an integration relies on the previous 200 MB export file limit, it must explicitly provide maxFileSize in the data transfer IP request. The value is expressed in MB ( min 10 MB and max 1 GB). Larger values can affect export performance.

Access Restrictions

This section intentionally left blank.

Bug Fixes

BugDB	SR	Internal	Summary
37924918		POL-17141	Data File Sets IP does not return the message text in the response for error codes DAT-IP-DAFI-013 and DAT-IP-DAFI-014
Description:	When encountering error codes DAT-IP-DAFI-013 and DAT-IP-DAFI-014, the associated error messages are not being displayed in the response. The expected behavior is that the error messages corresponding to these error codes should be returned in the response, providing more context and information about the error
Resolution:	When a data file set cannot be downloaded because its ZIP file is quarantined or still undergoing virus scanning, the application now displays a clear message explaining the condition and next action.
39943794		POL-19122	Improved performance for large data transfer exports with configurable file sizing
Description:	Data transfer IP uses a 200 MB file size value to DBMS_CLOUD.EXPORT_DATA, which could severely degrade performance for large exports.
Resolution:	Data transfer IP supports the optional maxFileSize attribute for CSV, JSON, and XML exports in SaaS deployments. This attribute is not supported for on-premises deployments. When maxFileSize is not specified, exports use the default file size of 10 MB. The application displays OHI-IP-ORV-011 when maxFileSize is outside the supported range: “The value of maxFileSize must be between 10 MB and 1024 MB” It displays OHI-IP-ORV-012 when maxFileSize is specified for PARQUET exports: “maxFileSize is not allowed for dataTransferFormat PARQUET”
39610347	4-0002666364	POL-18834	Incomplete premium calculation for invoice catch-up periods.
Description:	Premium is not calculated for the full duration of an invoice catch-up period when the period spans multiple months.
Resolution:	Policy calculation period generation includes all catch-up periods for invoice and sample invoice operations. This supports premium calculation for the full catch-up duration before the regular collection cycle begins.
40011945	4-0003751096	POL-19211	Activity processing supports financial transaction identifiers of up to 19 digits.
Description:	Activity processing could fail when a financial transaction identifier exceeded the 14-digit limit used for related activity records. This could interrupt workflows such as daily billing.
Resolution:	Related activity identifiers now support up to 19 digits, allowing activity processing to continue when larger transaction identifiers are used.
39286257	4-0002579687	POL-18670	Registrations are not re-applied when the pay date of the registrations is before the effective date of the earliest mutation.
Description:	When Apply Registrations was executed, a policy calculation period was removed because its end date was after the look-back date. However, the related applied registration was not unzipped because the registration pay date was before the look-back date. As a result, the policy calculation period was recalculated and invoiced again while the original registration remained applied.
Resolution:	The Apply Registrations logic now also considers the pay dates of affected policy calculation periods when determining from which date registrations must be re-applied. Applied payment registrations with a pay date before the mutation effective date are now correctly unzipped and re-applied when they are linked to affected policy calculation periods. This fix was applied for policy activities, group account activities, and direct process-and-apply registrations processing.
39233319	4-0002548324	POL-18625	Automatic recovery can fail to identify the latest errored task
Description:	When an earlier task has a higher identifier than a more recently created task, automatic recovery can fail to identify and recover the latest errored task.
Resolution:	Retrieval of errored tasks is optimized and based on latest creation date.
39939859	4-0003388831	POL-19118	Calculate Premium skips explicit Group Account when Ignore Changed Group Clients is Yes
Description:	When Calculate Premium is run with both Group Client and Group Account, and Ignore Changed Group Clients is set to Yes, the system may complete without creating child activities or showing premium calculation errors. This occurs even when the Group Account belongs to an approved Group Client. The same policy is processed correctly when the flag is No or only Group Client is supplied.
Resolution:	Updated the Group Account selection logic so it correctly recognizes valid Group Accounts and creates the required Group Account and Policy activities when Ignore Changed Group Clients is Yes.
40052081		POL-19251	Add index on the date of birth column of relations table
Description:	Customer dynamic logic may contain queries that search for person records in the relations tables using date of birth along with other attributes. Due to the absence of an appropriate index, these queries can be expensive and may result in performance degradation.
Resolution:	Add the index on the date of birth column to improve query performance.

BugDB

Internal

Summary

37924918

POL-17141

Data File Sets IP does not return the message text in the response for error codes DAT-IP-DAFI-013 and DAT-IP-DAFI-014

Description:

When encountering error codes DAT-IP-DAFI-013 and DAT-IP-DAFI-014, the associated error messages are not being displayed in the response. The expected behavior is that the error messages corresponding to these error codes should be returned in the response, providing more context and information about the error

Resolution:

When a data file set cannot be downloaded because its ZIP file is quarantined or still undergoing virus scanning, the application now displays a clear message explaining the condition and next action.

39943794

POL-19122

Improved performance for large data transfer exports with configurable file sizing

Description:

Data transfer IP uses a 200 MB file size value to DBMS_CLOUD.EXPORT_DATA, which could severely degrade performance for large exports.

Resolution:

Data transfer IP supports the optional maxFileSize attribute for CSV, JSON, and XML exports in SaaS deployments. This attribute is not supported for on-premises deployments. When maxFileSize is not specified, exports use the default file size of 10 MB.

The application displays OHI-IP-ORV-011 when maxFileSize is outside the supported range: “The value of maxFileSize must be between 10 MB and 1024 MB”

It displays OHI-IP-ORV-012 when maxFileSize is specified for PARQUET exports: “maxFileSize is not allowed for dataTransferFormat PARQUET”

39610347

4-0002666364

POL-18834

Incomplete premium calculation for invoice catch-up periods.

Description:

Premium is not calculated for the full duration of an invoice catch-up period when the period spans multiple months.

Resolution:

Policy calculation period generation includes all catch-up periods for invoice and sample invoice operations. This supports premium calculation for the full catch-up duration before the regular collection cycle begins.

40011945

4-0003751096

POL-19211

Activity processing supports financial transaction identifiers of up to 19 digits.

Description:

Activity processing could fail when a financial transaction identifier exceeded the 14-digit limit used for related activity records. This could interrupt workflows such as daily billing.

Resolution:

Related activity identifiers now support up to 19 digits, allowing activity processing to continue when larger transaction identifiers are used.

39286257

4-0002579687

POL-18670

Registrations are not re-applied when the pay date of the registrations is before the effective date of the earliest mutation.

Description:

When Apply Registrations was executed, a policy calculation period was removed because its end date was after the look-back date. However, the related applied registration was not unzipped because the registration pay date was before the look-back date. As a result, the policy calculation period was recalculated and invoiced again while the original registration remained applied.

Resolution:

The Apply Registrations logic now also considers the pay dates of affected policy calculation periods when determining from which date registrations must be re-applied. Applied payment registrations with a pay date before the mutation effective date are now correctly unzipped and re-applied when they are linked to affected policy calculation periods. This fix was applied for policy activities, group account activities, and direct process-and-apply registrations processing.

39233319

4-0002548324

POL-18625

Automatic recovery can fail to identify the latest errored task

Description:

When an earlier task has a higher identifier than a more recently created task, automatic recovery can fail to identify and recover the latest errored task.

Resolution:

Retrieval of errored tasks is optimized and based on latest creation date.

39939859

4-0003388831

POL-19118

Calculate Premium skips explicit Group Account when Ignore Changed Group Clients is Yes

Description:

When Calculate Premium is run with both Group Client and Group Account, and Ignore Changed Group Clients is set to Yes, the system may complete without creating child activities or showing premium calculation errors. This occurs even when the Group Account belongs to an approved Group Client. The same policy is processed correctly when the flag is No or only Group Client is supplied.

Resolution:

Updated the Group Account selection logic so it correctly recognizes valid Group Accounts and creates the required Group Account and Policy activities when Ignore Changed Group Clients is Yes.

40052081

POL-19251

Add index on the date of birth column of relations table

Description:

Customer dynamic logic may contain queries that search for person records in the relations tables using date of birth along with other attributes. Due to the absence of an appropriate index, these queries can be expensive and may result in performance degradation.

Resolution:

Add the index on the date of birth column to improve query performance.

Issues that were backported in previous Release / Patch

No backports.