Release Notes for Oracle Health Insurance Claims Adjudication Patch 4.23.1.0.2
This document contains the release notes for Oracle Health Insurance Claims Adjudication Patch 4.23.1.0.2.
| Version compatibility: Oracle Health Insurance Claims Adjudication Release 4.23.1.x is only compatible with other Oracle Health Insurance applications release version 4.23.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. |
| 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 |
|---|---|---|---|---|
35854447 |
NXT-27774 |
BP |
Dynamic logic timeout property is ignored when compiling dynamic logic at startup time |
|
Description: |
The dynamic logic timeout property (ohi.dynamiclogic.timeout or ohi.dynamiclogic.timeout.{0}) is ignored when the dynamic logic is compiled at system startup time. |
|||
Resolution: |
Load the system property from the database if the loading of system properties is not completed. If loading of system property is completed then load from cache. |
|||
35825206 |
3-32793189991 |
NXT-27736 |
BP |
Error CLA-FL-BENS-031 is attached to claim line when it is submitted with 'processed as IN' checked and there are multiple benefit specifications that qualify |
Description: |
When a claim with an out of network provider is resubmitted with 'Process as In’ checked off and the product configuration has multiple benefits differing only in provider group that qualify, wrong error message is attached to the claim line |
|||
Resolution: |
Added fix to allow benefit specific selection, by making counting specific provider group scope to be counted as in if process-as-in is marked true in the claimline, even if the provider specified does not lie in any of the product provider groups |
|||
35971792 |
NXT-28012 |
BP |
Date format is different in different wigets and search floorplans |
|
Description: |
The date is displayed as YYYY-MM-DD in some widgets and in some widgets its displaying as DD-MM-YYYY |
|||
Resolution: |
Date fields are displayed in same format in search/view-edit page when the same date fields are also used in widgets for that page |
|||
35963374 |
NXT-28001 |
BP |
Dynamic Logic is not compiled at startup |
|
Description: |
Dynamic logic was not always recompiled at application startup. |
|||
Resolution: |
During application startup, any dynamic logic having tec_byte_code as null will be compiled and tec_byte_code will be populated accordingly. |
|||
36102569 |
3-35011487731 |
NXT-28265 |
BP |
The custom JET fields createdByJET and lastUpdatedByJET are not working in pages for auditable resources |
Description: |
The custom JET fields createdByJET and lastUpdatedByJET are not working in generic pages |
|||
Resolution: |
The custom JET fields createdByJET and lastUpdatedByJET can be added to generic floorplans and works fine |
|||
36027408 |
NXT-28131 |
BP |
Reference sheet: Unable add a record that has flex code based field |
|
Description: |
Create a record definition with flex code definition fields and select the reference sheet checkbox field. Navigate to reference sheets page, create an entry using the record definition created above. Click on reference sheet line, add a record. Select the flex code lov and save. An error is thrown. |
|||
Resolution: |
User will be able to create a reference sheet line based on a dynamic record definition which has a flex code field without any errors |
|||
35917718 |
NXT-27908 |
BP |
Unable to see external links icon after adding it in floorplans |
|
Description: |
The icon for external link is not getting displayed when configured in floorplans |
|||
Resolution: |
External link configured in floorplans are displayed in UI |
|||
36010990 |
3-34821774461,3-34621023981 |
NXT-28089 |
BP |
Previous instance of policyProduct does get removed timely when reprocessing a Claim |
Description: |
Before gathering enrollment data , we remove previous enrollment details from claims . Policy product details are also removed as part of it using JPQL. However, the old policy product list remains available in in-memory claim object which can lead to data inconsistency during policy product selection. |
|||
Resolution: |
While removing previous enrollment details from claims, now the policyProductList is also set to null for the claims object |
|||
36100302 |
3-35009181691 |
NXT-28258 |
BP |
After applying the template during generation of a pricing worksheet, an error is thrown. |
Description: |
Getting an error for configuration of draft provider pricing clause through Apply template and Apply option. getting the error GEN-ORA-01400: "DYLO_CODE" column is mandatory for table "PRI_DRAFT_PPRC_DYN_LOGIC". |
|||
Resolution: |
No error is thrown during the generation of Draft Provider Pricing Clauses through Apply Template and Apply Option. |
|||
36125708 |
3-35164428231 |
NXT-28309 |
BP |
Fee Schedule Procedures requests are encountering - GEN-PROC-ERR |
Description: |
When the number of fee schedule lines exceeds 1000 for a specific fee schedule and procedure, the update of fee schedule lines using feescheduleprocedures IP gives the below error: 'ORA-01795: maximum number of expressions in a list is 1000' |
|||
Resolution: |
In the during the processing of IP call a select query is called which used to have all associated feeScheduleLines ids in where in clause, which would throw error if they were more than 1000. Now the query runs with 1000 items at a time, thus avoiding the database exception. |
|||
36051382 |
3-34786906091 |
NXT-28171 |
BP |
Logging improvement to diagnose when claims processing transaction is rolledback and retried in a new transaction |
Description: |
Logging improvement to diagnose when claims processing transaction is rolledback and retried in a new transaction |
|||
Resolution: |
The logging has been improved to help diagnose when claims processing transaction is rolledback and retried in a new transaction |
|||
35684561 |
3-33893255611 |
NXT-27441 |
BP |
Claim type cannot be updated via claims update IP or derivation rule |
Description: |
GEN-RULE-009 error is returned while updating claim type using claims update IP or claim level derivation rule. |
|||
Resolution: |
User can now update claim type using update IP |
|||