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.
In accordance with the OHI error correction policy (Document 1494031.1 on My Oracle Support), error correction support will be provided for this release and the previous two releases.

Enhancements

No enhancements.

Upgrade Steps for Installation

To perform the upgrade, perform the following steps:

  1. Perform any pre-upgrade steps.

  2. Stop all the managed nodes running the existing version of the application.

  3. Perform any pre-undeploy steps.

  4. Undeploy the existing version of the application.

  5. Back up the database.

  6. Perform any post-undeploy steps.

  7. Unpack the release bundle into a directory that we refer to as OHI_ROOT from now on.

  8. Change Installation Configuration: In <OHI_ROOT>/util/install, make a copy of ohi_install.cfg.template and name it ohi_install.cfg.

  9. Edit ohi_install.cfg to contain your specific database connection data and other configuration settings. The settings are explained in the file itself.

  10. Make sure NO connections are present to the database using the OHI_xxx_USER account (where xxx is the abbreviation of the application)

  11. 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 .

  12. Make the required changes to the ohi properties file

  13. Perform any post-upgrade steps

  14. Start WebLogic application server

  15. Deploy the Application

  16. Perform any post-deploy steps

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

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'.

Issues that were backported in previous Release / Patch

No backports.