Release Notes for Oracle Health Insurance Claims Adjudication Patch 3.22.2.0.3
This document contains the release notes for Oracle Health Insurance Claims Adjudication Patch 3.22.2.0.3.
| Version compatibility: Oracle Health Insurance Claims Adjudication Release 3.22.2.x is only compatible with other Oracle Health Insurance applications release version 3.22.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 |
|---|---|---|
AUT-2954 |
Include JVM GC metrics in Prometheus Metrics for GC monitoring have been added, controlled by a number of system properties: JVM metrics are enabled by ohi.instrumentation.gather.jvm (this used to be ohi.instrumentation.gather.jvmtelemetry) System metrics are enabled by ohi.instrumentation.gather.system (this used to be ohi.instrumentation.gather.jvmtelemetry) Garbage Collection metrics are enabled by ohi.instrumentation.gather.gc |
|
NXT-18517 |
Mask the Operational Data This enhancement introduces the capability to mask operational data within the application. The purpose of this enhancement is to create a representative operational test data for non-production environments. The user can specify which fields containing personally identifiable information (PII) as well as how the information is transformed. This feature is now available for on-premises deployments. It will be made available for cloud deployments in a future release. Documentation Links: |
|
NXT-26741 |
Additional Dynamic Fields on Claim Line This enhancement increases the number of single value, non-time valid number dynamic fields that can be stored on the claim line and CTR claim line entities by 5. |
|
OIG-2764 |
Reducing Application Clients Configuration This enhancement enables a user to re-use application clients, configured in the Authorization Server, across OHI REST clients. |
|
POL-9591 |
Throttle number of global level activities that can run in parallel Feature to limit the number of parent activities that can run in parallel at any given point in time. Documentation Links: |
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 |
|---|---|---|---|---|
34982437 |
3-29348208321, 3-29584669481 |
NXT-26221 |
BP |
Data Replication is not proper on Activity restart |
Description: |
The data replication process started before the necessary configuration (titles in this error) was loaded to claims and hence the activity failed with Business Error. . After the configuration issues were fixed then restarting the failed activity should have processed the target events (replicated members), but they were not - because the activity fetches the records from rep_target_events where processed_timestamp is null |
|||
Resolution: |
If activity-related to type process_target_repl_events failed with any status other than completed the activity restart must pick up the records from rep_target_events depending on the activity status and process the records. |
|||
35243215 |
NXT-26712 |
BP |
Quick search fields popup is misaligned in Claims page in Firefox browser |
|
Description: |
There is no spacing between the label and text area for the field member last name ( claim ) and too much space between member claim line label and value. It varies from machine to machine, depends upon screen resolution |
|||
Resolution: |
Alignment issues in firefox browser in Quick Search 'AND' mode popup is fixed |
|||
35212959 |
NXT-26674 |
BP |
Error Message on manual Benefits page is not shown at the right place |
|
Description: |
While updating coverage amounts in Manual Benefits dialog, if there is any business error then the error messages shouldn’t be shown on the claim details page rather the error message should be shown in the 'manual benefits' drawer. |
|||
Resolution: |
While updating coverage amounts in Manual Benefits dialog, if there is any business error then the error message is shown in the 'manual benefits' drawer. |
|||
35077009 |
3-32110222731 |
NXT-26409 |
BP |
Fee Schedule activity import is marked as success while it is still in progress . |
Description: |
Fee Schedule activity import is marked as success while it’s child activities are still processing insert/update logic . This was due to task ID of the child activities is assigned to parent activity ID instead of the activity ID itself . |
|||
Resolution: |
Now , the main activity progress is in sync with child activities completion . Task ID of the child activity is same as the activity ID itself |
|||
34987152 |
3-32247856831 |
NXT-26247 |
BP |
The number of items in shared Eclipselink caches is maximized |
Description: |
The shared Eclipselink caches could grow unlimited, which resulted in memory shortage. To prevent that, the number of items in such a cache is now limited using the system properties ohi.persistence.cache.size.default and ohi.persistence.cache.{0}.size. |
|||
Resolution: |
The number of items in shared caches is now limited using the system properties ohi.persistence.cache.size.default and ohi.persistence.cache.{0}.size. |
|||
35153747 |
3-32317309991 |
NXT-26573 |
BP |
Automatic activity fail over sometimes results in duplicate child activities |
Description: |
When a JVM processing activity is restarted, the activity failover happens and the other JVM in the system re-submits that activity. This creates duplicate child activities upon rolling restart. This leads to reprocessing the data file that was already successfully processed before the JVM is restarted |
|||
Resolution: |
The unique Identifier issue was fixed already, the issue was not reproducible |
|||
35043816 |
3-31945494731 |
NXT-26347 |
BP |
Time-Valid flex codes are not showing nested properties |
Description: |
Flex codes configured under procedure is not showing up in Claim lines. |
|||
Resolution: |
Users can now configure a floorplan at claim lines level for flex codes configured under procedure level. |
|||
35276544 |
NXT-26770 |
BP |
Claimline sequence is not generated correctly when trying to create third claim line in one go without saving any claim line |
|
Description: |
Create a Claim. Start Adding more than 2 Claim Lines. After adding second claim line when user try to add third line, again the sequence is showing as 2 instead of 3 |
|||
Resolution: |
Claimline sequence is generated correctly when trying to create multiple claim lines in one go without saving any claim line |
|||
35263200 |
3-32225018171 |
NXT-26747 |
BP |
Incorrect selection of policy product parameters in case of upgrade with product history |
Description: |
There was an intermittent issue with the way policy product is selected while loading policy product parameters if there are products with history in the enrollment response . This leads to wrong limits and parameters being applied on the claim line rule coverages . |
|||
Resolution: |
To resolve the issue , we make sure that correct policy product is available in the benefit context and use it for processing . |
|||
35177167 |
3-32387051031 |
NXT-26629 |
BP |
Referencesheetlines can not be created with blank endDate via API or IP |
Description: |
When trying to create reference sheet lines using API or IP with empty enddate i.e. endDate as "". Application is causing NPE |
|||
Resolution: |
An empty string for a date has been handled so that NPE will not be there. Also this empty string will update the endDate as null in database. |
|||
34982471 |
NXT-26230 |
BP |
Some activities are stuck in 'in process' status if new nodes are started while the activities are running |
|
Description: |
Some activities are stuck in 'In Process' status if new nodes are started while the activities are running The fix for this issue will prevent NPEs from being thrown by oracle coherence |
|||
Resolution: |
Added check on startup service, so that the system starts only when fully initialized |
|||
34982424 |
3-32110222731 |
NXT-26220 |
BP |
FeeSchedule integration point is failing intermittently with optimistic lock exception |
Description: |
FeeSchedule integration point is failing intermittently with optimistic lock exception: 'Resource busy and acquire with NOWAIT specified or timeout expired'. This was due to child activities acquiring lock on fee schedule which would be processed by other child activities as well. |
|||
Resolution: |
The lock on fee schedule in fee schedule integration point (activity based) is no longer acquired |
|||
35233080 |
3-32535028871,3-32637203321 |
NXT-26702 |
BP |
DynamicRecordSetup non-entity cache holds redundant FieldDetails objects |
Description: |
Too many redundant FieldDetails objects (which are already part of FlexCodeSetup non-entity cache) are cached in DynamicRecordSetup non-entity cache. This is causing memory issues. |
|||
Resolution: |
The memory utilization of non-entity cache DynamicRecordSetup is optimized |
|||
35224499 |
3-32535028871,3-32637203321 |
NXT-26685 |
BP |
External intervention rules business process cache holds live domain object ClaimForm |
Description: |
The key used in external intervention rules business process cache holds live domain object ClaimForm which is memory intensive as it holds the transaction related objects. |
|||
Resolution: |
The external interventions rules business process cache key is changed to use the ID of the ClaimForm instead |
|||