Release Notes for Oracle Health Insurance Claims Adjudication Patch 4.23.1.0.11

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

Version compatibility: Oracle Health Insurance Claims Adjudication Release 4.23.1.x is only compatible with other Oracle Health Insurance applications release version 4.23.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.

Bug Fixes

BugDB SR Internal Summary

37151585

NXT-30475

Internal system user is used for resolving the claim pends via pend resolution criteria IP

Description:

When pend reasons are resolved by the pendresolution criteria IP, internal system user is used for resolving the claim or claim line pends. Instead of this the current user should be used to resolve the pends via pend resolution criteria IP.

Resolution:

Instead of System User , the information of user who triggered the pend resolution criteria IP will now be used for resolving the pend.

37436525

3-38082342431

NXT-30872

Improve the Activity recovery query when node crashes

Description:

When a node is crashed, the other nodes try to recover the activities from the crashed node. During this recovery the select query on activities was too costly resulting in SQLException "Socket read interrupted" - i.e connection timeout.

Resolution:

The SELECT query was optimized, and the index on the activity table was updated to prevent a full table scan. This significantly reduced the recovery cost and effectively resolved the connection timeout issue.

37761311

3-39441721251

NXT-31329

Query to fetch user role history list for a user should be case insensitive

Description:

Query to fetch user role history list was performing a case sensitive match for the user login name, so when a new role was added/deleted for the user with a different case in login name, the said query could not retrieve the complete list from the database.

Resolution:

The query is fixed to perform a case insensitive match on the user login name.

37665685

NXT-31174

Activities are not purged when auto-purge job is enabled

Description:

Auto-purge job fails due to integrity constraint violation when child record is present in act_activity_dyn table

Resolution:

Changing the deletion order to delete child entries first before deleting act_activities entries resolved the issue.

37235842

3-38352943611

NXT-30610

Limit consumptions do not appear if there are more than 50 records.

Description:

Only upto 50 limit consumptions can be displayed in the claims benefits tab.

Resolution:

All the limit consumptions on the claim are displayed.

37739982

3-38722563251

NXT-31261

Add logging to diagnose missing counter periods for product limits with carry over setting

Description:

Add logging to diagnose missing counter periods for product limits with carry over setting

Resolution:

Application logs have the additional log statements when they are enabled through application.

Issues that were backported in previous Release / Patch

No backports.