Release Notes for Oracle Health Insurance Claims Adjudication Patch 3.22.2.0.12
This document contains the release notes for Oracle Health Insurance Claims Adjudication Patch 3.22.2.0.12.
| 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. |
| 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 |
|---|---|---|---|---|
35204698 |
3-32427188011 |
NXT-26667 |
BP |
Routing slips 'PRICINGDONE' and 'PREPROCESSING' are not reset during the automatic reprocess of the claim |
Description: |
We see that a Pend Rule with Reprocess delivers an (unexpected) different result compared to a Manual Submit of a similar Claim, this is because of the routing slips 'PRICINGDONE' and 'PREPROCESSING' are not reset |
|||
Resolution: |
'PRICINGDONE' and 'PREPROCESSING' routing slips are now reset during the automatic reprocess of the claim |
|||
35491920 |
3-32026064771, 3-33959947311 |
NXT-27121 |
BP |
Performance issue when updating the status of base financial objects in generate financial messages activity under high concurrency |
Description: |
High wait event "enq: TX - allocate ITL entry" occurs when updating the status of base financial objects to 'FM' in generate financial message activity under high concurrency and this causes the activity to run very slow |
|||
Resolution: |
update base financial object at the end of parent activity instead of updating after every child activity. This should minimize the number of sessions opened for the update. |
|||
35513269 |
3-33075425901 |
NXT-27150 |
BP |
Tasks and activities fail over happens in all the nodes |
Description: |
When a JVM processing task/activity leaves the cluster, that task/activity is recovered by all the JVMs in the cluster. This can produce incorrect results as the recovery should be performed only by one (master) node |
|||
Resolution: |
Added condition so that task/activity recovery can be done by the master node of cluster only |
|||
35527915 |
3-30739647241 |
NXT-27169 |
BP |
Blocked threads are waiting on coherence during cmt import |
Description: |
During CMT import when non entity cache is under construction, threads accessing that cache waits on coherence. |
|||
Resolution: |
Moved non entity caches from coherence to JVM memory |
|||
35685778 |
3-33858160991 |
NXT-27456 |
BP |
Dynamic logic cache reloads every time on business cache invalidation even if there is no dynamic logic update |
Description: |
Dynamic logic cache uses a business process cache which is invalidated on any change in configuration entities (that implements ProcessCacheInvalidating) even though there is no change in dynamic logic itself . On invalidation of the cache , byte code is loaded again for all the dynamic logic which is CPU intensive and can slow down other processes running in parallel during the class loading . |
|||
Resolution: |
Now , the cache invalidation and reloading happens only on change in dynamic logic entity. |
|||
35709581 |
3-33964183741 |
NXT-27495 |
BP |
Activity Message is lost when generate financial message activity is recovered |
Description: |
Activity message (ACT-FL-DAFI-001) is lost when generate financial message activity is recovered |
|||
Resolution: |
The activity message is ACT-FL-DAFI-001 is removed when the recover process starts, but if the error persists during reprocess of the activity then the messages is recreated. |
|||
35731060 |
NXT-27535 |
BP |
Flex code fields with search criteria not loading correct LOV values |
|
Description: |
Flexcodes LOV doesn’t load correct results when searching with criteria. Query constructed had a missing parenthesis to group 'and' and 'or' conditions |
|||
Resolution: |
Search query is constructed properly for flexcode lov and expected results are shown |
|||
35733366 |
3-33917283371 |
NXT-27540 |
BP |
Message parameters configured as {…} is not being replaced with parameter values. |
Description: |
Message parameters are not being replaced with parameter values when the parameterized string is used as {…} |
|||
Resolution: |
Message parameters are replaced with appropriate parameter values in the same message when the parameterized string used is {…} |
|||
35800320 |
3-34207093491 |
NXT-27714 |
BP |
Adjudicaiton limit counters does not show all limit consumptions |
Description: |
When there are more than 50 consumptions under a counter, API returns only first 50 consumptions. |
|||
Resolution: |
User can now access all the consumptions without limit. |
|||