Release Notes for Oracle Health Insurance Claims Adjudication Patch 3.22.1.0.4
This document contains the release notes for Oracle Health Insurance Claims Adjudication Patch 3.22.1.0.4.
| Version compatibility: Oracle Health Insurance Claims Adjudication Release 3.22.1.x is only compatible with other Oracle Health Insurance applications release version 3.22.1.x unless explicitly stated otherwise. |
| OHI applications expose the technical ID (created by sequence generator) in HTTP API and IP. This might be changed to an alternate technical ID (the data type might not be an integer) in a future release. Hence, it is advised to follow the generated HATEOAS links instead of hard-coding/bookmarking the IDs in the external integrations. |
| 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 | BP | Summary |
|---|---|---|---|---|
34189635 |
NXT-24779 |
BP |
On a claim with many claimlines, opening a claimline summary causes the page to shift up |
|
Description: |
Open a claim with many claimlines and go to claimline tab Scroll down and try to open summary panel for one of the claimline. Panel opens and the page gets scrolled to the top, user loses the context which claimline user had clicked |
|||
Resolution: |
The Claim line now opens up as a drawer on the right side of the page. Functionality matches the previous version of the claim line summary. The user can click out or click on the cancel icon to close the drawer. |
|||
34359270 |
3-30012711611 |
NXT-25051 |
BP |
Adding a new service address does not create deep link from rendering address. |
Description: |
After creating a new service address from the deep link pop-up, the created value is not getting populated in the service address lov. |
|||
Resolution: |
Creating a new service address from deeplink gets populated in service address LOV. After adding the values, saving the record works for one row. Multiple rows cannot be added at the same time, an intermediate 'Save' is required for this patch |
|||
34484334 |
3-30297787561 |
NXT-25233 |
BP |
Advanced Search with flex code not working. |
Description: |
When a flex code type field is added in the advanced search, search is not possible by using this field and also console errors are thrown when search is triggered. |
|||
Resolution: |
Advance Search is possible on flex codes type of fields without any errors. |
|||
34460209 |
3-30242875981 |
NXT-25197 |
BP |
Procedure code 394 against dental gets transformed to 394 pre illness code. |
Description: |
When two procedures have the same code, the last procedure with that same code in the LOV is getting selected and saved. |
|||
Resolution: |
Proper values are selected from the LOV dropdown and saved properly even when two procedures have the same code. Earlier only the last procedure was getting saved |
|||
34378134 |
3-30011552221 |
NXT-25073 |
BP |
Extract activity stays in 'in process' status sometimes waiting on AtomicSafeInitializer |
Description: |
While initializing ExtractGlobalPlan, sometime extract activity stays in 'In Process' status by waiting on AtomicSafeInitializer and never completes. As a result, if any new extract activities are submitted, it will be also in 'In process' status and if such submission continues, finally the activity processing thread pool is exhausted. |
|||
Resolution: |
Modified the way of initializing ExtractGlobalPlan. Now ExtractGlobalPlan is initialized immediately after it is created on each node. |
|||