Release Notes for Oracle Health Insurance Claims Adjudication Patch 3.21.2.0.5
This document contains the release notes for Oracle Health Insurance Claims Adjudication Patch 3.21.2.0.5.
Bug Fixes
BugDB | SR | Internal | BP | Summary |
---|---|---|---|---|
33576762 |
3-26738959731 |
NXT-23821 |
BP |
Selected coverage specification is filtered out on provider group scope |
Description: |
The overriding coverage specification is filtered out as part of benefit selection process on provider group scope, which should not happen. Filter benefit selection process is skipped when an overriding coverage specification is selected. |
|||
Resolution: |
Selected coverage specification is not filtered out on provider group scope. |
|||
33722790 |
3-26858967101 |
NXT-24053 |
BP |
Extra Logging For 'Read Consumption Batch still in progress issue' |
Description: |
HTTP GET on some (not all) read consumption batch requests still in progress. |
|||
Resolution: |
Extra logging added to help in debugging |
|||
33752774 |
3-28259794771 |
NXT-24085 |
BP |
Task Processing error - SEARCH THE LOGGING FOR OCCURRENCES OF "NULL" |
Description: |
When claims are reprocessed through UI, claims are occasionally getting the technical error - 'SEARCH THE LOGGING FOR OCCURRENCES OF "NULL"'. |
|||
Resolution: |
The issue is happening due to task details not getting synchronized in time and the query to find the result returning null which causes processing error. Added retries to fetch the task again in case task details are not found in first attempt. This is a workaround to prevent the error and business impact until root cause is known and long term fix is applied. |
|||
33764790 |
NXT-24106 |
BP |
Extra logging for 'Write Consumption Batch Process Stuck' |
|
Description: |
For a WriteConsumptionBatch process that was not completed, data was uploaded in the Data File Set table. However, user could not see the data loaded in OHI. The status of the CONSUMPTION_IMPORT activity shows “In Process†in the OHI UI. |
|||
Resolution: |
Added activity retry mechanism; If an activity is not fetched for the first time, system will try another 2 times to fetch the activity. if it is not still not found the system will handle the validation. Also, added extra logging in a few places like Write Consumption Batch Process and in Activity Processing to get more details if an error occurs. |