Release Notes for Oracle Health Insurance Claims Adjudication Patch 3.21.3.0.7

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

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-22639	The pricing and benefits steps in the claims have been tuned.	Group membership (both for diagnosis and procedure) is now faster. The functionality did not change.
NXT-24452	Extensibility: Additional Fields on Provider Identifier	The number of dynamic fields on the Provider Identifier table is extended: 20 Char fields (adding 15) 5 Number fields 20 Date fields (adding 15) 50 Flex fields (adding 45) 5 Prov fields

Summary

Description

Included in Patch

NXT-22639

The pricing and benefits steps in the claims have been tuned.

Group membership (both for diagnosis and procedure) is now faster. The functionality did not change.

NXT-24452

Extensibility: Additional Fields on Provider Identifier

The number of dynamic fields on the Provider Identifier table is extended: 20 Char fields (adding 15) 5 Number fields 20 Date fields (adding 15) 50 Flex fields (adding 45) 5 Prov fields

Upgrade Steps for Installation

To perform the upgrade, perform the following steps:

Perform any pre-upgrade steps.
Stop all the managed nodes running the .existing version of the application.
Perform any pre-undeploy steps.
Undeploy the existing version of the application.
Back up the database.
Perform any post-undeploy steps.
Unpack the release bundle into a directory that we refer to as OHI_ROOT from now on.
Change Installation Configuration: In <OHI_ROOT>/util/install, make a copy of ohi_install.cfg.template and name it ohi_install.cfg.
Edit ohi_install.cfg to contain your specific database connection data and other configuration settings. The settings are explained in the file itself.
Make sure NO connections are present to the database using the OHI_xxx_USER account (where xxx is the abbreviation of the application)
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 .
Make the required changes to the ohi properties file
Perform any post-upgrade steps
Start WebLogic application server
Deploy the Application
Perform any post-deploy steps

Additional Upgrade Steps for Installation

The following phases are defined:

pre-upgrade: Application is still running
pre-undeploy: Application is stopped, but not undeployed.
post-undeploy: Application is undeployed. Database is backed up
post-upgrade: Released upgrade script has run.
post-deploy: New application is deployed and is up and running.

Stage: post-undeploy

Action: Grant additional privilege to OWNER Schema

The following steps are to be performed before running the upgrade script:

Please run the following SQL statement as SYSTEM user

GRANT CREATE TRIGGER TO OHI_CLAIMS_OWNER;