Release Notes for Oracle Health Insurance Claims Adjudication Patch 4.24.1.0.18
This document contains the release notes for Oracle Health Insurance Claims Adjudication Patch 4.24.1.0.18.
| Version compatibility: Oracle Health Insurance Claims Adjudication Release 4.24.1.x is only compatible with other Oracle Health Insurance applications release version 4.24.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. |
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.templateand name itohi_install.cfg. -
Edit
ohi_install.cfgto 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 | Summary |
|---|---|---|---|
38746894 |
NXT-33176 |
While changing the version value from working copy to any other, getting boilerplate errors in dropdown values |
|
Description: |
Open any claim in Finalized status. Change the dropdown value from working copy to any other value. Click on dropdown again. Boilerplate errors coming in dropdown values |
||
Resolution: |
Boilerplates are not shown in Claims page version dropdown and proper values are shown now |
||
39518699 |
NXT-34324 |
OAuth client secrets are missing when ohistore is used as the keystore |
|
Description: |
OAuth clients sometimes showed |
||
Resolution: |
OAuth client credential keys are now fetched correctly. |
||
39483337 |
NXT-34304 |
Diacritic search returns incorrect results for reserved words and special characters |
|
Description: |
Diacritic search returned incorrect results when search values contained reserved words or special characters. |
||
Resolution: |
Diacritic search now returns the correct results for values that contain reserved words or special characters. |
||
39391455 |
4-0002762009 |
NXT-34196 |
Registration Import Can Cause OOM Due To Middle Tier Financial Objects Linking |
Description: |
During registration import, the current middle-tier implementation of claims-side subject registration linking can create a very large in-memory object graph within a single transaction. In high fan-out scenarios, this leads to excessive heap growth and recurring OOM events. |
||
Resolution: |
Logic written in Java at middle tier has been moved to named native SQL query. So the logic can be performed in the DB layer instead of loading the objects in the memory. |
||
39294580 |
4-0002606913 |
NXT-34119 |
Advanced search criteria are not retained when users return from a detail page to the search page |
Description: |
Advanced search criteria are not retained when user performs search, navigates to Claims detail page and returns to search page |
||
Resolution: |
Advanced search criteria are now retained when users return from a claim detail page to the search page. |
||