Release Notes for Oracle Health Insurance Claims Adjudication Patch 3.21.3.0.8

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

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

ID Summary Description Included in Patch

NXT-24489

JSON Re-Indexing Package

This enhancement introduces the package OHI_REFERENCE_SHEET_LINES_INDEX_MAINTENANCE_PKG, that creates an oracle text index OHI_REF_SHEET_LINE_IDX1 on OHI_REFERENCE_SHEET_LINES table in Oracle 19c format with Sync frequency option. This package needs to be executed in the Post-upgrade stage.

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

Additional Upgrade Steps for Installation

The following phases are defined:

  1. pre-upgrade: Application is still running

  2. pre-undeploy: Application is stopped, but not undeployed.

  3. post-undeploy: Application is undeployed. Database is backed up

  4. post-upgrade: Released upgrade script has run.

  5. post-deploy: New application is deployed and is up and running.

Stage: post-upgrade

A new OHI_REFERENCE_SHEET_LINES_INDEX_MAINTENANCE_PKG has been provided as part of the patch. Post upgrade of the patch login as ohi_<app>_owner and execute the below command to recreate the index.

begin
  ohi_reference_sheet_lines_index_maintenance_pkg.create_index(1);
end;
/

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.

Deprecated items (to be removed in future release)

This section intentionally left blank.

Breaking Changes

This section intentionally left blank.

Bug Fixes

BugDB SR Internal BP Summary

34095720

NXT-24602

BP

Optimize the initialization of dynamic logic execution

Description:

Initializing ExpandoMetaClass when adding extensions of the dynamic logic (even when the logic does not have any extensions) consumes some CPU cycles. Optimize the meta class initialization for dynamic logic that does not have extensions.

Resolution:

Performance of dynamic logic execution (that does not have any extensions) has been improved

Issues that were backported in previous Release / Patch

No backports.