Release Notes for Oracle Health Insurance Claims Adjudication Patch 4.23.1.0.1
This document contains the release notes for Oracle Health Insurance Claims Adjudication Patch 4.23.1.0.1.
| 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 |
|---|---|---|---|---|
35700098 |
NXT-27485 |
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. |
|||
35709574 |
3-33964183741 |
NXT-27494 |
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. |
|||
35722569 |
NXT-27517 |
BP |
Financials page :Once a hold is expired or released, the row should not be editable |
|
Description: |
In Financial Holds page, once a hold is expired or released, the row shouldn’t be editable |
|||
Resolution: |
If status is released or expired , financial hold rows are in read-only mode |
|||
35726305 |
NXT-27523 |
BP |
Messages Drawer is not loading results in draft provider pricing clause page. |
|
Description: |
When clicked on invalid link on errored DPPC records, the messages drawer that opens up does not load any results and shows as loading indefinitely. |
|||
Resolution: |
When clicking on invalid link on errored DPPC records, the message drawer that opens up shows all the messages linked to that record. |
|||
35731084 |
NXT-27536 |
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 |
|||
35733356 |
3-33917283371 |
NXT-27539 |
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 {…} |
|||
35766953 |
NXT-27630 |
BP |
Slowness observed in claims processing |
|
Description: |
The query to find claims lines for duplicate check also considers linked relations now . With this change , there was slowness observed in claims processing . |
|||
Resolution: |
Claims should process efficiently as before . |
|||
35767231 |
3-34060667661 |
NXT-27644 |
BP |
Search bar disappears when floorplans with different quick search attributes having criteria are switched. |
Description: |
When two search floorplans are configured on a page with different quick search attributes and the search is made on the non-common field among the floorplans, the search bar disappears. |
|||
Resolution: |
The search criteria and sort criteria are cleared when the floorplans are switched to allow entering fresh search and sort criteria. |
|||
35794256 |
NXT-27698 |
BP |
Issue with Diacritics search with special characters |
|
Description: |
While performing diacritic search with special character followed by A (stop list or Stop word). the search ended up with unknown result set. The list for various language is as mentioned below. |
|||
Resolution: |
The issue seems to be with the behavior of Oracle text index with Stop list and Stop word functionality when these stop list words are used along with special characters then the same will not be indexed and leads to this behavior. The same has been fixed by modifying the index metadata. |
|||
35794870 |
NXT-27701 |
BP |
Memory leakage with coherence processing pattern |
|
Description: |
DHL observed performance issues with activity processing, many of the activities got stuck while processing due to OOM. |
|||
Resolution: |
Memory leaks are fixed in coherence. |
|||
35800361 |
3-34207093491 |
NXT-27715 |
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. |
|||
35820630 |
NXT-27733 |
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 |
|||
35834881 |
NXT-27746 |
BP |
Quick search And mode: Unable to search using quick search And mode text box, when widgets are added |
|
Description: |
In claims(landing) page, do a quick search using And mode text box, check if you are able to enter any value. Now click on "Add card" and add few widgets. Refresh the page and login again. Again try to do a quick search using And mode text box, check if you are able to enter any value. On clicking quick search, And mode text box is not shown. |
|||
Resolution: |
Quick Search popup opens when widgets are enabled. |
|||
35839913 |
3-32026064771 |
NXT-27751 |
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. |
|||
35860963 |
NXT-27784 |
BP |
Clicking the 'Cancel' button, the 'Confirm Cancel' dialog doesn’t close |
|
Description: |
When user clicks the 'Cancel' button, the 'Confirm Cancel' dialog remains on screen and nothing happens in Activity page |
|||
Resolution: |
When clicking the 'Cancel' button in the 'Confirm Cancel' dialog, the dialog disappears and user is redirected to the Create Activity screen. |
|||
35876769 |
NXT-27798 |
BP |
Datafile Link Query Improvement |
|
Description: |
This fix improves the performance of the datafile query by returning the datafile link using message code/datafile code. |
|||
Resolution: |
Improved the query performance to generate datafile links |
|||