Release Notes for Oracle Health Insurance Claims Adjudication Patch 4.25.1.0.25

This document contains the release notes for Oracle Health Insurance Claims Adjudication Patch 4.25.1.0.25.

Version compatibility: Oracle Health Insurance Claims Adjudication 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
NXT-30732	Counter IP carry over date This enhancement introduces the capability to control the carry over settings when creating external consumption. Writing an external consumption request doesn’t have the product limit (override) in context so it will always use the setting on the limit. This enhancement introduces an additional parameter to the Adjudication Counter IP, carryOverDate, which can be used to override the carry over settings on the limit. Furthermore, this enhancement introduces the capability of creating new counter periods for plan year limits. This requires the presence of a start date in the request.	4.26.1.0.0
POL-19010	Extensible Waiver Reasons With this enhancement it is now possible to configure non time valid dynamic fields for Waiver Reasons

Summary

Patch

NXT-30732

Counter IP carry over date

This enhancement introduces the capability to control the carry over settings when creating external consumption. Writing an external consumption request doesn’t have the product limit (override) in context so it will always use the setting on the limit. This enhancement introduces an additional parameter to the Adjudication Counter IP, carryOverDate, which can be used to override the carry over settings on the limit. Furthermore, this enhancement introduces the capability of creating new counter periods for plan year limits. This requires the presence of a start date in the request.

4.26.1.0.0

POL-19010

Extensible Waiver Reasons

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

Configuration Properties

This section intentionally left blank.

Web Services

Ref Action Description

Ref	Action	Description
NXT-30732	Modified	Adjudication Counters Integration Point Added carryOverDate to the request
NXT-34861	Modified	Data Transfer IP Introduced an optional attribute `maxFileSize` in the request.

NXT-30732

Modified

Adjudication Counters Integration Point

Added carryOverDate to the request

NXT-34861

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

Ref	Action	Description
NXT-30732	Modified	Adjudication Limit Counters Added field 'carry over date' to write consumption section and its value is passed to the Create Consumption IP

Ref

Action

Description

NXT-30732

Modified

Adjudication Limit Counters

Added field 'carry over date' to write consumption section and its value is passed to the Create Consumption IP

Breaking Changes

Ref Action Description

Ref	Action	Description
NXT-34861	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.

