Release Notes for Oracle Health Insurance Claims Adjudication Patch 4.24.1.0.13
This document contains the release notes for Oracle Health Insurance Claims Adjudication Patch 4.24.1.0.13.
| Version compatibility: Oracle Health Insurance Claims Adjudication Release 4.24.1.x is only compatible with other Oracle Health Insurance applications release version 4.24.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. |
Bug Fixes
| BugDB | SR | Internal | Summary |
|---|---|---|---|
36989310 |
3-36700304951 |
NXT-30214 |
System randomly throws optimistic locking exception while updating dynamic logic on CFS deployments |
Description: |
In certain scenarios, updates made to dynamic logic were not immediately reflected at runtime because the internal cache reload process could occur before the relevant database transaction was committed. This timing issue could cause the cache to be repopulated with stale data. |
||
Resolution: |
The dynamic logic cache reload process is now triggered only when the update transaction is committed, ensuring that the cache consistently reflects the most recent changes. |
||
38426687 |
NXT-32515 |
Pend rule does not fire for subclaim after reprocessing a large claim |
|
Description: |
Pend rule is not reapplied to a subclaim when a large claim is reprocessed. |
||
Resolution: |
Resolved pend rules are cleared upon claim submission. During reprocessing of a large claim, pend rules can now be reattached to the subclaim. |
||
38009274 |
NXT-30407 |
Proper error message has to be returned during task purge process. |
|
Description: |
When task purge is initiated by directly calling ohi_task_purge_pkg.purge_data the purge functionality fails with error "ORA-02292: integrity constraint (OHI_CLAIMS_OWNER.OHI_TASK_ATTRIBUTE_FK2) violated - child record found". The reason for this failure is ohi$user_constraints and ohi$user_cons_columns is not initialised with parent child table lists and columns which gets initialised only when triggered from ohi_data_purge_pkg.purge_data, This results in attempt to purge only parent table and since child table records are not purged yet ORA-02292 is raised. To avoid this we need to provide proper error message instead of ORA-02292 which is raised by oracle database. |
||
Resolution: |
When task purge is initiated by directly calling ohi_task_purge_pkg.purge_data, the purge functionality now fails with the error 'Operation not successful, use "Data purge package" to purge tasks'. |
||