Release Notes for Oracle Health Insurance Claims Adjudication Patch 3.21.3.0.11
This document contains the release notes for Oracle Health Insurance Claims Adjudication Patch 3.21.3.0.11.
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. |
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 ofohi_install.cfg.template
and name itohi_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:
-
Open a command window and browse to
<OHI_ROOT>/util/install
. -
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
Bug Fixes
BugDB | SR | Internal | BP | Summary |
---|---|---|---|---|
34891413 |
3-30739647241 |
NXT-26023 |
BP |
Claims processing is slow during CMT import |
Description: |
If a CMT data set containing large number of items that execute dynamic logic (eg: to validate if the dynamic field is valid as per the field validation dynamic logic) are imported when claims are processed (which involves executing a number of dynamic logic during claims flow), both CMT import and claims processing become very slow because execution of dynamic logic in both CMT import and claims processing is handled inefficiently. |
|||
Resolution: |
The execution of dynamic logic in both CMT import and claims processing has been optimized. |