NXT-34861

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
39810315	4-0003373758	NXT-34670	Coverage Regime Tranche Type updates is not working
Description:	When updating a Coverage Regime tranche type (for example, changing a tranche from Days to Units), the application displays a successful update confirmation, but the change is not persisted. The tranche continues to retain its original value type after the update.
Resolution:	Fix added to update Coverage Regime tranche type. The updated tranche type is now persisted correctly.
39943787		NXT-34861	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”
38511105	3-41886923721	NXT-32710	Writing incident data files in Object Storage fails intermittently
Description:	Writing an incident data file in Object Storage fails intermittently with NoSuchElementException
Resolution:	The intermittent issue that prevented incident data files from being written to Object Storage has been resolved. The fix improves the reliability of file creation and storage operations.
39790582	4-0003327505	NXT-34645	Corrected audit information for CTR status history.
Description:	CTR status-history records could display the Internal System User instead of the user recorded in the corresponding claim status history. Default insertion auditing replaced the original audit information.
Resolution:	Updated CTR generation to copy createdBy, creationDate, lastUpdatedBy, and lastUpdatedDate from the matching ClaimStatusHistory record, identified by status and timestamp. The CTR audit customizer preserves these values during insertion. Unmatched records use default auditing and generate a warning. Reversal auditing remains unchanged. No Header DYLO changes are required. The change applies to newly generated CTR records; existing records are not backfilled.
39807380	4-0003097859	NXT-34664	Product reload does not reflect updates to dynamic fields of product benefit specification limits
Description:	When a product benefit specification limit’s dynamic field is updated in Prod def and the product is rebuilt and reloaded to claims, the existing value is not overwritten correctly. Expected : The product benefit specification limit’s dynamic field should be overwritten correctly. Actual : The product benefit specification limit’s dynamic field is not overwritten.
Resolution:	When a product benefit specification limit’s dynamic field is updated in Prod def and the product is rebuilt and reloaded to claims, the existing value is overwritten correctly.
39872519	4-0003490677	NXT-34757	Show a Loading Indicator While Claim Line Messages Load
Description:	When a user selects More in the Claim Line Summary drawer, messages appear slowly or remain unavailable until the user reopens the drawer.
Resolution:	The Claim Line Summary drawer displays a loading indicator while it retrieves messages when a user first opens More. Messages load in the drawer without requiring the user to reopen it.
39920331		NXT-34812	Dynamic logic security checks fail for unresolved Groovy receiver types
Description:	Dynamic logic execution could fail with a NullPointerException when the receiver type of a Groovy method call could not be resolved during security rule evaluation.
Resolution:	Dynamic logic security predicates now safely handle unresolved receiver types, allowing valid dynamic logic execution to continue without a NullPointerException.
39926620		NXT-34835	Advanced Search LOV does not open for Last Validated By and Last Build By
Description:	The Advanced Search Operator LOV does not open for the Last Validated By and Last Built By fields.
Resolution:	The Operator LOV now opens for the Last Validated By and Last Built By fields, and Advanced Search works.
39878787		NXT-34763	Activities are purged via the DB purge but the dependent table - CLA_WRITE_PROD_BEN_SPECS is not purged
Description:	As part of the purge the activities table is getting purged but this table CLA_WRITE_PROD_BEN_SPECS is still having reference to the activities table. So, when the user goes to the import history page under the (operations → Data Exchanges →Inbound Exchanges →Inbound benefits/Products(HTTP) then user is being thrown error Because the activity is not present in the DB.
Resolution:	Resolved an issue where activity purge processing did not remove dependent product benefit specification records. This could cause errors when viewing inbound product/benefit import history after a purge. The purge process now removes these dependent records as well, ensuring import history remains accessible.
39828846	4-0003326305	NXT-34695	Reference sheet lines remain unavailable after creating flex codes removed through CMT
Description:	Reference sheet lines are not returned when they reference a flex code that was missing during an earlier lookup and is subsequently created. The missing lookup result remains cached, so the reference sheet lines remain unavailable until the affected application nodes are restarted.
Resolution:	When a previously missing flex code is created, its flex-code lookup is refreshed. Associated reference sheet lines are returned without restarting application nodes.
39715912	4-0001855450	NXT-34576	Combination checks should not be executed in the presence of a fatal message irrespective of the origin
Description:	Execution of combination checks is prevented if a fatal message of a certain origin is attached. This check on fatal message should be done irrespective of origin and combination checks must not be executed.
Resolution:	Previously, combination checks were skipped only when a fatal message had a SanityChecks or Enrollment origin. They are now skipped whenever a fatal message is present, regardless of its origin.

BugDB

Internal

Summary

39810315

4-0003373758

NXT-34670

Coverage Regime Tranche Type updates is not working

Description:

When updating a Coverage Regime tranche type (for example, changing a tranche from Days to Units), the application displays a successful update confirmation, but the change is not persisted. The tranche continues to retain its original value type after the update.

Resolution:

Fix added to update Coverage Regime tranche type. The updated tranche type is now persisted correctly.

39943787

NXT-34861

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”

38511105

3-41886923721

NXT-32710

Writing incident data files in Object Storage fails intermittently

Description:

Writing an incident data file in Object Storage fails intermittently with NoSuchElementException

Resolution:

The intermittent issue that prevented incident data files from being written to Object Storage has been resolved. The fix improves the reliability of file creation and storage operations.

39790582

4-0003327505

NXT-34645

Corrected audit information for CTR status history.

Description:

CTR status-history records could display the Internal System User instead of the user recorded in the corresponding claim status history. Default insertion auditing replaced the original audit information.

Resolution:

Updated CTR generation to copy createdBy, creationDate, lastUpdatedBy, and lastUpdatedDate from the matching ClaimStatusHistory record, identified by status and timestamp. The CTR audit customizer preserves these values during insertion. Unmatched records use default auditing and generate a warning. Reversal auditing remains unchanged. No Header DYLO changes are required. The change applies to newly generated CTR records; existing records are not backfilled.

39807380

4-0003097859

NXT-34664

Product reload does not reflect updates to dynamic fields of product benefit specification limits

Description:

When a product benefit specification limit’s dynamic field is updated in Prod def and the product is rebuilt and reloaded to claims, the existing value is not overwritten correctly. Expected : The product benefit specification limit’s dynamic field should be overwritten correctly. Actual : The product benefit specification limit’s dynamic field is not overwritten.

Resolution:

When a product benefit specification limit’s dynamic field is updated in Prod def and the product is rebuilt and reloaded to claims, the existing value is overwritten correctly.

39872519

4-0003490677

NXT-34757

Show a Loading Indicator While Claim Line Messages Load

Description:

When a user selects More in the Claim Line Summary drawer, messages appear slowly or remain unavailable until the user reopens the drawer.

Resolution:

The Claim Line Summary drawer displays a loading indicator while it retrieves messages when a user first opens More. Messages load in the drawer without requiring the user to reopen it.

39920331

NXT-34812

Dynamic logic security checks fail for unresolved Groovy receiver types

Description:

Dynamic logic execution could fail with a NullPointerException when the receiver type of a Groovy method call could not be resolved during security rule evaluation.

Resolution:

Dynamic logic security predicates now safely handle unresolved receiver types, allowing valid dynamic logic execution to continue without a NullPointerException.

39926620

NXT-34835

Advanced Search LOV does not open for Last Validated By and Last Build By

Description:

The Advanced Search Operator LOV does not open for the Last Validated By and Last Built By fields.

Resolution:

The Operator LOV now opens for the Last Validated By and Last Built By fields, and Advanced Search works.

39878787

NXT-34763

Activities are purged via the DB purge but the dependent table - CLA_WRITE_PROD_BEN_SPECS is not purged

Description:

As part of the purge the activities table is getting purged but this table CLA_WRITE_PROD_BEN_SPECS is still having reference to the activities table.

So, when the user goes to the import history page under the (operations → Data Exchanges →Inbound Exchanges →Inbound benefits/Products(HTTP) then user is being thrown error Because the activity is not present in the DB.

Resolution:

Resolved an issue where activity purge processing did not remove dependent product benefit specification records. This could cause errors when viewing inbound product/benefit import history after a purge. The purge process now removes these dependent records as well, ensuring import history remains accessible.

39828846

4-0003326305

NXT-34695

Reference sheet lines remain unavailable after creating flex codes removed through CMT

Description:

Reference sheet lines are not returned when they reference a flex code that was missing during an earlier lookup and is subsequently created. The missing lookup result remains cached, so the reference sheet lines remain unavailable until the affected application nodes are restarted.

Resolution:

When a previously missing flex code is created, its flex-code lookup is refreshed. Associated reference sheet lines are returned without restarting application nodes.

39715912

4-0001855450

NXT-34576

Combination checks should not be executed in the presence of a fatal message irrespective of the origin

Description:

Execution of combination checks is prevented if a fatal message of a certain origin is attached. This check on fatal message should be done irrespective of origin and combination checks must not be executed.

Resolution:

Previously, combination checks were skipped only when a fatal message had a SanityChecks or Enrollment origin. They are now skipped whenever a fatal message is present, regardless of its origin.

Issues that were backported in previous Release / Patch

No backports.