Release Notes for Oracle Health Insurance Claims Adjudication Patch 4.25.1.0.16
This document contains the release notes for Oracle Health Insurance Claims Adjudication Patch 4.25.1.0.16.
| 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
| ID | Summary | Patch |
|---|---|---|
NXT-33697 |
UI: European date/number formatting for English Language With this enhancement, support is added to keep the UI in English language while using European date and number formats (e.g., dd/MM/yyyy and 1.234.567,00), when user sets 'en‑EU' in the existing ohi.ui.default.locale system property. If the property is not set, date and number formats continue to follow the user’s selected locale (language + region), with no change in behaviour. |
4.26.1.0.0 |
Bug Fixes
| BugDB | SR | Internal | Summary |
|---|---|---|---|
39112860 |
NXT-33870 |
Access Mapping: "userviewpreferences API" is missing from "CO0019, Login Access JET" |
|
Description: |
Add "userviewpreferences API" to "CO0019, Login Access" since it is required for pages where table preferences can be saved |
||
Resolution: |
Added "userviewpreferences API" to "CO0019, Login Access JET" in function api access mapping seed data |
||
39100039 |
NXT-33860 |
Widgets are returning no results, and the page displays an error message stating: "No applicable floorplan found" |
|
Description: |
When a page contains multiple widgets with the same resource, each with distinct List of Values (LOVs), some widgets occasionally fail to load, resulting in "floorplan not found" errors for certain LOVs. |
||
Resolution: |
Fix added to resolve widget results not loading and the floorplan-related error shown in the UI. |
||
38999356 |
4-0002125064 |
NXT-33673 |
Resources cannot be searched when code starts with %255% |
Description: |
POST search API requests were failing with an IntrusionDetectionException when the query contained specific special patterns. These legitimate input param were incorrectly identified as potential intrusion attempts, resulting in search failures. |
||
Resolution: |
Enhanced the intrusion detection mechanism to correctly handle search query parameters, preventing legitimate requests from being incorrectly flagged. |
||
39154506 |
NXT-33942 |
Decimal values were incorrectly converted to whole numbers in Flex Code fields even when the field definition supported decimals |
|
Description: |
When a field definition allowed decimal values, the corresponding Flex Code field incorrectly converted entered decimal numbers into whole numbers. This resulted in loss of precision and inconsistent behavior between field definitions and Flex Code values. |
||
Resolution: |
This issue was resolved by updating the Flex Code handling logic to correctly preserve decimal values when the associated field definition supports decimals. The fix ensures that numeric inputs are no longer truncated or rounded to whole numbers, and that validation and data processing are aligned with the field configuration to maintain decimal precision |
||
39091870 |
NXT-33837 |
User not able the switch to next row when enter key is pressed in a table row.. |
|
Description: |
User is unable to switch to the next available row in edit mode when the Enter key is pressed while editing a table row. |
||
Resolution: |
A fix has been implemented to ensure that pressing the Enter key moves focus to the next available row and switches it into edit mode. |
||
39007701 |
NXT-33685 |
Operational reports should allow users to enable usage of full view to display data grid |
|
Description: |
In operational report page data-grid is not utilizing the full available space on the page, resulting in white space below the data grid. |
||
Resolution: |
The pageSize configuration has been removed, as the data grid will now display at full height based on the available screen height. |
||
39014223 |
NXT-33711 |
After the ADB patch, the extract activity failed with |
|
Description: |
The extract activity failed with ORA‑00028 (“your session has been killed”) following the ADB patch. During the patching process, DBMS_CLOUD was temporarily invalidated. Since OHI_OBJECTSTORAGE_PKG depends on DBMS_CLOUD, some existing application/JDBC sessions continued to use a cached (stale) package state. As a result, the scheduled exchanges/extract activities referenced the stale package state, and the affected sessions were terminated, causing the activity failures. |
||
Resolution: |
ORA‑00028 is now handled by the application, and the affected activities are automatically re-tried when this error is encountered. |
||
39004630 |
NXT-33682 |
Episodes Page: Inline edit - changes show up only after refresh |
|
Description: |
In Episodes page, inline edit row level save any of the fields(LOV or text fields) in more section or table is not working. Values are not shown after save, but displayed after refresh or searching again |
||
Resolution: |
Values are shown immediately after save using Inline Edit action |
||
38548182 |
NXT-32793 |
Dynamic fields with conditional display are not displayed on click of attach and next button at claim line level |
|
Description: |
Dynamic fields configured with conditional display were not appearing at the claim line level after clicking the Attach and Next action |
||
Resolution: |
Dynamic fields now display correctly based on configured conditions after clicking on attach and next at the claim line level. |
||
39179792 |
NXT-33981 |
Entering 0% for quantifier in Pricing Worksheets incorrectly saves as null |
|
Description: |
When users entered a quantifier value 0% in Pricing Worksheets, JET UI treated 0 as “empty” and overwrote it with an empty/null value. the quantifier appeared blank in DPPC/PPC views. |
||
Resolution: |
Updated quantifier handling to treat 0 as a valid value instead of empty, ensuring 0 is preserved in UI state and API payloads. |
||
39069394 |
NXT-33792 |
Data exceeding the 50-record threshold is not displaying in claims history. |
|
Description: |
In Claims History, records beyond the 50-count limit are not appearing. |
||
Resolution: |
In Claims History, it is possible to see upto 200 history records |
||
38508719 |
NXT-32706 |
Query API on the reference sheet line fails when comparing a character field containing a timestamp with a date value. |
|
Description: |
Comparison fails when a character field containing a timestamp is compared with a date value in the reference sheet line. |
||
Resolution: |
If the input payload value is in a Date format, the existing value in the corresponding reference sheet line column will always be treated as a Date for comparison, regardless of that column’s defined data type. However, for other input types (such as numbers), the comparison will use the data type defined for the corresponding reference sheet line column. |
||
39030847 |
NXT-33742 |
The validation message is unclear when a large claim submission is attempted while an activity is still in progress. |
|
Description: |
When a large claim submission activity is in progress, both the large claim and its sub-claims remain in a submittable status. If a submission is attempted again during this time, the error message does not clearly display the exact reason. |
||
Resolution: |
Added a new validation message to handle cases where a large claim submission has an associated activity that is not yet completed. |
||
39015660 |
NXT-33715 |
Episodes Page: Inline edit - changes show up only after refresh |
|
Description: |
In Episodes page, inline edit row level save any of the fields(LOV or text fields) in more section or table is not working. Values are not shown after save, but displayed after refresh or searching again |
||
Resolution: |
Values are shown immediately after save using Inline Edit action |
||
39137165 |
NXT-33910 |
Getting error after configuring dynamic fields of all ref types in Authorization search floorplans |
|
Description: |
Unable to load the page after configuring dynamic fields of ref types in Authorization search page |
||
Resolution: |
Search page loads now when dynamic fields of type LOV is configured in search |
||
39086919 |
NXT-33830 |
Client side Advanced search is not working for between |
|
Description: |
Advanced search between operator is not working for client side search like tabs |
||
Resolution: |
Advanced search between operator works as per specifications |
||
38998705 |
NXT-33670 |
Daily claim productivity per user operational report does not show correct result for manual step |
|
Description: |
If pend is resolved in a manual step i.e claim does not get back first to change and user resolves the pend then the report does not show correct value. |
||
Resolution: |
the Daily claim productivity per user operational report now shows attribution value to claims pended and then resolved in manual steps. |
||
39159286 |
NXT-33954 |
Process Fields dates in Claimline Summary page display one day earlier in negative UTC time zones |
|
Description: |
In the Claim Line → Summary → Process Fields section, date values such as Price Input Date, Benefits Input Date, Benefits Age Input Date (and Waiting Period Input Date) displays one day earlier for users in negative UTC time zones (e.g., US Eastern). |
||
Resolution: |
Updated Process Fields date formatting to use the OJET date converter directly on the raw date‑only string, matching the standard datefield behavior and preventing timezone‑based day shifts. This ensures consistent calendar date display across all time zones. |
||
38998256 |
NXT-33165 |
Incorrect counter creation for cross-year consumption on extended renewal period for calendar year reference limit |
|
Description: |
When a family limit is configured for the reference calendar year and the renewal period exceeds one year, consumption events occurring in different calendar years, both before and after the enrollment subscription date of a member’s policy product, result in the creation of multiple counter periods with the same start date. |
||
Resolution: |
The logic has been updated to address the scenario where a family limit is configured for the reference calendar year and the renewal period exceeds one year; now, only a single counter is created for consumption events across different calendar years, ensuring the renewal period is honored and preventing multiple counter periods with the same start date. |
||
39171129 |
NXT-33965 |
Incorrect enrollment response makes the claim get stuck |
|
Description: |
Incorrect enrollment response makes the claim get stuck in processing status instead of erroring out the enrollment request task. |
||
Resolution: |
When incorrect enrollment response which would cause parsing error is send during enrollment callout the task errors out instead of remaining in processing status. |
||