Release Notes for Oracle Health Insurance Claims Adjudication Patch 4.25.1.0.24

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

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.
As per the Service Description, you are obligated to request a service upgrade within 90 days of this release being generally available (GA). In line with the Oracle Cloud Services Pillar document, Section 4.2.2 End of Life, this release will be EOL in 12 months.

Enhancements

No enhancements.

Configuration Properties

This section intentionally left blank.

Web Services

This section intentionally left blank.

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.

Access Restrictions

This section intentionally left blank.

Bug Fixes

BugDB SR Internal Summary

39681053

4-0002951167

NXT-34519

End benefits and End Pricing should execute on Manual Adjudication

Description:

Submitting a Claim from Manual Adjudication should run the configured end-benefits and end-pricing derivation rules for claim and claim line

Resolution:

Claims submitted from Manual Adjudication will now complete the full acceptance processing before finalization which ensure configured end-benefits and end-pricing derivation rules

39744287

4-0003256595

NXT-34607

Claim Event Rules of level large claim are not executed

Description:

Claim event rules are not executing when a large claim has an event rule and when applicable to sub claims is null then event rules are not executing properly.

Resolution:

When Large claim has an event then large claim event should be executed, if applicable to sub claims is true then only sub claims events should be executed

39834074

4-0003422821

NXT-34703

Cleared dynamic fields could still return the previous value during the same processing flow.

Description:

When a dynamic field was cleared by assigning null, the value was removed, but a cached copy could still be used for later reads in the same flow. As a result, the dynamic field could appear to still contain its old value immediately after being cleared. This could affect dynamic fields, including flex-code dynamic fields, across single-value time valid, multi-value non-time-valid & time-valid, configurations.

Resolution:

The cache is now invalidated when a dynamic field is cleared. After assigning null, later reads correctly and returns no value instead of the previously cached value.

39828258

NXT-33244

Tooltip missing in collapsible icon for table More section

Description:

Tooltip missing for icons on claims page for table More section

Resolution:

Tooltips have been added to the relevant icons to improve usability and provide clear context for each action

39684793

4-0003087849

NXT-34524

Large Claim Submit link not shown for In Process large claim when completed LARGE_CLAIMS_SUBMIT activity is purged

Description:

The large claim submit link is not available for an IN PROCESS large claim when the latest completed LARGE_CLAIMS_SUBMIT activity is no longer present in ACT_ACTIVITIES / CLA_CLAIM_ACTIVITIES.

Current link visibility logic appears to depend on finding the latest LARGE_CLAIMS_SUBMIT activity and checking that its status is CO. Since activity retention is configured as 60 days, completed activity rows can be purged. After purge, an otherwise submittable IN PROCESS large claim has no submit link in UI.

This makes submit-link availability depend on purgeable activity history rather than the current functional state of the large claim/subclaims.

Resolution:

Users can now submit an IN PROCESS large claim again when the previous completed large claim submit activity is no longer available.

38763155

NXT-33200

Claim Task Performance reporting view returns incorrect time intervals.

Description:

The Claim Task Performance reporting view could show incorrect waiting and processing durations when an interval contained full minutes, hours, or days. Only the seconds portion of the interval is included.

Resolution:

The duration calculations now include days, hours, minutes, and seconds, providing the complete interval in milliseconds.

Issues that were backported in previous Release / Patch

No backports.