Release Notes for Oracle Health Insurance Claims Adjudication Patch 4.23.2.0.4
This document contains the release notes for Oracle Health Insurance Claims Adjudication Patch 4.23.2.0.4.
| Version compatibility: Oracle Health Insurance Claims Adjudication Release 4.23.2.x is only compatible with other Oracle Health Insurance applications release version 4.23.2.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. |
Enhancements
| ID | Summary | Patch |
|---|---|---|
POL-15792 |
Optimize loading of SVNTV fields into the memory during extracts Currently, the system loads all the Single Value Non-Time Valid(SVNTV) dynamic fields associated with resources into the memory which causes OOM. Only the required SVNTV dynamic fields should be loaded into memory while processing the extracts. |
4.23.1.0.10, 4.24.1.0.1 |
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 |
|---|---|---|---|
37014448 |
3-37140647951 |
NXT-30266 |
Retrieval access restrictions Brand/Payer missing for CtrClaims and related entities. |
Description: |
Retrieval access restrictions for Brand/Payer are not present in generic API. When the brand/payer is restricted, a user can still get the CtrClaim and its related entities with the API. |
||
Resolution: |
Brand and payer access restriction have been added on retrieval of a ctrclaim and its related entities such as ctrclaimLine, ctrclaimmesssage, ctrclaimlinemessage, etc. Now these records will not be accessible through API without proper access roles granted to the user. |
||
37337998 |
3-37575580501 |
NXT-30773 |
Field values are intermittently not being set when using the JET UI |
Description: |
An intermittent issue with setting field values in the JET UI is noticed. To reproduce Create a field, such as 'endDate', for any usage , Set a value for this field and save it , Verify if the value is reflected correctly ,Update the value and save it again. Occasionally, the updated value is not being saved properly. Specifically, the payload sent from the UI intermittently omits the updated field value |
||
Resolution: |
The value updates successfully regardless of how many times it is modified. |
||
37151579 |
NXT-30474 |
Internal system user is used for resolving the claim pends via pend resolution criteria IP |
|
Description: |
When pend reasons are resolved by the pendresolution criteria IP, internal system user is used for resolving the claim or claim line pends. Instead of this the current user should be used to resolve the pends via pend resolution criteria IP. |
||
Resolution: |
Instead of System User , the information of user who triggered the pend resolution criteria IP will now be used for resolving the pend. |
||
37110398 |
NXT-30436 |
Popuptail is displaying title as "Default" in all popups regardless of resource |
|
Description: |
PopupTail is displaying title as "Default" in all popups regardless of resource. "Default" is displayed for most popupTails but for certain resources from the JET code we display them as Procedures, Providers etc( ie ResourceName from a fixed list) |
||
Resolution: |
Popuptail displays the Title as per the resource name. |
||
37015993 |
NXT-30269 |
Messages LOV doesn’t show data properly on add message pop-up |
|
Description: |
Messages LOV when selected occupies the entire page, hiding many fields. |
||
Resolution: |
Messages LOV display width is reduced and is now displayed similar to other LOVs. |
||
37156609 |
NXT-30487 |
Activity remains in IP status as the technical flag for submission is not cleared on TE activities |
|
Description: |
The activities remain stuck in IP status as the technical flag for submission (TEC_IND_SUBMISSION) flag was not cleared for the parent activities with status TE. These TE activities occupy the entire submission bucket, the size of which is determined by the property ohi.processing.max.concurrentparentactivities.size, which has a default value of 8. If the bucket is full, the newly submitted activity will remain in IP. |
||
Resolution: |
The query to fetch the count of currently submitted activity was modified to fix the issue. |
||
37563879 |
3-36224017471 |
NXT-31091 |
Floorplan conversion script fails when the payload size is large |
Description: |
Floorplan conversion script fails to convert set1, set2, set3 to sets array and results in error during upgrade. This is due to large payload size which was not handled by liquibase conversion script. |
||
Resolution: |
Liquibase script is modified to handle usecase where floorplan size is large and there is no error during conversion of region set1, set2, set3 to sets[] |
||
37157409 |
3-36913840401 |
NXT-30490 |
Extract requests can have a limited number of characters in the condition |
Description: |
Extract request with a large query fails with activity message "ORA-06502: PL/SQL: numeric or value error ORA-06512: at line 1". This is because the selection is stored in a variable with a maximum of 32000 characters. |
||
Resolution: |
Selection is now stored as a clob of which the maximum size depends on environment settings: (4 GB - 1) * DB_BLOCK_SIZE initialization parameter (8 TB to 128 TB). Contact database administrator for more details if needed. This change allows for a more extensive query in the extract request and a lesser chance of running into the ORA-06502 error. |
||
37248618 |
NXT-30631 |
Unauthorized error while uploading file in Inbound configuration migration |
|
Description: |
401 Unauthorized error is returned while uploading file in Inbound configuration migration |
||
Resolution: |
Able to upload file without any error in Inbound configuration page |
||
37235834 |
3-38352943611 |
NXT-30609 |
Limit consumptions do not appear if there are more than 50 records. |
Description: |
Only upto 50 limit consumptions can be displayed in the claims benefits tab. |
||
Resolution: |
All the limit consumptions on the claim are displayed. |
||