Release Notes for Oracle Health Insurance Claims Adjudication Patch 3.21.1.0.3
This document contains the release notes for Oracle Health Insurance Claims Adjudication Patch 3.21.1.0.3.
Version compatibility: Oracle Health Insurance Claims Adjudication Release 3.21.1.x is only compatible with other Oracle Health Insurance applications release version 3.21.1.x unless explicitly stated otherwise. |
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
UI Changes
Ref | Action | Subject | Description |
---|---|---|---|
NXT-22340 |
Modified |
Conditional display properties |
Conditional display properties are configured to work with flexcode based fields. |
Bug Fixes
BugDB | SR | Internal | BP | Summary |
---|---|---|---|---|
32873325 |
3-25808562021 |
NXT-22579 |
BP |
Conditional display triggered on flexcodes based fields is not working |
Description: |
Conditional display triggered on flexcodes based fields is not working. |
|||
Resolution: |
User will now be able to configure conditional display properties on flexcode based fields. |
|||
32874329 |
3-25212425011 |
NXT-22583 |
BP |
Tune the Limit Consumption query for faster response. |
Description: |
After upgrading to 3.20.2, increase in the average processing timings when compared to the previous base line tests was reported. Limit consumption query needs optimization to fix this. |
|||
Resolution: |
The query has been tuned to have a better execution plan and will reduce the overall execution time of the query. |
|||
32887581 |
3-25909862119 |
NXT-22597 |
BP |
Error in finalization step if there there are no existing counter periods for provider limit counter |
Description: |
There is error in finalization step if there are no existing counter periods for provider limit counter. Code returns null in such cases leading to null pointer. |
|||
Resolution: |
If there are no existing counter periods for provider limit counter, finalization will continue as expected. Empty list is returned instead of null in such cases. |
|||
32893870 |
3-25694698761 |
NXT-22613 |
BP |
SEND_FINANCIAL_MESSAGES activity type should be allowed to be recovered |
Description: |
When claims fail in delivery to OHI, a new batch with the identifier "SEND_FIN_MESSAGE" is created which should allow re-trigger but is not available as option currently. The icon to re-trigger only appears when activity is in one the failure states and is a top level activity |
|||
Resolution: |
The icon to re-trigger is now available when the activity is in one of the failure states and does not have origin spawned or when it in one of the failure states and is a top level activity. |
|||
32899580 |
3-25807956661 |
NXT-22622 |
Claims floorplans field LOV not working |
|
Description: |
When creating dynamic record - picklist configuration, LOV values are not showing up on click of the magnifier. |
|||
Resolution: |
Now configuring dynamic record with picklist, shows up the LOV values. |
|||
32903594 |
3-25943541561 |
NXT-22628 |
BP |
Enrollment client does not initialize property in all culster nodes if properties come from the database |
Description: |
Enrollment client properties are specified in the database (not in the properties file). In one of the cluster nodes the Enrollment Client is initialized properly but in the other node Enrollment Client initialization seems to happen before initialization of the properties collection was completed. |
|||
Resolution: |
While multi node cluster started one of the node is not ready with initialized state to properly configure enrollment client information. With this fix each node will ensure to populate the enrollment client with appropriate values. |